Implant price variance: how to price-check a bill-only request before it becomes a PO

For most hospital purchases the price is settled before anyone orders. The PO pulls a price from the item master, and accounts payable matches the invoice against it. Bill-only runs the other way: the surgery happens first, the rep’s usage sheet lists what was implanted and at what price, and the PO is written afterwards to match the sheet.

If the price on the PO was copied from the rep’s sheet, and the invoice came from the same sales order, the invoice will match the PO every time. The match passes and says nothing about whether the price was the contract price. Implant price variance, the gap between what a line is billed at and what the contract says, has to be tested somewhere other than the invoice match, and the cheapest place is the request, before the PO exists.

Why implants concentrate price errors

Several conditions stack up on one transaction. There is no PO in advance, so no system price to start from. The price arrives from the supplier’s side. Many components are not in the item master, because a set holds many sizes and a case uses a few. Part numbers change when a product line is updated. And implant contracts are often more than a flat price list: they can carry tiers, caps per construct and carve-outs for newer technology.

A 2012 study in The Journal of Bone and Joint Surgery covered more than 15,000 knee and hip replacements at 61 hospitals in 2008. The average implant cost per case ranged from $1,797 to $12,093 for knees and from $2,392 to $12,651 for hips. Hospital characteristics explained 61% of the variation in knee implant cost, and patient characteristics explained only a few percent. The data is old, and the study measured cost differences, not pricing errors, so read it as context, not a benchmark. The lesson that holds is that what a hospital pays for an implant depends far more on the hospital, and on choices made inside it, than on the patient.

The general price-accuracy problem

Price accuracy is weak across hospital purchasing generally. A Vizient article published in April 2026 reports, from Vizient’s own data, that only 61% of purchase orders are issued at the correct contract price, that about 52% of POs are still placed manually, and that more than 30% of item file attributes contain errors. Among the reasons it gives: unit-of-measure mismatches and misaligned contract tiers.

An older baseline is a contract price alignment paper published by AHRMM and co-written with GHX. It reports 9.25 million price exceptions tracked on the GHX exchange in 2013, estimates $10 to $25 of provider labor to resolve each one, and notes that agreed prices had historically taken 45 to 60 days to be loaded into every party’s system.

Neither source is specific to implants. But bill-only has every condition they blame: manual entry, gaps and errors in the item file, and tiers and units of measure that must be right on every line.

Five causes of implant price variance

Code each variance to a cause, because each cause has a different owner.

Cause	What it looks like on the request	Who fixes it
Price not in effect on the surgery date	Old price billed after a renewal, or the new price not yet loaded	Contracting
Wrong tier	Line priced at a tier the hospital is not on	Contracting and the supplier’s contract team
Unit-of-measure mismatch	Pack price billed per each, or the reverse	Whoever maintains the price file
Substituted or renumbered part	New catalog number at a higher price, often described as new technology	Value analysis and contracting
Off-contract item	No contract price exists	The approver now, sourcing next

Line-level checking rules

Run the line check in this order, because each step depends on the one before.

1. Match on the manufacturer catalog number, normalized. Strip dashes, dots, spaces and letter case first. Reps, price files and EMR records format the same number differently.
2. Use the price in effect on the date of surgery. Not the date the request was keyed. A late request can straddle a renewal.
3. Confirm the tier. The price file should hold one active tier per contract for any given date. If it holds all of them, someone will pick the wrong one.
4. Check unit of measure and quantity together. Compare the billed unit with the contract unit before comparing prices. A GHX guide to bill-only automation recommends that each bill-only line carry a quantity of no more than one and no more than one lot or serial number, which makes each line easier to check against a single contract price.
5. Apply an explicit tolerance. Allow a few cents for rounding and stop anything above contract beyond that. Flag lines priced well below contract too, since they can point to a wrong item or unit of measure.

Then decide the outcomes. Lines within tolerance pass without review. Any line above contract, or with no contract price, stops for a person. Software can run these checks on every request at submission, but the rules are the same from a spreadsheet.

An illustrative knee request, with round fictional prices:

