Tracking Payor Contracts: The Terms You Negotiated and Stopped Enforcing

A health system will put six months and outside counsel into a payor negotiation. Rate schedules modeled to the service line. A timely-filing window pushed from 90 days to 180. An escalator tied to an index. A recoupment lookback capped at twelve months instead of the payor's opening position of twenty-four.

Then it gets signed, scanned, and filed. And from that day forward the only clauses anyone enforces are the ones attached to an invoice.

The escalator that needed someone to notice an anniversary. The lookback cap that only helps if someone catches the payor reaching past it. The notice period the payor was supposed to honor before changing a policy. These do not fail loudly. They just never get exercised, and the money they represent never appears as a loss, because nobody counted it as revenue in the first place.

The asymmetry is the whole story

Payors encode the rate terms. They have to - those are inputs to an adjudication system that runs continuously, at scale. Even that gets loaded wrong often enough to sustain an entire underpayment-recovery industry.

Health systems track their payor terms in a spreadsheet maintained by managed care, a second spreadsheet maintained by revenue cycle, and the memory of whoever did the negotiation. One side has the agreement encoded in software. The other has it encoded in prose and goodwill.

The administrative terms - notice, lookback, appeal rights - sit in prose on both sides. That produces a predictable pattern. Terms that generate a claim get enforced, because a claim generates a denial and a denial generates a person. Terms that generate nothing get forgotten, no matter how hard they were to win.

What goes unenforced

Rate escalators and anniversary increases. They apply on a date. If nobody checks the remittance against the schedule after that date, the old rate continues, and it will continue until someone runs an audit that nobody has scheduled.

Notice periods before policy changes. Agreements and state law both set windows for advance written notice before a payor changes a medical policy, a fee schedule or a prior-auth requirement. The sharper version is what those clauses permit: Molina's publicly filed regulatory amendment lets the health plan amend the agreement unilaterally, to maintain compliance with any law or program requirement, on forty-five business days' notice - "unless a shorter time is necessary for compliance." Notice arrives in a portal or a bulletin nobody monitors, and the window closes before anyone reads it.

Claim turnaround and interest on late payment. Nearly every state has a prompt-pay statute and most attach interest to late payment. Two things get missed. The statutes do not reach self-funded ERISA plans, which cover about two-thirds of workers with employer coverage, so for that book interest exists only if your contract says so. And where the statute does apply, the payor is generally supposed to pay the interest automatically rather than on request - which means the only way to know it never arrived is to reconcile remittance dates against the standard, per claim. Almost nobody does.

Recoupment and audit limits. The lookback cap, the notice requirement before an offset, the right to appeal. Payors do reach past these - far enough, often enough, that states legislated caps. New York limits overpayment recovery to 24 months from the original payment and requires 30 days written notice, with carve-outs for suspected fraud and for self-insured plans. The cap only helps if the person receiving the offset letter has a fast way to check what the contract and the statute permit.

Audit rights running the other way. Audit clauses in these agreements usually run one direction: the payor audits you. Where a system has managed to negotiate a right to review payor payment accuracy - and most have not - it goes unexercised, because exercising it requires knowing you have it.

Ongoing compliance obligations. The ones with no invoice and no end date. Exclusion and preclusion screening that is supposed to run on a schedule against lists that update monthly. Liability and professional coverage that has to stay at the negotiated limits, with your entity named, through every renewal. Business associate agreements that need countersigning when a subprocessor changes. Licensure and credentialing that lapses quietly. Each is small, each recurs forever, and none of them generates a claim - which is exactly why they are the first thing to slip and the last thing anyone notices.

The regulatory flow-downs. Any agreement with a Medicare Advantage or Medicaid plan carries a regulatory amendment attached - the kind Molina files as a 10-K exhibit. They arrive whether or not the system takes delegated risk, and they are federal and state both: Molina's is governed by a three-way agreement between DHCS, CMS and the plan. They carry their own terms, including a ten-year audit and inspection right for HHS and the Comptroller General, and a requirement to get every downstream entity to agree in writing. They sit in a different silo than the rate terms even though they arrived in the same envelope. We pulled that Molina amendment apart, clause by clause, alongside six other agreements.

Why the spreadsheet loses

Not because the people are careless. Because of arithmetic.

A mid-sized system holds dozens of payor agreements. The base contract is often short. The provider manual it incorporates by reference is not, and that manual changes without your signature. Each agreement carries more substantive terms than any one person tracks, live simultaneously, on different clocks, owned by different departments that do not share a system.

Managed care owns the negotiation. Revenue cycle owns the claim. Compliance owns the regulatory amendment. Finance owns the escalator's effect on the model. The contract is one document; the accountability for it is split four ways, and the split happens at exactly the moment the document goes into storage.

So the failure is structural. There is no handoff between the agreement and the work it creates.

What tracking requires

Storage is not tracking. Search is not tracking. Knowing where the PDF lives tells you nothing about whether its terms held last month.

Tracking means the contract has been decomposed into individual terms, each with a party who owes it, a trigger that activates it, a piece of evidence that would satisfy it, and a clock. It means somebody - or something - checks each one on its own schedule and can show what it checked.

Some of those terms are one-time. Some are evergreen. Some are conditional on facts that change, like a service line opening. Some are dormant until an event fires them, like a recoupment letter arriving. A system that handles only due dates handles the first kind and nothing else.

Where a machine helps

Reading is the bottleneck, and reading is what has gotten cheap.

Harper reads the executed agreement, the amendments and the regulatory attachments, and pulls out each obligation with the clause and page it came from. Each becomes a tracked item with an owner and a schedule: the escalator as a dated check against remittance, the timely-filing window as a standing parameter revenue cycle can query, the flow-down requirements as ongoing obligations with evidence attached, the recoupment cap as a rule to test any offset letter against.

Then it does the recurring work. It watches for the anniversary. It re-reads the amendment when it lands. It flags the offset letter that reaches past the cap. And when something is ambiguous or carries real money, it escalates to a person with the clause and the evidence already assembled.

Keep whatever CLM you use to draft and store these agreements - that is a different job and those tools are good at it. What is missing sits after signature: the layer that makes sure the terms you fought for are the terms you get.

A test worth running

Pick your three largest payor agreements. For each, answer without opening a spreadsheet:

What is the timely filing window, and has any denial in the last quarter cited a shorter one?

When does the rate escalator apply, and did the last remittance after that date reflect it?

What is the maximum recoupment lookback, and has any offset in the last year reached past it?

If those take a week to answer, they are not being enforced. Not because anyone chose that - because nothing in the stack was built to hold the answer.