Direct answer: trade promotion spend is not one number to sum; it is five separate states. Do not add planned budget, approved commitment, submitted claims, accepted actual spend and paid amounts together. Tag every record with exactly one state and report the states side by side. Two reports can reach the same quarterly review with different trade promotion spend for the same promotion because one shows approved promotion agreements and the other shows submitted claims; neither figure is wrong, but they are not the same measure. The fix is definitional before it is technical: agree the states with finance and explain variance as a movement between states rather than an unexplained adjustment.
Define five trade promotion spend states with finance
Each state answers a different question. Write the definitions into the finance policy or a one-page convention note, including who may move a record from one state to another and what evidence is required.
- Planned budget: the amount allocated to the promotion in the annual or quarterly plan. It is a ceiling, not a spend, and it can be revised through a controlled version.
- Approved commitment: the value of promotions formally approved by the right authority, whether or not execution has started. This is the figure that reserves budget and blocks other activity from consuming it.
- Submitted claim: the value the field team or distributor has claimed with supporting evidence, before a reviewer has accepted it. Pending claims belong here, not in actuals.
- Approved actual (accepted spend): the portion of submitted claims accepted after evidence and condition review. This is the only figure that should be compared with budget as spend to date.
- Paid amount: cash or credit actually released to the partner. Payment lags acceptance according to payment terms and reflects cash timing, not promotion performance.
An operational reporting convention is not accounting treatment. Confirm accrual timing, cut-off and tax treatment with finance instead of inferring them from a dashboard.
Worked example: one promotion, one currency, one period
The following is a hypothetical illustration only. A six-week end-cap display with an off-invoice discount across 120 target stores runs from 1 July to 30 September 2026. All amounts are in USD.
| Spend state | What it captures | Amount (USD) | How to use it in review |
|---|---|---|---|
| Planned budget | Allocation approved in the quarterly plan | 48,000 | Ceiling for the promotion; compare only with approved actual |
| Approved commitment | Signed promotion agreement and agreed mechanics | 41,500 | Reserves budget; shows 6,500 still uncommitted |
| Claims submitted (gross) | All claims received with evidence | 38,900 | Workload and evidence view, not an amount spent |
| of which pending review | Awaiting evidence check or approval | 6,400 | Tracked with an ageing date; never counted as actual |
| of which rejected | Failed conditions, evidence or mechanics | 2,100 | Held outside actuals with a reason code for rework or dispute |
| of which accepted | Reviewed and approved for settlement | 30,400 | Reported as approved actual against budget |
| Paid to date | Cash or credit released | 24,000 | Cash timing view; explains the gap to accepted actual |
These rows are nested, not additive. Submitted claims equal pending plus rejected plus accepted, and paid amounts can never exceed accepted actual. Read this way, the table tells a story: commitment sits 6,500 below plan, 2,100 of claims failed review, and 6,400 of accepted spend has not yet been paid.
Rules that stop double counting
- Never add commitments to actuals. A commitment reserves budget; an actual consumes it. Summing the two overstates the total and makes every variance conversation unreliable.
- Report nested sets as nested. Show gross submissions with pending, rejected and accepted beneath them so a reader can see where claims sit without adding the lines together.
- Keep rejected claims visible but outside actuals. A rejection is a review outcome, not an amount. If the partner corrects and resubmits, the claim re-enters as a new submission with its own date.
- Fix the date convention. Commitment is usually dated at approval and actual at acceptance. State which date each report uses, or a promotion that spans a quarter end will move between reports.
- Version the plan and the definitions. When a mechanic changes mid-flight, the approval history and the affected commitment should be traceable; see version control for changes to a live trade promotion.
- Do not read effectiveness into the numbers. An accepted claim, or even a fully paid claim, says nothing about sales uplift. Measuring return needs an agreed baseline, cost scope and treatment of other influences.
Month-end checklist: who confirms what
- Trade marketing: attach the approved plan version and commitment reference to every live promotion.
- Field and distributor operations: submit claims with evidence tied to the store, campaign, task and period, and flag anything executed outside the agreed mechanics.
- Claim reviewer: record acceptance or rejection with a reason code and date, so the pending bucket has an ageing profile.
- Finance: confirm which state drives accrual and payment, and reconcile paid amounts back to accepted claims.
- Sales operations or promotion coordinator: publish a one-page bridge from planned to committed to submitted to accepted to paid, naming the largest movement and its cause.
- Verification: trace two claims end to end. If two reports disagree, the difference should be explainable as one of the five states, not as an unexplained adjustment.
What to ask before you automate the model
Airpalm publicly describes mobile visits, route planning, store audits, sales orders, inventory and promotion management (airpalm.com, checked 9 October 2026). That scope can put promotion activity and store evidence next to execution data, which helps evidence review; see what trade promotion management is and how it works and the note on store trade promotion claim reconciliation. Warehouse-level settlement, accruals and payment runs are typically owned by finance systems, so confirm rather than assume.
- Which of the five states does the tool record, and which does it only display?
- Can a reviewer see the full history of a rejected claim that was later corrected and resubmitted?
- Which role is permitted to change an accepted amount, and is the change logged?
- What is standard, what is configured, and what must be integrated with a finance system?
A practical next step is to take the promotion you closed last quarter, rebuild the five states from source documents, and compare the result with the figure in your last spend report. Where they differ, you have found a definition gap worth fixing before the next planning cycle.
Frequently asked questions (FAQ)
Should approved commitments appear inside actual spend reports?
They should appear as a separate line, never inside or added to actuals. A commitment reserves budget at the point of approval; an actual consumes it when a claim is accepted. Adding the two overstates the total and makes budget variance impossible to explain.
Where do rejected claims belong in the spend view?
Outside approved actuals but still visible in the same report. Keep a rejected bucket with reason codes and dates so rework, disputes and recurring evidence problems are apparent. If the partner corrects and resubmits, the claim re-enters as a new submission rather than being silently restored.
Is a paid amount the same as promotion spend?
No. Accepted spend is the amount the business has agreed it owes after review; payment is a cash event that follows acceptance according to payment terms. A paid claim is not evidence that the promotion worked, and an unpaid accepted claim is still an incurred cost in the period.
Who should own the definitions of the spend states?
Finance owns the policy and the treatment that feeds reporting and accrual; trade marketing owns the plan and commitment record; sales operations or the promotion coordinator owns the reporting bridge. Capture the agreed definitions in one versioned convention note so the same words mean the same thing in every review.
Put this guide into practice
This general-purpose worksheet is a starting point. Adapt its fields, responsibilities and rules to your business process.
