Key Takeaways
- Vero, Transformance’s AI agent, puts the retailer’s debit note, the evidence and the agreement terms in one case; ClaimIQ auto-validates about 40% of trade deductions by rules (Transformance customer data, 2026). A person decides.
- A year-end deduction is a claim you recompute from the annual agreement and your own books, not a number you just reconcile.
- Eight fields per customer and condition are enough to check every claim; your team types them once a year from the signed agreement.
- Most over-deductions have nameable causes: a gross base instead of a net one, the wrong tier, an instalment counted twice, the same condition under a second name.
- Clear the supported part against the accrual with a credit note and dispute the rest with the recomputation and the credit-note numbers.
In This Article
- Key Takeaways
- How do you check a year-end rebate or fee deduction against the annual agreement?
- When do year-end conditions hit, and why do they arrive without context?
- What do you take from the annual agreement before you can check anything?
- How do you recompute a year-end rebate with tiers, step by step?
- How do you check advertising allowance, listing fee and free-goods deductions?
- Where do year-end deductions go wrong, and who owns each gap?
- When do you accept, dispute or clear the deduction against the accrual?
- What does an AI agent change in the year-end check?
How do you check a year-end rebate or fee deduction against the annual agreement?
Vero, Transformance’s AI agent, prepares each year-end deduction as a case. The check has four moves: agreement terms as fields, a recomputation from your books, the proof, no double payment.
Year-end conditions: what the annual agreement fixes, what the retailer’s debit note must show, how to check it and who owns the gap (an example design, not a standard)
Terms differ by retailer and year; use your own agreement. Operational check only, not legal advice.
What a year-end deduction is. A year-end deduction is an amount a retail key account withholds from a payment, or charges by debit note, for conditions the annual agreement settles after the invoices. That separates it from a shortage or a pricing deduction: there an operational record decides, here a calculation you can rebuild yourself.
Why a few customers raise most of the claims. Grocery retail is concentrated. In Germany, for example, the four largest retail groups held 76.7% of 279.2 billion euros in retail food sales in 2025 (our sum of NielsenIQ/Tradedimensions shares, published by the German food industry federation BVE, 2026). For a food or beverage supplier, a handful of annual agreements decides the largest debit notes of the year.
For the whole deduction process from remittance to repayment, see managing trade deductions in CPG and how to resolve retailer deductions. This guide covers only the year-end settlement: fields, recomputation, proof and owners.
Takeaway: every condition has its own test, but all of them start from the agreement.
When do year-end conditions hit, and why do they arrive without context?
Retrospective terms are agreed in the annual negotiation, fixed in the agreement, accrued during the year and claimed after the cut-off, often as one large debit note or remittance line.
On the invoice versus after the invoice. Some terms are netted on the invoice, such as an off-invoice allowance; those rarely create a deduction. Retrospective terms (year-end rebate, retrospective rebate, advertising allowance, listing fee, free goods) are settled months after the invoices. They explain why the largest debit notes of the year arrive after the cut-off.
Why the context is missing. The debit note usually carries the retailer’s own reference number, but rarely the agreement clause it relies on. Often it does not arrive alone but as a line in a consolidated remittance from a central payer that settles for many member stores and nets their claims (central settlement and buying groups). An AR analyst who looks for the agreement only when the claim lands is searching last year’s PDF under time pressure.
Takeaway: the claim arrives late, so the checklist has to be ready before it does.
What do you take from the annual agreement before you can check anything?
Capture eight fields per customer and condition: period, paying entity, base, excluded sales, tier, cut-off, settlement mode, and what was already given during the year.
- Validity and settlement period. Calendar year or the retailer’s fiscal year; without it you recompute on the wrong sales.
- Paying entity. The payer, the ship-to and the retail group can differ; the rebate belongs to exactly one of them.
- Rebate base. Net or gross, before or after off-invoice discounts; this is where most errors start.
- Excluded sales. Returns, credit notes, promotional goods or whole product lines, as the agreement defines them.
- Tier. Thresholds, rates, and whether the rate reached applies retroactively to all sales or only to sales above the threshold.
- Cut-off and claim deadline. Until when the retailer may claim, per the agreement or its own terms.
- Settlement mode. A credit note from you, an offset against open items by the retailer, or a payment.
- Given during the year. Instalments or advance payments on the rebate, with their credit-note numbers.
This is a data-capture design, not a standard. The agreement is usually a PDF; the fields are typed once a year and reused for every claim from that customer. Some conditions add fields: the activity for an advertising allowance, the item and chain for a slotting fee.
Takeaway: with the eight fields in place before the cut-off, you check the claim without hunting for the agreement.
How do you recompute a year-end rebate with tiers, step by step?
Rebuild the rebate-eligible base from your own books, find the tier it reaches, apply the rate, subtract what was already given, and compare the result with the deduction.
Worked example (illustrative, fictional supplier and key account, USD). A retail key account claims its year-end rebate by debit note and deducts it from the next payment. The debit note uses its purchases from you: 2,480,000 USD net. The agreement’s tiers (illustrative): up to 2,000,000 USD 1.5%; from 2,000,000 USD 2.0% on all purchases (retroactive). During the year you already gave instalments of 12,000 USD by credit note.
The 16,800 USD gap has two causes. 4,800 USD comes from the wrong base: 240,000 USD of returns, credit notes and excluded sales, times 2.0%. 12,000 USD is the instalments the retailer did not subtract. So the deduction is not “16,800 USD too high”; it is two named errors with two owners. Key account management settles the base definition with the buyer, and AR proves the instalments with the credit-note numbers.
Retroactive or incremental. With a retroactive tier, the rate reached applies to all sales; with an incremental tier, only to the part above the threshold. In the example, the incremental version gives 2,000,000 x 1.5% plus 240,000 x 2.0% = 34,800 USD instead of 44,800 USD. Field 5 records which applies, so it lives in the capture sheet, not in the key account manager’s memory.
For the tax treatment of rebates and credit notes, talk to your tax adviser; this guide covers the recomputation only.
Takeaway: compute from your base, not the retailer’s, and show each cause on its own line.
How do you check advertising allowance, listing fee and free-goods deductions?
Each needs its own proof: the allowance proof of the activity, the slotting fee a listing confirmation per item and chain, free goods proof that no cash was also deducted.
Rebate or advertising allowance? A rebate-type condition is a rate on a base, so you check it by recomputing. An advertising allowance pays for an agreed activity, so you check it with proof that the activity ran.
Advertising allowance. Check the activity, period and amount against the agreement and ask for proof of performance: a copy of the circular, evidence of the online placement, a shelf photo of the secondary display. Where the allowance is a percentage of sales, the same base check as for the rebate applies. If the activity falls outside the period or the proof is missing, do not accept; request the backup.
Listing (slotting) fee. Compare the item numbers on the claim with the listing confirmation per chain or region. Typical gaps are an item that was never listed or has been delisted, and the same fee charged again by a second entity of the retail group. A one-off fee appears exactly once.
Free goods. Free goods are a discount in units instead of cash. Check that the delivery note shows the free units and that the same value was not also deducted in dollars. That happens when the units shipped at zero price and the retailer still claims a free-goods value at year end.
Promotion deductions such as bill-backs and scan-based allowances are checked against the promotion record; the steps are in the promotion deductions section of the retailer deductions guide.
Takeaway: recompute the rebate, prove the allowance, confirm the listing, read the delivery note for free goods.
Where do year-end deductions go wrong, and who owns each gap?
Six patterns cause most gaps: wrong base, wrong tier, instalment counted twice, the same condition claimed twice, the wrong entity and a claim after the cut-off; each has one owner.
- Wrong base. Gross instead of net, returns or excluded sales not removed. Owner: key account management, which defines the base clearly in next year’s agreement.
- Wrong tier. The retailer counts another entity’s purchases or excluded lines and so reaches the higher tier. Owner: master data (customer hierarchy, product exclusions).
- Instalment counted twice. The year’s instalments are missing from the final settlement. Owner: AR, which tags every instalment credit note with the agreement reference.
- Same condition claimed twice. Once as a year-end rebate and again as a retrospective rebate, or once in a consolidated remittance and again as a separate debit note. Owner: key account management and AR, matching reference numbers.
- Wrong entity. The claim comes from an entity with no agreement, or lands on the wrong customer account in your books. Owner: master data.
- Claim after the cut-off. The settlement arrives after the deadline in the agreement. Owner: key account management; finance keeps the accrual until it is resolved.
Pattern 4 is the easiest to miss when it spans two channels: the rebate sits as a line in the central payer’s consolidated remittance and arrives weeks later again as its own debit note. Only a match across all of the customer’s remittances finds it.
Tag each pattern on the case as the root cause, so next year’s agreement and the accrual rate change; the deduction reason codes guide shows how to build the codes. When pattern 1 or 2 repeats for a customer, finance adjusts the accrual for the current year.
Takeaway: fix the owner’s input, not just the number.
When do you accept, dispute or clear the deduction against the accrual?
Accept what the agreement and your recomputation support and clear it against the accrual by credit note; dispute the rest with the recomputation, base breakdown and credit-note numbers.
- Accept. The claim is right. Issue the credit memo, clear the residual item from the deduction and release that amount of the accrual.
- Partly accept. As in the example: accept 32,800 USD against the accrual and dispute 16,800 USD. The disputed part stays open as its own residual item with a cause.
- Dispute. One dispute per claim reference, with the recomputation, the base breakdown and the instalment credit-note numbers. A template is in how to check a retailer debit note.
- No backup from the retailer. Request the backup with a deadline. A claim without a reference is not accepted automatically, even if it fits the accrual.
Deadlines come from the agreement or the retailer’s own terms; record them on the case from the day you log it. When the retailer repays the disputed part, it often arrives as a positive line on a later remittance. Match it to the dispute case (B2B invoice dispute workflow), then reconcile the accrual (reconciling trade promotion accruals with deductions).
How SAP documents the settlement. In SAP S/4HANA, condition contracts in Settlement Management hold the rebate rules. SAP describes the sequence as delta accruals settlements, partial settlements and a final settlement at the end: “In a partial or final settlement, you also determine the business volume beginning with the ‘CC Valid from’ date. You reverse the accruals from previous delta accruals settlement.” (SAP Learning, Executing Condition Contract Settlement, accessed 6 Nov 2026). SAP calls Condition Contract Management the successor to the classic SD/MM rebate agreements used in SAP ECC (SAP Learning, Explaining Condition Contract Management, accessed 6 Nov 2026). More on SAP in consumer goods: AR automation for CPG and FMCG companies on SAP.
Takeaway: accept, split or dispute, but never write the whole claim off against the accrual.
What does an AI agent change in the year-end check?
Vero prepares each year-end deduction as a case in Customer 360, with the claim and its evidence; your team keeps the agreement fields and the recomputation, and a person decides to accept or dispute.
Read and classify. Transformance reads debit notes, remittances and backup in any format, with over 97% extraction accuracy across 100+ document types and 170+ languages (Transformance platform data, 2026). ClaimIQ identifies deductions with 97% accuracy (Transformance platform data, 2026) and classifies each into one of six categories in under 15 seconds, against 45 minutes by hand (Transformance customer data, 2026).
Investigate and propose. ClaimIQ auto-validates about 40% of trade deductions by rules. Vero investigates the rest from Customer 360, its working memory for every customer, fetches internal and external information and proposes acceptance, partial acceptance or a dispute with the evidence. Your team maintains the agreement fields and does the recomputation; the case holds the claim with its evidence. Promotion records come from your trade promotion system.
Approve and post. Nothing posts to the ERP without human sign-off; the 4-level approval model (read, recommend, execute, post) follows your amount thresholds, and a full audit trail records every step. ClaimIQ customers recover 5-10% of revenue (Transformance customer data, 2026).
Takeaway: the agent gathers and prepares; your team decides.
Who Transformance is for
- ERPs: SAP S/4HANA (on-premises, private or public cloud) and SAP ECC run in production with customers today, as do NetSuite (including OneWorld subsidiaries), Microsoft Dynamics 365 Finance & Operations and Business Central, and Odoo; Oracle and Infor are supported; other ERPs connect through our integrations hub.
- Size: mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities and shared service centres.
- Payment volume: from under 1,000 to over 100,000 payments a month.
- Industries: manufacturing, consumer goods and food and beverage, logistics, e-commerce, agriculture, energy and professional services.
- Scope: cash application alone, or the full order-to-cash: cash application, deductions, AR collections and cash forecasting.
Conclusion: recompute before you reconcile
A year-end deduction is a claim with a base, a tier and a proof. Capture the eight fields before the cut-off, recompute from your own books, and show every gap with its cause and owner. Book a Call to see how Vero prepares your trade deductions as cases.
Key terms
- Deduction management: validating, disputing and clearing amounts customers withhold from payments.
- Trade deductions: deductions for promotions, allowances, fees and rebates.
- MDF and co-op advertising: a supplier’s contribution to the retailer’s advertising or placement.
- Slotting fee: a one-off payment to list and place a new item.
- Off-invoice allowance: a promotion discount taken on the invoice.
- Credit memo: the supplier’s document that accepts a valid deduction.
Related guides
- Which ERP systems does Transformance integrate with?
- How do you resolve retailer deductions in CPG?
- How to check a retailer debit note
- Reconciling trade promotion accruals with deductions
- Central settlement and buying groups
- Deduction reason codes
Frequently Asked Questions
How do you check a year-end rebate deduction from a retailer?
Rebuild the rebate-eligible base from your own books, apply the tier from the annual agreement, subtract instalments already given and compare the result with the deduction. Show each gap with its cause.
Which documents do you need to check a deduction against the annual agreement?
The signed agreement, the debit note with its reference, your own sales and credit-note data for the period, and the proof the condition needs, such as a circular copy for an advertising allowance.
How do you tell a rebate deduction from an advertising allowance?
A rebate-type condition is a rate on a base and is recomputed. An advertising allowance pays for an agreed activity and is proven by performance.
What do you do if the deduction is higher than the agreement?
Accept the supported part and clear it against the accrual with a credit memo. Dispute the rest with the recomputation, the base breakdown and the numbers of earlier credit notes.
Which ERPs and editions does this work with?
Transformance runs in production with customers on SAP S/4HANA and SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations and Business Central, and Odoo; Oracle and Infor are supported, and other ERPs connect through our integrations hub. The ERP connection typically takes 2-3 days, and your IT team may be involved.
What company size and payment volume is this for?
Mid-market to large enterprise teams with 250 to 2,000+ employees, including groups with several entities, handling from under 1,000 to over 100,000 payments a month.
How long does it take to start, and what does it cost?
A full rollout takes up to 4-8 weeks (Transformance customer data, 2026). The cost depends on scope and the number of entities: Book a Call and we size it with you.
SAP, SAP S/4HANA, Microsoft, Dynamics 365, Business Central, Oracle, NetSuite, Odoo and Infor are trademarks of their respective owners (SAP SE, Microsoft Corporation, Oracle Corporation, Odoo S.A., Infor). Transformance is not affiliated with or endorsed by them.
