How do I reconcile FBA Inventory Ledger summary and detail rows?

Freeze one ledger scope before joining anything

Use exports for the same marketplace, exact start and end dates, and the same aggregation dimensions. Preserve the original files and record the export timestamps. A summary grouped by SKU and disposition cannot be reconciled safely against detail grouped by FNSKU, fulfillment center, or a different date basis until those dimensions are made explicit. Keep rows with blank identifiers visible; excluding them can manufacture a match.

Write the summary balance equation first

For each supplied summary row, calculate beginning quantity plus receipts plus transfers in plus customer returns plus adjustments in, minus shipments, transfers out, removals, and adjustments out. Compare that calculated ending quantity with the supplied ending quantity as an exact unit equation. Do not change a component simply to close the equation. A failed balance is its own exception even before detail coverage is considered.

Normalize detail events without guessing their sign

Map each seller-supplied event type to an explicit signed quantity and retain the source event reference, date, SKU, FNSKU, fulfillment center, and disposition. Unknown event labels should remain unmapped instead of being folded into adjustments. Aggregate the mapped detail on the same join keys as the summary, then compare its net movement with the summary movement. Duplicate event references and detail rows outside the requested window need separate review rather than automatic deletion.

Separate balance, coverage, and unmatched-key exceptions

A balanced summary can still lack detail coverage, and matching detail movement does not prove the ending balance is right. Queue three findings independently: summary equations outside tolerance, summary rows whose detail net does not cover the reported movement, and detail groups with no matching summary key. Show the absolute unit delta and affected identifiers so a reviewer can return to the original export instead of interpreting a single pass or fail flag.

Investigate the report evidence before taking account action

Check date boundaries, timezone, aggregation level, disposition changes, fulfillment-center transfers, delayed events, and report regeneration before treating a difference as loss or an amount owed. Inventory reconciliation does not establish reimbursement eligibility, authenticate source records, or prove that Amazon made an error. Keep the output as a deterministic review aid; any case, accounting entry, or inventory adjustment remains a human decision based on current Seller Central evidence.

Tools that help with this

• Free one-row FBA Inventory Ledger summary balance check (free)
• FBA Inventory Ledger Reconciliation Exception Finder ($1.00) — Join supplied summary and detail rows and rank balance and coverage exceptions
• FBA Reimbursement Deadline + Evidence Tracker ($1.00) — Organize dated evidence only after a ledger exception is independently verified
• Marketplace Payout Reconciliation Analyzer ($1.00) — Trace a confirmed cash reimbursement through a supplied settlement separately

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

• Why can eBay Promoted Listings show good ROAS but lose money?
• How do I reconcile a marketplace payout to orders and the bank deposit?
• Which FBA report should I use for lost, damaged, returned, or removed inventory?
• How do I check whether Amazon already reimbursed an FBA inventory event?
• How do I track FBA reimbursement deadlines and missing evidence?

Browse all guides →