Line	Requested	Contract on surgery date	Finding
Femoral component	$2,400	$2,400	Match
Tibial insert	$1,150	$950	Prior tier billed, $200 over
Bone screws, 4 at $300	$1,200	$300 per pack of 4	Unit of measure, $900 over
Patellar component, new part number	$600	Not on file; predecessor $450	Renumbered part, route to contracting

If the PO copied these prices, an invoice match would have caught none of the three problem lines.

Construct and capitated pricing

Caps come in two forms. The first is a price ceiling per implant line item, regardless of manufacturer or technology. A 2019 JAMA Network Open study of spinal implant procurement at a large academic medical center describes this approach for specialty devices. The center reported a 35% reduction in its annual expense for those devices after its first negotiation round and 2% after its second, and found revisions, complications and patient-reported outcomes statistically equivalent across the periods it compared. A line check handles this form well, because the ceiling is simply the contract price.

The second form is a flat price for a construct. A 2006 Orthopedics Today article describes hospitals paying one price per category for the collection of components that make up an implant, such as hip stem, femoral head, acetabular shell and liner. It is candid about the operational cost: contract managers and materials management must coordinate with the OR nurses who enter the orders so each implant is paid at the correct cap level.

A line check cannot enforce a construct cap. Take an illustrative primary hip cap of $4,500.

Component	Billed, and matching the price file
Stem	$2,200
Head	$900
Shell	$1,300
Liner	$700
Case total	$5,100 against a cap of $4,500

Every line matches the price file and the case is $600 over. The test has to run on the whole case: group the construct’s lines, total them, and compare the total with the cap for that category.

Test the other direction as well. If a case uses only a head and a liner and the full construct price is applied, the cap costs more than the parts it covers.

Construct pricing only works at the request if the contract says in writing which components count toward the cap, which add-ons bill separately, how revisions are priced, and who assigns the category. For newer technology, the Orthopedics Today article lists the carve-out criteria hospitals used: the product is unique to a single manufacturer, it has clinical data supporting better outcomes, and a hospital clinical review committee has approved it.

Off-contract and non-file items

These never pass without review, and the approver agrees a one-time price with a documented basis, such as the contract price of the closest comparable item. Record it as one-time so it does not become the default.

Then tell contracting: item, surgeon, supplier and how often it has appeared. A useful rule: the second use of an off-contract item in a quarter triggers a contracting conversation, so the next case has a price before it starts.

What to do with a variance

There are three paths.

Path	What happens	Cost
Return to the rep before approval	Rep corrects the line and resubmits	One corrected line
Approve at contract price and notify	PO goes out at contract price, then the invoice mismatches and AP holds it	A price exception to resolve on both sides
Pay and pursue a credit	Supplier credits and rebills	The most labor and the longest delay

The AHRMM paper calls credit and rebill labor-intensive, which is a good reason to make the first path the default. Treat a variance as a loading or keying problem until shown otherwise. The conversation is easier when it concerns a line on a pending request than money already paid.

Time is the constraint. The GHX guide, written by a provider and supplier work group, recommends that the rep’s case sheet reach the provider the same day where possible, and that the bill-only PO reach the supplier within five business days of the case. A price check that cannot finish inside that window gets skipped, which is the argument for making it mechanical.

Close the loop with sourcing

A request-level check produces data contracting rarely sees. Report monthly: variance count and dollars by supplier, category and cause, the days between each contract’s effective date and its price load, and the surgeries that fell in that gap.

Rebate and tier calculations usually rest on purchase dollars, so an overbilled line inflates eligible spend on paper, and an off-contract or renumbered item may not count toward a commitment at all. The AHRMM paper draws a similar link, listing inaccurate rebates and chargebacks among the costs of misaligned pricing. Getting the price right at the request is part of collecting what both sides agreed.

A test to run this month

1. Pull 90 days of bill-only POs for one high-volume service line.
2. Reprice every line against the contract price file in effect on the date of surgery.
3. Code each variance to one of the five causes.
4. For capped categories, total each construct and compare it with the cap, in both directions.
5. For each variance, record where it was found: before the PO, at invoice, in a later audit, or only now.

That last field tells you where your control actually sits. One rule of thumb to keep: if the price on the PO and the price on the invoice came from the same document, the match between them is not a price check.