Payment Posting Backlog: The Payer Already Told You

Ask your billing team how much insurer money has arrived unrecorded. We asked at one group: the answer took two days, and it was $326,000.
Updated August 2026

Tomorrow morning, ask your billing team one question: how much money has arrived from insurers that we haven’t recorded yet, and for which insurers?

Time the answer. If it comes back in under a minute with real numbers in it, you can stop reading. We asked that question at a group recently and the answer took two days.

What the question is really asking

Every payment an insurer sends arrives with a notice attached: what they paid, what they denied, and what the patient owes. The industry calls these remits. The check is the money. The notice is the information. And cash lands in the bank whether or not anyone reads the notice, which means a practice can be collecting money and going blind at the same time. A deposit with no recording is money you have and knowledge you don’t.

What happens when payment posting falls behind?

Four leaks at once: receivables overstate, patient statements stall, secondary claims wait, and denials age unread toward their deadlines. The cash arrives fine. The knowledge doesn’t.

One backlog, four leaks

Let the unread pile grow and it leaks in four directions at once.

Your receivables look bigger than they are. The insurer paid. Your books still say you’re owed.

Patient bills don’t go out. A patient’s share isn’t official until the insurer’s notice is recorded, so every statement waits in line behind the reading.

Claims to a patient’s second insurance wait in the same line, for the same reason.

And the denials buried inside the unread notices age quietly toward their filing deadlines. A denial you haven’t read is a denial you aren’t fighting, and past the deadline it becomes permanent.

What the two days bought them

At that group, $326,000 had arrived from insurers and sat unrecorded for an average of 19 days. The receivables report was overstated by exactly that much. Patient statements were running a full billing cycle behind, the same statements that fund upfront collection at the desk when they arrive on time. And nobody could say how many denials were inside the pile, because reading the notices was the step being skipped.

What was actually in the pile

Working a backlog oldest first teaches you its anatomy fast, and the anatomy is roughly the same everywhere. Most of the pile records clean in minutes apiece: routine payments that just needed a human to confirm a match. A slice turns out to be denials, and those convert straight into work with deadlines attached, which is the part that makes the age of the pile matter. And a handful won’t match anyone: payments for patients the system can’t find, usually because a name or ID was entered differently at registration. That last group is small and loud. It’s a registration-quality finding hiding inside a payment backlog, and it’s worth writing down every time it appears, because it points at the front desk process that created it.

Where backlogs come from

Rarely laziness. Most systems record the clean majority of payments automatically, and the exceptions fall to a human queue. The queue is nobody’s whole job. Volume spikes after growth or a payer change, the queue deepens, and skipping it feels safe because the cash already arrived. That instinct is exactly backwards. The cash was never the fragile part. The information was.

One more wrinkle: even the automatic recording needs watching. It breaks silently. An insurer changes its file format, a feed stops matching, and payments that used to record themselves start falling into the manual queue instead. Nobody announces that either. The queue just deepens faster than usual, and the first sign is usually somebody wondering why patient statements feel slow.

Treat that as a formal symptom. When patient statements lag, look one step upstream at recording first; the statement complaint is often the only signal the backlog sends before the receivables report starts lying.

The report that ends the debate

The fix is small. Two columns per insurer: dollars that arrived on payment notices this month, and dollars from those notices not yet recorded, with the age of the backlog in days. That’s the whole report. The old argument, is this a recording problem or a payment problem, stops eating meetings and becomes a glance. And the two columns settle what happens next. The backlog gets an owner, because a number with an age on it demands one. The work sorts oldest first, because the deadlines live at the old end of the pile.

The find, the fix, the lock

Find: $326,000 arrived and unrecorded, 19 days deep, with an unknown number of denials aging inside it.

Fix: the arrived-versus-recorded report by insurer, and the backlog worked oldest first so the denials inside got found while they could still be fought.

Lock: the report refreshes daily, and any backlog older than five days flags itself. The pile can’t quietly rebuild, because noticing the pile is the report’s whole job.

Ask the question anyway

Even if you’re confident. Especially if you’re confident. The question costs nothing, the timer tells you most of what you need to know, and whatever number comes back is sitting inside your receivables total right now, pretending to be money you’re still owed. It’s also the first thing to rule out when your P&L and your bank stop agreeing, and step one of reading any payer honestly.

We’ll measure your arrived-versus-recorded gap by insurer on your own data, including the denials hiding inside it. Grab 30 minutes with us. Prep nothing.

Read next