It’s no secret, GPO contracts are complex. A single agreement can carry two different GPO prices based on eligibility requirements. And, that gap is exactly where medical device manufacturers lose margin without ever seeing an error message. GPO contracts answer the important question of, “What price does this customer get, right now?” But, due to the highly complex nature of these agreements, that answer isn’t always readily available. 

Customer price depends on eligibility, effective dates, and fee terms that shift constantly and rarely get checked in time.

Every error covered below takes a different shape. But, they all trace back to the same root cause: teams have no visibility into the terms that decide price, eligibility, and fees before a transaction happens. That’s why the fix, in each case, starts at the contract itself. 

Let’s dive in.

1. Eligibility tracking across GPO contracts is complicated. Here’s why:

GPOs don’t contain a single, straight-forward price. Instead, they’re full of sets of conditions (membership, tier, product category, effective dates) that determine which of several possible prices applies to a given order. Medical device manufacturers sell into hundreds of hospital accounts at any given time. Tracking those conditions across every account accurately is a common challenge. But, it is what truly separates a clean invoice from a margin leak.

Same product, two different prices

The same product can carry two different prices depending on which GPO a hospital is eligible under. 

Yes, you read that right: two hospitals can order the identical SKU in identical quantities and legitimately owe different amounts. 

This occurs because each is contracted through a different GPO, or a different tier within the same GPO. In GPO contracts, price is a property of the relationship between the buyer’s eligibility and the agreement terms in force at the time of the order. When that relationship isn’t tracked precisely, the seller has no reliable way to know which of the possible prices is correct.

How to Fix: Confirm the specific GPO and tier governing each account before applying a price, rather than assuming eligibility based on a similar account or a prior order.

Mid-year GPO switches

Eligibility isn’t permanent. A hospital can move from one GPO to another mid-year, and pricing has to follow. GPO membership changes that happen mid-contract mean pricing has to follow the effective date of the new eligibility, not the old terms.

Hospitals commonly switch GPOs, merge into health systems with different affiliations, or opt in and out of agreements at renewal. A hospital that switched GPOs three months ago should already be billed under the new terms. “Should” is the operative word, because if the seller’s system hasn’t caught up, every invoice since the switch is priced against a membership that no longer exists. 

How to Fix: Capture a new GPO or tier the moment it’s confirmed against the actual agreement, so the invoice cycle follows the new eligibility’s effective date.

2. Inconsistent eligibility tracking

Incomplete eligibility tracking is a direct margin loss, and the gap it creates most often resolves in the buyer’s favor; the hospital is undercharged relative to what it’s actually eligible for. That’s a hard problem to fix, because most GPO and IDN agreements restrict retroactive price increases.

Undercharges are far harder to fix than overcharges. An overcharge gets caught fast because the hospital is motivated to dispute it. An undercharge, on the other hand, has no one pushing to surface it, and if a manufacturer tries to bill for the difference later, hospital A/P typically resists a late charge against an already-closed invoice. 

How to Fix: Don’t wait for a discrepancy. Proactively tracking to catch the mismatch before the invoice goes out by pulling eligibility and pricing terms into a centralized system, checked at the time of order.

Three facts sellers need at all times

Sellers need three linked facts for every account at all times: 

• Current GPO eligibility 
• The price that eligibility entitles the customer to 
• The exact period it covers 

Any one of those three held loosely, like a stale roster, a price sheet that hasn’t been updated on the contract’s effective date, or an assumed rather than confirmed eligibility period, is enough to misprice a transaction. Across hundreds of accounts changing constantly, “loosely” is the default unless you have a tool in place to actively keep these facts current.

“Current eligibility” isn’t something to take a guess on. Each GPO issues its own membership and eligibility roster naming which accounts belong, under which tier, and as of which effective date. That roster is the seller’s source of truth, which is exactly what an intelligent contract repository is built to reconcile against automatically, rather than a spreadsheet someone has to remember to update.

Cherry-picking the best eligible price

Terms that aren’t tracked put the power into the buyer’s hands. In essence, buyers can effectively “cherry-pick” the most favorable eligible price if the seller isn’t tracking eligibility as precisely as the buyer is. Hospital procurement teams are often tuned into which agreements they’re eligible under, because securing the best available price is their job. If a hospital has access to a favorable price through a regional buying group, an IDN agreement, or a GPO tier the seller hasn’t fully reconciled, the buyer has every incentive to invoke it.

When the seller’s tracking is less precise than the buyer’s, the buyer’s more accurate picture of eligibility effectively sets the price. In practice, these errors are common and consistently favor the buyer, whether through deliberate cherry-picking or simply a stale price sheet that never got updated.

Manufacturers aren’t only on the defensive here, either. Primary-vendor commitments and no-stacking clauses, negotiated directly into the agreement, limit how many eligibility paths a given account can invoke at once and prevent a buyer from layering a regional group price on top of an IDN or GPO tier that already covers them. Written into the contract, those terms are only as good as the seller’s ability to actually track which accounts they apply to.

3. Correcting a pricing error: it depends on the channel

How a mispriced GPO transaction gets fixed isn’t the same for every manufacturer. The remediation path is tied to how the product reached the hospital in the first place, and the two most common paths, selling through a distributor versus selling direct under the GPO contract, run on very different clocks. Both, though, run into the same upstream problem: knowing which terms and which window actually apply requires that those terms were captured from the agreement in the first place.

Selling through a distributor: the chargeback window

