How to Submit a Rebate / Claim Request (Step-by-Step)

To submit a rebate or claim request: confirm the scheme covers your claim and is in-window, gather the required documents, reference the specific invoices and scheme number, submit with the correct amount and complete evidence, then track it through validation, approval and settlement. Most rejections come from missing documents or out-of-window timing — both avoidable.

The five steps

1. Confirm eligibility. Check the scheme or agreement actually covers your claim and you are within the claim window.
2. Gather documents. Pull the invoices, scheme reference and any stock or damage evidence before you start.
3. Reference invoices and scheme. Link the claim to specific invoices and the scheme/agreement number — vague references are the top cause of delay.
4. Submit. Enter the correct amount with complete documentation attached.
5. Track status. Follow the claim through validation, approval and settlement, responding quickly to any query.

This is the action-level companion to the claim process explained, under the claims management hub.

The pre-submission checklist: what to verify before you type anything

Nine out of ten rejection reasons are checkable before submission, which makes the pre-submission pass the highest-leverage five minutes in the whole process:

• The scheme covers you. Your outlet/region/tier is in scope, the products claimed are in the scheme's product list, and the period matches. Schemes come in many shapes — slab, target, visibility, QPS — and each defines eligibility differently; the types of trade schemes in India guide maps the landscape.
• The window is open. Note the scheme's claim-by date at scheme launch, not at quarter end. An expired window is the one rejection with no cure.
• The amount follows from the data. Recompute the claim from the rate and the eligible base before submitting — slab boundaries and excluded SKUs are where amounts go wrong. The full arithmetic walkthrough is in how to calculate FMCG distributor claims.
• Every document in the pack exists and is legible. A referenced-but-missing attachment is functionally identical to no attachment.
• No duplicate. Confirm the same invoices haven't already been claimed under the same scheme — duplicate claims are flagged fast and remembered long.

Documents you need

Document	Why
Relevant invoices	Anchor the claim to real transactions
Scheme / agreement reference	Proves eligibility and the rate
Stock / damage records	For price-protection, buyback or damage claims
Calculation basis	Shows how the amount was derived

What evidence does each claim type need?

The table above is the common core; each claim type adds its own layer. Submitting the wrong pack shape for the claim type is one of the quietest causes of rejection:

• Scheme / rebate claims — invoice list, scheme number, and the calculation showing rate × eligible base. If the scheme is a secondary scheme settled on sell-out, the sell-through data itself is the evidence — the mechanics are in secondary scheme settlement.
• Price-protection claims — a dated stock statement proving inventory on hand on the price-change date, plus the price-change communication. The credit-note treatment that follows is covered in price protection and rate-difference credit notes under GST.
• Damage / expiry claims — batch details, damage or expiry notes, and photographic evidence where the agreement requires it.
• Display / merchandising claims — the agreed plan and proof of execution (photos, audit reports) for the claimed period.
• Chargeback-style claims — the reference to the specific billback or chargeback arrangement; the recovery path when these are disputed runs through the chargeback dispute process.

Statuses your claim passes

Submitted → validated → approved → settled. Knowing the status at any moment — and what is needed to advance it — is half the battle, which is why a system beats email threads for claim submission. See the rebate-specific context in rebate management software and volume rebates.

What happens behind each status transition — who validates, which approver the value routes to, what SLA applies — is approval-workflow design, and it is worth understanding as a submitter too: a claim that arrives complete and clearly referenced sails through routing that a vague claim fights at every step. The brand-side view is in designing claim and rebate approval workflows.

Common rejection reasons (and the fix)

Most rejections are self-inflicted. Missing documents, out-of-window timing, a wrong amount, or a claim the scheme never covered — all caught by an eligibility check and complete evidence at submission. The operational view of reducing rejections is in distributor claims management.

Mapping each rejection to its prevention:

Rejection reason	How to avoid it
Missing or illegible documents	Assemble the full evidence pack before opening the claim form; check every attachment opens
Out-of-window submission	Diary the claim-by date at scheme launch; submit early in the window, not on the last day
Amount doesn't match the calculation	Recompute from rate × eligible base; show the working in the claim
Scheme doesn't cover the claim	Run the eligibility check — scope, products, period — before drafting
Duplicate claim	Search for the invoice numbers before submitting
Vague references	Name the exact scheme number and list invoice numbers, never "Q1 scheme"

Resubmission etiquette: how to come back from a rejection

A rejection with a coded reason is an invitation to fix and resubmit — handled well, it costs days; handled badly, it costs the relationship. Four rules:

1. Fix what the reason says, completely. If the rejection cites a missing stock statement, resubmit with the stock statement — not with a promise of one.
2. Reference the original claim. The reviewer should see the history in one place, not treat the resubmission as a stranger.
3. Resubmit once. Batch every fix into a single resubmission. Drip-feeding corrections resets the review clock each time.
4. Watch the resubmission window. Rejections usually carry their own deadline; an expired resubmission window closes the claim as surely as an expired claim window.

If the rejection itself seems wrong — the reviewer misread the scheme, or applied the wrong rate — that is a dispute, not a resubmission: contest it through the dispute path with your evidence, rather than resubmitting the identical claim and hoping for a different reviewer.

The claim-quality checklist

Run this ten-point pass before hitting submit — a claim that scores ten sails; each miss is a probable query loop:

#	Check	Pass looks like
1	Scheme reference	Exact scheme/agreement number named
2	Eligibility	Scope, product list and period all confirmed
3	Window	Claim-by date verified open
4	Invoices	Specific invoice numbers listed, all in scope
5	Amount	Recomputed independently; matches to the rupee
6	Calculation basis	Working shown, slab/rate identified
7	Claim-type evidence	The right pack for the type (stock, damage, display proof)
8	Attachments	Every document present and legible
9	Duplicates	Invoice numbers not previously claimed
10	Contact	A named owner who will answer queries fast

Speed and accuracy compound

Every clean submission trains the reviewing side to trust your claims, and trusted claimants get faster cycles — while every sloppy claim buys extra scrutiny for the next ten. The disciplines that make submission fast and accurate at volume — templates per claim type, evidence captured at the moment of the event rather than reconstructed at quarter end — are expanded in submitting rebate requests fast and accurately.

For the brand-side mirror of this article — giving your distributors and dealers a portal where eligibility, windows and evidence requirements are enforced at intake instead of policed after — see channel partner incentive tracking, or book a demo to watch a claim go from submission to settlement on live data.

GST note: This article is general information, not tax or legal advice. Where settlement involves GST credit notes, positions — including CBIC Circular No. 251/08/2025-GST and the Finance Act 2026 amendments to Section 34 of the CGST Act, assented 30 March 2026 but not yet notified into force as of publication — must be re-verified at publish time with a qualified professional.