What is a zero balance review? (And why your hospital is leaving money behind)

What is a zero balance review? (And why your hospital is leaving money behind)

Author: Kelsey Taylor
Author: Kelsey Taylor
July 13, 2026

Your AR dashboard looks clean. Denials are trending down, follow-up queues are current, and thousands of accounts have closed at zero. That's the problem. 

A closed account and a correctly paid account are not the same thing. Some of what your team marked "resolved" was actually written off, adjusted in error, or paid by the wrong payer.  For many providers, once the balance hits zero, nothing in the workflow ever looks at it again. 

The problem is bigger than most finance teams assume  

Hospitals absorbed $130 billion in underpayments from Medicare and Medicaid in 2023 alone, and those shortfalls have grown roughly 14% a year since 2019, according to the American Hospital Association's Costs of Caring report. 

Commercial contracts add another layer on top: Industry benchmarking puts contractual underpayments as high as 7% to 11% of net patient revenue. None of that shows up as open AR. It shows up, if it shows up at all, buried inside accounts your system already considers finished. 

A zero balance review is a retrospective audit of closed accounts, built to find the revenue that never should have been written off. 

This post explains why zero balances hide errors, where those errors come from, and how to build a review process that gets the money back before your window to recover it closes. 

Why a $0 balance doesn't mean the claim was paid right 

Closing an account at zero only means the debits and credits net out to nothing in your billing system. It says nothing about whether the payer paid the contracted rate, billed the correct party, or processed the claim at all before it was written off. 

Primary failure patterns  

These failure patterns account for most of the recoverable revenue inside zero balance populations: 

  • Contractual adjustment errors. When a payer pays less than the contract requires and the shortfall gets adjusted off instead of appealed, the account closes at zero and the underpayment disappears from view. 
  • Incorrect write-offs. Balances get written off as uncollectible, small-balance, or timely-filing losses when they were actually valid, collectible amounts; the write off's often happen due to staff error, bad payer correspondence, or misapplied write-off thresholds. Once written off, the account zeroes out and the revenue is treated as gone. 
  • Underpayments obscured by netting. Credits and charges offset each other on the ledger, producing a $0 balance that conceals a real shortfall underneath. 

 

primary failure patterns spotted in zero balance review audits

 

The flaws in standard AR workflows that result in revenue leakage 

Most revenue cycle teams are built to chase open balances, not closed ones. Follow-up queues, denial worklists, and AR aging reports all trigger off accounts that still show a dollar amount due. Once an account nets to zero, it drops out of every one of those workflows by design. 

That's not a staffing failure – it's how the systems are built. Nobody is assigned to re-open a resolved account and ask whether "the resolution" was correct. Meanwhile, timely filing limits and payer audit windows keep running, whether or not anyone is looking. The longer a zero balance error sits, the narrower the path to recovering it gets. 

Where to start: A five-part review process 

A structured zero balance review turns an invisible problem into a working queue, the same way denial management does for open claims. Five actions make up the core of that process: 

  1. Run periodic retrospective reviews of closed accounts, prioritized by payer, claim type, and dollar threshold. Don't try to review everything – start with the payers and claim types most likely to carry contractual complexity or high dollar volume. 
  2. Build or contract for detection logic that flags anomalies automatically. Two rules do most of the work: adjustment amounts that exceed expected contractual variance, and write-off codes that don't correspond to any documented denial or appeal. 
  3. Fix coordination of benefits upstream, not downstream. Verify payer sequencing and eligibility at registration, not at billing. Every COB error caught before the claim goes out is one that never becomes a zero balance problem later. 
  4. Attach every finding to a timely filing checkpoint. An identified underpayment is only recoverable if it's worked before the payer's reconsideration window closes. Build the deadline into the workflow, not just the finding. 
  5. Feed findings back into contract management. If one payer shows a repeated pattern of underpayment, that's not a one-off recovery – it's a compliance issue that belongs in your next renegotiation. 

If a payer or claim type shows systematic underpayment across multiple accounts, escalate it to contracting immediately rather than waiting for the next full review cycle. 

Five Part Zero Balance Review Process

The honest obstacle: Most teams don't have the bandwidth 

Here's what makes this hard to act on: your team is already stretched thin managing open AR and current denials. Zero balance review is additive work that requires access to historical claims and remit data that isn't always easy to pull.  It also competes for attention with problems that are more visible day to day. 

If you can't stand up a full review program right now, triage. Start with a single high-dollar payer or claim type – workers' compout-of-network Medicaid, or another category with known contract complexity – and run one retrospective pass before expanding. A narrow, consistent review beats a comprehensive one that never gets off the ground. 

How EnableComp can help  

EnableComp's zero balance review process applies specialized analytics along with clinical and billing expertise to find recoverable revenue in closed accounts that standard AR workflows miss.  

Instead of a manual audit, EnableComp uses systematic detection logic to surface underpayments, erroneous write-offs, and COB errors at scale, paired with a recovery workflow built around payer-specific timely filing requirements. If a triage pass on your highest-dollar payer surfaces the patterns described above, that's the signal it's time for a structured review. 

Schedule a consultation to see how much revenue you’re leaving behind. 

 

About the author 

Kelsey Taylor, BSN, RN, is the Senior Director of Clinical Denials at EnableComp, bringing over 10 years of experience in healthcare management and clinical operations to the role. Her background spans clinical quality, care management, and product management, giving her a well-rounded lens on how revenue cycle, training, and clinical operations intersect. She's passionate about empowering teams to deliver patient-centered, impactful results and frequently speaks on topics like DRG revenue integrity, complex revenue recovery, and denial prevention strategy.