Paid Is Not the Same as Owed
How underpayment against contract terms hides in plain sight, classified as a routine adjustment — and what it takes to detect it.
A denied claim announces itself. It lands in a work queue, carries a reason code and demands a decision: correct it, appeal it, write it off or escalate it.
An underpaid claim can be more dangerous precisely because it looks finished. Money arrived. The remittance posted. The contractual adjustment cleared the remaining balance. The account closed at zero. From the billing system's point of view, the claim is resolved.
But paid is a transaction status. Owed is a contract calculation. Those are not the same question.
The electronic remittance advice, or 835, is the standardized record of claim adjudication. CMS describes it as the transaction that reports payment and the adjustments applied at the claim or service-line level. Claim Adjustment Group Codes, Claim Adjustment Reason Codes and Remittance Advice Remark Codes explain why the payer did not pay the submitted charge in full.
One of those group codes is CO — Contractual Obligation. CMS defines CO as an adjustment resulting from a contractual agreement between payer and payee, or from a regulatory requirement, that is generally treated as a provider write-off rather than patient responsibility.
That code is essential for posting. It is not proof that the amount assigned to it matches your contract.
Assume a practice bills $1,000 for a service and its contract says the allowed amount should be $500. Assume there is no deductible, coinsurance or other patient responsibility.
The payer instead allows and pays $440, then assigns the remaining $560 to a contractual adjustment. If the billing system auto-posts the remit, the account can reach a zero balance immediately.
The claim is paid. The account is closed. The practice is still short $60.
Most revenue cycle operations are designed to find exceptions: rejections, denials, unpaid balances, aging receivables and missing remittances. Underpayments often create none of those signals. If a contractual adjustment is posted automatically and the account balance falls to zero, there may be nothing left for staff to work.
That creates a structural blind spot. The organization can have strong clean-claim performance, low denial rates and respectable days in A/R while still losing money after adjudication. The leakage sits between what the payer calculated and what the contract required.
Contract variance can originate from multiple layers of reimbursement logic. A payer may be using the wrong contracted fee schedule or an outdated effective date. The claim may be mapped to the wrong product, network or provider agreement. Modifier, multiple-procedure, bilateral, professional-component, technical-component, unit or site-of-service logic may be applied incorrectly. A service may be downcoded, bundled or reduced under a payer policy that conflicts with the contract or applicable law. Credentialing status can also push an otherwise valid service to an out-of-network or nonparticipating rate.
Provider-level adjustments can complicate the picture further. CMS notes that 835 remittances can carry provider-level balance adjustments unrelated to a single claim — including recoupments and other payment changes. If reconciliation stops at the claim screen rather than following the money through the remit and the deposit, the financial effect can be misclassified or missed entirely.
This is not just an abstract contract-management issue. In April 2026, the Maryland Insurance Administration issued a bulletin reminding health plans and third-party administrators that unilateral downcoding is prohibited under Maryland's prompt-payment framework. The bulletin states that a payer may not simply change a submitted service code to a lower-paying code based on its own assessment and place the burden on the provider to resubmit for the higher level.
The practical lesson reaches beyond Maryland: a payment can be administratively complete and still warrant review. The fact that cash posted does not remove the need to understand why the allowed amount changed.
You cannot reliably find contract underpayments by asking staff to look harder at remits. The work has to be systematic. MGMA's 2026 underpayment education describes the core approach directly: model the contract, compare expected reimbursement with actual allowed amounts and payments, surface discrepancies at scale, then prioritize the variances worth pursuing.
For a physician practice, that means connecting information that often lives in separate places: the executed contract and amendments; fee schedules and effective dates; CPT/HCPCS and modifier rules; provider, product and network mapping; the submitted claim; the 835 remit; patient responsibility; and the actual payment deposited.
A traditional A/R report tells you what remains open. Underpayment analysis asks what should never have been closed at the amount received. That is a different dataset and a different management question.
For CFOs and practice administrators, the most useful measures are not just gross collection rate or days in A/R. They include actual-to-expected reimbursement variance, underpayment dollars by payer, zero-balance claims with material variance, recurring variance by CPT or service family, age of unresolved underpayments, recovery yield and the administrative cost required to enforce the contract.
Those measures also change payer negotiations. A contract that looks competitive on its fee schedule may perform very differently after incorrect reductions, recurring underpayments and the labor required to obtain the negotiated rate are included. The economic value of a payer relationship is not simply the rate written in the contract. It is the rate the practice can actually collect, consistently, without disproportionate administrative friction.
Denials are visible because they leave work behind. Underpayments can disappear because the system does exactly what it was configured to do: accept the payer's adjudication, post the adjustment and close the balance.
That is why the question cannot stop at “Did we get paid?”
The better question is: “Did we get paid what the contract says this service was worth?”
Emphanex starts with that distinction. We compare what the payer adjudicated with what the available evidence says should have happened, then separate legitimate contractual adjustments from payment variance that deserves investigation. The objective is not to challenge every adjustment. It is to stop treating every zero balance as proof that nothing is left to recover.
This article is for general informational purposes only and does not constitute legal, coding, reimbursement or compliance advice. Contract interpretation, payment accuracy and recoverability depend on the specific payer agreement, plan terms, claim facts, provider status and applicable law.