Glossary

What is FBA reimbursement?

Money Amazon owes you when it loses, damages, or mishandles your FBA inventory.

An FBA reimbursement is money Amazon owes you when it loses, damages, destroys, or otherwise mishandles your inventory inside its fulfillment network, or when it makes a fee or refund error that costs you. When a customer return never makes it back to a sellable shelf, when a unit goes missing during a warehouse transfer, or when Amazon reimburses a customer but never collects the item, that's value that left your business through no fault of your own. An Amazon FBA reimbursement is the mechanism that makes you whole, but only if the discrepancy is found, documented, and claimed inside Amazon's filing windows.

For most sellers, reimbursements are the single most overlooked source of recoverable cash in their P&L. Amazon's systems generate some reimbursements automatically, but a meaningful share of legitimate claims never surface unless someone reconciles inventory ledgers, removal reports, and returns against actual settlements. That reconciliation gap is exactly where BeanHawk focuses, surfacing the discrepancies Amazon owes you on, so the recovered money flows back into clean, properly booked accounts instead of quietly disappearing.

Two things make reimbursements confusing. The money arrives inside a settlement, mixed in with sales, refunds, and fees. And the event that triggered it happened weeks earlier, in a warehouse you'll never see.

What counts as an FBA reimbursement (the categories Amazon owes on)

Reimbursements fall into a handful of recurring categories, and knowing them is the difference between catching money and leaving it on the table. Each category maps to a different Amazon report: inventory adjustments, reimbursements, removal orders, returns. That's why reconciliation is the core skill, not luck.

The dollar value Amazon assigns to a reimbursed unit is based on its own estimate of your item's value, and that estimate doesn't always match your true landed cost. That gap matters for your books and is worth reviewing case by case rather than assuming the credit is correct.

  • Lost inventory: units that disappear inside the fulfillment network or during inbound check-in or warehouse transfers
  • Damaged inventory: units Amazon or its carrier damages while in its custody (distinct from customer-damaged returns)
  • Customer return discrepancies: a refund was issued but the item never came back, or came back unsellable and wasn't credited
  • Disposal and removal errors: units disposed of or removed without your instruction, or removal orders that never arrived
  • Fee and weight/dimension errors: you were overcharged on fulfillment fees due to incorrect measured dimensions or weight
  • Inbound shipment shortages: Amazon receives fewer units than the carrier delivered and the shipment closes short
  • Chargeback and refund errors: a customer was refunded twice, or refunded outside the return window without the item coming back

How a reimbursement actually gets created inside Amazon

Every unit you send to Amazon lives in a ledger. Each time something happens to it (receipt, sale, return, transfer, damage, disposal) Amazon writes an event with a reason code and a quantity delta. Those events roll up into the inventory adjustments and ledger reports you can pull from Seller Central. A reimbursement is what happens when the system decides one of those negative adjustments was Amazon's fault rather than yours.

Some of that decision-making is automated. If a fulfillment center writes off a unit under a warehouse-damage code, Amazon frequently issues a credit without you asking. Other cases sit in a holding pattern by design. A lost unit is often marked lost, then researched, and if it turns up within the research period it goes back on the shelf instead of being paid out. Reasonable, but it means a unit that's never found and never revisited can sit unresolved indefinitely.

The manual path is a claim. You identify a unit-level discrepancy, gather evidence, and open a case referencing specific IDs. Approved claims show up as reimbursement lines in a later settlement, usually with a case ID you can trace back. Credits can also be reversed later if a lost unit turns up.

How to find reimbursements Amazon won't hand you automatically

Amazon does auto-reimburse some discrepancies, but it does not catch everything, and it will not chase a claim on your behalf. The recoverable money typically lives in the gaps between three things: what your inventory ledger says you sent in, what Amazon's reports say happened to those units, and what actually hit your settlements. Reconciling those sources (inventory adjustments, the reimbursements report, removal order detail, and customer returns) is how legitimate claims get identified.

The practical method is a three-way match at the unit level. Start with every negative adjustment in a period. Filter out the ones that are legitimately yours: customer-damaged returns you accepted, disposals you ordered. For what's left, ask whether a matching reimbursement line exists in the same or a later period. A negative adjustment with no offsetting credit is a candidate. Then check its age against the current filing window before you spend time on it.

This is why FBA reimbursement services and software exist as a category. Whether you reconcile in-house or use a tool, the workflow is the same. Pull the reports, match unit-level events, flag unresolved discrepancies, file a clear case, and book the recovery correctly when it lands.

