Seller guide
How do I check whether Amazon already reimbursed an FBA inventory event?
Join a seller-owned FBA event ledger with seller-supplied reimbursement and settlement records, preserve ambiguous matches, and separate approved, reversed, inventory-credit, cash, and unresolved states before any case decision.
Create one stable seller reference for the inventory event
Record event type, observed anchor date, SKU or FNSKU, ASIN where available, quantity, disposition, fulfillment center, source reference, and current case status. Keep marketplace order, shipment, removal, case, and reimbursement identifiers only in the seller's protected working record; a public or shared analysis can use a redacted reference. One stable reference prevents the same units from being rediscovered as a new issue in each report.
Search the Reimbursements report with more than one key
A reimbursement row can expose reimbursement ID, approval date, case or order reference, reason, SKU, FNSKU, ASIN, condition, amount, cash quantity, inventory quantity, and an original reimbursement link. Compare the strongest available identifiers plus date, reason, and quantity. Do not declare a match from SKU alone: one SKU can have many independent events, and a nearby approval date can belong to different units.
Distinguish the form and current state of the reimbursement
Separate cash quantity from inventory quantity and preserve amount per unit, total, currency, and condition. Follow original-reimbursement identifiers when a later row reverses or adjusts an earlier event. Label exact matches, plausible matches, conflicting matches, and no located match instead of forcing a yes-or-no answer. An approved row can still need settlement reconciliation, while an inventory credit is not a bank deposit.
Reconcile cash only when it appears in the settlement scope
For a cash reimbursement, locate the seller-supplied settlement component and verify its currency, sign, amount, payout scope, and date. Keep account-level adjustments and reserves visible. A matching bank deposit total does not prove this individual event was paid, and a reimbursement row does not guarantee that the amount has reached a closed payout. Treat inventory and cash ledgers as connected but separate evidence.
Stop duplicate work and escalate ambiguity for review
Mark a resolved event only after the seller-owned record identifies the outcome and the relevant report or settlement evidence. Keep ambiguous quantities, reversals, conflicting identifiers, and missing settlement links open for human review. Before any submission, verify the current Seller Central status and prior cases. This workflow does not prove eligibility, authenticate evidence, file a claim, predict a decision, or establish that Amazon owes an amount.
Tools that help with this
- FBA Reimbursement Deadline + Evidence Tracker ($1.00) — Flag prior reimbursement status and missing evidence in a dated event ledger
- Marketplace Payout Reconciliation Analyzer ($1.00) — Tie seller-normalized reimbursement components to a supplied settlement and deposit
- FBA Stranded Inventory Recovery Queue ($0.50) — Keep stranded-inventory recovery work separate from completed reimbursement outcomes
Every paid output is a draft for your review before you publish, appeal, or activate anything. Friday does not access your seller account.
More seller guides
- How do I organize FBA case evidence without creating duplicate claims?
- How do I track FBA reimbursement deadlines and missing evidence?
- Which FBA report should I use for lost, damaged, returned, or removed inventory?
- How do I reconcile a marketplace payout to orders and the bank deposit?
- How do I recover FBA stranded inventory before auto-removal?