Amazon FBA Reimbursements and SAFE-T Claims India

Why reimbursement money leaks quietly

Every FBA seller in India loses inventory inside Amazon fulfilment centres. Units go missing during inbound receiving, get damaged in the warehouse, or vanish during a customer return that never comes back. Amazon does owe you for most of these events, but it rarely pays automatically and it never chases you to file. The result is a slow leak that a growing seller barely notices, because it hides inside a large GMV number. On a catalogue doing a few crore a year, unclaimed reimbursements of one to two percent of revenue are common, and that is often the difference between a healthy contribution margin and a thin one.

The core idea is simple. Amazon keeps a ledger of everything that happens to your units. When their system logs a loss or damage event that is their fault, a reimbursement should follow. When it does not, you have the right to file a claim within a defined window. Miss the window and the money is gone.

The three buckets that actually pay

Reimbursements fall into predictable categories, and each has its own report and evidence trail.

• Warehouse lost and damaged: Units marked lost or damaged inside the fulfilment centre before a sale. These show in the Inventory Adjustments report and the Reimbursements report.
• Customer returns not restocked: A customer is refunded, the unit is meant to return to your inventory, but it never gets scanned back in within the return window. You are owed either the unit or its value.
• Inbound shipment discrepancies: You sent 500 units, Amazon received 470. If the difference is not reconciled, you can open an inbound discrepancy case with your shipment ID, invoice, and carrier proof of delivery.

Each bucket needs a different pull. Do not rely on a single dashboard number. The Reimbursements report tells you what Amazon already paid, the Inventory Adjustments report tells you what changed, and the Returns report tells you what customers sent back. Reconciling across the three is where the recoverable gap appears.

Where SAFE-T fits

SAFE-T, the Seller Assurance for e-commerce Transactions claim, is a separate mechanism and it is often confused with FBA reimbursements. SAFE-T applies mainly to prepaid, self-ship, and Easy Ship orders where Amazon issues a refund to the buyer against your wishes, or where a return comes back empty, damaged, or as a different item. Classic abuse cases include a customer returning a brick instead of a phone, or a used item swapped for your new one.

When Amazon refunds the buyer and debits your account, you file a SAFE-T claim to recover that debit. The claim needs photographic evidence of the returned item, the order ID, and a clear description of the mismatch. Approval is not guaranteed, and the reimbursement is capped, but on high-value SKUs the recovery is meaningful. Sellers who photograph every high-value return at the point of receiving win far more SAFE-T claims than those who argue from memory.

Filing windows you cannot miss

Timing is the part that quietly kills recovery. Reimbursement eligibility is not open forever. For lost and damaged FBA units, the practical filing window is commonly around 60 days from the event or the transaction date, and it has tightened over the years. Customer return reimbursements typically become claimable after the return window closes without a restock, usually 45 to 60 days after the refund. SAFE-T claims must be filed shortly after the return is received, often within a matter of days of the refund event.

This is why the cadence matters more than the effort. A seller who audits once a year will find that most of the recoverable events have already aged out. A seller who runs the reconciliation monthly captures almost everything, because nothing sits long enough to expire.

A monthly reconciliation you can run

Build a repeatable process rather than a heroic annual cleanup.

• Pull the Inventory Ledger, Reimbursements, and Returns reports for the prior month on a fixed date.
• Match lost and damaged adjustments against reimbursements already issued, and list the unmatched events.
• List customer refunds where the unit was never restocked past the return window.
• Open cases for each gap through the standard reimbursement path, quoting FNSKU, quantity, and the event date.
• Value each claim against your landed cost, not the MRP, so your finance record is accurate.

Keep one tracker per month with the case ID, amount claimed, and status. Amazon sometimes reverses a reimbursement later if the unit is found, so you need the audit trail to dispute a clawback.

When to use a tool or a partner

Manual reconciliation works up to a point. Once your monthly units cross a few thousand, the report volume makes eyeballing impractical, and specialist reimbursement software or an operator partner pays for itself. Most such tools work on a success fee, taking a share only of recovered amounts, so the downside is limited. The one caution is data access. Give read scoped access, review the claims they file, and never let an outside party mass-file weak claims, because Amazon does track claim quality and abusive filing can invite scrutiny on your account.