Insights Rebates

GPO rebates vs. local contract rebates: what to track separately and why

Supplier rebates on GPO contracts, GPO fee share-backs and local agreement rebates are three separate receivables. How each works, how to verify it and how it reaches the cost report.

Many hospital ledgers have one line called rebates, and three different kinds of money land on it: a check from a supplier under a group purchasing contract, a distribution from the GPO itself, and a credit tied to a contract your own team negotiated. They look alike on a bank statement and nowhere else. Each rests on a different agreement and evidence trail, and each goes quietly wrong in its own way.

They meet again in one place, the Medicare cost report. Nothing here is legal or accounting advice; take safe harbor and cost report questions to your compliance and reimbursement teams.

Three money flows behind one GL line

Flow Who pays you What it is based on Where the terms live
1. Supplier rebate on a GPO contract The supplier, directly or through the GPO Your purchases under the GPO agreement, at the tier you have activated The GPO contract plus your tier and commitment paperwork
2. GPO administrative fee share-back The GPO Fees suppliers paid the GPO on your purchases, and your sharing percentage Your membership or fee-sharing agreement
3. Local agreement rebate The supplier Whatever you negotiated: volume, share of spend, growth, product mix Your own contract

Federal auditors draw the same line. In a January 2005 review of three large GPOs and 21 of their members, the HHS Office of Inspector General examined “net revenue distributions” from the GPOs separately from rebates that members received “directly from vendors or passed from vendors through the GPOs.”

The two flows behaved differently. Members offset $200 million of the $255 million in distributions on their cost reports, or 78 percent. Rebates were handled far better: of $285 million examined, about $3 million was not offset, spread across seven members.

How GPO administrative fees work

Suppliers pay the GPO a fee when members buy under its contracts. The GAO’s 2014 report on the five largest national GPOs found these fees were “almost always based on a percentage of the purchase price.” The five collected about $2.3 billion in 2012 and passed about $1.6 billion, roughly 70 percent, on to customers or owners.

The portion passed on ranged from 37.6 percent to 100 percent across the five, so your share-back depends on your agreement, not on an industry norm.

The rate also varies by vendor. All five GPOs reported 3 percent as their most frequent vendor fee, yet their averages weighted by purchasing volume ran around 1 to 2 percent. Those averages include distributor fees, which are often below 1 percent, so manufacturer fees are likely higher than that average. The 3 percent figure also appears in the GPO safe harbor at 42 CFR 1001.952(j): the GPO’s written agreement with each member must either state that vendors will pay 3 percent or less of the purchase price, or specify the amount, or maximum amount, each vendor will pay.

So you cannot compute a share-back from your purchase history alone. You need the fee the GPO received on your purchases, vendor by vendor. The same regulation gives you a way to get it.

Local agreements layered on top

Large systems often negotiate below the GPO price. A ZS analysis written for medical technology suppliers describes integrated delivery networks seeking extra discounts through individual purchasing contracts that use the general GPO agreement as the starting point. It cites an estimate that one-third to one-half of medtech sales through GPOs flow through such contracts, with the GPO still collecting its administrative fee.

So the same purchases can produce a local rebate from the supplier and a fee share-back from the GPO. Whether the GPO contract’s own rebate also continues depends on the wording of the local agreement.

Both kinds of contract carry prerequisites that are easy to miss. The GAO describes commitment provisions in GPO contracts: customers that buy at least a set percentage of a product group from one manufacturer (80 percent in its example) receive a rebate or a lower price, and the commitment levels can be tiered.

Qualifying for a tier is not the same as holding it. An AHRMM paper on contract price alignment notes that the manufacturer must verify eligibility and tier, then accept or counter the request, and that agreed prices have historically taken 45 to 60 days to reach every party’s systems. A rebate calculated at the tier the supplier has on file is correct on the supplier’s side and short on yours. The fix is paperwork: a signed commitment letter, a confirmed acceptance and an effective date.

Who calculates and what you can check

Flow Calculated by What you can check
1. Supplier rebate on a GPO contract The supplier, from its sales records and distributor sales reports Recompute from purchase history at the activated tier; request the supplier’s calculation detail
2. Fee share-back The GPO, from the fees vendors pay it Reconcile to the GPO’s annual written disclosure and your sharing percentage
3. Local agreement rebate The supplier, under your contract Recompute in full: you hold the contract and the purchase data

Flow two is the hardest to check because its inputs sit outside your systems. Flow three is the easiest, and any shortfall there is yours to find.

The discount safe harbor in plain language

Paragraph (h) of 42 CFR 1001.952 defines a rebate as “any discount the terms of which are fixed and disclosed in writing to the buyer at the time of the initial purchase to which the discount applies, but which is not given at the time of sale.” For a buyer that files a cost report, the safe harbor sets four conditions:

  • The discount is earned on purchases of the same good or service within a single fiscal year of the buyer.
  • The buyer claims it in the fiscal year it is earned or the following year.
  • The buyer fully and accurately reports it in the applicable cost report.
  • On request, the buyer gives the Secretary or a state agency the information the seller supplied.

