How do you audit Amazon reimbursements?
A reimbursement audit is a reconciliation, not an investigation. Every fact it needs is already recorded in your Seller Central reports. What is missing is the join between them, because Amazon reports refunds, returns and reimbursements in separate places and never presents them against each other.
Why this happens
Each report is individually correct. The refund report shows refunds. The returns report shows returns. The reimbursement report shows reimbursements. None of them shows a refund that had no return and no reimbursement, because that fact only exists in the gap between three documents. A monthly finance review looks at totals and sees nothing wrong, because nothing is wrong with any of the totals.
How it works
Pull the three reports for the same period
Refunds, returns and reimbursements from Seller Central, covering an identical date range. Extend the range slightly on the returns and reimbursements reports, since both lag the refund that triggered them.
Join on order ID
Every refund should have a corresponding return, a corresponding reimbursement, or a documented reason for neither. The rows with no match on either side are your working set.
Separate seller-fulfilled from FBA
The two use different recovery routes with different eligibility and different deadlines. Auditing them together produces a list you cannot act on.
Check the not-received claims against tracking
For refunds issued on non-delivery, pull the carrier scan history. A delivery scan against a not-received claim is the clearest case in the set.
Check inventory adjustments against credits
On the FBA side, units recorded as lost or damaged should have a matching reimbursement. Some categories are reconciled automatically and some are not, and the boundary moves.
Sort by deadline, not by value
A large claim outside its window is worth nothing. Work the cases closest to expiry first, regardless of amount.
A worked example
IllustrativeOne month of seller-fulfilled orders at a mid-sized retailer.
- The refund report shows 1,240 refunds issued.
- Joining to returns leaves 180 refunds with no return recorded after the return window closed.
- Joining those to reimbursements leaves 155 with no reimbursement either.
- Pulling tracking on the not-received subset shows 61 with a completed delivery scan.
Two distinct claim types out of one reconciliation: refunds where nothing came back, and not-received claims contradicted by the carrier. Neither is visible in any single report.
| Report | Shows | Cannot show |
|---|---|---|
| Refunds | Every refund issued | Whether the item came back |
| Returns | Every return received | Which refunds had no return |
| Reimbursements | What Amazon credited | What Amazon did not credit |
| Inventory adjustments | Units lost or damaged | Which were never reimbursed |
| Carrier tracking | Where the parcel went | Nothing, until joined to a claim |
Common mistakes
- Auditing totals rather than orders. The totals reconcile; the individual orders do not, and the gap only appears at order level.
- Using the same date range for all three reports. Returns and reimbursements lag the refund that caused them, so a strict range drops the most recent cases.
- Auditing FBA and seller-fulfilled together. Different routes, different eligibility, different deadlines, and a mixed list cannot be worked.
- Prioritising by value. The largest claim in an expired window is worth less than the smallest claim inside one.
- Running it once. An audit finds a backlog. What produces the backlog is that nobody is checking continuously.
What we see in the data
Across more than 5,000 seller-fulfilled orders examined at one live account in a single month, 395 orders worth £15,967 were identified as eligible for claim. That account was already using an FBA recovery service; none of these had been surfaced, because seller-fulfilled orders sit outside what those tools examine.
How this was measured →Checklist
- ✓Export refunds, returns and reimbursements for the same period, extending the range on the latter two.
- ✓Join all three on order ID.
- ✓Split the result into seller-fulfilled and FBA.
- ✓Isolate refunds with no return recorded after the return window closed.
- ✓Isolate refunds with no matching reimbursement.
- ✓Pull carrier tracking for every not-received refund and look for a delivery scan.
- ✓Sort the working set by filing deadline and start with the closest.
- ✓Record what you filed and what was granted, so the next audit starts from a known position.
Questions
How do I audit Amazon reimbursements?
Pull your refunds, returns and reimbursements reports for the same period and join them on order ID. Refunds with no corresponding return and no corresponding reimbursement are your working set. Then check not-received refunds against carrier tracking, split seller-fulfilled from FBA, and work by filing deadline rather than by value.
What data do I need for a reimbursement audit?
Three Seller Central reports — refunds, returns and reimbursements — plus carrier tracking for seller-fulfilled orders and inventory adjustment records for FBA. Every fact needed is already recorded; what is missing is the join between the reports.
How far back should an audit go?
As far as the filing windows allow, since anything older cannot be claimed regardless of what it shows. Working back beyond that is useful only for understanding the scale of what has already been lost, which is worth knowing once.
Can I automate a reimbursement audit?
Yes, and the reconciliation itself is well suited to it: the reports are structured, the join is on a single key, and the eligibility rules are consistent. What makes it impractical by hand is that the filing windows are shorter than most reporting cycles, so a monthly audit reliably finds expired claims.
How often should I run one?
Continuously rather than periodically. A one-off audit finds a backlog, and the backlog exists because nothing was checking between audits. The windows are short enough that any interval measured in weeks loses claims.