How Do I Catch Payer Underpayments Hidden in CO-45 Adjustments?

What It Takes to Surface Underpayments Buried in CO-45

The goal is simple: every posted allowed amount checked against your contracted rate, so a payer paying under contract gets caught and disputed instead of written off. Here is what does that, move by move.

1. Load Every Payer’s Contracted Fee Schedule

Nothing works without this. If the contracted fee schedule is not in the system next to the remit, the poster has no benchmark to check the allowed amount against, so every CO-45 gets written off on trust. Load each payer’s contracted rates by CPT code, starting with your highest-volume contracts, so the system knows what the allowed amount should be and can compare it to what the payer actually paid. The contract is the yardstick; without it, you are measuring nothing.

2. Run an Allowed-Versus-Contract Variance Report

With the fee schedules loaded, run a monthly variance report that compares the allowed amount on every posted remit to the contracted rate for that code. Where the payer allowed less than the contract says it should, the difference is an underpayment hiding inside a CO-45, not a legitimate adjustment. This report is what turns a blind write-off pile into a list of specific lines where a payer paid you under contract, on the codes and payers where it is happening most.

3. Route Underpaid Lines to a Payer Dispute Queue

A variance report only recovers money if the underpaid lines get worked. Route each one to a payer dispute queue with the contract citation attached, the CPT code, the contracted rate, the amount allowed, and the shortfall, so the dispute is a documented claim of underpayment rather than a vague complaint. Payers correct underpayments far faster when you cite the specific contract term they violated than when you simply ask why a claim paid low.

4. Never Swap a Code to Chase a Higher Rate

This is the guardrail. The goal is to recover the rate your contract already entitles you to, not to change how a service is coded to earn more. Dispute the underpayment on the correct code with the contract in hand; never alter the code to inflate the allowed amount. Recovering a contractual underpayment is legitimate and expected. Manipulating the coding to do it is not, and the whole point of loading the fee schedule is to collect what you are owed cleanly.

5. Hand Variance Auditing to a Dedicated Team

Practices that stop leaking money into CO-45 do it by handing contract-variance auditing to a dedicated team: remote specialists who keep the fee schedules loaded, run the variance report every month, build the dispute packets with citations, and work the recoveries, live in 1 to 2 weeks. The billing office stops writing off underpayments on trust, a trained backup covers every gap, and the money your contracts entitle you to stops disappearing. Below is what it sounds like when nobody owns it yet, in billers’ own words.

Why This Keeps Happening

If CO-45 is just the contractual adjustment, why does it hide underpayments? Because the code itself carries no proof that the allowed amount is correct. CO-45 means the charge exceeded the allowed amount and the difference is written off; it does not verify that the allowed amount matches your contract. Without the contracted fee schedule loaded next to the remit, the poster has no benchmark, so a correct adjustment and an underpayment look identical on the page, and both get written off on trust. The payer states the allowed amount, and if nobody is checking it against the contract, the payer is effectively grading its own homework. A disciplined revenue cycle management workflow puts the contract back in the loop.

For a procedure-heavy specialty like orthopedics, the exposure is concentrated exactly where it hurts. A small per-claim shortfall on a low-volume code is noise, but the same shortfall on your highest-volume procedure codes, the ones you bill dozens of times a week, compounds into real money over a quarter. When a payer allows even a few percent under the contracted rate on your bread-and-butter CPTs, and every instance disappears into CO-45, the leak is both invisible and large. Surfacing it is exactly what an AI automation layer with human oversight is built to do, comparing every allowed amount to the contract at a scale no poster can match by hand.

And the reason it persists is that underpayments never announce themselves. A denial bounces, errors out, demands a resubmission; an underpayment does none of that. The claim pays, just a little light, and the CO-45 absorbs the difference silently. There is no queue, no alert, no work item, unless you build one. MGMA benchmarks focus practices on first-pass denial rates, but the money lost to quiet underpayments never shows up in a denial statistic at all. It shows up only in a variance report you have to run on purpose, which is why most practices never see it.

Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:

The Solution