Volume changes the calculus. A few hundred units a month is spreadsheet territory. Past a few thousand it becomes a data problem rather than an attention problem, and that's where amazon reimbursement software starts to pay for itself.

A worked example: one lost unit, start to finish

Say you sell a kitchen gadget that costs you $9 landed and retails for $32. In March you ship 400 units into FBA. Amazon's receive report closes the shipment at 396 received. Four units are unaccounted for, and no reason code explains where they went.

Nothing happens for a while, because a four-unit shortage is invisible in a business selling hundreds of units a month. In May you pull the inventory ledger for the SKU. It shows a receipt of 396 against a shipped quantity of 400 and no corresponding reimbursement line. That's a documented discrepancy worth roughly $128 at retail, or $36 at your cost.

You open a case with the shipment ID, the FNSKU, carrier tracking showing 400 units delivered, and the packing list. Amazon approves a credit at its own estimated item value, landing at $110, which shows up in a June settlement.

Now the accounting. The $110 isn't revenue. Four units left your balance sheet and never produced a sale, so $36 of inventory comes off at cost and the remaining $74 is compensation above your cost basis. If the $110 lands in sales income and the inventory is never written down, your gross margin looks better than it is and your inventory valuation is overstated. Multiply that by a year of small discrepancies and your books drift meaningfully from reality.

Those numbers are made up to show the shape of the transaction. Amazon's valuation logic is its own, so treat every credit as something to check rather than something to accept.

Booking reimbursements correctly in your accounting

A reimbursement is not sales revenue, and treating it as such quietly distorts your margins. It is compensation for inventory or fees lost inside Amazon's network, so it should be recorded in a way that reflects what it actually offsets, typically as a contra against cost of goods sold or inventory shrinkage, or as other income, depending on how your books are structured and your accountant's guidance.

Getting this right matters for two reasons. First, lumping reimbursements into top-line sales inflates revenue and understates your true cost of goods sold, which throws off gross margin. Second, a reimbursed unit's value may differ from your real landed cost, so if you simply zero out the inventory at Amazon's estimate, your inventory valuation drifts from reality. Mapping reimbursements to a dedicated account in your chart of accounts keeps the picture honest and makes month-end reconciliation far less painful.

Fee reimbursements deserve their own treatment. If Amazon refunds an overcharged fulfillment fee because a unit was measured wrong, that credit offsets a fee expense, not inventory. Booking it against the same expense account the fee hit keeps your fulfillment cost per unit accurate, which is the number you use when you price a product.

This is a big part of what good amazon accounting software is for. The settlement file already separates reimbursement line types, so a tool that reads the settlement can map each type to the right account and post a summarized journal that ties to the deposit. By hand it means opening the settlement, categorizing lines, and typing a journal entry every two weeks.

For sellers running amazon fba bookkeeping in QuickBooks or Xero, the practical setup is three dedicated accounts: inventory reimbursements, fee reimbursements, and reversals. That's enough granularity to answer the questions that matter (how much did Amazon owe us, how much came back, how much got clawed back) without turning your chart of accounts into a swamp.

Time limits and documentation that make or break a claim

Amazon enforces filing windows on reimbursement claims, and those windows have changed over time, so verify the current limits against Amazon's published policy rather than relying on a number you read once. The takeaway is the same regardless of the exact deadline: discrepancies left unreviewed for too long become unrecoverable, which is why ongoing reconciliation beats an annual scramble.

Strong claims are documented claims. When you file, reference the specific unit-level events: shipment IDs, removal order IDs, FNSKUs, dates, and the relevant report rows. Clean records also protect you if Amazon later reverses an auto-reimbursement or asks you to substantiate the value of the affected inventory.

Keep the evidence in one place per claim: carrier proof of delivery, the packing list, the ledger export showing the adjustment, and the case correspondence. A reopened case with the original evidence attached goes much further than a fresh complaint written from memory. And be disciplined about volume, because dozens of speculative cases with thin evidence earn slower responses and blanket denials.

Common mistakes that cost sellers real money

Most reimbursement losses aren't dramatic. They're small process failures repeated for a year.

The subtlest is the last one. A recovery that never appears as a distinct line in your books is indistinguishable from a good sales month, so you can't tell whether your process is working or whether Amazon's error rate on your account is getting worse.

  • Treating reimbursements as free money instead of compensation for a real loss, which hides the underlying inventory shrinkage
  • Booking credits to sales revenue, inflating both revenue and gross margin
  • Never writing down the inventory the reimbursement was paid for, leaving phantom units on the balance sheet
  • Ignoring reversals, so recovered totals only ever go up
  • Reconciling once a year, by which point older discrepancies are past the filing window
  • Accepting Amazon's valuation without checking it against landed cost on higher-value SKUs
  • Filing vague cases with no shipment IDs attached, then treating the denial as final
  • Using a recovery service without exporting the underlying claim data

