Denials Use the Front Door. Recoupments Use the Back.

Most revenue cycle teams are built to guard one door.

A claim goes out, a denial comes back, and somebody works it. There's a queue, a code, a deadline, a letter. After a decade of investment, most health systems guard that front door pretty well.

Cleveland Clinic guards it better than almost anyone. According to Becker's, they run a 15% incoming denial rate and overturn 92% of what they fight.

So it says something when Cleveland Clinic leaders, alongside SCA Health and Erlanger, show up in a new Becker's whitepaper about a different problem entirely.

Payer recoupments. The money that leaves through the back door.

What the whitepaper says out loud

The argument is simple, and it should make every CFO a little uneasy. Recoupments surface months or years after the revenue was booked. They show up as offsets and provider-level balance adjustments, not denials.

And standard denial workflows don't catch them.

Medicare's Recovery Audit Contractors can reach back three years from the date of payment. Revenue you closed out in a prior fiscal year can walk out quietly on next Tuesday's remit.

For an ASC with three people in billing, that's not a workflow gap. It's a blind spot. Nobody's watching the back door, because nobody was ever hired to.

A denial asks permission. A recoupment doesn't.

What it looked like from the payer's side

The PromptWrx leadership team spent years building AI for health insurers. On that side, prepay and post-pay aren't two problems. They're one pipeline.

Whatever gets through the front-door review gets a second look later. Payment integrity teams and recovery vendors, often paid a share of what they recover, work the paid claims with the same rules and a lot more time. DRG validation, coordination of benefits, data mining, policy edits applied after the fact.

When they find something, they don't send a letter asking for a check. They take it out of the next payment.

On that side, we thought hard about whether a recovery was defensible. We almost never thought about whether anyone on the provider side would notice. Most of the time, the honest answer was no.

An offset doesn't look like a loss. It looks like a smaller deposit.

That's what makes the back door so effective. The payer recovers on its timeline, against its current policy, and the provider has to reconstruct a two-year-old claim from one line in an 835: a PLB segment, adjustment code WO, a dollar amount, and maybe a reference number.

You can't appeal what you never saw.

Six things we recommend

1. Read the PLB, not just the claim lines. Recoupments live in the provider-level adjustment segment of the 835. If cash posting nets them out and moves on, the trail is gone before anyone starts. Tie every overpayment recovery back to the original claim, patient and date of service.

2. Give the back door an owner. Recoupments aren't denials and they aren't cash posting, so in most shops they belong to no one. Give them their own queue and their own deadlines.

3. Treat every records request as the first move. An ADR, a records request, a new payment policy bulletin, a cluster of DRG validation letters. These are the warning signals. Log them as the start of an audit, because they usually are.

4. Check the clock before you pay it back. The RAC lookback is three years. Commercial lookbacks are set by your contract, and many states cap them too. A recoupment outside the window is one you shouldn't be paying.

5. Fight with the policy as it read on the date of service. Retro audits have a habit of applying today's policy to yesterday's claim. Pull the version that was in effect when the care was delivered. That one detail settles more of these than you'd expect.

6. Send every loss upstream. An uncontested recoupment is a coding or documentation lesson nobody learned. Route the pattern back to pre-bill, or you'll pay it again next year.

Bringing it home

The leaders in the whitepaper are right that this is a hidden margin threat. But hidden is a choice. The data's in the 835. It always was.

Providers spent the last decade building a better front door. The payers noticed, and moved around back.

That's why PromptWrx built Reve the way we did: the same people who built the payer models, now working only for providers, and never for a payer. Reve reads what comes back the way the other side reads what you send, including the adjustments that never hit a denial queue. Every one goes through the same triage: correct it, appeal it with the payer's own policy in hand, or write it off on purpose.

Do you want to be right, or do you want to get paid? With a recoupment, you already got paid. The question is whether you get to keep it.

Read the PLB. Name an owner. Watch the signals. Check the clock. Cite the old policy. Fix it upstream.

Then lock the back door.