Expiry Return Docs That Distributors Actually Accept

The ₹1.8 lakhs that's been "under review" for three months

You shipped back 47 cartons of expired biscuits. The paperwork was filed. The credit note request was submitted. That was three months ago, and the status is still "under review," which is corporate language for "we found a reason to reject it but haven't told you yet."

Meanwhile, that ₹1.8 lakhs is stuck in a bureaucratic purgatory — not your money, not theirs, just absent from your working capital while someone in a claims processing department decides whether your batch number documentation meets their internal threshold for "acceptable." For a mid-size FMCG distributor whose entire monthly margin might be ₹4-6 lakhs, having ₹1.8 lakhs frozen in rejected claims is not an accounting inconvenience. It's a cash flow event.

This is not a one-off. FMCG distributors across India lose 15-25% of legitimate expiry claims to rejections. Not because the products weren't expired — they very obviously were, they're sitting in a warehouse smelling like stale cooking oil — but because the paperwork wasn't structured the way the claims department wanted it. The products are expired. The claim is valid. The documentation doesn't pass muster. And so the distributor eats the loss on stock they didn't want, couldn't sell, and tried to return through the proper channel.

why companies reject claims they know are valid

It's tempting to think that companies are acting in bad faith when they reject claims. Some are, particularly during quarter-end when return provisions affect their reported numbers. But most of the time, the rejection is a systems problem, not a malice problem. The claims department at a large FMCG company processes thousands of return requests per month. They have a checklist. If your submission doesn't hit every item on that checklist, it gets flagged, and flagged claims enter a queue that moves at geological speed.

The most common rejection reasons, in order of how much money they cost distributors: incomplete documentation (about 35% of rejections), timeline violations where you filed outside the return window (25%), quantity mismatches between what you claimed and what your paperwork shows (20%), poor quality evidence like blurry photos or illegible invoices (12%), and actual policy violations where the product category isn't eligible for returns (8%). That last category is the only one that's genuinely non-recoverable. The other 92% are paperwork problems, which means they're preventable problems, which means every rejected claim in those categories is money you left on the table because your documentation process has gaps.

