How to Run an FBA Reimbursement Audit
Run your own FBA reimbursement audit: the reports to export, the order to check them in, a claim tracker, and how far back each case type's window reaches.
7 min readUpdated
Short answer. An FBA reimbursement audit is a routine you run on your own reports. Amazon sets a separate claim window for each case type, and the windows differ in length, in the event they run from and in when they open, so set the period you check from the table below. Then take out what Amazon has already reimbursed, check what is left one case type at a time, and keep a tracker of each claim and its last day to file. (Amazon's announcement, 24 July 2024)
This guide follows Amazon.com (US) sources: Amazon's announcements and guides posted by Amazon staff on the Seller Forums.
Last checked against Amazon's announcements: 5 November 2026
What an audit covers
An audit checks five places a reimbursement can be due. Each has a guide of its own:
- Units lost or damaged in a fulfillment center. See FBA lost and damaged inventory reimbursement.
- Customer returns that didn't come back. See FBA customer return reimbursement claims.
- Inbound shipments checked in short. See FBA inbound shipment shortage claims.
- Removal orders that came back short or damaged. The lost and damaged guide covers them near its end.
- FBA fees charged from a size or weight Amazon has wrong. See Amazon FBA fee overcharges.
How to recover Amazon FBA reimbursements explains what each one is. This guide is the routine: how far back to look, in what order, and how to keep track.
Set the period from the windows
Each case type has its own window, and the window decides how far back an audit needs to reach. Amazon's announcement posted 24 July 2024, effective 23 October 2024, sets four of them, and Amazon's US guide to disputing incorrect charges, posted on 17 April 2026, sets the one for fees:
| Case type | When you can file |
|---|---|
| Lost or damaged in a fulfillment center | no later than 60 days after the item was reported lost or damaged |
| FBA customer returns | between 60 and 120 days after the customer refund or replacement date |
| Removal shipment lost in transit | 15 to 75 days from the shipment-creation date |
| Other removal claims | within 60 days of the shipment being delivered back to you |
| FBA fee errors tied to weight or dimensions | within 90 days of the disputed charge |
Two of these open late. Amazon's announcement says a customer returns claim must not be submitted before 60 days, and a removal-in-transit claim not before 15 days. So export far enough back to reach the far end of the longest window you check, and keep the recent refunds and removals on your list until their window opens.
Shipments to Amazon are not among the case types in the announcement. For those, an Amazon staff guide says "Your shipment must be fully closed and past its reconciliation eligibility date before you can investigate discrepancies." (Amazon staff guide, 14 July 2026). Check each shipment's eligibility date instead.
The reports to export
- To start: Shipped to FBA, Inventory Event Detail, Reimbursements and Inbound Shipments.
- For refunds: the settlement report and the FBA customer returns report.
- For fees: the FBA Fee Preview report, and the settlement report for what each order was charged.
- For removals: your removal order reports.
- From your own records: what you shipped per FNSKU in each shipment, and your manufacturing cost per SKU.
How to prepare your Seller Central reports covers each export and how to keep the files clean.
Check them in this order
- Take out what Amazon has already paid. Amazon's announcement says: "Almost all reimbursement claims related to warehouse lost and damaged and customer returns cases will now be proactively reimbursed." Almost all is not all, and the same announcement goes on: "However, if you do not receive an automatic reimbursement and you believe that your inventory has been lost or damaged, you will need to file a manual claim." So the audit still checks warehouse and returns cases. Match each FNSKU against the Reimbursements report first, so the rest of the audit only covers what is left.
- Inbound shipments. List the closed shipments and set shipped against received, per FNSKU. An Amazon staff guide says "Many discrepancies resolve automatically as Amazon's reconciliation system identifies units received under different shipments or at other facilities", so look for missing units under other shipments before you count them as lost anywhere else.
- Lost and damaged units. Filter the inventory ledger for lost and damaged events and set them against the reimbursements for the same FNSKU.
- Customer returns. Set the refunds whose returns window is open against the units the FBA customer returns report shows came back.
- Removal orders. Set what each removal order asked for against what came back, and in what condition.
- Fees. Set the fee charged on each order against Amazon's rate for the product's size, and look for orders with more than one fulfillment-fee line.
Each step is a short job for one FNSKU and a long one across a catalog. That is the part software can carry.
Keep a claim tracker
Write down each candidate as you find it, with:
- the FNSKU, the case type and the quantity;
- the date its window runs from, and its last day to file, from the FBA claim deadline calculator;
- the evidence: the report rows that show the gap, and your manufacturing cost;
- the case ID once you raise it, and what came back.
Our advice on cost: Enter your per-unit manufacturing cost for each SKU, keep the supplier invoices behind it, and update it when your costs change. Raise the ones closest to their last day first. A tracker also shows repeats: the same FNSKU or the same kind of gap turning up audit after audit is worth fixing at its source, in how the units are packed, labeled or shipped.
How often to run it
Often enough that nothing passes its window between two checks, with time left to gather records and file. Set the interval from the shortest window in the table above, not from the calendar. The shortest are those for items lost or damaged in a fulfillment center and other removal claims: each closes 60 days after its event, and that sets the pace for the rest.
Check it with Leviathan Recon
Leviathan Recon does the matching from reports you export yourself. Upload them and Recon rebuilds your unit ledger per FNSKU, sets it against the balance Amazon reports, and gives each FNSKU a status. Two of them answer this guide's question:
- Reimbursed: short, but Amazon has already reimbursed the gap.
- Take Action: short, and not reimbursed. These are the ones to raise.
Its reconciliation modules follow the same checks as this audit:
- Shipment reconciliation: "Did FBA receive what you actually shipped?"
- Returns reconciliation: "Did each refunded return land back in sellable stock, or get reimbursed?"
- Removal reconciliation: "Did your removal orders come back complete, damaged, or not at all?"
- Adjustment reconciliation: "What did Amazon's inventory adjustments actually change?"
For fees, FBA fee reconciliation flags fees above Amazon's rate card for a product's size, and extra fulfillment-fee lines on an order. Open any figure to see the rows it came from.
The tracker lives in Recon's Action Center, with each case's status, remarks and attachments. You raise each case in Seller Central yourself, and Recon takes no percentage of anything Amazon reimburses. Start the 14-day free trial, with no card on file.
Checklist
- Set the period from the window for each case type you check.
- Export the reports, plus your own shipment and cost records.
- Take out what Amazon has already reimbursed.
- Check inbound shipments, then lost and damaged units, customer returns, removal orders and fees.
- Log each candidate with its last day to file and its evidence.
- Raise each case in Seller Central, closest to its last day first, and record the outcome.
- Run the audit again before the shortest window in the table can pass.
Related guides
- How to recover Amazon FBA reimbursements: what each kind of reimbursement is, and how to claim it.
- FBA lost and damaged inventory reimbursement: units lost or damaged inside a fulfillment center, and removal orders.
- FBA customer return reimbursement claims: refunds whose unit didn't come back.
- FBA inbound shipment shortage claims: shipments Amazon checked in short.
- Amazon FBA fee overcharges: fees charged from a size or weight Amazon has wrong.
- Amazon settlement reconciliation guide: where refunds and fees show in the settlement report.