DIY, a recovery service, or software

There are three honest options, and the right one depends on your volume.

Doing it yourself costs nothing but time, and at low volume that's genuinely the right answer. Everything you need comes from Amazon's own reports. Budget an hour or two a month and keep a simple tracker of open cases.

An fba reimbursement service takes a percentage of what it recovers, usually filing on your behalf, so you pay nothing if nothing is found. The trade-offs are real though: you're handing account access to a third party, the percentage compounds over years, and many services optimize for claim volume rather than the health of your account.

Software sits in the middle. It reconciles continuously, flags discrepancies, and leaves the filing decision with you, usually on a flat subscription rather than a cut of recoveries. The version worth paying for connects the recovery to the books.

If you're evaluating amazon seller tools in this category, four questions separate the good from the noisy. Does it reconcile at the unit level or just scrape the reimbursements report? Does it track case status and reversals? Does it push a balanced journal into your ledger, or stop at a CSV? And can you export everything, so switching tools doesn't cost you your claim history?

Frequently asked questions

What is an Amazon FBA reimbursement?
It is money Amazon credits back to you when it loses, damages, or mishandles your FBA inventory, or when it makes a fee or refund error in its own systems. It compensates you for value lost inside the fulfillment network, and it is not a sale. You generally have to identify and often file these claims yourself, because Amazon does not catch every discrepancy automatically.
Does Amazon reimburse sellers automatically?
Amazon auto-reimburses some discrepancies, but not all, and it will not file a claim for the ones it misses. Many legitimate reimbursements only surface when you reconcile your inventory ledger, removal reports, and returns against actual settlements. That gap is where most uncollected money sits.
Are FBA reimbursements taxable income?
They offset a real loss of inventory or an overcharged fee, so they flow into your taxable picture. How you record them (contra to COGS, inventory adjustment, or other income) affects the presentation, not whether they count. Map them to a dedicated account and confirm the treatment with your accountant rather than burying them in sales revenue.
Do I need an FBA reimbursement service or can I do it myself?
You can do it yourself, since all the data comes from Amazon's own reports. Services and software exist because the manual process is time-consuming, the data is spread across reports that don't line up cleanly, and there are filing deadlines. Below a few hundred units a month, a spreadsheet and a recurring calendar reminder is a perfectly defensible choice.
How is a reimbursement different from a customer refund?
A customer refund is money you return to a buyer. A reimbursement is money Amazon pays you to cover inventory or fees lost inside its network, including cases where Amazon refunded a customer but never recovered the item. They sit on opposite sides of your ledger and should never be netted together casually.
How do I record a reimbursement in QuickBooks Online?
Create dedicated accounts rather than dropping the credit into sales. Use one account for inventory-related reimbursements (mapped as a contra to COGS or an inventory adjustment) and a separate one for fee reimbursements posted against the original fee expense. Then write down the lost inventory at landed cost. If you're using quickbooks for amazon sellers with a settlement connector, check that it maps reimbursement line types separately instead of collapsing them into one bucket, because that collapse is where most misreporting starts. One naming collision to watch: the expense reimbursement workflow QuickBooks Online documents is about paying an employee back for out-of-pocket spend, which is a different transaction with different accounts. An Amazon credit is not that, so don't follow those instructions by analogy.
What should amazon reimbursement software actually do for me?
At minimum it should reconcile inventory events against settlements at the unit level, surface discrepancies with evidence attached, track case status including reversals, and let you export the raw data. Stronger tools also post the recovery to your ledger correctly, which is the difference between finding money and having clean books. BeanHawk does both. Compare it against dedicated recovery services and against amazon accounting software that only handles settlement-to-journal, since the right answer depends on whether recovery or bookkeeping is your bigger pain.
Can a reimbursement be taken back after it's paid?
Yes. If Amazon reimburses you for a lost unit and later locates it, the credit is typically reversed and the unit returns to your available inventory. Fair enough, but it has to be recorded, otherwise your cumulative recovery figures overstate what you kept. Track reversals in their own account so you can see gross and net recovered separately.

Related terms

Go deeper

See what Amazon owes you — free

Connect your seller account and get a free reimbursement audit. No credit card, keep 100% of what you recover.