General operational information only. Payer, state, contractual and regulatory requirements vary. Confirm current requirements with the applicable payer or agency.
Quick answer
What practice leaders need to know
Evaluate a medical billing partner against a written operating model, not a sales promise. Define the exact scope, baseline performance, system access, compliance responsibilities, reporting, escalation, fees and exit process before signing. The practice should retain visibility into its claims, remittances, payer correspondence and financial data, while both parties document who owns every handoff from charge capture through final account resolution.
Start with the problem the practice needs to solve
Outsourcing works best when leadership can describe the present operating problem and the result it expects. Establish a baseline for charge lag, unsubmitted encounters, rejections, denials, payment posting, insurance aging, patient balances and unresolved enrollment issues. Separate problems caused by staffing capacity from those caused by documentation, payer setup, fee schedules or system configuration. A billing company cannot responsibly guarantee collections because payment depends on covered services, documentation, patient benefits, payer decisions and practice actions. It can, however, commit to defined workflows, response times, reporting and accountable follow-up. Put the baseline, target outcomes and measurement method in writing so both parties evaluate progress from the same facts.
Define the exact service boundary
List every revenue-cycle function and assign an owner. The scope may include demographic review, eligibility, authorization support, coding, charge entry, claim edits, submission, rejection correction, payment posting, denial work, insurance A/R, credit balances, patient statements and reporting. Credentialing, prior authorization, coding review and patient calls are often separate services, so do not infer that they are included. Define what the practice must provide, when it must provide it and what happens when information is missing. A responsibility matrix should identify the accountable party, system of record, turnaround expectation and escalation route for each handoff. This prevents two teams from assuming the other is working the same task—or duplicating work without realizing it.
Protect practice ownership and system visibility
The practice should understand who owns the billing account, clearinghouse connection, payer portals, phone numbers, payment processor, reports and exported data. Prefer named practice-controlled accounts where feasible, with role-based access granted to the vendor. Confirm that leadership can see claim status, remittances, adjustments, notes and work queues without waiting for a prepared presentation. Ask how audit history is preserved and how access is removed when personnel change. If a vendor uses its own platform, document the data available during the relationship, the export formats and the time and cost required to retrieve a complete record. Visibility is not micromanagement; it is necessary for oversight, continuity and an orderly transition.
Address privacy and security responsibilities
A billing partner commonly creates, receives, maintains or transmits protected health information on behalf of a regulated practice and may therefore be a business associate under HIPAA. HHS explains that covered entities need appropriate written assurances from business associates and that contracts address permitted uses, safeguards, incident reporting, subcontractors, return or destruction of information and other obligations. Qualified counsel should review the relationship and agreement. Operational due diligence should also cover role-based access, multifactor authentication, secure file exchange, device controls, audit logs, workforce training, access termination, incident response and subcontractors. A signed business associate agreement is important, but it does not replace the practice's risk analysis or ongoing oversight.
Examine compliance and coding controls
Ask how the company separates administrative billing work from clinical and coding decisions that require qualified judgment. Determine who reviews documentation, who may change codes or modifiers, how corrections are approved and how the audit trail is retained. The OIG's General Compliance Program Guidance describes the value of written policies, education, communication, auditing and corrective action. A prospective partner should be able to explain its compliance structure, exclusion-screening practices, quality reviews and response to suspected overpayments or inaccurate claims. Avoid compensation or performance language that pressures staff to submit unsupported claims. The practice remains responsible for accurate claims and should preserve an escalation route for uncertain documentation, medical necessity and coding questions.
Evaluate the actual team and subcontractors
Meet the people who will manage the account, not only the salesperson. Ask where work is performed, which functions are subcontracted, how staff are trained, how workloads are assigned and what coverage exists for absence or turnover. Confirm that specialty experience means experience with comparable provider types, services, payers and claim patterns rather than a broad healthcare label. Request references that resemble the practice, while respecting confidentiality. Understand who can access patient information and whether subcontractors are bound by appropriate privacy and security obligations. The proposal should identify the regular contact, operational lead, escalation contact and executive sponsor, along with expected response and meeting cadence.
Require a controlled onboarding plan
A sound transition begins with an inventory of systems, payers, provider and location records, open claims, remittances, deposits, outstanding tasks and access credentials. Establish a cutover date and decide who works claims created before and after it. Reconcile open A/R so accounts do not disappear between reports, and preserve filing and appeal deadlines. Validate provider, group, taxonomy, location and payer identifiers before new claims are released. Test claim acknowledgements, ERA posting and deposit reconciliation with controlled examples. The onboarding plan should also cover staff communication, secure access, reporting definitions and the first management review. Rushing submission volume before configuration is verified can create a larger cleanup project than the one outsourcing was meant to solve.
Inspect rejection, denial and A/R workflows
Ask the partner to demonstrate how an account enters a work queue, receives a status, is assigned to an owner and advances to a documented next action. Rejections should be separated from payer denials because they occur at different stages and require different controls. Denial reporting should identify root cause, payer, provider, service, financial exposure, deadline and whether the cause is preventable or appealable. Insurance A/R should be prioritized by filing and appeal risk, value, claim status and recoverability rather than age alone. A note that says called payer is activity, not resolution. Good documentation shows evidence, result, next action and follow-up date.
Use reporting that supports decisions
Agree on the formulas and sources for first-pass performance, rejection and denial rates, days in A/R, aging, net collection rate, charge lag, payment lag and unresolved claim volume. Define whether the denominator is claims, claim lines, encounters or dollars and what exclusions apply. Review trends by payer, provider, location and service, not only a total collection number. The monthly report should connect movement to operational causes and actions: what changed, why it changed, which balances are at risk, who owns the correction and when leadership will see the result. The practice should be able to reproduce material figures from underlying system reports rather than relying on an unexplained dashboard.
Set communication and escalation rules
Define routine meeting frequency, response expectations, urgent-event criteria and escalation levels. Decide how the vendor requests missing documentation, reports payer or enrollment barriers and communicates patient-facing issues. Use a shared issue log for material dependencies, owners and due dates instead of scattering decisions across email and chat. The practice needs a named person who can answer clinical, operational and financial questions, and the vendor needs authority boundaries for adjustments, appeals, refunds and patient communication. Review recurring dependencies as process problems rather than repeatedly solving them one claim at a time. Clear governance makes the relationship more resilient when either organization changes personnel.
Compare pricing on the same scope
Percentage-of-collections, per-claim, hourly and fixed-fee models allocate incentives and risks differently. Determine exactly which receipts are included in a percentage calculation, whether patient payments, old A/R or refunds affect the fee and how reconciliations are handled. Identify implementation, clearinghouse, statement, postage, software, credentialing, coding, prior-authorization and termination charges. A low headline rate can exclude essential work, while a higher rate does not prove stronger performance. Compare proposals using the same responsibility matrix and estimated volume. Qualified legal and financial advisors should review commercial, regulatory and tax implications before the practice commits.
Plan the exit before the relationship begins
The contract should state the term, renewal, termination notice, transition assistance, final fee calculation, data return, access removal and responsibility for open balances. Confirm how the practice will receive claim notes, remittances, correspondence, payer identifiers, patient statements, reports and work queues in usable formats. Decide who will handle claims during the notice period and how deposits, refunds and unresolved appeals will be reconciled after termination. Test data exports early rather than discovering limitations during a pressured transition. A credible partner should be able to describe an orderly handoff because continuity protects patients, the practice and the integrity of the revenue record.
Working reference
Medical billing partner due-diligence scorecard
Compare vendors against the same evidence and practice-specific scope before evaluating price.
| Area | Evidence to request | Risk to resolve |
|---|---|---|
| Scope | Responsibility matrix for every revenue-cycle function | Gaps or duplicated work |
| Access | Practice visibility, audit history and export process | Dependency on vendor-controlled accounts |
| Compliance | Policies, training, audit and escalation structure | Unsupported claims or unaddressed errors |
| Operations | Onboarding, queue and deadline workflows | Lost claims or unworked balances |
| Reporting | Definitions, source reports and action owners | Metrics that cannot be verified |
| Commercial terms | Complete fee schedule, exit and transition language | Unexpected cost or difficult handoff |
Common questions
Questions practice teams ask
What should a medical billing proposal include?
It should define scope, practice responsibilities, onboarding, access, reporting, communication, fees, privacy and security, performance review and exit support.
Should a practice give the billing company full system access?
Provide role-based access appropriate to assigned duties. Preserve practice ownership, audit visibility and a documented process for granting and removing access.
Can a billing company guarantee collections?
No responsible evaluation can guarantee payment. Collections depend on covered services, documentation, patient benefits, payer decisions, timely practice input and many other factors.
How should billing performance be measured?
Use consistently defined measures, underlying source reports, payer and provider detail, trends, exception ownership and documented corrective actions.
Is a business associate agreement enough for HIPAA compliance?
No. Appropriate contract terms are important, but the practice must also evaluate safeguards, access, subcontractors, incidents and the relationship within its risk-management program.
What happens to accounts when the contract ends?
The agreement should define responsibility during transition and delivery of claims, notes, remittances, reports, payer correspondence and other necessary data in usable formats.
Primary references
Sources and further reading
Requirements can change. Use these primary sources to confirm the current rule that applies to the payer, service and date of care.
Ready to turn this guidance into action?
Tell us what is happening in your practice, and we will help you identify the most useful next step.