Why Your Amazon Settlement Report Never Matches What You Expect
A line-by-line walk through where the numbers actually come from — and where they quietly diverge.
InviPulse TeamJune 2, 20264 min left
Every two weeks, Amazon deposits a number into your bank account and calls it a settlement. Most sellers glance at the total, confirm it landed, and move on. That's the moment reconciliation actually starts mattering — because the total is a net figure sitting on top of hundreds or thousands of individual transactions, and any one of them can be wrong without changing the sign of the total enough for you to notice.
What a settlement actually contains
A settlement period bundles together several categories of movement, not one:
Order proceeds
Item price plus shipping, per unit sold in the period.
Fees
Referral fees, FBA fulfillment, storage, and any per-order charges.
Refunds & returns
Customer refunds, return shipping, and restocking adjustments.
Reimbursements
Amazon's own compensation for lost or damaged inventory.
Each of those categories is itself a report Amazon publishes separately — and the settlement is only the sum of them, delayed by whatever falls inside that two-week window. A refund issued on day 13 of a 14-day period might not clear until the next settlement, which is the single most common reason a settlement total looks "wrong" when it isn't.
The reconciliation unit is the order, not the period
Trying to match a settlement total against your books almost never works cleanly, because the settlement and your bookkeeping period rarely start and end on the same day. Match at the order level instead — every settlement line should trace back to a specific order ID — and the period-level total takes care of itself.
Where the gaps actually come from
In practice, four patterns account for nearly every reconciliation discrepancy we see:
| Pattern | How it shows up | How to catch it |
|---|---|---|
| Timing lag | A refund or fee posts in a later settlement than the order | Reconcile by order ID, not by settlement period |
| Fee miscategorization | A referral fee charged against the wrong category rate | Compare the applied rate to Amazon's published category table |
| Duplicate adjustments | The same reimbursement or chargeback appears twice | Deduplicate by Amazon's own adjustment ID, not by amount |
| Silent fee changes | A per-unit fee changes mid-month without a specific notification | Diff this month's per-category rates against last month's |
Fee changes are the one that costs the most
Amazon updates FBA fulfillment fees periodically, and the change doesn't always arrive as a headline announcement — sometimes it's a rate table update you'd only notice by comparing numbers. A 40-cent-per-unit increase across a few thousand monthly units is real money that a quarterly "does this look right" glance will not catch.
A worked example
Take a single order: a $24.99 item, standard size, fulfilled by Amazon.
- Order proceeds$24.99
Item price
- Referral fee$3.75
15% of price
- FBA fulfillment$5.42
Standard size
- Net proceeds$15.82
What actually settles
That last figure — net proceeds — is the number that should show up, order by order, inside the settlement report. If it doesn't, the difference is almost always one of the four patterns above, not a mysterious Amazon error.
The settlement total is an opinion. The order-level trace is the fact.
Automating the match
Once you accept that reconciliation happens at the order level, the process becomes mechanical rather than judgment-heavy — which is exactly the kind of work software should be doing instead of a spreadsheet.
Export the settlement report, export the all-orders report, and VLOOKUP order IDs between them in a spreadsheet — checking fee amounts, refund amounts, and reimbursement amounts against expectation for every row.
Orders, settlements, and fee schedules sync automatically. Every settlement line is matched against its order on arrival, and anything that doesn't match — a fee outside the expected range, a missing reimbursement, a duplicate adjustment — is flagged the same day, not at month-end.
Amazon allows reimbursement claims within a rolling window (18 months for most claim types at the time of writing), so it's worth reconciling at least that far back once, then keeping current afterward. Older gaps may no longer be claimable, but they're still worth knowing about for accurate historical margin reporting.
Treat it the same way as one against you — the goal is an accurate ledger, not a one-directional audit. A rate applied incorrectly in your favor this month is a rate that can just as easily flip against you next month if it isn't understood.
Yes — for sellers on multiple marketplaces, the settlement report applies Amazon's own conversion rate at time of disbursement, which won't match the rate your accounting system uses unless you specifically align them. Reconcile in the original transaction currency first, then convert.
Reconciliation isn't glamorous, but it's the difference between a profit number you can defend and one you're hoping is close enough.
Two of the most common sources of a gap are worth understanding on their own: how referral fees vary by category and price band, and what actually happens to a lost FBA unit between the warehouse and your inventory count.