Amazon FBA Reimbursements Report Explained: Cash, Inventory and Coverage
Read an Amazon FBA Reimbursements report without double-counting cash and inventory, and organize payment evidence for a defensible reconciliation.
Separate cash compensation from inventory compensation, keep the reimbursement and case references, and match each record to the event it resolves. A cash amount of zero does not by itself prove that nothing was reimbursed.
Read the report as evidence of an outcome
Amazon's report definition lists approval date, reimbursement and case identifiers, product identifiers, currency, monetary amounts, cash and inventory quantities, and original-reimbursement fields. Keep those distinctions in your working copy. A row is not simply a dollar amount to subtract from every incident for the product.
The workflow below is our recommended way to organize that evidence. Its purpose is to answer two separate questions: what compensation is recorded, and which event does it cover? Treat a result as provisional when the second question is unresolved.
Separate compensation quantity from compensation value
Maintain distinct columns for units compensated in cash and units compensated in inventory. Track recorded money in its own currency. This prevents a zero cash amount from automatically becoming an unpaid case and prevents returned stock from appearing as recovered cash.
Illustrative example: a row records two cash-compensated units and one inventory-compensated unit. The cash amount is $16. For the worksheet, record three compensated units and $16 cash, then investigate which incident those units cover. Do not describe the inventory unit as an additional $8 cash payment.
| Item | Value | How to use it |
|---|---|---|
| Cash-compensated quantity | 2 units | Track quantity coverage |
| Inventory-compensated quantity | 1 unit | Track inventory resolution separately |
| Total compensated quantity | 3 units | Cross-check, do not add again |
| Recorded cash | USD 16 | Keep in cash results only |
Avoid summing the total quantity twice
If you keep both component quantities and a total, use the total as a cross-check. Adding cash quantity, inventory quantity and their total together would count the same compensation twice. A worksheet should have one documented calculation for compensated units.
Do the same check when a file includes multiple rows for a reimbursement. Decide the grain of your working table: one line per source row, one per product within a reimbursement, or one event record linked to several lines. Record that choice so a later import does not silently change it.
Check references before assigning coverage
Review reimbursement and case references alongside the product identifiers and timing. Product identity narrows the search, but it does not establish which of several incidents was compensated. Keep a candidate match separate from a verified event-to-payment link.
Suppose a fictional product has a two-unit incident and a separate three-unit incident. A two-unit reimbursement might resolve the first. If you subtract it from both incidents because the product matches, your worksheet will understate the unresolved quantity. Preserve one explicit allocation with the supporting evidence.
Review related records and coverage gaps
When a row points to an original reimbursement, investigate the relationship before treating it as an independent recovery. Your working record should retain both references and the explanation you verified in Seller Central. Do not guess whether a row increases, replaces or reverses an earlier result from its position in the file.
An empty search also needs context. Check the period, account and marketplace covered by the export, plus the date it was generated. No matching row in the supplied file means exactly that; it is not proof that no reimbursement exists anywhere in the account.
Record unresolved questions explicitly. Examples include a reimbursement whose incident is unclear, a file that ends before a later outcome, or a currency mismatch. Those belong in an investigation queue rather than in a confirmed unpaid total.
Report outcomes without overstating recovery
Use separate totals for verified cash, verified inventory resolution, events still awaiting matching and candidates requiring eligibility review. Keep currencies apart unless you document a deliberate conversion for internal reporting. Do not combine USD and EUR values into a single unlabeled number.
FluxPilot can use an optional reimbursements file alongside the ledger to help review apparent coverage. Inspect the matches, especially when a product has repeated incidents. Confirmed payment evidence, an estimated unresolved value and a possible claim are different states; preserving those states makes the result useful.
Frequently asked questions
Does zero cash mean Amazon did not resolve any units?
Check inventory compensation and the surrounding evidence before concluding that an event is unpaid.
Can I subtract all reimbursements for a product from one incident?
Only allocate compensation when you have enough evidence to link it to that incident. Repeated incidents require separate records.
Sources and further reading
Workflows and examples are from FluxPilot. Amazon policies change; verify the current policy for your marketplace before filing a claim.
Amazon report definitions: Inventory Ledger and Reimbursements