To find unbilled work, match completed care with claim-release proof. Then sort each gap by its true stage. Use the current filing rule to rank work. Do not rank it by age or balance alone.
An AR report may miss unreleased work.
What counts as unbilled work?
Unbilled work is a supported service that has not reached claim release. This is a work status. It does not mean that a claim must be sent.
The care note may show that a service took place. The claim queue may still be blank. An item may be on hold for a missing fact.
Keep these states apart. A claim that was sent and rejected is not unbilled. A sent claim with no payer receipt is also at a later stage. Use the claim-status follow-up guide for those items.
Staff must not add care facts to clear a gap. They must not guess at a date or service. The provider owns the care record. The right billing lead decides if the facts support claim work.
Where should the team look for gaps?
Compare work lists that should link but may not move at the same time. Start with proof that care took place. End with proof that the claim left the office.
The lists may come from the schedule, care record, charge log, hold queue, claim batch, send log, and payer reply. Systems vary. Use a stable account or visit key. Do not match by name alone.
| Comparison | Exception found | Safe next owner |
|---|---|---|
| Completed visit list to care record | Note status is blank or not clear | Provider or record owner |
| Care record to charge queue | Supported work is not in the queue | Billing lead |
| Charge queue to claim-release log | Ready item has no send proof | Claim send owner |
| Send log to payer reply | Sent item has no receipt proof | Claim follow-up owner |
| Hold queue to task list | Hold has no cause, task, or owner | Revenue-cycle lead |
The charge-capture guide shows how care facts move into billing. This check asks if that hand-off took place.
How should each gap be sorted?
Give each gap one clear stage before setting its rank. A mixed list can hide which task comes next.
Use stages such as these:
- Not ready: A source owner still owes a needed fact or review.
- On hold: The cause, task, and owner are known.
- Ready but not released: The item passed its local checks, but no send proof exists.
- Sent but rejected: The item left the office but did not reach payer review.
- Sent with no receipt: Send proof exists, but payer proof does not.
- Already reviewed by the payer: Move it to pay, denial, or follow-up work.
This sort can stop repeat claims. Staff should not send a new claim only because a row is on the gap list. First check what took place.
How should filing risk change the rank?
A checked deadline can raise the rank when a valid next step still exists. An unknown rule goes to a fact-check list. It does not go to the bottom.
The CMS Medicare Claims Processing Manual, Chapter 1 gives one program example. It says the Medicare contractor receipt date helps decide if a claim was timely. It also sets a filing limit for that program. This rule does not set a deadline for all payers or plans.
For each item, log the payer, plan, claim type, rule source, start event, due date, checker, and open doubt. The timely-filing guide shows why later tasks may use other dates.
Readiness also affects rank. A ready item near a checked date may need fast review. A claim with a missing care fact needs a fast route to the source owner. It does not need made-up text. A high balance does not make weak proof safe.
What daily or weekly control can keep work visible?
Use one gap log with a source, stage, due date, task, and owner. Check it on a set office cycle. Save the date and result of each check.
The log can show the visit key, service date, record state, claim stage, hold cause, payer, plan, rule source, send proof, receipt proof, next task, owner, and last check. Mark a blank fact as unknown. Do not fill it with a guess.
Close a row only when proof shows where it went. A sent claim needs send proof. A payer-stage claim needs a reply or status check. An item that will not be billed needs an approved reason under the site's rules.
Old rows still need a path. Deleting one does not solve it. If the same gap returns, group cases by cause. A weak form, queue, map, or hand-off may need a fix.
What does a safe unbilled-work check look like?
A safe check follows the real file to the first missing proof. It does not fill the gap with a guess.
Hypothetical scenario: A dental office matches its completed-service list with its claim-release log. One service is in the signed care note. It is not in the charge queue.
The reviewer checks the patient and visit keys. The reviewer does not write a new care note. The billing lead reads the source file and payer steps. The row gets a rule source, task, and owner.
If a claim is sent, the team keeps the send and receipt proof. This does not promise claim acceptance, coverage, or pay. It shows that lost work was found and moved through a set process.
Frequently asked questions
Does every completed visit need a claim?
No. A visit may include work that does not belong in that payer path. The right reviewer must use the care record, plan, and office rules. The gap check finds missed choices. It does not make them.
Should staff send an incomplete claim near a deadline?
Staff should not make up or change facts to meet a date. Route the item through the site's care, billing, payer, contract, or legal path. Any claim must use the true record and current rule.
This guide is general administrative information, not legal, medical, clinical, dental, coding, documentation, compliance, contract, accounting, financial, patient-billing, or coverage advice, and not a statement that any service, charge, record, claim, deadline, submission, correction, or workflow is complete, timely, billable, covered, or payable. Requirements and outcomes vary by payer, program, plan, patient, provider, service, record, claim, agreement, jurisdiction, and date.
