How Much Is Amazon Holding of Yours Right Now? The Audit to Run

Why the summary report hides the number

A settlement summary shows one blended figure for fulfillment fees, one for storage, one for reimbursements — each already netted against everything else that happened that month. A $65,000 error sitting inside two months of transactions looks, at summary level, like a slightly higher-than-usual fee month, nothing more. The audit that actually finds this money has to run at the transaction level: individual shipment IDs, individual settlement lines, individual claim windows — not the rolled-up total that's designed to make reconciliation easy, not designed to make errors visible.

This isn't a design flaw in Amazon's reporting so much as a mismatch of purpose: a settlement summary exists to tell you what hit your bank account, not to tell you whether every line inside it was correct. Those are different questions, and answering the second one requires a different report altogether — or the same reports, read at a level of detail most sellers never open them to.

The five places to check, in order of where the money usually is

• Customer returns that never returned. Compare refunds issued against units actually received back into inventory. This is consistently the largest single category — the window doesn't open until 60 days after the refund and closes at 120, so anything not checked in that gap is easy to miss entirely.
• Lost or damaged inventory inside fulfillment centers. Since 1 November 2024 Amazon auto-pays many of these, so the audit here is checking what its automation missed, not assuming nothing's owed.
• Fulfillment fee and dimension errors. Compare the fee actually charged per unit against the current size-tier and weight-band rate card for the shipped, sealed package — not the spec sheet.
• Removal and inbound shortfalls. Compare units Amazon's own removal or receiving record confirms against what you actually shipped or requested.
• Storage and aged-inventory surcharges. Confirm the charges match the size tier and month, since misclassification here compounds monthly rather than showing up once.

Run these five in this order because the first two are usually the largest dollar amounts and the most time-sensitive, while the last three are more about ongoing accuracy than a single recoverable event. A weekly audit that only ever gets through the first two before time runs out is still catching the majority of the value; one that jumps straight to storage-fee accuracy while returns pile up unchecked has its priorities backwards.

A worked example of what a real transaction-level audit finds

In one account we audited, a transaction-level pass through two months of inbound shipping deductions — not the settlement summary, the individual shipment-level charges underneath it — found roughly $65,000 of incorrect deductions that a summary-level review had never surfaced. Nothing about the monthly total looked unusual; the errors were spread thin enough across dozens of shipments that no single line stood out until they were totaled deliberately. That's the pattern worth internalizing: an error large enough to matter in aggregate is often small enough per transaction to be invisible without a line-by-line pass.

What running this audit actually requires

Pull the inventory adjustment report, the FBA customer returns report, the removal shipment status report, the fee preview or fulfillment fee report, and the storage fee report for the same trailing period — typically 90 to 120 days, to cover the longest claim window. Join returns against received units to find gaps. Join removal confirmations against original shipment quantities. Recalculate fulfillment fees against actual shipped-package dimensions rather than the spec sheet. None of this requires special access; it requires time, a consistent method, and doing it on a schedule rather than once. The data is already in Seller Central — the audit is the discipline of actually reconciling it.

One practical wrinkle: Amazon settles some fees up to 15 days after the sale, so the most recent one to two weeks of any report will always look slightly off compared to a fully reconciled month. Treat the trailing 15 days as an estimate rather than a discrepancy — a variance of a few hundred dollars in that window on an otherwise healthy account is normal lag, not an error worth chasing, and auditing it as if it were a finding wastes time on numbers that will settle themselves.

What to do when the audit finds a discrepancy that isn't in your favor

Run the audit in both directions, not just the direction that benefits you. In one account, a client asked us to dispute a fulfillment-fee measurement, and the transaction-level check found Amazon was actually under-charging on nine of the products in question — disputing the measurement would have triggered a re-measurement that could have corrected the fee upward instead of down. We advised against filing. A re-measurement request reopens the number in both directions, and an honest audit has to be willing to find that the discrepancy runs against you as readily as it finds one in your favor. Filing only the claims that help you, while ignoring the ones that don't, is the kind of asymmetric use of Amazon's dispute process that erodes trust with Seller Support over time, even if no individual claim is dishonest.

Making this a standing check, not a one-time find

A one-time audit catches what's wrong today. It does nothing about the packaging change your supplier makes next quarter, the return that goes missing next month, or the next removal shipment that comes up short. Full Circle has managed more than $500M in Amazon spend across 100+ brands, and running this transaction-level check on a weekly cadence, rather than a quarterly or annual one, is the single biggest driver of what actually gets recovered across the accounts we track — net of reversals, $803,457 across 53 accounts since 10 February 2026. Dr. Shield runs this audit continuously, priced on the call as a contingency against what's found, precisely because a one-time sweep only ever answers “how much was Amazon holding as of the day we checked” — and the honest answer to that question changes every week.