So what does “someone whose whole job it is” look like on an orthopedic remit? The specialist starts by loading the thing the poster never had: your contracted fee schedules, by CPT code, starting with the highest-volume contracts. With the contract sitting next to the remit, every allowed amount finally has a benchmark. Then they run a monthly allowed-versus-contract variance report that flags every line where the payer allowed less than the contract requires, turning the blind write-off pile into a specific list of underpayments. Most of this money leaks because nobody has a yardstick, and that is exactly what dedicated denials and underpayment management is built to install.

Then they recover it cleanly. Each underpaid line goes to a payer dispute queue with the contract citation attached, the CPT code, the contracted rate, the allowed amount, and the shortfall, so the dispute is a documented claim the payer has to answer rather than a vague call about a low payment. Nothing is ever recovered by swapping a code to chase a higher rate; the goal is only the rate your contract already entitles you to, disputed on the correct code with the contract in hand. That is the difference between recovering what you are owed and creating a coding problem.

Behind all of it, AI drafts the first pass and a credentialed human verifies. The workflow compares every allowed amount to the contract and flags the variances; a person confirms each one is a real underpayment and owns the dispute and the recovery. Every security control that protects the contract and claim data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving billing and contract data through a variance workflow is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced team catch your underpayments better than your own billing staff? Because loading fee schedules and running contract-variance audits is their entire day, not the thing they never get to between posting and denials. The people auditing your remits are credentialed medical professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US revenue cycle, contract analysis, and payer-dispute workflows. They know how to load a contracted fee schedule, how to read an allowed-versus-contract variance, and how to build a dispute packet a payer has to answer. That is not a generalist task handed to whoever is free; it is a specialty.

We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical practice is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and no one on our side goes out without a trained backup already inside your workflow, so the variance report never gets skipped because the one person who runs it is on vacation.

And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; the full detail lives in our HIPAA and security posture.

Put the routine and the people together, and a specific list of things simply stops happening.

How We Permanently Fix the Process

A person alone is not the fix, and neither is a bot alone. The fix is a documented variance workflow: every payer’s contracted fee schedule loaded and kept current, a monthly allowed-versus-contract report that flags every shortfall, a dispute queue that attaches the contract citation to each underpaid line, and the guardrail that recovery never means recoding, all written down and worked the same way every time. Before we take a single remit for a new practice, we load your top contracts and run a first variance pass so we can see where money is actually leaking, and we build the workflow against that, not against a generic template.

From there the workflow becomes a living playbook rather than a report nobody remembers to run. It records which contracts are loaded, how the variance report is built, which payers underpay which codes, and the exact dispute steps with citations. It is written down, kept current as contracts renew and rates change, and owned by the team. When your specialist is out, a trained backup runs the same variance report and works the same disputes the same way, so the audit never lapses because one person stepped away.

That is the difference between catching one quarter’s underpayments and fixing the process for good, and it is what a dedicated revenue cycle management partner actually buys you. A biller leaving used to mean the variance report stopped running and the underpayments went back to hiding in CO-45. Under this model the workflow keeps running, the playbook stays, the backup steps in, and the money your contracts entitle you to stops leaking into the write-off pile.

The Whole Thing in Four Sentences

You catch payer underpayments hidden in CO-45 by loading your contracted fee schedules and checking every allowed amount against the rate you agreed to, because without the contract loaded, the poster cannot tell a correct adjustment from an underpayment and writes off both on trust. Writing off every CO-45, calling the payer without a citation, or spot-checking from memory all fail the same way, they miss the systematic few-percent shortfalls on your highest-volume codes. The fix is to load every contract, run a monthly allowed-versus-contract variance report, route underpaid lines to a dispute queue with the citation attached, and recover the difference without ever recoding. An orthopedic group runs exactly this model with us today, names withheld, no patient data shown.

If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.

Ready to recover your hidden underpayments? Try us risk free: two weeks, your real remittance volume and top contracts, dedicated specialists running the variance report and working the disputes, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.

Written By

Dan Nandan

Founder and CEO, Staffingly, Inc. · Piscataway, NJ

Dan Nandan has spent 25+ years in IT consulting and healthcare BPO, was among the first in the US to build an RPO/BPO delivery network in India, and has been featured in Computerworld. He runs the operations and the dedicated virtual teams behind the workflows on this page; the team-voice answers above come from the remote specialists who work them every day.

Connect on LinkedIn

Where the Claims on This Page Come From