Amazon FBA Reimbursement Audit Checklist: From Reports to Review-Ready Cases
Run an FBA reimbursement audit with a practical checklist for report coverage, lost units, later adjustments, reimbursement matching and case evidence.
Start with a complete Inventory Ledger export, check later activity, compare reimbursement history, verify cost evidence and review the current policy for each event category. Keep a separate record for every candidate. An unmatched row is a reason to investigate, not a confirmed debt.
Define what this audit can answer
An inventory audit is most useful when it answers a narrow question: which events in a defined period still need investigation? A large total labeled missing inventory can hide duplicated exports, later corrections and payments that have already resolved the issue. Your first deliverable should be a traceable list of events, with the evidence and uncertainty beside each one.
This checklist focuses on fulfillment-center inventory review using reports. Inbound shipment shortages, customer returns and removal orders need their own evidence and policy checks. Keep those categories separate instead of applying one rule to every negative quantity. This is FluxPilot's recommended operating workflow; it is not an Amazon eligibility decision.
1. Freeze the scope and save the originals
Choose one seller account, marketplace and reporting period. Record the export date as well as the period covered. A file generated on October 3 can describe September activity; those are two different dates with two different purposes. Give each original file a clear name and keep it unchanged.
Save the ledger, reimbursement history and any supporting cost file in a folder for that review. If a later export changes a result, you can compare versions rather than guessing why your dashboard moved. Work from a copy when adding formulas, filters or review notes.
- Record account, marketplace, period and export timestamp.
- Confirm that report filters did not hide products or relevant activity.
- Keep a register of the files included and any known coverage gaps.
2. Build an event list before adding dollar totals
Create one working record for each event you plan to review. Retain the product identifiers, source reference, date, quantity and source filename. Use product names only as a readable label: two products can have similar names, and a name can change between exports.
Do not combine every row for the same product into one claim. A product could have two unrelated incidents in the same month. Separate records let you investigate each incident, assign a payment accurately and preserve the reason a record was closed.
| Checkpoint | Evidence to retain | If evidence is missing |
|---|---|---|
| Scope | Marketplace, period, original export | Obtain the missing report |
| Event | Identifier, date, source reference, units | Keep candidate unverified |
| Resolution | Later movements and reimbursement link | Continue investigation |
| Value | Unit cost, currency, supporting document | Leave estimate unpriced |
| Eligibility | Category, policy source, trigger date | Check Seller Central |
| Outcome | Case reference, decision, final status | Assign owner and next action |
3. Check resolutions without counting a unit twice
Investigate later inventory movements and reimbursement records before treating an event as open. A candidate can disappear from the queue because the inventory was found, because compensation was recorded, or because the original interpretation was wrong. Write down which explanation applies.
Worked example, using fictional data: an event affects five units. Evidence identifies one distinct unit found later, two units compensated in cash and one different unit compensated in inventory. One unit remains for review. That arithmetic is valid only if those resolution records describe distinct units; overlapping records cannot be subtracted twice.
4. Check costs and the applicable policy
Keep quantity reconciliation separate from valuation. If the remaining unit has a documented illustrative cost of $8, your internal estimate is $8. That figure is a prioritization aid, not a promise of what Amazon will reimburse. If cost evidence is absent, mark the candidate unpriced and request the document.
Amazon's October 15, 2025 announcement lists different submission windows for lost or damaged items, customer returns, removal orders and re-evaluation requests. Check the current policy in your marketplace before acting. Record the relevant trigger date rather than starting a deadline clock on the day you downloaded a report.
5. Prepare evidence, then close the loop
Give each review-ready candidate an owner, a next action and a concise evidence summary. The summary should explain the original event, what was checked afterward, what appears unresolved and what you want Seller Support to investigate. Preserve uncertainty instead of rewriting a possible match as a confirmed fact.
After a response or a new report, revisit the record. Keep confirmed recovered cash, resolved inventory and unresolved estimates in separate totals. A useful audit ends with both an action queue and a list of reasons records were closed; those reasons help the next review avoid the same false positives.
FluxPilot Recover starts with a supported Inventory Ledger file and can use optional reimbursement and cost files to help organize that review. Verify candidates against Seller Central before submitting a case. The goal is fewer unexplained events and better evidence, not a larger headline estimate.
Frequently asked questions
Does every unmatched event qualify for reimbursement?
No. First check report coverage, later resolutions, prior payments and the policy for that event category.
Should I audit only once at year end?
Our recommendation is a regular review that also considers category-specific deadlines. A year-end accounting review alone may be too late for some cases.
Sources and further reading
Workflows and examples are from FluxPilot. Amazon policies change; verify the current policy for your marketplace before filing a claim.
Amazon announcement: claim submission windows effective October 15, 2025 Amazon FBA inventory reimbursement policy (check your marketplace)