Overpayments belong in liabilities
A payer sends you $4,200 you were not owed.
Congratulations. You now owe a payer $4,200, and it is sitting in your revenue account looking like income.
How the money arrives
Overpayments are not rare and they are not usually anybody’s mistake. They come from ordinary friction.
Coordination of benefits is the biggest one. A family has two plans, both pay as primary for a while, and six months later somebody reconciles and the secondary wants its money back.
Retroactive eligibility termination is the second. A client’s coverage ends on the first of a month and the payer does not process the termination until the fifteenth. Everything paid in between comes back.
Duplicate payment is the third and the easiest to miss, because a duplicate looks like a normal remittance on a normal claim. The only thing wrong with it is that there are two.
Then there is the plain rate correction, where the payer decides it loaded your contract wrong and adjusts in its own favour, retroactively, across every claim in a span.
Where it hides
In a cash-basis book, nowhere. It lands in revenue and stays there until the recoupment arrives, at which point revenue goes down in a month that had nothing to do with it.
In an accrual book it can still hide, because the posting decision happens at the claim level. Cash comes in, somebody applies it to the claim, the claim’s balance goes negative, and the negative balance sits there as a credit inside A/R rather than as a liability on the balance sheet. Net A/R looks fine. It is fine, arithmetically. It is just describing two different things in one number: money owed to you and money owed by you.
The practical symptom is an A/R aging report where some rows are negative and nobody can explain them.
What it does to a closed month
Illustrative arithmetic, not a client engagement.
March looks like a good month. July looks like a bad one. Neither is true, and the person reading the trend has no way to know.
If that recoupment lands in a month where you were already watching margin, you will spend a week looking for a cost problem that does not exist.
The correct treatment
A credit balance owed back to a payer is a liability. It belongs on the balance sheet, not inside A/R and not inside revenue.
Mechanically: when a claim goes to a credit balance, move it. Debit revenue (or a contra-revenue account if you want to keep the trail visible), credit a liability account — “Payer credit balances” or “Due to payers,” whatever you want to call it. When the recoupment arrives, it clears the liability. Revenue in the recoupment month is untouched, because the recoupment has nothing to do with that month.
The number you want on the balance sheet is the total of every negative claim balance in the system, refreshed at every close. That is a query, not a project.
And it should never be netted against A/R on a report that anyone outside the practice reads. A lender looking at $364,000 of receivables would like to know that $19,000 of it is money you owe someone else.
The part people resist
Booking the liability makes the month look worse, and the month it makes worse is the current one.
That is correct. The current month is when you found out. The alternative is to leave a known obligation off the balance sheet because recognising it is inconvenient, which is the kind of thing that reads very badly eighteen months later in a diligence process.
Five checks you can run this week
1. Run every claim with a negative balance and total it. That total is your unbooked liability. Most practices have never seen this number.
2. Check whether your A/R aging nets credits against debits. If it does, the headline number is understating both sides.
3. Look for the same claim paid twice. Sort remittances by claim and count. Duplicates are the easiest overpayment to find and the one most likely to still be sitting there.
4. Pull the last twelve months of recoupments and find the month each one relates to. If more than a quarter of them relate to a prior period, your monthly revenue trend is fiction.
5. Open a liability account and book the balance this close. It takes one entry and it stops the problem from compounding.
The number to actually track
Total of every negative claim balance in the system, carried as a liability and refreshed at each close.
Pair it with recoupments taken in the period, mapped back to the month they relate to. If more than a quarter relate to a prior period, your revenue trend is fiction.
Netting credits against debits inside A/R understates both sides and hides an obligation you already owe.
Where this sits
This is the eighth and last of the stages where ABA revenue leaves. It is where money that was collected goes back out, and where money that was never collectible finally gets recognised.
An overpayment is the one item in the cycle where more cash arriving is a worse outcome, not a better one.
A Leak Map Assessment measures all eight — the reservoir, authorization burn, cancellations, session conversion, conversion to billed, clean claims, rate integrity and recoupments. A claims audit is a different instrument. It starts once a session has been converted and billed, and reconciles the back half of the cycle to cash.
Aimline closes the books, oversees the revenue cycle, and sits in the CFO seat for ABA practices. We run claims audits scoped to a payer book, and Leak Map Assessments that measure the full cycle — three weeks, $7,500 fixed. Either one gives us a verified number to run oversight against, and the report is yours whether or not you engage us to fix what it finds.
