Amazon Reimbursements Report: How to Verify You’ve Been Paid (and Avoid Duplicate Claims)

The Reimbursements report is Amazon’s official ledger of every payment they have made back to you for lost, damaged, or incorrectly handled inventory. It covers warehouse events, inbound shipment losses, removal order claims, and any other scenario where Amazon owes you money. Every row represents a single reimbursement transaction with a unique ID, the reason for the payout, the product affected, and the amount credited to your account.

For removal order sellers, this report is your source of truth for answering one critical question: did Amazon actually pay me for the claim I filed? Without it, you are relying on memory and case notes in Seller Support, which are unreliable at scale. Once you have more than a handful of open claims, the only way to confirm payment is to match your filed case references against the reimbursement records.

The report also reveals auto-reimbursements. Amazon sometimes detects lost or damaged inventory internally and issues a payout before you even notice the problem. These automatic payments are a double-edged sword: they save you from filing a claim, but they also mean you might accidentally file a duplicate if you are not checking the report first. Duplicate claims get rejected and can flag your account for excessive case volume.

Think of the Reimbursements report as the closing step in your removal order workflow. You file a claim, Amazon investigates, and eventually either pays or denies. The Reimbursements report is where you confirm which of those outcomes actually happened, and for how much.

The Reimbursements report lives under Reports > Payments > Reimbursements in Seller Central. You can generate reports for any date range within the last 18 months. For weekly reconciliation, pull the last 30 days to catch any recent payouts. For a full audit, pull the maximum range and export to CSV.

There is also a secondary path: Reports > Fulfilment > FBA Customer Returns covers return-specific reimbursements, but for removal order work, the Payments > Reimbursements route is the one you need. It contains all reimbursement types in a single report, including warehouse events, removal order claims, and inbound shipment losses.

When you export the report, you get a flat CSV with one row per reimbursement event. Large accounts can generate thousands of rows per month across all reimbursement types. The key is filtering efficiently so you only look at the rows that matter for your removal order reconciliation. We will cover the specific fields and filters in the next section.

The Reimbursements report is one piece of a larger workflow. To run an effective removal order recovery operation, you need to integrate this report check into your weekly routine alongside the Removal Order Detail report and your own claims tracker.

Here is the recommended weekly sequence: First, pull your Removal Order Detail report to identify new discrepancies. Second, check the Reimbursements report to see if Amazon has already paid for any of them. Third, file claims for genuine gaps using the claims filing process. Fourth, follow up on any pending claims that have not appeared in the Reimbursements report after 7 days using a chaser template. Finally, escalate any denied claims using the denied claim escalation template.

This cycle repeats every week. Over time, you build a complete picture of what Amazon owes you, what they have paid, and what is still outstanding. The sellers who recover the most money are not necessarily the ones with the biggest claims. They are the ones who check consistently and follow up relentlessly.