The Coding-to-Billing Handoff
The coding-to-billing handoff transfers a complete, supported charge instruction or coded encounter plus its status and unresolved exceptions. Billing accepts the item only when required information is present and should route coding questions back to qualified coding review.
Updated 2 min read
On this page
Key takeaways
- Billing ownership does not confer authority to make unsupported coding changes.
- Acceptance requires defined information and an observable state.
- Reconciliation prevents completed coding work from disappearing between queues.
What it controls
The coding-to-billing handoff transfers a complete, supported charge instruction or coded encounter plus its status and unresolved exceptions. Billing accepts the item only when required information is present and should route coding questions back to qualified coding review.
Ambiguous handoffs invite billing staff to infer missing details, change codes to clear edits, or release work before documentation questions are resolved. They also hide coding backlog inside billing queues.
Design the work
Define the unit of transfer and required fields: source encounter, documentation status, diagnoses, procedures, modifiers, units, provider and location context, coding notes permitted by policy, and open exception reason. Keep PHI in approved systems.
Separate sent, received, accepted, rejected, and returned states. Define who owns deadline monitoring while a question is pending and what evidence proves a supported correction was accepted.
Minimum controls
- Required-information contract and source-system reference.
- Qualified authority for coding changes and documented rationale.
- Acceptance and incomplete-item return states.
- Reconciliation of coding-complete items to billing disposition.
Keep claim-specific information in the approved system
Put it into practice
Prepare the coded item
Complete supported coding and identify unresolved documentation or policy questions.Transfer and accept
Use the approved queue, validate required information, and acknowledge ownership.Resolve exceptions
Return questions to the qualified role and preserve correction and acceptance evidence.
Review and improve
Review the control on a fixed cadence and after a material policy, payer, system, staffing, or workflow change. Compare the current process with its documented design, sample the evidence it produces, and record exceptions separately from completed routine work. A control that exists only in a policy but leaves no observable evidence cannot be evaluated reliably.
Use findings to change the upstream process, not merely to clear the current queue. Assign one owner, one next action, and one follow-up date. Preserve the definition and baseline used for the review so a later result can be compared without changing the measurement after the fact.
Frequently asked questions
Can billing correct a modifier?
Only when organizational policy, role qualification, documentation, and approved guidance authorize that correction; otherwise route it to coding.
Who owns a claim while coding information is incomplete?
The documented handoff design should name the current owner, next action, deadline monitoring, and escalation path.
Operational terms
Authoritative sources
- Medicare Claims Processing Manual (opens in a new tab)
Centers for Medicare & Medicaid Services
- Medicare Billing: CMS-1500 and 837P (opens in a new tab)
Centers for Medicare & Medicaid Services