Refunded orders, returned units and reimbursements measure different events. A refund moves money to the customer, a physical return moves inventory, and a reimbursement compensates the seller for an eligible issue. They can involve different quantities, dates and amounts, so equal totals are not the expected result. Reconcile the events by order, product and underlying issue rather than forcing three monthly numbers to agree.
For an FBA seller, the goal is to explain each refunded item’s inventory and financial outcome: received and sellable, received but unsellable, legitimately not expected back, still unresolved, or linked to a reimbursement. This guide builds an operational reconciliation with hypothetical records. It is not a claim-eligibility calculator, a reimbursement-service comparison or a substitute for your accounting treatment.
What does each number actually count?
A refunded-order count is the number of distinct orders with refunds in the selected scope. It is not necessarily the number of refunded units or refund transactions. One order can contain several products, one product can have multiple units, and the customer can receive a partial refund or more than one adjustment.
Returned units count physical items recorded as coming back. They may arrive after the refund and be classified as sellable or unsellable. A return authorization or a carrier scan is also different from the fulfillment center’s receipt and disposition record.
Reimbursements have their own quantities and monetary amounts. A payment may relate to a customer return, but it can instead relate to a warehouse or inbound-inventory issue without a customer refund. A reimbursement record can account for cash or inventory. Counting every reimbursement row as one returned unit mixes incompatible measures.
Start every reconciliation by naming the measure, date basis, marketplace, fulfillment method and currency. “October refunds” is incomplete unless you know whether October describes the sale, refund posting or another event. The same filter label across two reports does not establish the same population.
Which records should you put beside each other?
Keep the original exports, then build a working ledger that connects the records. Use order and item details for what was sold; refund and payment transactions for the financial adjustment; customer-return records for receipt and disposition; and reimbursement records for recovery. Use inventory movements to investigate a stock discrepancy or an item later found.
Amazon’s FBA report specification lists order ID, SKU, FNSKU, quantity, return date, reason and detailed disposition for returns. Its reimbursement fields include reimbursement ID, case ID, approval date, cash and inventory quantities, and original reimbursement ID. These are useful matching fields, not a promise that every source has a unique one-to-one match.
| Record | What to retain in the working ledger |
|---|---|
| Original sale | Order ID, item identifier, SKU, units, sale date, marketplace |
| Refund event | Source transaction ID, order and item reference, date, amount, currency |
| Physical return | Order and product reference, quantity, received date, disposition |
| Reimbursement | Reimbursement and case IDs, reason, linked order if present, cash and inventory quantities |
| Adjustment or reversal | Original event reference, posting date, amount or quantity, supporting explanation |
Add your own review columns: current status, evidence location, next action, owner and date last checked. These columns are an analyst’s workflow, not fields that every Amazon export supplies. Do not copy customer personal details into a working table when order and item identifiers are sufficient.
The report scope matters. Amazon’s seller-fulfilled Returns Reports documentation explicitly excludes FBA returns and returnless refunds. Use the FBA-specific source for FBA inventory, and do not treat an absent row in a report that excludes the event as evidence of missing money.
How do you match records without creating duplicates?
Start with the strongest shared identifiers: marketplace and seller account, order ID, then order-item identifier when present, or SKU/FNSKU with quantity and transaction context. ASIN alone is too broad because many orders can contain the same ASIN. Order ID alone is too broad for a multi-product order.
Keep raw refund events separate from the per-order summary. If two refund events belong to one order, retain both amounts but count the distinct order once. If two units are refunded in one transaction, the transaction count is one and the affected quantity is two. A partial monetary refund does not automatically mean a whole unit was physically returned.
Aggregate each source to the intended level before joining. Joining two refund rows directly to two return rows for the same order can create four combined rows and double the totals. Check record counts and monetary totals before and after every join. If the totals change without a documented reason, fix the matching rather than adjusting the answer manually.
When identifiers are missing or quantities conflict, put the record in an exception queue. Do not silently assign a same-value credit to the nearest refund. Match a reversal using its original reference where available, and retain the evidence for any manual match. A plausible link is still a hypothesis until supported.
What does a reconciled example look like?
Consider five hypothetical FBA orders reviewed at an October 31 cutoff. Order B contains two units; every other order contains one. Each order receives one full refund during October. All figures are illustrative USD amounts, and the reimbursement on E is assumed to be a valid posted credit for that specific issue. The example does not imply a universal processing or eligibility timetable.
| Order | Units refunded | Customer refund | Units received | Outcome at cutoff | Cash recovery |
|---|---|---|---|---|---|
| A | 1 | $40 | 1 | Sellable return | $0 |
| B | 2 | $60 | 2 | One sellable and one unsellable | $0 |
| C | 1 | $25 | 0 | Documented returnless refund | $0 |
| D | 1 | $35 | 0 | Return unresolved | $0 |
| E | 1 | $50 | 0 | Linked reimbursement posted | $32 |
| Total | 6 | $210 | 3 | Five orders reviewed | $32 |
The totals are five refunded orders, six refunded units, three received units and $32 of reimbursement cash. They are different because the ledger explains different events. Refunded units total 1 + 2 + 1 + 1 + 1 = 6. Physical receipts total 1 + 2 = 3. Customer refunds total $40 + $60 + $25 + $35 + $50 = $210.
At this cutoff, the six affected units are accounted for as three physically received, one intentionally not expected back, one unresolved and one not received but linked to the posted reimbursement. This is a classification for these records, not a universal formula. Other cases may involve replacements, partial quantities or a reimbursement for a unit already received in an eligible condition.
The scoped refund-and-reimbursement cash movement is −$210 + $32 = −$178. That is not the seller’s order profit or bank payout. The calculation excludes original sales receipts, Amazon fee adjustments, taxes, inventory costs and other transactions. Calling it “net return loss” would overstate what the table establishes.
Order D needs follow-up because its outcome is unresolved. It is not automatically a valid claim. Order C has no physical return by design. Order B’s unsellable unit needs an inventory-value and cause review, but unsellable status alone does not prove Amazon owes a reimbursement.
How should later returns and reimbursement reversals be handled?
Continue the event trail without rewriting the earlier cutoff. Suppose E’s unit is received on November 6 and a linked $32 cash reversal posts on November 7. This is a hypothetical continuation, not a prediction that Amazon will make those exact adjustments in every similar case.
| E event | Date | Cash change | Physical return quantity |
|---|---|---|---|
| Customer refund | October | −$50 | 0 |
| Reimbursement posted | October 28 | +$32 | 0 |
| Unit received sellable | November 6 | $0 | 1 |
| Reimbursement reversed | November 7 | −$32 | 0 |
As of November 7, E’s retained reimbursement cash is $32 − $32 = $0. Total physical receipts across the five orders are now four units. The original five orders still had refunds, and the original customer refund total remains $210. A later inventory receipt does not undo the fact that the customer received money back.
Amazon’s inventory reimbursement policy allows reimbursement reversals when a payment was made in error or reimbursed inventory is later found and returned. Investigate the stated reason and stock movement; a reversal should not be explained away solely because an equal credit appeared earlier.
If E’s recovered unit carries an appropriate inventory value of $18 in your records, that is a stock value to assess under your accounting method. It is not another $50 sale, and it is not $32 of cash that can still be counted after the reversal. Keep money, physical quantity and inventory valuation in separate columns.
Why does returned to inventory not always mean available to sell?
Read the disposition as well as the status. In an Amazon moderator’s explanation of return-report status, a unit returned to inventory can be sellable or unsellable. A received item should therefore not be treated as recovered full-value inventory just because the status says it is back.
For an unsellable unit, establish what happened next: inspection, removal, disposal, a permitted recovery route or an eligible reimbursement. Record the actual costs and supported recovery value. Do not assume the condition code alone establishes fault, and do not count a unit as both disposed of and still held for resale.
This distinction also prevents a common COGS error. If inventory cost remains charged because the unit was lost or unusable, adding another full write-off can duplicate the loss. Conversely, reversing all COGS merely because a refund exists can create inventory value for an item never recovered. Give your accountant the event evidence instead of forcing a universal journal entry onto different situations.
Which mismatches deserve investigation first?
Separate explainable timing from a substantive discrepancy. An open return within the relevant process can remain in an awaiting-outcome group. A returnless resolution belongs in a no-return-expected group. A payment found in a later period should be linked back to the issue, while retaining its actual posting date.
Prioritize exceptions by money at risk, applicable deadline and evidence needed. Examples include an eligible issue with no recorded resolution, a reimbursement reversal with no explained inventory outcome, quantities that exceed the original affected units, and the same credit attached to more than one loss. Keep pending, rejected, partially resolved and fully resolved cases distinct.
Check current marketplace and issue-specific rules before submitting a claim. The date of a refund, warehouse event, removal or reimbursement can matter differently. A management reporting cutoff does not extend an Amazon deadline, and a software flag does not establish eligibility. Preserve documents while investigating instead of waiting until the end of a long reporting period to gather them.
Where can sellerboard help with this workflow?
Use two sellerboard views for two different jobs. The Money Back Returns page compares customer refunds, recorded returns and reimbursements to flag potentially reimbursable FBA cases. The Refunds export under Reports groups refunded orders by product, with identifiers, order counts and refund amounts. The first helps build an exception queue; the second supplies product-level context, not a unit-by-unit reconciliation.
First, download the relevant files and record each report’s scope and cutoff. In Profit → Reports, choose Refunds, set the date range and export Excel or CSV. In Money Back → Returns, download the case report with its transaction IDs and supporting data. Keep raw exports separate from your working ledger. Reports downloads require a paid subscription.
Next, match each flagged case to the order, Amazon return records and reimbursement history. For order D in the example, use that evidence to decide whether the missing unit remains unresolved or has a documented outcome. Review manually issued refunds, non-returnable products and cases already resolved outside sellerboard before including them in a claim; an absent return alone does not establish eligibility.
Then keep outcomes distinct in the ledger. C’s documented returnless refund explains a missing physical unit. E’s $32 credit, later receipt and $32 reversal form a linked sequence, even though they cross reporting cutoffs. Treat any estimated reimbursement shown in sellerboard as an investigation aid, not booked recovery or guaranteed cash.
Finally, check current Amazon eligibility and supporting evidence before manually submitting a valid case to Seller Support. sellerboard does not submit these cases automatically. Partial refunds, reversal links and inventory valuation still need the event-level checks described above.
Which mistakes make the figures look wrong?
- Expecting order counts, unit counts, report rows and dollar amounts to match.
- Comparing sale-date figures with refund-date or receipt-date figures without a bridge.
- Joining several source rows at order level and multiplying their amounts.
- Assuming an absent physical return means reimbursement is owed.
- Treating unsellable inventory as proof that Amazon caused the loss.
- Counting an approved or estimated amount as posted cash, or ignoring a later reversal.
- Counting returned inventory as new revenue or adding the same inventory cost twice.
- Treating the net settlement deposit as a complete explanation of all return events.
What else should you know about refund reconciliation?
Can there be a refund without a return?
Yes. A documented returnless resolution is one example, and the physical return may also still be pending. Amazon describes refunds where eligible buyers keep the item in its FBA Returnless Resolutions guidance. Missing receipt data alone does not identify which situation applies.
Can returned units exceed refunded orders?
Yes. One refunded order can contain two or more returned units. Returns in a calendar period can also relate to orders refunded in an earlier period. Inspect quantities and event dates before assuming duplication.
Should reimbursement equal the refund amount?
Do not assume so. Confirm the event type, quantity, valuation and applicable Amazon policy. Compensation for an inventory issue is not automatically a reversal of everything charged on the customer’s order.
Does a reimbursement in the report mean the bank received that amount?
No. Distinguish approval, account posting, settlement and bank deposit. Reconcile account transactions into settlements, then match the net settlement payments to the bank. Fees and other adjustments affect the deposited amount.
When is an exception finished?
When its financial and inventory outcomes are supported and the record explains them, or when a documented decision closes further action. Keep later linked adjustments traceable even after closing the initial investigation.
A useful reconciliation explains why the numbers differ and leaves a small, evidence-backed list of exceptions. The objective is not identical totals; it is one coherent history of the money, the units and the resolution for each issue. sellerboard’s refund exports and Money Back Returns view can help surface records and exceptions for that review.
