Most of the contract risk conversation in procurement focuses on what suppliers can do to you — price increases, lock-in terms, penalty clauses. Less attention goes to the clauses that run the other way: commitments the supplier made to return value to the buyer once certain conditions are met. Volume rebates, retrospective discounts, growth incentives. These are real entitlements, and in a surprising number of cases, they sit unclaimed in contracts that nobody is actively monitoring.
This happens because rebate clauses are typically buyer-initiated — the buyer has to know the threshold has been crossed and actively claim the rebate. Unlike a price increase, which the supplier will apply without prompting, a rebate requires the buyer to track their own purchase volumes against the agreed thresholds and raise an invoice or credit request. In a procurement team running on spreadsheets and managing 300 contracts, that active tracking rarely happens consistently.
How volume rebate triggers work in practice
The standard structure is a tiered volume threshold that entitles the buyer to a rebate — either as a percentage credit on invoices already paid, a reduction on future purchases, or a direct payment — once cumulative spend or purchase volume crosses a defined level in a given period.
A typical clause might read: "In the event that the Buyer's total purchases of Goods under this Agreement exceed £150,000 in any Contract Year, the Supplier shall apply a retrospective rebate of 3% on all purchases made in that Contract Year, credited to the Buyer's account within 30 days of year-end."
The mechanism is straightforward, but three things can cause it to go unclaimed. First, the threshold needs to be tracked against actual spend — if you don't know you crossed £150,000 by October, you don't know to expect a credit in January. Second, the credit is often passive — the supplier may or may not apply it automatically; many contracts say "shall apply" but in practice the buyer needs to follow up. Third, the rebate clause may use a different accounting period than the one the procurement team tracks spend against, causing the threshold-crossing to be missed or miscalculated.
Retroactive discount structures: a different mechanism, same problem
Retroactive discounts work differently from rebates but present the same tracking challenge. Rather than a credit applied at year-end, a retroactive discount means that if spend crosses a threshold, the per-unit price drops — retroactively — for all purchases in the period. Some contracts call these "look-back pricing adjustments."
The language might be: "If cumulative orders in any Quarterly Period exceed 5,000 units, the unit price for all units purchased in that Quarterly Period shall be retrospectively adjusted to £[lower rate], with the difference credited against subsequent invoices."
For procurement teams buying in variable quantities — seasonal businesses, project-based purchasers — these quarterly thresholds can flip in and out of being triggered depending on the period. Without active tracking, it's entirely possible to cross the threshold in Q3, not notice, and miss the credit that should have appeared on Q4 invoices. By the time year-end reconciliation happens, the discount period has closed and the credit opportunity may be time-barred by the contract's claim submission window.
Growth incentive clauses: the most overlooked category
A third variant, less common but worth knowing about, is the growth incentive clause. These are most often found in distribution and logistics agreements, and in supplier contracts where the buyer has committed to growing spend with that supplier over time. The clause typically provides a one-off payment or price improvement if the buyer's spend grows by a specified percentage year-on-year.
Growth incentive clauses are sometimes negotiated as a buyer-side protection mechanism — "we'll commit to increasing our spend with you by 20% next year if you give us a better rate structure." Once the contract is signed and the year passes, if the growth target was met, the buyer has a legitimate claim. But if nobody in the current team remembers the clause was negotiated, or if the team has changed since then, the claim simply doesn't get made.
We're not suggesting this is common enough to be a systematic revenue-recovery exercise. But in a contract portfolio of 300+ agreements, even if only 5 to 10 contracts have unclaimed rebate or growth incentive triggers, the aggregate value can be material — particularly if any of those contracts are high-volume goods or services supply agreements.
Why suppliers don't proactively tell you
The blunt answer is that there's no commercial incentive for a supplier to remind a buyer that a rebate trigger has been crossed. The credit comes out of the supplier's margin. The supplier will apply it if the buyer claims — the contract requires it — but they are not going to flag it unprompted in most cases.
This is worth naming clearly: the absence of a supplier reminder is not evidence that the threshold hasn't been crossed. The buyer has to maintain their own view of where they stand against the thresholds in their contracts. That's operationally difficult when the thresholds are buried in clause 8.4 of a 35-page agreement that was filed two years ago.
What Atira surfaces when we process a contract
When we extract clause data from a supplier contract, rebate structures and volume thresholds are among the fields we specifically identify: the threshold value or volume, the rebate percentage or amount, the measurement period, the mechanism for claiming (automatic credit, buyer-raised invoice, or supplier notification), and any time window on claims. For contracts with tiered structures — multiple threshold levels, each triggering a higher rebate rate — we extract each tier separately.
The output gives procurement teams a view of which contracts have active rebate clauses, what the thresholds are, and how close current spend might be to triggering them. That view doesn't replace the work of comparing contract periods against actual ERP purchase data — that's a procurement analytics function, not a contract intelligence function — but it provides the starting point that most teams are currently missing: a structured list of which contracts have value-return mechanisms at all, and what the trigger conditions are.
The ones that surprise teams most are often not the large supply contracts, where procurement has been paying attention, but the mid-tier service agreements that were negotiated three years ago by someone who's since left. The rebate clause was negotiated in good faith and reflects a real commercial agreement. It just needs to be found and tracked.