Rebate Claim Documentation: What You Need for Each Claim Type

Every rebate claim has to prove three things: that the entitlement exists, that the quantity or value is right, and that the qualifying event actually happened. Every document below serves one of those three, and a claim that cannot answer all three is not assessable regardless of how much paperwork accompanies it.

That framing is worth holding onto, because it turns a long checklist into three questions. Most rejected claims fail on one specific question, and knowing which one tells you what to ask for.

The document table

One row per claim type. Adopt it as an internal standard if it is useful — that is what it is for.

Claim type	Proves entitlement	Proves quantity	Proves the event	Typical rejection reason
Volume / purchase rebate	Trading agreement with rates and thresholds	Purchase invoices for the period; cumulative volume statement	The purchases themselves	Threshold not actually reached
Secondary sales scheme	Scheme circular, qualifying SKUs, period	Distributor secondary sales report; stock movement statement	Sell-through data or sampled verification	Secondary data missing or unverifiable
Price protection / rate difference	Price change notification with effective date	Stock-on-hand statement at the effective date, by location	The price change itself	Stock statement dated wrongly or not location-wise
Damage and breakage	Damage policy or scheme terms	Damage register, quantity and batch	Photographs, inspection report, destruction certificate	No independent verification of the damage
Expiry and returns	Returns policy, expiry norms	Return note, batch and expiry date	Goods receipt or destruction certificate	Batch not traceable to an original invoice
Promotional and display	Promotion agreement, stores, period	Store list, number of sites	Dated, located photographs; store confirmation	Undated or unattributable photographs
Co-op advertising	Co-op agreement and approved plan	Media schedule and third-party invoices	Tear sheets, broadcast logs, ad copy	Spend not tied to the approved plan
Freight support	Freight terms in the agreement	Transporter invoices, lorry receipts	Delivery confirmation	Freight not scheme-linked
Special pricing claimback	The specific price authorisation	Invoices to the authorised customer	Sale to the named end customer	No authorisation on file for that customer
New-product listing	Listing agreement, SKUs, outlet count	Outlet list, item setup confirmation	Confirmation the item was listed	Listing not evidenced beyond the agreement

Two patterns repeat down the "typical rejection" column. Most rejections are about the event column, not entitlement — the agreement exists and the quantity is arguable, but nobody can show the thing actually happened. And most of the rest are about dates: an effective date, a batch date, a photograph date.

Proof of performance

Proof of performance is the evidence that an agreed activity actually took place, and it is where most promotional claim disputes live.

The failure mode has a name in every organisation that has dealt with it: the photographs-in-a-folder problem. A distributor submits forty images of product displays. None carry a date, a location, or anything tying them to the agreed activity. They may all be genuine. They prove nothing, because the same forty images could support any claim in any period at any store.

Verifiable evidence has four attributes:

1. Date — embedded in the file or the capture system, not typed into a filename.
2. Location — the specific store or outlet, identifiable in your own master data.
3. Partner identity — who executed it, so it can be matched to the claiming party.
4. Link to the agreed activity — which promotion, which SKUs, which period.

Strip any one of those and the evidence stops being evidence. The practical fix is almost always at capture: a simple app or form that stamps date, location and promotion reference at the moment of the photograph costs very little and eliminates the whole category of dispute. Retrofitting the four attributes afterwards is impossible, which is why this has to be decided before the promotion runs.

The secondary sales data question

A question worth answering directly, because sell-through schemes depend on it: will retailers actually share their invoices as evidence up the chain?

• In modern trade and integrated supply chains — sometimes. Where systems are connected and the commercial relationship supports it, item-level sell-out data does flow. This is the exception rather than the rule.
• In general trade — usually not. Retailers regard their sales data as commercially sensitive, and they are under no obligation to hand it to a supplier two tiers up. Expecting it is not a negotiating position, it is a planning error.

What to accept instead, in rough order of reliability:

