The contract says one price. The invoice says another. In most health systems that is not an occasional error, it is a steady rate of drift, and it has a structural cause. Four sources of truth describe the same item at the same time: the group purchasing organization award, your local direct agreements, the distributor price file loaded against your accounts, and the item master in your ERP.
Watch the handoffs. The GPO negotiates a tiered price with a manufacturer. Your system signs a commitment to qualify for a tier. The manufacturer notifies the distributor. The distributor activates the price against your ship-to accounts and item numbers. Your item master maps that item to a purchase unit of measure and a contract reference. Five handoffs, five chances for the record to disagree with itself.
Pricing accuracy is also a compliance question, not only a savings question. Administrative fees paid by manufacturers to group purchasing organizations sit inside a safe harbor that carries disclosure conditions, and rebate, discount and value-added arrangements are evaluated against Anti-Kickback considerations. That makes the documentation behind your prices part of your compliance posture, so treat the terms and the disclosures with the same care as the numbers.
How a contract term becomes the price you are charged
Supply chain teams tend to treat price as a field. It is closer to the output of a small workflow, and each stage of that workflow holds a condition that can fail quietly without generating an error anywhere in the system.
- Award and tier, the agreement sets a base price plus tiers that depend on committed volume, market share or conversion to one product family, so your tier is a claim you have to keep true.
- Letter of commitment, tier eligibility usually rests on a signed commitment with its own term and expiry date, and it lapses without notifying anyone who buys.
- Price activation, the manufacturer notifies the distributor, who loads the price against your accounts, and that activation commonly lags the contract effective date.
- Item mapping, the contract names a manufacturer catalog number while your item master carries a distributor number, a packaging configuration and a purchase unit of measure.
- Rebate and fee terms, growth rebates, administrative fees and value-added credits settle on their own cycle against volume data your team did not produce.
Nobody owns that chain end to end. Contracting owns the award, value analysis owns the conversion decision, the distributor owns activation, and accounts payable owns the invoice. The price is the only thing that passes through all four, and it is the one thing none of them is accountable for verifying.
Contract award documents produce a savings number that goes into a report before a single line has been bought at the new price. If activation lags six weeks, if the tier was never certified, if half the volume still flows to the legacy item, the report stays green while the invoices tell a different story. Reconciliation is what converts the claim into a fact.
Where the reconciliation actually breaks
These five failures cover most of what an invoice audit finds. They are worth naming individually because each one needs a different control, and a single generic price variance report will surface them all as the same alert.
- Unit of measure mismatch. The contract prices per each while purchasing buys by case, or the packaging configuration changed, so a correct price looks like a variance and a genuine overcharge hides inside the rounding.
- Effective date lag. The contract starts on the first of the month and the distributor activates two or three weeks later, producing a window of overpayment that is recoverable only if somebody claims it.
- Silent tier loss. Committed volume slips or conversion stalls, eligibility drops to a lower tier, and the price resets without a conversation because the condition lived in a document nobody monitors.
- Off-contract buying. A clinician preference item, a backorder substitution or a rush purchase moves spend outside the award, which both costs more per unit and erodes the volume the tier depends on.
- Expired commitment letters. The letter supporting tier eligibility runs out, the pricing continues briefly, then corrects retroactively and arrives as a credit dispute nobody budgeted for.
Building a contract to invoice control loop
Step 1, Make the pricing terms readable by a system
Extract the commercial mechanics from each agreement into structured fields: item, price, unit of measure, tier and its qualifying condition, effective and expiry dates, rebate basis, and the commitment document that supports eligibility. Until those live as data rather than as language in a PDF, every reconciliation is manual and every audit starts over.
Step 2, Reconcile the price file against the contract
Compare the distributor file to the contracted terms, not to last month file. Month over month comparison only detects change, so a price that has been wrong since activation stays invisible. Run the comparison at each load, flag items where contract and file disagree, and record when each corrected price took effect.
Step 3, Audit invoices at the line
Match invoice lines to the contracted price and unit of measure, and route mismatches as claims with an owner and a deadline. Health systems running invoice automation already have the matching engine in place, so the work is feeding it contract terms rather than building new tooling.
Step 4, Track tier conditions as obligations
Tier eligibility, commitment letter expiry, conversion milestones and rebate submission deadlines are obligations with dates and owners. Put them in a register that alerts before the date, not after the price changes. A tier lost quietly costs more over a year than most negotiated wins recover.
Step 5, Close the loop with value analysis
Report realized price against awarded price by item family every month, and send off-contract volume back to the value analysis committee that approved the conversion. That feedback is what turns compliance from an audit exercise into a purchasing behavior, because the clinicians who drive substitution finally see the consequence.
Put contract terms where the invoice can see them
Aavenir Contractflow holds GPO and direct agreement pricing as structured terms, and Obligationflow tracks tier conditions, commitment expiry and rebate deadlines with named owners and alerts.
Why pricing governance belongs to compliance too
Two points matter here, described at a general level. Administrative fees paid by manufacturers to group purchasing organizations operate within a safe harbor that is conditioned on written disclosure of the fee arrangement to members, and rebates, discounts and bundled credits are assessed against Anti-Kickback considerations that depend on how the benefit is documented and passed through. A Stark and Anti-Kickback audit checklist is the right place to test your records. Confirm specifics with counsel.
A discrepancy map for the first ninety days
Start with the five patterns below. For each one, trace the root cause rather than the symptom, because a variance report tells you the price is wrong and almost never tells you which handoff produced it.
| Discrepancy type | Root cause | Where it surfaces | Control to apply |
|---|---|---|---|
| Price above contract | Activation lag at the distributor | Invoice line audit, weeks after go live | Activation confirmation before the effective date |
| Apparent variance, correct price | Unit of measure or packaging mismatch | Price file load and match exceptions | Normalize purchase unit of measure in the item master |
| Tier price withdrawn | Commitment or conversion condition missed | Retroactive correction or credit dispute | Tier conditions tracked as dated obligations |
| Spend outside the award | Preference items and backorder substitution | Monthly contract coverage reporting | Off-contract volume returned to value analysis |
| Rebate short paid | Volume data assembled by the counterparty | Quarterly settlement reconciliation | Independent volume calculation and submission deadlines |
The discipline is the same one health systems apply on the revenue side, where payer contract automation turned rate sheets into terms a system can check. Do it on the supply side as well. Hold the pricing mechanics as data, reconcile against the contract rather than against last month, track tier conditions as obligations with owners, and keep the disclosure records that make the arrangement defensible.
For related guidance, see GPO contract price alignment, a supply chain guide, GPO and supply contract price compliance tracking and The provider’s guide to GPO and 340B contract control.
