Three numbers should match, and nobody checks
Every claim paid. None denied. The remittance shows a zero balance on all of them.
You were underpaid on about two-thirds of them, by 31 cents a unit, for the last eleven months.
The only leak with no error message
Every other failure in this cycle announces itself. A denial has a reason code. A short payment leaves a balance. An unbilled claim ages.
A rate variance does none of that. The claim adjudicates, the payment posts, the balance goes to zero, and the account closes. There is no report in any practice management system that flags a claim for having paid the wrong correct amount.
Three numbers should match: the rate in your contract, the rate loaded in your system, and the rate the payer actually paid. They drift for ordinary reasons, and once they drift, nothing brings them back on its own.
Where the drift comes from
A fee schedule amendment that arrived by email and never got loaded. An annual escalator in the contract that nobody applied. A new code added at a system default rate instead of a contracted one. A modifier priced as though it were the base code.
Credentialing level is the common one in ABA. BCBA, BCaBA and RBT services carry different rates, and when a service is mapped to the wrong level, every claim for that service is wrong in the same direction forever.
Place of service is the other. Clinic, home and school can price differently under the same contract, and a default location on a client record quietly applies the wrong one for a year.
None of these are mistakes anyone catches by looking at a claim. They are only visible in aggregate, and only if you go looking.
What the arithmetic looks like
One payer, trailing twelve months, illustrative. Contracted rates run about $18.40 a unit, which is roughly the $75 an hour we have used throughout.
Illustrative arithmetic, not a client engagement.
Look at which row is flagged. The largest variance per unit is $1.10, on 97156. The largest dollar loss is 31 cents, on 97153, because that is where the volume is.
This is the reason rate integrity gets missed even by people who go looking. The instinct is to check the codes where the rate looks wrong. The money is in the code you bill ten thousand times, where the rate looks nearly right.
Thirty-one cents a unit is a rounding error on a remittance. Across a year on one payer it is $6,696, and most practices carry more than one payer.
Check the other direction too
Anything paying above contract is not a win. It is a recoupment scheduled for a date you do not control.
Payers reconcile. When they do, an overpayment that accumulated quietly for eighteen months comes back as a single offset against current claims, and the cash hit lands in a week you did not plan for. That is stage 07, and it starts here.
A rate that is wrong in your favor is the same finding as a rate that is wrong against you. Both mean the three numbers do not match.
The clock on this one
Underpayment disputes have windows. Most contracts allow 90 to 180 days from the remittance to challenge an adjudicated amount, and a rate variance that has run for a year is mostly outside it.
Which means the recoverable portion is usually the last quarter or two. The rest is not a receivable, it is a lesson, and the value of finding it is that it stops today rather than that it comes back.
Fix the loaded rate and the leak closes on the next claim. Chase the history and you will get some of it. Both are worth doing, in that order.
Five checks you can run this week
You do not need anybody's help for these. Start with your largest payer by volume.
1. Find the current fee schedule. Current, not the one attached to the original agreement. If you cannot produce it in ten minutes, that is the first finding and it is a common one.
2. Export paid amount per unit by code and modifier for that payer, trailing twelve months. Your biller or your system can produce this in a few minutes. Use the median, not the average — one outlier claim will hide a systematic variance.
3. Compare three columns: contract, loaded, paid. The loaded rate is the one most often wrong, and it is the one you can fix yourself this afternoon.
4. Sort your variances by total dollars, not by variance per unit. The biggest number will be on your highest-volume code, almost every time.
5. Find the escalator or renewal date in each payer contract. An annual increase that was never loaded is pure silent underbilling, and it compounds from the effective date, not from the day you notice.
Check four is the one that keeps you from spending a day on a code worth $200.
The number to actually track
Rate variance per unit, by payer and by code, annualized to dollars. Target is zero variance rows, in both directions.
Run it quarterly. It is not a weekly number — rates do not change that often — but it is the number that, left alone for a year, quietly costs more than most denial problems.
Tracking average reimbursement per hour instead will not work. A blended average across payers and codes absorbs a 4 percent variance on one payer and shows you a number that looks stable while it erodes.
Where this sits
This is the sixth of seven stages, and the quietest. It produces no denials, no aging, no phone calls, and no alarm of any kind.
A claims audit will find this, because a claims audit reconciles what was billed to what was paid, and that comparison is exactly where a rate variance lives. If you suspect rate drift on a specific payer book, that is the right instrument and you do not need a full assessment to justify it.
A Leak Map Assessment measures all seven — reservoir, cancellations, session conversion, biller lag, clean claims, rate integrity and recoupments — because the practices that have a rate problem usually have two or three others feeding it.
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.