The seller has matching duties. Where the value is not known at the time of sale, the seller must note the discount program on the invoice or statement and, once the value is known, “provide the buyer with documentation of the calculation of the discount identifying the specific goods or services purchased to which the discount will be applied.”

Three practical readings, to discuss with counsel:

  • Asking a supplier for line-level calculation detail is not adversarial. The safe harbor’s seller standard calls for it.
  • Terms agreed verbally, or written down after the purchases they cover, sit awkwardly against “fixed and disclosed in writing.”
  • A rebate that drifts more than a year past the fiscal year it was earned in is a compliance question as well as a cash question.

Use the GPO’s annual disclosure as a control total

The GPO safe harbor has a second condition. Where the member is a health care provider, the GPO “must disclose in writing to the entity at least annually” the amount received from each vendor on purchases made by or on behalf of that member.

That document is the control total for flow two. An illustrative reconciliation, with round fictional figures:

Line Amount Where it comes from
Vendor fees the GPO received on our purchases $600,000 GPO annual disclosure
Sharing percentage 50% Membership agreement
Expected share-back $300,000 Calculation
Distributions received for the same period $262,000 Bank records and GL
Difference to explain $38,000

Explanations to test: timing across fiscal years, categories excluded from sharing, and a facility missing from the GPO’s member roster.

The disclosure has a second use. Where a vendor’s fee is a fixed percentage of purchases, divide the fee by that rate and you get the purchase volume that vendor reported for you. If your agreement only says “3 percent or less,” ask the GPO for the actual rate. For example, a $45,000 fee at 3 percent implies $1.5 million in reported purchases. If your own records show $2.4 million with that vendor, find out why. Part of the gap may be off-contract spend. Part may be a facility the vendor has not linked to your membership, and then the rebate in flow one may be missing it too.

Cost report treatment

42 CFR 413.98 states the principle in one sentence: “Discounts and allowances received on purchases of goods or services are reductions of the costs to which they relate.” They are cost reductions, not income, because “the true cost of the goods or services is the net amount actually paid for them.”

The GAO applies the same rule to GPO distributions, and notes that CMS updated its provider manual in December 2011 to specify that these distributions must be properly accounted for on the cost report. Its concern was oversight: HHS had not reviewed this reporting since 2005, and the GAO recommended that it determine whether hospitals report the revenue appropriately.

The Inspector General’s report explains why this matters for both kinds of hospital: cost-based providers such as critical access hospitals are paid on their reported costs, and for hospitals paid prospectively, overstated costs raise the cost-to-charge ratio used for outlier payments.

“The costs to which they relate” is a tracking requirement in disguise. To offset the right cost center, someone has to know what each payment relates to. A pooled rebates line with no evidence attached cannot answer that. Which cost center and year each receipt offsets is your reimbursement team’s call; your job is to give them the evidence.

One register, three flow types

One register is enough if flow type is a required field. Columns:

  • Contract or agreement, and the counterparty that pays
  • Flow type
  • Basis: purchases in scope, fee or sharing percentage, tier in force and its activation date
  • Earning period and fiscal year
  • Expected amount, with the calculation saved
  • Received amount, date and form (check, credit memo or distribution)
  • GL account and cost center
  • Evidence: contract clause, signed commitment letter, supplier calculation, GPO disclosure

A spreadsheet can hold this. Software can keep the expected column current as purchase files are loaded, so the comparison runs through the year instead of once at close.

Questions to ask this quarter

For your GPO:

  • At which tier is each facility activated on our ten largest contracts, and when did the supplier accept it?
  • Which commitment letters are on file for us, and which are unsigned or expired?
  • When will we receive the annual written disclosure of vendor fees, and what sharing percentage and exclusions apply to it?

For suppliers:

  • For each rebate payment, can you send the calculation detail that identifies the purchases it covers?
  • Where we hold a local agreement, does the rebate on the GPO contract continue or stop?
  • Does the sales data you measure us on include every facility and purchases through distributors?

For your own team, one test. Pick last year’s five largest receipts on the rebates line. For each, name who calculated it, which written term it was paid under, which fiscal year it was earned in and which cost center it reduced. Start with any receipt that fails one of the four.

Sources

Every outside fact in this article traces to one of these.

  • Where this is built in

    Rebate Recovery does this work as purchase data loads. Checks every supplier rebate contract against what you actually bought, then shows what suppliers owe you today, what this period is on pace to pay, and what is still within reach before it closes.

See what your contracts already owe you

Bring one supplier contract and a purchase extract. In a working session we load it, run the numbers and hand you the statement: earned, received, owed.