For an FMCG manufacturer, trade promotion is often presented as a commercial investment. In practice, it more closely resembles an uncontrolled budget: commitments made at the start of the year by sales teams, deductions taken unilaterally by retailers mid-year, year-end rebates estimated by intuition, and a reconciliation process that ties up accounting teams for the entire month of December.
According to the Promotion Optimization Institute, consumer goods manufacturers spend between 11% and 27% of gross revenue on trade spend (POI State of the Industry, via PRWeb). It is typically the second-largest cost item after manufacturing. Yet most mid-market food manufacturers still manage this budget in spreadsheets, with no formalised process in their ERP. The result: unresolved disputes, a quarterly P&L distorted by rough-cut provisions, and reduced negotiating leverage with major grocery retailers.
This article covers the full TPM cycle and explains how to configure it in the leading ERP platforms on the market.
Trade promotion: the forgotten process in manufacturing ERPs
What trade spend actually represents
Trade spend encompasses everything a manufacturer pays or concedes to a retailer in exchange for shelf access and sales stimulation:
- List prices and permanent discounts: the foundation of the commercial relationship, negotiated annually
- Temporary promotions: short-term promotional pricing (net-net), featured in retailer flyers or on-shelf
- Co-op advertising and trade marketing: feature displays, gondola ends, in-store animations, retailer catalogue placements
- Sell-out and scan data deductions: deductions calculated on volumes actually sold at checkout, reconstructed via Nielsen/Circana data
These four categories share one defining characteristic: they are commercially committed before they are accounted for. The agreement is made verbally or captured in a shared spreadsheet. The deduction arrives weeks later as a short pay — a payment below the invoice amount — often months after the original commitment. Without a promotion management system in the ERP, the company has no real-time visibility of its net-of-deductions position by retailer, SKU, or promotion type.
Why most mid-market manufacturers still manage TPM in spreadsheets
The root cause lies in the history of ERP projects. When a food manufacturer deployed SAP or Sage X3 ten years ago, TPM was not in scope: too complex, too business-specific, deferred to the next phase. That next phase never came. Sales teams kept their own conditions files, accounting teams built their own deduction-tracking tools, and the two systems never spoke to each other.
The cost of this fragmentation is real: unjustified deductions go unnoticed, the trade budget drifts without alerts, and the year-end close requires two to three weeks of manual effort to reconcile amounts that could have been calculated automatically.
The end-to-end TPM cycle your ERP must support
Step 1: creating commercial conditions
At the start of each year, the Head of Sales signs a master agreement with each retail chain. This agreement defines the base price list, permanent discounts by product family, co-op advertising budgets, and the triggering conditions for annual volume rebates (AVR).
In the ERP, this agreement must be captured as a commercial conditions contract: a structured document linked to the customer account, used as the reference for automatically calculating net prices and accruals. SAP calls this a “Rebate Agreement”. Oracle refers to it as a “Trade Deal”. Sage X3 manages it through commercial agreements. The terminology varies; the logic is the same.
Without this data entry in the ERP, the agreement stays in an email or a PDF and cannot be used to automate calculations.
From a regulatory standpoint, several markets have formalised similar obligations. In France, Egalim 2 (law of 18 October 2021, progressively in force since 2022) requires that all commercial conditions between food suppliers and distributors be formalised in an annual signed contract before 1 March (FAQ Egalim 2, DGCCRF). In the UK, the Groceries Supply Code of Practice (GSCOP) imposes similar transparency obligations on designated retailers. In both contexts, the ERP becomes a regulatory compliance tool, not just a commercial system.
Step 2: activating promotions
During the year, sales teams activate point-in-time promotions: a temporary price on a given SKU, an end-of-aisle feature in week X, an in-store activation during a seasonal event. Each activation carries a cost (reduced price = lost margin, feature display = co-op charged) and a duration.
The ERP must be able to create a promotional plan: SKU, retailer, promotion type, dates, mechanism (price reduction, free goods, back-end rebate). This plan serves as the calculation basis for accruals and as the reference for validating subsequent deductions.
Step 3: retailer deductions
This is where the majority of manufacturers lose control. Retailers do not pay their invoices in full: they deduct from the payment the amounts corresponding to promotions executed, co-op advertising, and rebates accumulating in-period. These deductions arrive as “short pays” — a wire transfer below the invoice, accompanied by a deduction notice that the manufacturer must analyse.
Two types of deductions coexist:
- Valid deductions: corresponding to a formalised agreement or a promotion activated in the promotional plan. The ERP can automatically match them against the plan if the data is in place.
- Invalid deductions: taken by the retailer without a prior agreement, for amounts different from what was agreed, or for promotions that were never activated. Without a dispute management process, these deductions are often silently absorbed for lack of time to contest them.
Recovering invalid deductions is one of the most direct ROI levers of a TPM project. For a manufacturer with €5 million in annual deductions, recovering even 10–15% of contestable amounts represents €500,000 to €750,000.
Step 4: AVR accruals and accounting
Annual volume rebates (AVRs) are conditional discounts: the manufacturer commits to paying a rebate to the retailer if the retailer reaches a defined purchase volume. The accounting challenge is that this commitment is conditional and progressive: a 2% AVR on annual volume must be accrued each month as sales occur — not just in December when it crystallises.
In the ERP, this translates into an automatic rebate accrual calculated at each billing event. SAP handles this via Accruals linked to Rebate Agreements. Dynamics 365 offers the same logic in its Trade & Logistics module. A poorly calibrated accrual (too low during the year, then massively adjusted in December) distorts the quarterly P&L and complicates dialogue with finance and controlling teams.
Step 5: reconciliation and year-end close
Annual reconciliation means comparing, retailer by retailer and SKU by SKU, the provisioned amounts against the deductions actually taken and the rebates due. It is a matching exercise between three sources: the promotional plan in the ERP, deduction statements received from retailers, and sell-out data (scan data).
Without integrating these three sources into a single tool, this reconciliation is done manually in spreadsheets over two to three weeks. With TPM configured in the ERP, it can be automated at 60–80%: provisioned amounts and valid deductions are matched automatically, leaving only disputes and anomalies to be processed manually.
TPM modules in the leading ERP platforms
SAP Trade Management: the reference for large enterprises
SAP offers two approaches depending on the deployment context. For groups running SAP S/4HANA, the SAP Rebate Management module (within FI/SD) handles rebate agreements, accruals, and settlements. For advanced TPM needs (promotional planning, P&L forecast by promotion, sell-out analytics), SAP Trade Management (formerly SAP CRM) provides broader functional coverage, including a complete workflow for creating and validating promotional plans and performance dashboards.
This setup suits groups whose trade budget exceeds €20–30 million and that have sales teams structured by retailer. Below that threshold, configuration complexity frequently outweighs the operational benefit.
Vistex is the most widely deployed third-party module extending SAP for commercial conditions management and TPM in the European food industry. It extends SAP with a more business-accessible interface for sales and accounting teams, covering the full cycle from rebate management to customer deductions.
Oracle Trade Management Cloud
Within the Oracle Fusion suite, Trade Management Cloud provides a dedicated TPM module: promotional plan creation, commercial agreement management, accrual calculation, and deduction reconciliation. Its key strength is native integration with other Oracle modules (OTC, Finance, Demand Planning), enabling measurement of each promotion’s impact on P&L and volume forecasts.
Dynamics 365 with third-party modules
Microsoft Dynamics 365 Finance & Supply Chain Management covers rebate and commercial conditions management in its native module. For full TPM requirements (promotional planning, dispute management, P&L by promotion), third-party solutions such as Exceedra or Vistex for Dynamics integrate natively with D365 and add the missing functionality.
Sage X3 for mid-market manufacturers
Sage X3 offers commercial agreement management that covers permanent discounts, customer- and family-level pricing, and rebates. For mid-market food manufacturers whose trade budget does not exceed €5–10 million, Sage X3 provides sufficient functional coverage without requiring a third-party module. The main limitation is the absence of a promotional planning module: managing temporary promotions and activations remains largely manual.
Specialist TPM solutions: when to go beyond native ERP
When the volume of promotions, the number of managed retailers, and the complexity of commercial conditions exceed native ERP module capabilities, specialist solutions can complement or partially replace ERP coverage.
Exceedra is a TPM/TPO (Trade Promotion Optimisation) platform used by mid-market manufacturers across Europe. It covers promotional planning, P&L by promotion, deduction tracking, and reconciliation, with native connectivity to SAP, Oracle, and Dynamics.
Anaplan is used for financial planning of the trade budget and “what-if” scenario modelling: what is the net revenue impact if I shift this promotion by two weeks? This planning layer connects to the ERP to retrieve actuals and feed forecasts.
Kantar Retail and scan data platforms (Nielsen/Circana) provide the sell-out data needed to calculate deductions based on volumes actually sold at checkout. Integrating these feeds into the TPM tool (via API or EDI files) is the prerequisite for automating the reconciliation of sell-out deductions.
The threshold for switching to a specialist solution is typically a trade budget above €10 million annually, more than five major retail accounts to manage, or a monthly deduction volume exceeding 500 lines to reconcile.
Deduction reconciliation: the most critical step
Identifying invalid deductions
The first step in reconciliation is classifying each received deduction into two categories. Valid deductions correspond to an agreement formalised in the promotional plan — the ERP matches them automatically if the data is in place. Invalid deductions are either retailer errors, different interpretations of the commercial conditions, or charges for promotions that were never activated.
Contesting an invalid deduction requires producing a case file: proof of the agreement (or its absence), billing history, and a record of communications. An ERP that archives commercial contracts and promotional plans provides this evidence automatically.
Regulatory compliance in retail relationships
Several jurisdictions have enacted laws governing commercial practices between manufacturers and retailers. In France, the Loi Sapin II (2016), complemented by Egalim 2, sets out rules on commercial transparency in food distribution. In the UK, GSCOP imposes obligations on major grocery retailers regarding supplier treatment. More broadly, EU unfair trading practices legislation (Directive 2019/633) sets a common baseline across member states.
In all these frameworks, the ERP plays a traceability role: archiving the history of conditions granted, corresponding services rendered, and amounts paid enables manufacturers to demonstrate compliance under regulatory scrutiny or in commercial disputes.
TPM KPIs to track in your ERP
An effective TPM dashboard tracks at minimum these indicators:
Net Trade Rate: total trade spend (discounts, promotions, co-op) as a percentage of gross revenue. Compare with the sector benchmark (11–27% per POI). A rate above 20% without deduction control is a warning signal.
Invalid deduction rate: amount of contested deductions as a percentage of total deductions received. Organisations with a formalised dispute management process typically reduce this below 5%.
AVR accrual vs. actual variance: gap between the cumulative monthly accrual and the AVR crystallised at year-end. A variance above 10% indicates an accrual model requiring recalibration.
Promotional ROI by SKU: incremental revenue generated during and after the promotion, divided by the total cost of the promotion (discount + co-op). Most FMCG manufacturers calculate this in a post-mortem spreadsheet; the goal is to produce it in near-real time from the TPM system.
Reconciliation cycle time: number of days between receiving a deduction and classifying it (valid/invalid/disputed). A cycle under 30 days is achievable with a structured ERP process.
Roadmap for structuring TPM in your ERP
If your TPM management is currently spreadsheet-based, here is a pragmatic sequence:
Months 1–2: audit of existing commercial conditions. Identify agreement types (permanent discounts, AVRs, co-op advertising), the retailers involved, and annual amounts by category. This audit typically reveals inconsistencies between commitments made and amounts actually deducted.
Months 3–4: data entry of agreements into the ERP. Configure Rebate Agreements (SAP), Trade Deals (Oracle), or commercial agreements (Sage X3). Activate automatic accrual calculation. Allow 3 to 5 days of configuration time for an experienced implementation partner.
Months 5–6: deduction workflow deployment. Connect retailer deduction statements to the ERP’s AR module. Implement the classification process (valid/invalid) and the dispute management workflow for invalid deductions.
From month 7 onwards: measure and optimise. Analyse the ROI of the first promotions processed through the system. Adjust accrual models. Consider integrating scan data feeds for sell-out deductions.
To deepen your understanding of managing retail relationships from your ERP, see our grocery and food retail ERP comparison 2026: Blue Yonder, SAP, Cegid and Orisha and our food and beverage ERP guide for SMEs and mid-market: Sage X3, Dynamics and Infor. Download our ERP evaluation grid to assess commercial conditions and TPM modules across the leading vendors on 30 criteria.
