Skip to content
allanninal.dev/build
Collaborate

Part 2 of 7 · Rebate claim tracker series ~5 min read

How a rebate agreement becomes a rule

A rebate agreement is three pages of which about eleven lines matter, and the eleven lines are never in the same place twice.

Key takeaways

  • Five fields decide a rebate: basis, tiers, period, window, exclusions.
  • Retrospective or incremental is the single most important distinction.
  • Exclusions are where the arguments come from, so extract them explicitly.
  • An amendment is a new version, not an edit. Keep both.
  • Anything the model cannot find stays null and gets asked about.

The five fields

How a rebate agreement is reduced to five structured fieldsA vertical chain of five steps entered by a box labelled The agreement PDF, three pages with eleven useful lines. Step one is Basis: spend, units or growth. Step two is Tiers, threshold and rate, with a side box for the flag marking retrospective or incremental. Step three is Period: calendar, financial or rolling. Step four is Claim window, days after period end. Step five is Exclusions, the expensive field. A note says everything else in the document is boilerplate that has never once affected a claim.AWS ACCOUNTThe agreement PDFthree pages,eleven useful linesBasisspend, units,or growthTiersthreshold and rateAnd the flagretrospective orincrementalPeriodcalendar, financial,or rollingClaim windowdays after period endExclusionsthe expensive fieldEverything else in the document is boilerplate that has never once affected a claim.
Fig 1. The extraction, top to bottom. The side box on tiers is the difference between a rebate worth four hundred pounds and one worth four thousand.
  • App integration
  • Management
  • Analytics

Retrospective versus incremental

An incremental tier pays the higher rate only on the spend above the threshold. A retrospective tier pays it on everything from the first pound. The wording is often no more explicit than ’on total qualifying purchases’, and the difference at a hundred and forty thousand pounds of spend is several thousand pounds.

It also completely changes the behaviour of the system. Under an incremental tier, being just short of a threshold costs you almost nothing. Under a retrospective one, the last four thousand pounds of purchases earns a return of over a hundred percent, and that is worth interrupting somebody about.

Exclusions are the expensive field

What ’qualifying purchases’ usually excludes

  • Freight and delivery lines. Almost universally excluded, and almost never stripped out of the figure people quote.
  • Promotional and deal stock already bought at a discount, which is the exclusion that causes the largest gaps.
  • Specific ranges — third-party brands the supplier distributes but does not own, and clearance lines.
  • Credits and returns, which reduce the figure, and sometimes only if returned within the period.
  • Anything unpaid at period end, in about a third of agreements. This one quietly links your rebate to your own payment behaviour.

Getting the exclusions out of the document on day one is what makes your accrual match the supplier’s figure at claim time. A system that accrues on gross spend will be over by five to twelve percent every single time, and every claim becomes a negotiation you start from a weak position.

One model call, per document

This is the natural place for a model: pulling eleven specific facts out of prose that no two suppliers write the same way. It runs once per agreement and once per amendment, which is a handful of times a year, not per transaction.

What it must not do is infer. If the document does not say whether the tiers are retrospective, the field stays null and somebody is asked — because the guess is wrong half the time and the consequence is an accrual that is wrong by a factor of four.

Amendments are versions

How rebate agreement changes become dated rule versionsThree boxes stacked on the left. Annual renewal, new rates and the same structure, labelled expected. Mid-year letter, with effect from the first of July, labelled the awkward one. And Verbal agreement confirmed by email, labelled still a version. All three converge on A new rule version, effective from a date, which leads down to Both versions kept, because the period spans the change. A note says a mid-year change means one period evaluated under two rules, and overwriting the old one loses half the year.Annual renewalnew rates,same structureexpectedMid-year letter'with effect from1 July'the awkward oneVerbal agreementconfirmed by emailstill a versionA new rule versioneffective from a dateBoth versions keptthe period spansthe changeA mid-year change means one period evaluated under two rules. Overwriting the old one loses half the year.
Fig 2. Three ways terms change, all producing the same thing: a dated version. The box underneath is the reason you never edit a rule in place.
  • Storage
  • App integration
  • Front-end & mobile

Why the original stays

The extracted rule is what the system evaluates, but a disputed claim is settled by reading the actual sentence. Keeping the source document alongside the rule, with the page the terms came from, turns a two-week email exchange into a two-minute one.

It also gives you a way to check the extraction later. A rule that has been quietly wrong for eight months is worse than no rule, and the only way to catch it is being able to put the two side by side.

Next: what an accrual actually is.

All posts