Amazon FBA Reimbursements: Claim Every Dollar (2026)

Amazon owes most FBA sellers money right now. Warehouses lose and damage inventory, customers get refunds for items they never send back, and fee calculations run on wrong dimensions, and while Amazon reimburses much of this automatically, audits of seller accounts routinely surface unclaimed money equal to 1% to 3% of annual FBA revenue. On $800,000 of FBA sales, that's $8,000 to $24,000, sitting behind reports most sellers never open.

The catch: the window to claim it has gotten short. Amazon cut its claim deadlines dramatically in late 2024, and changed how much it pays in 2025. Here's the current state of play: what's reimbursable, the deadlines, DIY vs paying a service, and (the part everyone skips) how to book the money so it doesn't wreck your margins twice.

What Amazon actually owes you for

• Inventory lost in the warehouse. Units that disappear from your inventory ledger without a sale, removal or disposal to explain them.
• Inventory damaged by Amazon. Warehouse-damaged units, including damage during Amazon's own handling and transfers between fulfillment centers.
• Customer refunds without returns. Amazon refunds the buyer instantly; the buyer has a return window to actually send the item back. When it never arrives, you're owed a reimbursement, and this category alone is often the biggest bucket.
• Returns mishandled. Items returned in unsellable condition but graded sellable (or vice versa), wrong items returned to your inventory, refunds issued for more than the order amount.
• Inbound shipment discrepancies. You ship 500 units, Amazon receives 488, and the 12 never get reconciled.
• Disposals and removals gone wrong. Inventory destroyed without permission, or lost in transit during a removal order.
• Fee overcharges. Fulfillment fees computed on wrong weights or dimensions, sometimes for months across thousands of units. Not a reimbursement in the inventory sense, but claimable money in the same workflow, and re-measurement requests fix it going forward.

The deadlines: everything got shorter

For years sellers could claim up to 18 months back, which made "do a big cleanup annually" a workable strategy. That era ended in October 2024. The windows now run roughly like this: claims for inventory lost or damaged in fulfillment centers must be filed within 60 days; customer-return claims sit in a window that opens after the return deadline passes and closes about 105 days after the refund; removal-order claims run from 15 to 75 days after shipment creation; inbound discrepancies keep a longer window with a required waiting period while Amazon finishes receiving. Check the current policy in Seller Central before relying on any of these numbers, because Amazon shortened them once with modest notice and can do it again.

The strategic consequence is bigger than the details: reimbursement recovery is now a monthly discipline, not an annual cleanup. Money not claimed inside the window isn't late, it's gone. A seller who reconciles quarterly forfeits every 60-day claim from the first two months of the quarter, permanently, which is exactly the kind of quiet leak our money leak checklist exists to catch.

What auto-reimbursement misses, and the 2025 payout change

Amazon does auto-reimburse many warehouse losses, and in 2025 it moved to paying claims based on your product's manufacturing cost rather than its sale price. Amazon estimates that cost itself unless you tell it otherwise, and its estimates skew low. You can supply your own figures through the manufacturing-cost settings in Seller Central, and you should: a seller whose true unit cost is $14 collecting auto-reimbursements at Amazon's $9 estimate donates $5 per lost unit indefinitely.

This is where reimbursements connect to landed cost. Your defensible number comes from purchase invoices, freight allocations, and the duty tracking covered in our tariff accounting guide. At 2026 duty rates, the gap between "factory invoice price" and true cost is wider than it's ever been, and Amazon isn't going to include your tariffs in its estimate voluntarily. Documented landed cost also means claim disputes end quickly: you attach the invoice trail, they pay.

Beyond low valuations, auto-reimbursement has coverage gaps: refund-no-return cases that resolve wrong, grading errors, inbound shrinkage below Amazon's attention threshold, fee mis-measurement. The gaps are exactly why the audit-and-claim workflow exists.

The manual claim workflow

The raw material is three reports in Seller Central: the Inventory Ledger (every movement of every unit), the Reimbursements report (what Amazon already paid), and the FBA customer returns report. The monthly pass looks like this:

1. Pull the inventory ledger and isolate unreconciled events: lost, damaged, and disposed units that lack a matching reimbursement or recovery.
2. Cross-reference refunds against returns: every refund older than the return window without a received return and without a reimbursement is a claim.
3. Compare received quantities to shipped quantities on inbound shipments past their reconciliation window.
4. File cases through Seller Central's fulfillment help flow, one issue type per case, with the ledger extract and (where relevant) cost documentation attached.
5. Log claim IDs and chase anything unresolved after two weeks. Persistence changes outcomes; first-response denials on legitimate claims are common and often reverse on appeal with the same evidence restated.

Budget two to three hours a month for a mid-six-figure account. It's dull work with a triple-digit hourly rate attached, which is a rare combination.

Two habits raise your win rate substantially. Keep an evidence pack per SKU: supplier invoice, freight allocation, and the manufacturing-cost figure you filed with Amazon, so any claim attaches proof in one step instead of a scavenger hunt. And write case notes like someone else will read them, because someone will: claims get transferred between Amazon associates, and a case that restates the facts cleanly (shipment ID, event date, ledger line, amount) survives the handoff, while "see previous message" dies in it. Sellers treat claim-writing as customer service; it's closer to small-claims litigation, and the tidy filer wins.

Reimbursement services vs DIY

