A zero-balance review checks how a claim reached zero. It traces each payment, payer change, move, undo, and fix back to a source. A local zero only proves that the ledger closed. It does not prove that the close was right.
This looks back at closed work. It is not a zero-payment remit or the daily payment close.
What is a zero-balance review?
A zero-balance review tests closed claims against their source files. The reviewer traces each post that cut the balance. Each step needs clear support.
A zero may come from payer funds, patient funds, a payer change, a balance move, an undo, or a mix of posts. Some paths are sound. Some may link to the wrong claim. Others may lack a source.
The review does not decide what the office may bill or collect. Send contract, books, patient bill, legal, code, and care questions to the right owner. The reviewer states the gap and keeps the first trail.
Why can a zero balance still be wrong?
A ledger can reach zero through a post that lacks support. A batch total may match while one claim does not.
A payment may land on the wrong claim. A manual change may clear the rest with no linked reason. A move may send the balance to an account no one checks. A later undo may reopen the payer issue while the first account still looks closed.
The payment-posting quality-control checklist shows why totals are not enough. A zero-balance review checks some claims after they leave that daily queue.
An odd zero does not prove bad acts. It is a gap that needs proof. The cause may be a link fault, a timing gap, a valid contract step, or a need for staff help.
Which records should be matched?
Match the final ledger to the claim, payer reply, funds, and each balance change. Use claim and bank keys. Do not match by patient name alone.
CMS says a Medicare remit gives claim or line results. It also gives the reason and value for each change. See the CMS health care payment and remittance advice guidance. That page does not set the right contract or patient result for all payers.
| Closure path | Evidence to match | Review concern |
|---|---|---|
| Payer payment | Claim, remit, bank trace, and post | Funds link to the wrong claim or line |
| Patient payment | Receipt, account, use, and refund trail | Funds were used on a weak balance |
| Payer change | Full remit or other approved source | Cause is gone, vague, or stretched |
| Balance move | First and new ledger posts | Work moved to an unseen account |
| Undo or fix | First post, new post, cause, and reviewer | Old trail was lost or new post lacks support |
| Mixed close | Each fund and change in time order | Total matches, but one part does not |
The billed, allowed, and paid amounts guide shows why a gap is not always a patient amount or a valid write-down.
How should claims be picked for review?
Use a written risk plan and keep a fair sample. No one list fits every practice.
The plan may include claims with a manual change, no linked remit, a balance move, a recent undo, a fixed claim, or an open second payer. It may also pull a plain sample from routine closes.
Write down the time span, systems, filters, reviewer, and skips. Do not call a claim wrong before the check. If the system cannot show why it closed, state that fact.
How should the reviewer trace the close?
Keep the first trail, then read the posts in time order. Each post should point to a source and the person or rule that allowed it.
Start with the claim that left the office. Check payer receipt. Find each remit tied to it. Match funds to the right remit. Trace each change, move, undo, and patient-ledger post.
If a post lacks proof, do not erase it. Put the claim in a work queue. Name the missing fact, next owner, next task, and check date. A later fix should keep the old post and show why the new post was made.
Use the zero-payment remittance guide when the payer result itself shows no funds. This review asks a new question: why did the office ledger reach zero?
What does an incorrect close look like?
An incorrect close has a balance post that does not match the source on hand. The reviewer should state the mismatch. The reviewer should not guess at the final result.
Hypothetical scenario: A claim reaches zero after a manual change. The note points to a payer remit. That remit lists a payment and change for a different claim key.
The reviewer saves both claim files and the ledger trail. The claim moves to a work queue. The posting lead checks if the wrong source was linked or if another source exists. A contract or patient-account choice goes to the right owner.
If a fix is approved, the first post stays in view. The new post states the cause and reviewer. The team then checks if the same map touched more claims. A repeat gap may lead to a process fix. It does not prove intent or pay.
When is the review done?
The review ends when the proof, owner choice, and any fix are logged. An open claim may move to another set queue. It must keep a named owner.
The close note should say what was tested, what matched, what failed, and where the proof sits. It should also say if related claims need a check.
Frequently asked questions
Does a zero balance mean the payer paid in full?
No. The zero may come from funds, payer changes, moves, undos, or other posts. Match the remit, bank trace, ledger, plan, and account proof before making a claim.
Does every zero-balance claim need to be reopened?
No. Use a set sample and clear gap rules. A well-backed close may stay closed. A weak post should go to the right owner. Keep the first history.
This guide is general administrative information, not legal, medical, clinical, dental, coding, documentation, audit, contract, accounting, financial, tax, patient-billing, collections, or coverage advice, and not a statement that any zero balance, payment, remittance, adjustment, transfer, write-off, correction, patient amount, or claim closure is accurate, authorized, final, collectible, covered, or payable. Requirements and outcomes vary by payer, program, plan, patient, provider, claim, service, remittance, ledger, agreement, jurisdiction, and date.