• Distributor secondary sales reports — what the distributor sold to retailers. The standard basis for most sell-through schemes.
• Stock movement statements — opening stock, purchases, closing stock, with sales derived. Useful as a cross-check on the above.
• Sampled verification — physically verifying a subset of outlets and extrapolating.
• Third-party audit — an independent agency verifying offtake, used where amounts justify the cost.

This matters more than it appears, because it determines whether a scheme is administrable at all. A sell-through scheme designed on the assumption of retailer invoices, launched into a general-trade channel that will not provide them, cannot be settled on its own terms — and the usual outcome is that it gets settled on whatever data is available, which means it is not really the scheme that was designed.

Decide the evidence basis before designing the scheme, not after the first claims arrive. Sharing secondary sales data with brands covers the partner's side of that reluctance, and the secondary sales data quality specification covers what "usable" actually means once data does flow.

The ten reasons claims get rejected

Roughly in order of how often they occur:

1. Missing or wrong agreement reference — the validator cannot find the entitlement.
2. Out of period — the claim covers dates the agreement did not.
3. Quantity mismatch — claimed units exceed what the underlying records support.
4. Non-qualifying SKUs — products the agreement excludes, or superseded codes.
5. Duplicate submission — usually the same claim resubmitted after a delay.
6. No proof of performance — for any activity-based claim.
7. Wrong rate applied — often the current rate rather than the one live at the transaction date.
8. Claim window expired — submitted after the agreed deadline.
9. Underlying invoice credited — the sale the claim rests on was reversed.
10. Partner details mismatch — a different legal entity, GSTIN or code than the agreement names.

The first three are the bulk, and all three are submission-process problems rather than entitlement problems. That is an encouraging finding: a better claim template with mandatory fields removes most of them before anyone has to adjudicate anything. See how to submit a rebate claim request for the template side.

A claim SOP you can adopt

• Submission format — one claim per agreement per period, itemised by SKU where the agreement is SKU-specific.
• Mandatory fields — agreement reference, period, claim type, quantity, rate or basis, gross amount, claiming entity and its registration details.
• Evidence attachment — per the document table above, attached at submission rather than on request.
• Submission window — a stated number of days after period end, after which the entitlement lapses.
• Acknowledgement — within a stated period, with a claim number the partner can quote.
• Validation SLA — a stated turnaround, and a status the partner can see.
• Dispute route — a named escalation with a response deadline.
• Settlement timing — how soon after approval, and by what instrument.

The two items most often omitted are the acknowledgement and the visible status. Both look like courtesies and are actually controls: a partner who cannot see where a claim stands will chase by email, resubmit, or eventually take the money as a deduction — and a resubmission is how duplicates enter the system in the first place.

Retention and the audit trail

Retain for at least your statutory record-retention period, and longer for the agreements themselves.

The document most often missing at audit is not the invoice or the claim. It is the version of the agreement that was live on the transaction date. Businesses retain the current agreement and overwrite the rest, so when an auditor asks why a claim from eighteen months ago was settled at 2.5%, the only available document says 2%. The claim may have been perfectly correct. It is now indefensible.

Retain agreement versions with their effective dates, not just the latest one. It costs nothing and it is the difference between an accrual that is evidenced and an accrual that is asserted — see how to audit rebate claims for the tests that depend on it.

Settlement documentation in India

In Indian channels the settlement document is almost always a credit note rather than a payment, which adds a documentary layer that has nothing to do with the claim's commercial merit and everything to do with whether the credit can be issued at all.

A GST credit note has to carry its own prescribed particulars and reference the original supply, and whether the note carries tax or is issued as a financial credit note determines the input-tax-credit consequence for the recipient. That is a tax position rather than a documentation preference, and it should be settled with your advisor for each scheme structure rather than decided claim by claim. See financial vs tax credit notes under GST and GST credit notes for rebates under Rule 53(1A).

This is general guidance, not tax or accounting advice.