A supplier offers a 3% year-end rebate. At closing, your team applies that rate to total purchases. The supplier uses a different purchase base, excludes a product category or calculates the rebate in bands. The two totals no longer match.
Tracking a supplier year-end rebate takes more than recording a percentage. Connect the agreement to eligible purchases, apply the right calculation and check that the rebate is settled. Here is a practical method for hotels, restaurants and groups operating across several properties.
What is a supplier year-end rebate?
A year-end rebate is a commercial discount calculated after a purchasing period under agreed conditions. It may depend on purchase value or quantity and include several tiers. Oracle’s annual supplier programme documentation describes this type of arrangement. French purchasing teams commonly call it a remise de fin d’année, or RFA.
Keep these items separate in your records:
| Item | What to check |
|---|---|
| Discount already shown on an invoice | The net price applied to that purchase |
| Rebate provided for in an agreement | The amount calculated for the agreed period and scope |
| Rebate credit note received | The amount acknowledged by the supplier |
| Credit applied or payment confirmed | Recovery of some or all of the rebate |
An estimated rebate and the credit note that settles it are not two separate savings. They are stages of the same process.
1. Define eligible purchases before applying the rate
Start with an agreement record covering the supplier, properties, dates, eligible products, exclusions and calculation method. Record the relevant date basis too: order, delivery or invoice, as specified in the agreement.
Oracle’s documentation distinguishes purchases that count towards reaching a tier from purchases that earn a discount. Those two bases may differ, so check your agreement before building a formula. Source: Oracle eligibility rules.
In this hypothetical example, all amounts exclude tax and use one common currency, with no particular currency implied. The agreement uses the same base for tier qualification and rebate calculation:
| Item | Amount in value |
|---|---|
| Invoices for the period, after invoice discounts | 134,000 |
| Products excluded from the agreement | −8,000 |
| Credit notes for eligible product returns, not yet deducted | −6,000 |
| Eligible purchases | 120,000 |
Exclusions and returns do not overlap in this example. Never deduct a correction twice if it is already reflected in the total. A delivery note and its invoice are not two purchases either: three-way matching helps keep the base free of duplicates.
For a hotel group, confirm whether properties can pool purchases to reach a threshold. Do not consolidate companies, suppliers or currencies just because their names look similar. Use the identifiers and rules specified in the agreement.
2. Separate retrospective rebates from graduated bands
Rebate tiers can work in different ways. SAP describes scales applying to total business volume as well as interval scales. Use the method specified in your agreement. Source: SAP rebate scales.
Example A: the achieved rate applies to the whole base
Our first hypothetical agreement provides:
- below 50,000 in eligible purchases: 0%;
- from 50,000 inclusive to below 100,000: 2% of the whole base;
- from 100,000 inclusive: 3% of the whole base.
At 120,000 in eligible purchases, the rebate is 120,000 × 3% = 3,600.
Example B: each band keeps its own rate
A different hypothetical agreement provides 0% on the first 50,000, 2% on the next 50,000 and 3% on the amount above 100,000.
For the same purchases, the calculation becomes:
(50,000 × 0%) + (50,000 × 2%) + (20,000 × 3%) = 1,600.
The headline percentages look similar, but the result differs by 2,000. Confirm the method and the treatment of amounts exactly at a threshold before agreeing the statement.
3. Track progress without buying just to reach a tier
Update the tracker using available documents. Keep the year-end forecast separate from purchases already made: it still depends on future orders, returns and exclusions.
A useful tracker can fit into the following fields:
| Field | Why the purchasing team needs it |
|---|---|
| Supplier, agreement and period | Find the applicable rules |
| Eligible purchases to date | Support the total with documents |
| Tier reached and next threshold | See the actual position |
| Rebate calculated to date | Estimate the rebate under the agreement |
| Separate forecast | Prepare the year-end discussion |
| Supplier statement and variance | Identify amounts to reconcile |
| Credit note received, credit applied or payment confirmed, balance | Separate acknowledgement from recovery |
| Owner and next action | Turn the check into a task |
Reaching a tier can help when the purchases meet a real need. Compare the additional rebate with any supplier price premium, storage cost and waste risk. An order placed solely to cross a threshold may cost more than the rebate it earns. Keep your supplier price list and price history alongside the rebate calculation during negotiations.
4. Reconcile the statement and confirm settlement
Before the agreement closes, request the supplier’s calculation detail. Compare scope, dates, purchases, adjustments and rates in that order. SAP describes comparing business volumes between partners before final settlement: it helps locate a disagreement instead of debating only the total. Source: SAP rebate settlement procedure.
Keep the agreement, eligible documents, your calculation, the supplier statement and settlement evidence together. If the confirmed statement is 3,600 and a first rebate credit note of 1,000 has been received and applied, the balance to track is 2,600, subject to any other settlements or adjustments. A credit note that has only been received still needs to be matched to its application or refund.
For a discrepancy, send the relevant lines and document references and request an explanation or correction. This follows the same discipline as checking supplier invoice errors. Pass the evidence to your finance team for accounting and tax treatment at closing.
Connect rebates to purchasing data in Eqolux
Eqolux supplier management brings together purchases by supplier, price history and year-end rebate agreement tracking. This provides a basis for preparing your calculation and discussing it with the supplier.
Check that your agreement’s parameters match the configured calculation; the workflow above does not imply that every contractual variation is automated. Your procurement dashboard puts rebates alongside other purchasing priorities: paid prices, supplier concentration and differences between properties.
To explore this workflow for your hotel or restaurant group, book a demonstration.
Frequently asked questions
Does a rebate apply to every purchase from the supplier?
Only if the agreement says so. Check products, properties, dates and the treatment of returns. The invoice total is not necessarily the eligible purchase base.
Can several restaurants pool their purchases?
Yes, if the agreement provides a common base for those properties. Keep the property-level detail to explain the total and allocate the rebate under the agreed rule.
What proves that the rebate has been settled?
Link evidence of the credit being applied or the payment being received to the agreement and confirmed statement. Neither a calculation nor receipt of a credit note alone proves recovery; track calculated, confirmed, credited and settled amounts separately.

