How to Match FBA Reimbursements to Inventory Ledger Events
Match Amazon FBA reimbursements to individual inventory events using identifiers, references, quantities and an explicit allocation record.
Match at the event level. Use available references first, then compare product identifiers, category, quantity and chronology. Record how much of each reimbursement is allocated to each incident, and leave ambiguous links for manual review.
Why matching by product alone breaks down
A product can appear in several unrelated incidents. If your spreadsheet joins everything on a product identifier and subtracts the same reimbursement from every matching row, it can close cases that were never resolved. The opposite error is also possible: a real reimbursement is left unmatched because the working file changed an identifier.
The method below is a review framework, not an Amazon allocation rule. Its central requirement is traceability. Another person should be able to follow a proposed match from the source incident through the supporting reimbursement record and understand how the quantity was assigned.
1. Preserve an event key and a reimbursement key
Keep the original source references wherever available. Add your own stable review ID to each incident so it survives sorting and new exports. For reimbursement records, preserve the source identifier and the individual line information rather than replacing it with a product-level monthly total.
Where a source reference is missing, mark that limitation. A constructed key using account, marketplace, product, date, category and quantity can help organize a review, but it may not be unique. Two genuine events can share those attributes. Do not automatically discard one without checking.
2. Compare the strongest evidence before weaker clues
Start with an explicit relationship you can verify, such as a source reference or case history. Then check whether the product, event category, quantity and timing are consistent. A matching product name is weaker evidence than a matching inventory identifier, and neither establishes the event relationship alone.
Record confidence in ordinary language: verified link, plausible candidate or unresolved. Use that confidence to choose the next action. A plausible match should prompt verification, not silently change a case to paid.
| Evidence | What it contributes | Remaining check |
|---|---|---|
| Verified source or case relationship | Connects outcome to incident | Quantity and any later changes |
| Consistent inventory identifier | Confirms product scope | Which incident is covered |
| Compatible date, category and units | Supports a candidate link | Explicit relationship |
| Similar title or amount alone | A weak search clue | Identity and event evidence |
3. Work through a repeated-product example
All figures here are fictional. Event A affects three units of FNSKU DEMO-001 on September 4. Event B affects two units of the same FNSKU on September 19. A later reimbursement covers two units. Verified case evidence links that reimbursement to Event B.
Allocate two units to B and zero to A. B can be marked resolved by that evidence; A still needs investigation. Subtracting the two units independently from both rows would leave one unit open on A while also closing B, which would invent coverage for two units.
If the case evidence is missing, retain the reimbursement as unallocated or a candidate match. Do not allocate it to the oldest event simply because that produces a tidy table. An unresolved relationship is a data task that you can act on.
4. Keep allocation totals within the available evidence
Create a small allocation register: review event ID, reimbursement line ID, allocated units, allocated cash when relevant, evidence and reviewer. A reimbursement assigned across multiple events needs enough evidence to support that split. Its total allocation must not exceed the documented compensation.
Recheck the register when you add a newer export or discover related records. Preserve the reason for a reassignment. A changed match can alter both the outstanding quantity and the estimated value, so a one-line explanation is more useful than silently overwriting a status.
- Do not allocate the same compensation twice.
- Keep cash and inventory resolution separate.
- Keep marketplaces and currencies explicit.
- Review later related records before treating a match as final.
5. Turn ambiguity into a next action
An unmatched reimbursement can indicate missing event data. An unmatched incident can indicate missing payment history. A third group has enough data but an unclear relationship. Give each group a specific follow-up: regenerate a report, inspect case history or ask for clarification with the relevant references.
FluxPilot's report workflow helps bring inventory candidates, reimbursement history and costs into one review. Treat suggested coverage as evidence to inspect, particularly for repeated products and partial resolutions. The useful outcome is an auditable explanation for each status.
Keep the match review separate from claim eligibility. Even a genuinely unresolved event still requires the applicable policy, evidence and timing checks before you decide to submit a case.
Frequently asked questions
Is a matching FNSKU enough to close an event?
It narrows the product scope. Verify which incident the reimbursement covers, especially when the same product has multiple events.
What should I do with ambiguous matches?
Keep them provisional, state the missing evidence and assign a next review action. Avoid presenting them as confirmed compensation.
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 FBA inventory reimbursement policy (check your marketplace)