Most providers sign payer contracts, file them and then trust that payments match. They often do not. Fee schedules update, carve-outs are missed, and lesser-of clauses are applied in the payer's favour. Without a way to calculate what each claim should have paid, underpayments go unnoticed.
This guide covers how providers manage payer contracts: what the repository should hold, how to model terms so software can calculate expected payment, how to detect and recover underpayments, how price transparency files help in negotiations, and where contract management usually fails.
What is payer contract management?
Losing money to underpayments?
Agnotic builds contract modeling and underpayment detection into provider revenue cycle systems.
Payer contract management is the provider-side work of storing, modeling, monitoring and renegotiating contracts with health plans. It turns each contract's payment terms into rules that calculate expected payment per claim, compares that with what the payer actually paid, and uses the results to recover underpayments and negotiate better terms.
It sits between managed care contracting, which negotiates the deals, and the revenue cycle team, which bills and collects. When the two do not share a model of the contract, nobody can say with confidence whether payments are right.
What should a contract repository hold?
A contract repository should hold every payer agreement, amendment and fee schedule, with key terms extracted into structured fields and linked to the documents they came from.
- Documents: Signed agreements, amendments, exhibits and correspondence, version-controlled.
- Parties and scope: Payer, products covered, provider entities, NPIs and tax IDs.
- Dates: Effective dates, renewal dates, notice periods and termination terms.
- Payment terms: Fee schedules, methodologies, carve-outs and escalators.
- Operational terms: Timely filing limits, appeal deadlines, prior authorization rules and dispute steps.
- Owners: The contract manager and the operational lead for each payer.
Renewal and notice dates need alerts. A contract that rolls over automatically because nobody saw the notice window can lock in below-market rates for another year or more.
Extracting terms from long contracts is slow work, and it is a good fit for AI-assisted review, as long as a contract analyst confirms every extracted term against the source clause before it drives payment calculations.
How do you model contract terms?
Model contract terms as rules that take a claim and return an expected payment, covering each payment method the contract uses. The model must handle the way terms combine, not just the base rate.
- Percentage of Medicare: Rates set as a percentage of the Medicare fee schedule for the date of service and locality.
- Fixed fee schedules: Payer-specific rates by code, with effective dates.
- Per diems and case rates: Daily or per-case payments for inpatient stays, often by level of care.
- Percentage of charges: Payment as a share of billed charges, often for items not otherwise listed.
- Carve-outs: Services such as implants or high-cost drugs paid separately from the main rate.
- Stop-loss and outliers: Extra payment when charges or costs exceed a threshold.
- Lesser-of clauses: Payment at the lower of the contract rate or billed charges.
- Multiple procedure rules: Reductions for second and later procedures on the same day.
Test each model against a sample of paid claims before relying on it. If the model and the payer disagree on most claims, the model is probably wrong; if they disagree on a few, those are your underpayment candidates.
How do you detect underpayments?
Detect underpayments by comparing the expected payment for each claim with the allowed amount on the payer's 835 remittance, and flagging differences above a threshold. Group the results by payer, code and reason to find systematic problems.
- 1. Calculate: Run every adjudicated claim through the contract model.
- 2. Compare: Match expected payment against the allowed and paid amounts on the remittance.
- 3. Flag: Mark claims where the variance exceeds a set amount or percentage.
- 4. Group: Look for patterns, such as one code always paid at last year's rate.
- 5. Act: Send systematic issues to the payer relations team and individual claims to appeal.
Patterns matter more than single claims. A fee schedule loaded late by the payer can underpay thousands of claims by a small amount each, which no one notices claim by claim but adds up across a year. Set thresholds so staff time goes to the variances worth chasing, and review the thresholds each quarter as volumes and rates change.
What do adjustment reason codes tell you?
Claim adjustment reason codes on the 835 explain why a payer paid less than billed. X12 maintains the code list, and CARC 45 is the one most tied to contracts: charge exceeds fee schedule, maximum allowable or contracted or legislated fee arrangement.
- CARC 45: The expected contractual reduction, but the amount still needs to match your model.
- Group codes: Each adjustment carries a group code, such as CO for contractual obligation or PR for patient responsibility, which shows who bears the amount.
- Other codes: Denials and reductions for authorization, bundling or medical necessity point to process issues rather than rates.
A CARC 45 adjustment is not proof that payment was right. It only says the payer applied its contract amount, and comparing that amount with your own model is the whole point of contract management.
How can price transparency files help negotiations?
Price transparency files show what payers pay other providers, which gives contract negotiators market data they never had before. Two federal rules require these files.
- Health plan files: Under 45 CFR 147.212, group health plans and issuers publish machine-readable in-network rate files, updated monthly, with negotiated rates tied to provider NPIs and tax IDs.
- Hospital files: Under 45 CFR 180.50, hospitals publish machine-readable files of standard charges, including payer-specific negotiated charges.
- Uses: Compare your rates with those of nearby providers for the same codes and plans, and spot where you sit below the market.
- Limits: Rates in the files can be expressed as percentages, case rates or bundles, so they need careful normalization before a fair comparison.
The files are very large and inconsistent in quality, so they need real data engineering to use. Load them into a database, normalize codes and provider identifiers, and filter to your market and service lines before drawing conclusions.
Behind both underpayment work and market comparison sits the same data foundation: claims, remittances, the charge master, contract terms and reference fee schedules, all linked at the claim and line level.
- Claims: 837 claim data with codes, units, modifiers and charges.
- Remittances: 835 data with allowed, paid and adjustment amounts and reason codes.
- Charge master: Current and historical charges, needed for percentage-of-charge and lesser-of terms.
- Reference schedules: Medicare fee schedules and payer fee schedules for each effective period.
- Volumes: Service mix and volume by payer, to model the effect of rate changes.
Linking these is harder than it sounds. Remittances do not always carry the provider's claim number cleanly, lines can be split or bundled by the payer, and charge masters change during the year. A reliable match between each 835 line and its 837 line is the first thing to build, and the first thing to test.
How should you prepare for renegotiation?
Prepare for renegotiation by modeling the financial effect of proposed terms on your actual volume, comparing your rates with the market, and documenting payer performance problems such as late payment or high denials.
- Rate modeling: Apply proposed rates to last year's claims to see the real revenue change.
- Market position: Use transparency data to show where your rates sit against peers.
- Payer performance: Days to pay, denial rates and underpayment totals by payer.
- Term changes: Escalators, carve-outs for new services and clearer dispute terms.
Start early. Pull the data at least two quarters before the notice date, so there is time to model several scenarios and respond to the payer's counter-proposal.
Bring operational asks as well as rate asks. Clearer authorization rules, longer timely filing limits or a faster dispute process can be worth as much as a rate increase, and payers sometimes concede them more readily.
How do you recover underpayments?
Recover underpayments by following the contract's dispute process within its deadlines, using claim-level evidence from the contract model. Systematic issues are usually best raised with the payer's provider relations team as a group, rather than claim by claim.
- Individual appeals: Claim, expected amount, paid amount, contract clause and calculation.
- Bulk reprocessing requests: A list of affected claims for a single root cause, such as an outdated fee schedule.
- Deadlines: Track each payer's appeal and dispute windows from the contract.
- Follow-up: Confirm reprocessed claims pay correctly and the root cause is fixed.
Keep a log of every recovery: the root cause, the number of claims, the amount recovered and the time it took. The log shows leadership what contract management returns, and it becomes evidence in the next negotiation when a payer's systems have repeatedly underpaid.
Where does payer contract management fail?
Contract management fails when contracts live only as PDFs, when models are not maintained, or when findings never reach the people who can act on them.
- PDF-only contracts: Terms that nobody has turned into rules.
- Stale models: Fee schedules not updated when Medicare or the payer changes rates.
- No owner: Underpayment reports produced but never worked.
- Missed notices: Renewal windows passing without review.
- Split ownership: Contracting, billing and finance each holding a different version of the terms.
The cure is a single shared model of each contract, owned by one team and used by all the others. When contracting updates a term, billing sees the new expected payment the same day, and finance forecasts from the same numbers.
How Agnotic can help
Agnotic Technologies builds payer contract management tools for providers and billing companies: contract repositories with structured terms, rule engines that calculate expected payment, underpayment detection from 835 data and dashboards by payer.
Agnotic also builds the data pipelines that load price transparency files and normalize them for market comparisons, giving negotiators evidence for their next round of talks.
Get paid what you negotiated
See Agnotic's revenue cycle management work, or read more in the revenue cycle hub.
Related reading on Agnotic
Continue with revenue cycle management, AI claims processing, eClinicalWorks denial appeals and provider credentialing.
