Amazon Inventory Ledger Unreconciled Quantity = 1: Are You Actually Owed a Reimbursement?

The short version

In a Detailed View Inventory Ledger export, reconciliation fields help show whether an inventory movement has been matched or resolved by another event. An unreconciled quantity can be a useful signal that a movement deserves investigation.

It is not, by itself, proof that Amazon owes a reimbursement. You still need the event type, reason, date, reference ID, and reimbursement history.

Read the row as a complete event

Treat each row as a piece of an event trail. A negative adjustment can look alarming on its own, but the same FNSKU may later have a found event or reimbursement that resolves it.

The best audit keeps the reference ID and checks whether the unreconciled quantity remains above zero after Amazon's reconciliation.

• FNSKU identifies the FBA inventory item.
• Event Type tells you what kind of movement occurred.
• Reason explains the adjustment category.
• Reference ID identifies the underlying event.
• Reconciled Quantity shows the amount already matched.
• Unreconciled Quantity shows the amount still not reconciled in that row.

A common false positive to avoid

If an export includes an Unreconciled Quantity column and that value is zero, do not infer a claim merely because Quantity is negative. The explicit reconciliation field should take priority.

FluxPilot's current analyzer follows this rule so fully reconciled rows stay out of the review queue.

When an unreconciled row becomes useful

An unreconciled loss or fulfillment-center damage event becomes useful when it is recent, traceable to a reference ID, not already reimbursed, and otherwise eligible under Amazon's policy.

That combination turns a noisy spreadsheet row into a concrete review task.