the documentation that actually gets approved (and why yours probably doesn't)

The single biggest point of failure is the batch number. This sounds absurd — you're returning physical products with batch numbers printed on them, how hard can it be? — but the gap between "batch number as printed on the carton" and "batch number as entered in your claim form" is where most rejections originate.

The invoice says the batch code is L24A3847. Your warehouse guy wrote "Batch: 2024" on the return form because he was in a hurry and that seemed close enough. The claims processor runs L24A3847 against their manufacturing records, finds it, then tries to match it to your claim form, finds "Batch: 2024," and flags a mismatch. Investigation initiated. Investigation means delay. Delay, in the context of expiry claims that already have tight windows, usually means the claim ages out of the eligible period while it's being "investigated."

The fix is unglamorous but effective: record the exact batch number — every character, every digit — at the point of goods receipt, when the product first enters your warehouse. Not at the point of return, when the batch number might be smudged, the packaging might be damaged, and everyone is trying to process returns quickly. The batch number you capture on day one should flow unchanged through your entire system: receipt records, inventory tracking, return documentation, claim submission. One source of truth, recorded once, used everywhere.

The same principle applies to the invoice. Not a photocopy of a photocopy. Not a screenshot from your phone. The original purchase invoice or a clearly legible certified copy, with invoice number, product details, quantities, and dates that match what the company has in their system. If the invoice says you bought 50 cartons and your claim says you're returning 47, the remaining 3 need to be accounted for (sold, presumably). If you can't show that reconciliation, the entire claim looks suspect.

Photographic evidence is no longer optional. Most companies now require clear, timestamped photos showing the product with visible batch number and expiry date, the full carton or case showing quantity, and close-ups of any damage. Phone cameras do timestamps automatically, which helps, but the photos need to be the original files — not screenshots of photos, not WhatsApp-compressed images, not crops. A claims processor who can't read the batch number in your photo will reject the claim rather than squint.

the timeline trap that catches everyone at least once

Every company has claim windows. These are non-negotiable deadlines, and missing them by even a day turns a valid claim into a rejected one.

The typical window for expired goods is 30 days after the expiry date. Some strict companies give you 15 days. Some lenient ones give 45. For short-dated returns (product approaching expiry that you want to send back before it expires), the window is usually 30-60 days before the expiry date. Transit damage? You might have 48 hours from the delivery date. Twenty-four at strict companies.

The critical nuance that trips people up: the clock starts from different points depending on the claim type. Expired goods count from the expiry date. Damaged-on-receipt counts from the delivery date. Transit damage counts from delivery date. Quality issues count from the discovery date (which you need to document, because "we discovered it last month but are filing now" doesn't fly without a contemporaneous record).

The practical implication is that you need a system that knows when products are approaching expiry and automatically flags the return window. Not a calendar reminder that you set and forget. Not a monthly review where you discover that 20 SKUs passed their return deadline last week. An automated alert, at 60 days, at 30 days, at 15 days, that says "these batches are approaching their claim window — initiate return process now or lose eligibility." A supplier returns tracking system that ties expiry dates to claim windows eliminates the most expensive timing failures.

building the documentation at receipt, not at return

Here's the counterintuitive insight that separates distributors who recover 90%+ of claim value from distributors who write off 25%: the best time to prepare return documentation is when the goods arrive, not when they expire.

At goods receipt, you have the original invoice in hand, the batch numbers are clearly printed on fresh packaging, the quantities are being counted anyway, and you have time. Nobody is in a rush to process a return at the receiving dock. Capture everything: invoice details, batch numbers character by character, manufacturing and expiry dates, quantity received, condition on arrival. Photograph anything that arrives short-dated (less than 60% of shelf life remaining) or damaged. Flag products that will expire within your typical sales cycle.

All of this data sits quietly in your system, doing nothing, until the day you need to file a claim. And on that day, instead of scrambling to reconstruct a paper trail from memory and faded labels, you pull up the batch record, attach the receipt documentation, add the current photos showing expired status, and submit a claim package that the processor can verify in five minutes. That's the difference between a claim that gets approved in two weeks and a claim that gets rejected because your documentation has gaps that you can no longer fill.

the quarterly review that pays for itself

Once a quarter, sit down with your claims data and look for patterns. Which companies have the highest rejection rates? (If one company rejects 40% of your claims and another rejects 5%, the problem might not be your documentation — it might be the relationship, or that company's internal policies, or a regional claims processor who's particularly rigid.) Which product categories generate the most claims? (If 60% of your expiry returns are in one category, you're probably over-ordering in that category.) What documentation gaps keep recurring? (If batch number mismatches show up in every rejected claim, you have a receiving process problem, not a claims process problem.)

The patterns tell you where to invest your effort. Fix the receiving process for batch numbers, and 35% of your rejections disappear. Set up automated timeline alerts, and another 25% disappear. Improve your photo documentation standard, and another 12% goes away. You don't need to solve all of these simultaneously. Pick the biggest bucket, fix the process, and measure the improvement next quarter.

the best claim is the one you never file

All of this documentation discipline is valuable, but the highest-return investment is reducing the volume of claims you need to file in the first place. That means ordering discipline: calculating actual sales velocity per SKU rather than ordering based on scheme incentives or salesperson pressure. It means FEFO enforcement in your warehouse: new stock behind old stock, every time, no exceptions. It means proactive sales push for aging stock before it crosses into return territory — promotional bundles, retailer schemes, accepting lower margin over zero margin.

A distributor in Hyderabad tracked this precisely: before implementing batch-level documentation at receipt, they wrote off ₹8 lakhs annually in rejected claims. After implementing systematic tracking — same products, same volumes, same companies — rejections dropped to ₹1.2 lakhs. The difference wasn't in the products. It wasn't in the relationships. It was in the paperwork, which is simultaneously the most boring and the most expensive variable in the equation.

ShelfLifePro tracks batch numbers from receipt to return, automates claim window alerts, and generates claim-ready documentation packages with built-in [supplier returns tracking](/supplier-returns-tracking). Because your margins shouldn't disappear into rejected paperwork.