An industry exists to do this for you: Getida, Seller Investigators, Refunds Manager, Carbon6 and a dozen others, all on contingency, typically 20% to 25% of recovered funds (a few advertise lower headline rates with narrower coverage). No recovery, no fee. They're competent at what they do, and for a seller with a big back catalog and zero internal process, the first sweep usually finds real money and the fee is fair value.

Two honest caveats. First, the services work from the same reports you have; there's no privileged access, so what you're buying is diligence and case-handling stamina, not secret data. Second, at 25% the arithmetic turns against you as your own process improves: a seller recovering $20,000 a year pays $5,000 for roughly 30 hours of work they could increasingly do in-house. Our usual advice: let a service run the historical sweep, then bring the monthly discipline inside, either DIY or bundled with your bookkeeping, since the person reconciling your settlements is already staring at the relevant reports. That's exactly how our Amazon bookkeeping service treats it: reimbursement review is part of the monthly close, not a separate industry.

How to book reimbursements (not as revenue)

Here's the accounting mistake that undoes the good work: reimbursements land inside your settlement deposits, and books that post deposits as sales quietly count reimbursements as revenue. They're not revenue. Nobody bought anything. A reimbursement is compensation for an inventory loss, and the clean booking runs through your shrinkage account:

• When units go missing or get destroyed, your inventory accounting records the loss: credit inventory, debit shrinkage (5030 in our chart of accounts).
• When the reimbursement arrives, it offsets that shrinkage: debit cash (via the settlement), credit shrinkage.
• The net of the two is your true unrecovered loss, which is a number worth watching: it's the scorecard for this whole process.

Booked as revenue instead, you inflate sales, overstate shrinkage, and hand yourself a top line that no longer ties to gross marketplace sales, which resurrects the 1099-K mismatch problem from a different direction. It also matters at exit: a quality of earnings analyst will strip reimbursements out of revenue in an afternoon, and finding them there makes every other line suspect. Reimbursements sitting correctly against shrinkage, with a documented monthly recovery process, reads as operational maturity. Same money, opposite signal.

One nuance: when Amazon reimburses at your cost, the credit fully offsets the inventory loss. It doesn't replace the profit you'd have earned selling the unit; that margin is simply gone, which is one more reason the manufacturing-cost figure you feed Amazon should be your full landed cost rather than a bare factory price.

What an audit actually finds: a worked example

Here's the shape of a first-time audit on a real-scale account: a seller doing $600,000 a year through FBA, three years in, never audited, decent operations. Twelve months back (where windows still allowed) plus the current claimable period turned up:

Category	Found
Refunds issued, item never returned	$4,100
Warehouse-lost units, never auto-reimbursed	$2,600
Inbound shipment shortfalls	$1,800
Fee overcharges from wrong dimensions	$1,450
Warehouse-damaged units, unresolved	$1,200
Total recovered	$11,150

That's 1.9% of annual revenue, right in the typical band. Through a 25% contingency service, $2,788 of it goes to the service; run in-house as part of the monthly close, the whole amount stays. Either beats the third option, which is what this seller had been doing: nothing, at a cost of about $900 a month in quiet forfeitures. The dimension-fee find is worth a special mention because it compounds: a wrong measurement doesn't just owe you back-fees, it overcharges every future unit until someone requests a re-measure. Fixing it was worth more going forward than the claim itself.

FBA reimbursement FAQ

Are reimbursements taxable income? They net against the inventory losses they compensate, so booked correctly there's no windfall to tax: the loss deduction shrinks by the recovery. Booked as revenue, you'll overpay tax on money that was never profit, one more argument for the shrinkage-offset treatment above.

Do reimbursements show up on my 1099-K? No. The 1099-K reports gross buyer payments; reimbursements arrive inside settlements but aren't sales. They're one of the standard reconciling items between your settlement activity and the 1099-K figure, which is why the reconciliation needs line-level care.

Can I still claim losses from last year? Almost certainly not; the old 18-month lookback is gone and expired windows don't reopen. The rational response is to grieve briefly and set up the monthly cycle so it never happens again.

Is it worth filing a $14 claim? Individually, marginal. As a policy, yes: the workflow finds claims in batches, small ones ride along with big ones, and Amazon's error rate doesn't confine itself to cheap SKUs. Sellers who set a "worth my time" floor tend to discover the floor was hiding a pattern.

Will filing lots of claims hurt my account? Legitimate, well-documented claims are a normal part of the FBA relationship; Amazon's own policies invite them. What draws trouble is sloppy or duplicative claims, which is another reason evidence-first beats volume-first.

The monthly reconciliation workflow, end to end

Pulling it together, the routine we run for clients looks like: reconcile settlements to gross sales, fees and refunds (the fix for the nine classic Amazon bookkeeping problems); tie inventory ledger movements to the books' inventory balance; flag and file every claimable event inside its window; post reimbursements received against shrinkage; and report unrecovered shrinkage as its own line so it can't hide. Sellers who run this loop keep the leak near zero and their COGS honest per the COGS formula. Sellers who don't fund Amazon's error rate out of margin, at a landed cost that tariffs just made 20% more expensive.

If you've never audited your account, the historical sweep plus a monthly process is a solved problem: it's built into our monthly bookkeeping plans, and the free Books Teardown will tell you whether reimbursements are being booked as revenue right now (they usually are); request one here. Amazon runs the best logistics network on earth and still misplaces a measurable slice of everything it touches; the sellers who get paid for that are simply the ones who check. Amazon's own error rate is the one expense line you can actually send back.