When a distributor buys the product and resells it to the hospital at the GPO contract price, the manufacturer reimburses the distributor for the difference through a chargeback. If that chargeback was calculated against the wrong tier or a lapsed eligibility period, the fix runs through the chargeback resubmission process, and that process operates on a short, fixed SLA, typically 30 to 60 days from the original transaction.

Miss the window, and the distributor generally can’t resubmit the claim. At that point, the shortfall isn’t a write-off in the accounting sense, since nothing was ever booked as a receivable, it’s margin that leaked out through a pricing error and is now unrecoverable through that channel. The practical fix isn’t a stricter internal calendar; it’s knowing, from the contract itself, exactly what the SLA window is and what eligibility applies, so a mispriced claim can be flagged and resubmitted while there’s still time.

Selling direct under a GPO contract: credit, debit memos, and audit rights

When a manufacturer sells straight to the hospital under a GPO contract, there’s no distributor or chargeback in the middle. Corrections run through credit and debit memos, issued under the agreement’s audit and reconciliation rights, and governed by the contract’s limitations period rather than a short cliff. That period is typically measured in months or years, not weeks, which leaves considerably more room to catch and correct an error. Leaving more time to fix an overcharge doesn’t help your team with an undercharge.

Most GPO and IDN agreements restrict retroactive price increases, so even with a year to act, a manufacturer often can’t issue a debit memo that raises a price after the fact. In that direction, the audit rights window is open, but the correction itself isn’t available to walk through it. Because that direction of error can’t be undone after the fact, the only real fix is prevention: knowing the agreement’s actual eligibility and pricing terms before the invoice goes out, not relying on audit rights to catch it months later.

An illustrative example

Take a hospital that moved to a new, lower-priced GPO tier mid-year. Its distributor kept submitting chargebacks at the old, higher contract price for several months before anyone caught the switch, so the hospital was undercharged relative to its new eligibility and the manufacturer overpaid the distributor on every affected claim.

Caught inside the 30- to 60-day SLA, this is a routine dispute. Caught six months later, the overpayment is gone for good, not because no one noticed, but because no one was checking the chargeback against current eligibility while there was still time to fix it.

4. Fees beyond the admin fee

The admin fee, typically 2–3% per transaction, is the one line almost every GPO contract discloses cleanly, since federal safe harbor rules under the Anti-Kickback Statute require it to be set out in writing. The rest of the fee stack doesn’t carry that same requirement, and it’s where most of the undercounting happens: data reporting fees, marketing or program fees, chargeback processing costs, distribution or logistics fees, and other contract-specific charges.

Sure, individually these are minor. But stacked across every transaction they add up to a meaningfully larger cost than the admin fee alone suggests.

No two fee stacks look alike

How that fee stack is written varies from contract to contract. One agreement might bundle everything into a single blended rate; another might itemize five line items across five sections, each defined slightly differently. The full fee stack for any given agreement can’t be assumed from a similar-looking contract elsewhere. The fix is the same one that applies to eligibility: pull the fee terms out of the contract into a current record for that agreement, rather than relying on memory or a similar-looking contract to fill the gaps.

5. Overlapping agreements and compounding risk

A single hospital can be eligible through several paths at once, meaning one hospital can have several simultaneous, technically valid routes to eligibility. These include:

• A direct letter of commitment
• An IDN-level agreement covering its parent system
• An affiliation agreement
• A health-system-specific agreement nested inside a national GPO contract
• A regional buying group on top of any of the above

Any one of those paths could legitimately apply to a given order, and they don’t always point to the same price.

Two failure modes: mispricing and double-counting

Overlap creates two risks. The first is mispricing: two eligible paths point to different prices, the wrong one gets applied, and the error repeats on every reorder. The second is double-counting: a fee tied to one agreement is also embedded in a second overlapping agreement covering the same account. Both risks scale with how many overlapping paths a given customer has, and large IDNs and health systems tend to have several. 

Both come back to the same fix: check every eligibility path an account could claim against every other one before applying any of them. The issue is that this is only realistic if those paths are already extracted from their underlying agreements and visible together in one place.

Learn how MHA uses Pramata to transform contract management.

READ MORE

Why the fix starts at the contract

Every problem listed above, mispriced tiers, missed correction windows, undisclosed fees, overlapping agreements, shows up differently, but none of it starts in billing. It starts with whether the agreement’s eligibility, effective dates, and fee terms were ever pulled out of the contract itself and into a single, current, connected record. A stale roster, an unlogged fee, an unchecked overlapping agreement: these are all versions of the same gap between what the contract actually says and what the seller’s systems reflect.

That’s why the fix isn’t a faster spreadsheet or a stricter review calendar. It’s an intelligent contract repository, one that extracts the terms that actually govern price and obligation directly from the agreement language, keeps that record current as contracts are amended or renewed, and surfaces it wherever a pricing or billing decision gets made. The right contract intelligence platform is built to do exactly that.

Where Pramata fits into eligibility management

Pramata’s contract intelligence platform is built to close that gap for exactly the scenarios covered here: it catches a mid-year GPO switch as soon as the new terms take effect, reconciles billing against each GPO’s own eligibility roster, keeps the full fee stack for every agreement in one place instead of scattered across contract language, and checks overlapping agreements against each other before a fee gets applied twice.

For medical device manufacturers managing GPO relationships across hundreds of hospital accounts, that means pricing errors get caught while the correction window, whichever one applies, is still open, instead of after it closes. The result is better control over your margin.

Sound like something your team could use? Contact Pramata today.

Frequently Asked Questions