Amazon Reimbursement Report: A Source-First FBA Audit

What the Reimbursements report can confirm

Amazon's FBA Reimbursements report records approved reimbursement activity, including the approval date, reason, item identifiers, quantities, reimbursement ID, and fields used to connect reversals. It is evidence of a reimbursement entry, not a complete list of every inventory event that might need review.

Use it beside the Inventory Ledger detailed report. The ledger supplies the event chronology—negative adjustments, later found units, reference IDs, and fulfillment-center context—while the reimbursements export supplies the approved entries and reversals you can verify in Seller Central.

Export a reproducible source set

Choose a deliberate as-of date and export overlapping periods long enough to include the original inventory event and any later found or reimbursement row. Keep the untouched downloads. If you narrow or re-export a period, record that change so another reviewer can reproduce the audit.

• Inventory Ledger detailed report for the event chronology
• Reimbursements report for approved quantities and reversals
• Optional seller cost file for internal exposure context only
• The as-of date used to calculate review labels

Reconcile quantities without forcing a match

Start with clearly identified fulfillment-center lost, misplaced, or warehouse-damaged rows. Group only records that share a defensible item identifier and event context. A later found adjustment is strongest when it uses the same item and reference ID within the relevant chronology.

A reimbursement can often be narrowed by FNSKU or seller SKU, reason category, and date order, but that is still a likely match rather than proof of a one-to-one causal link. Preserve every source-row number and leave ambiguous events unsupported instead of guessing.

Net reversals before calling a unit reimbursed

A positive reimbursement row can be followed by a reversal. Pair the original and reversal identifiers, calculate the net positive quantity, and retain both rows in the evidence trail. Then confirm the amount and current state in Seller Central; a quantity match alone does not validate Amazon's calculation.

Seller sourcing cost is useful for prioritizing internal review, but it is not the reimbursement amount. Amazon's current reimbursement calculations and eligibility rules must be checked in the authoritative policy and portal.

Treat timing labels as prompts, not eligibility decisions

Amazon says most fulfillment-center lost or damaged reimbursements are handled proactively, while sellers may still need to file manually when an automatic reimbursement does not appear. Current policy materials record a 60-day manual claim window for fulfillment-center lost or damaged inventory, and Amazon guidance says many proactive reimbursements appear within about 20 days.

Those numbers support a review queue: monitor a recent event, review an older unresolved event, and flag a deadline that is close or already past. They do not prove eligibility, extend a deadline, or replace the current Inventory Defect and Reimbursement portal.

Finish in Seller Central

For every open unit, verify the original event, later adjustments, reimbursement and reversal rows, current portal status, and policy in effect. Confirm the quantity and amount before filing or closing the review. Save the authoritative evidence and any case response under your organization's retention rules.

A conservative report audit reduces the search space. The final claim decision, supporting documents, wording, and submission remain a human Seller Central workflow.