Free Amazon FBA Reconciliation Template: Track Events, Evidence and Next Actions
Download a free CSV worksheet for manual FBA event reconciliation, with fictional examples, quantity formulas, cost checks and a monthly review routine.
Use one record per review event, subtract only distinct verified resolutions, keep unknown costs blank and assign a next action. Download the CSV below for manual review notes; it is not an Amazon report or an eligibility calculator.
Download the blank worksheet and worked example
This original FluxPilot worksheet is designed for a manual review register. It keeps the incident, quantity resolutions, estimate, reimbursement reference and next action on one row. Open the CSV in your spreadsheet software using an import preview, and preserve identifiers as text.
The blank file contains headers only. The separate example file contains fictional events, product identifiers and amounts. Use the example to understand the structure, then replace it with verified evidence from your own account. Neither file is an Amazon-issued report or a ready-made claim.
Use the real Inventory Ledger export for FluxPilot's report analysis. This worksheet is a companion for your notes and follow-up; it does not replace the original ledger, reimbursement history or cost evidence.
Use one row per incident, with stable references
Assign your own review ID and retain the source event reference when supplied. Add the source filename, event date, marketplace and inventory identifiers. A stable review ID lets you revisit the same incident after a new export or support response.
Do not create a new row merely because a candidate appears in the next month's overlapping export. Compare the source relationship first and add the new evidence to the existing record when it is the same incident. Keep account data separate if you review several seller accounts.
| Group | Fields | Purpose |
|---|---|---|
| Identity | Review ID, source file, event reference, product IDs | Trace the incident |
| Quantity | Affected, found, cash-compensated, inventory-compensated | Review distinct resolutions |
| Value | Unit cost, currency, unresolved estimate, recorded cash | Separate estimates from outcomes |
| Evidence | Reimbursement reference, match status, policy check | Retain review support |
| Follow-up | Next action, owner, last reviewed | Keep the queue actionable |
Calculate quantity only after verifying non-overlap
Columns H to K hold affected units, confirmed found units, cash-compensated units and inventory-compensated units. Column L holds the remaining quantity. Subtract resolution quantities only when evidence establishes that they are distinct and linked to this incident.
In L2, a suggested spreadsheet check is: =IF(SUM(I2:K2)>H2,"CHECK OVERLAP",MAX(0,H2-SUM(I2:K2))). Adapt separators to your spreadsheet locale. This flags an obvious over-allocation but cannot detect every overlap; a plausible total can still contain duplicated evidence.
The example file uses five affected units, one found unit, two cash-compensated units and one distinct inventory-compensated unit, leaving one for review. Its non-overlap assumption is fictional and explicit. Your real evidence must support the same type of calculation.
Do not treat the formula as a claim eligibility rule. It is a working quantity check. Source relationships, later changes and the current policy still require review.
Keep unknown value blank and recorded cash separate
Column M is unit cost, N is currency, O is estimated unresolved value and P is recorded cash. A suggested O2 formula is: =IF(OR(M2="",N2="",NOT(ISNUMBER(L2))),"",L2*M2). It keeps the estimate blank when the cost, currency or numeric remaining quantity is missing.
Using the fictional example, one remaining unit at an $8 cost produces an $8 internal estimate. The $16 recorded cash belongs in its own column. It is compensation evidence already linked in the example, not a new estimate or a promise of future recovery.
Keep currency totals separate. Add evidence for the unit cost and any deliberate conversion outside the compact worksheet if needed. The worksheet stores a review conclusion; the original reports and documents are what support it.
Run a monthly review with interim deadline checks
At the start of each review, record the files and their coverage, refresh later activity and reconcile existing open records before adding new candidates. Inspect event-to-reimbursement matches, review missing costs and give every unresolved record a next action.
Do not use the monthly schedule as a substitute for category-specific timing. Check open records between reviews when a policy deadline or requested response requires earlier action. Keep the date the policy was checked and the relevant trigger date in the supporting notes.
At close, report verified cash, resolved inventory, unpriced candidates and internally estimated unresolved value separately. Add counts of open records and unresolved evidence tasks so the report explains what remains to be done.
- Refresh evidence on existing incidents.
- Verify allocations and distinct unit resolutions.
- Review cost gaps and policy checks.
- Assign owners and concrete next actions.
- Archive the reviewed version with its source files.
Move from the worksheet to a report-review workflow
A spreadsheet is useful for a small queue and for understanding the review logic. As repeated products and multiple exports accumulate, the difficult part is preserving the relationships between source events, compensation and costs.
FluxPilot Recover accepts supported ledger files and optional cost and reimbursement files to help organize those findings. Use the worksheet's questions to inspect the results: what event is this, what evidence resolves it, and what action remains?
Keep the same discipline whichever tool you use. A traceable event record with an explained status is more useful than a large recovery total without supporting evidence.
Frequently asked questions
Does the CSV already contain formulas?
No. CSV stores the headers and example values only. Add the suggested formulas in your spreadsheet workbook and preserve a separate copy of the source reports.
Can I upload this worksheet as my Inventory Ledger?
No. Use the original supported Amazon report for analysis. This worksheet is for manual review notes and follow-up.
Does a remaining quantity prove eligibility?
No. Verify the source relationships, current policy, timing and required evidence before considering a claim.
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)