How Do I Reconcile Amazon FBA Inventory With My Accounting Records?

Why does Amazon's available quantity differ from inventory on the books?

Amazon screens and accounting records answer different questions. “Available” is an operational status: units that can currently be offered. The accounting asset should represent inventory the legal entity owns under its accounting policy, whether it is available, reserved, receiving, unsellable, in transit, or stored somewhere other than FBA. A seller can therefore have a correct Amazon screen and an incorrect general ledger—or the reverse.

Amazon describes the Inventory Ledger as a consolidated view of beginning balance, receipts, customer orders, returns, adjustments, reconciliation events, removals, and ending balance. That makes it the right starting point for an FBA warehouse roll-forward. It does not decide when title passed from a supplier, whether inbound goods are owned, how damaged units should be written down, or which unit-cost method the entity uses.

Which inventory populations should I separate before reconciling?

The first original control is an ownership-and-location map. It prevents the common mistake of comparing one FBA status with a company-wide asset.

Define one cutoff timestamp and one unit of measure. If Amazon reports individual units while purchasing records use cases, preserve the conversion factor by SKU. Map merchant SKU, FNSKU, ASIN, marketplace, disposition, and internal item code; never aggregate first by ASIN when multiple internal SKUs have different costs or owners.

What data proves the unit roll-forward?

For each SKU and disposition, use this control equation:

Expected ending units = starting units + receipts + customer returns + found/reconciliation increases − customer shipments − vendor returns − removals − disposals − lost/damaged decreases ± other identified events.

Retain the detailed event view for exception testing and the summary view for the control total. Also retain inbound shipment detail, removal orders, reimbursement activity, the SKU master, purchase receipts, and the prior close. Amazon states that the Inventory Ledger replaced several earlier FBA inventory reports; using a deprecated report name in an old procedure can cause teams to pull the wrong population.

Freeze exports as close as practical to the cutoff and label the download time. Near-real-time operational views can change after the accounting cutoff. A later Amazon adjustment should not be silently inserted into a closed month; document whether it corrects the prior period or belongs in the current period under the entity's materiality and close policy.

How do I convert reconciled units into accounting value?

Quantity control and valuation control should meet, but they should not be confused. After units reconcile, join each owned SKU to its approved cost layer or standard cost. A useful valuation bridge is:

Opening inventory value + owned purchases and capitalizable inbound costs − cost assigned to units sold − write-downs/write-offs ± cost corrections = closing inventory value.

The unit cost should come from the company's accounting records, not an Amazon selling price or estimated reimbursement. If a moving-average, FIFO, specific-identification, or standard-cost system is used, apply it consistently and retain the calculation. For U.S. tax reporting, IRS Publication 334 says businesses for which merchandise is an income-producing factor generally take inventories into account unless a small-business exception applies; the chosen method must still clearly reflect income. Financial-reporting and tax methods may differ, so the book-to-tax bridge belongs outside the Amazon unit reconciliation.

Which mismatch should I investigate first?

The second original control is a five-rung variance ladder. Work in this order so a mapping problem is not disguised as a write-off:

1. Scope: Same legal entity, marketplace, country, SKU population, disposition, and cutoff?
2. Identity: Duplicate SKUs, changed FNSKUs, bundles, case-to-each conversions, or merged ASINs?
3. Timing: Inbound shipped but not received, customer shipment after cutoff, return in processing, or removal not yet delivered?
4. Event completeness: Missing receipt, return, found/lost event, disposal, or manual stock journal?
5. Valuation: Units now agree, but unit cost, FX, landed-cost allocation, or impairment differs?

Keep quantity variance and value variance in separate columns. A zero-unit difference can still hide a dollar error if the wrong SKU cost was mapped. Conversely, a one-unit difference need not equal one current purchase price if the entity uses cost layers.

What does a complete hypothetical FBA reconciliation look like?

Hypothetical example—assumptions. A U.S. seller closes July for SKU ALP-12. Its FBA opening balance is 640 units. During July, Amazon reports 310 receipts, 420 customer shipments, 24 customer returns, 7 lost/damaged decreases, 3 found units, and 10 removals. The business also owns 80 units in transit to Amazon at cutoff. Its supported weighted unit cost is $18.40. Assume all FBA dispositions except the seven lost/damaged units remain saleable assets, and the in-transit goods have transferred to the seller.

Interpretation. Comparing the general ledger only with 540 FBA units would understate owned stock by the 80 units in transit. The seven lost/damaged units have already reduced the FBA roll-forward; the accountant must still decide whether a receivable, expense, or later reimbursement is supported. No reimbursement should be assumed merely because a ledger reason exists.

Limits. The example uses one cost for clarity. It does not cover kits, commingled stock, multiple currencies, consignment, bonded inventory, or lower-of-cost valuation tests. Those require policy-specific calculations.

What monthly process creates a reviewable close?

1. Confirm the entity, marketplaces, locations, cutoff, currency, and unit-of-measure policy.
2. Save the Inventory Ledger summary and detail plus inbound, removal, and reimbursement evidence.
3. Validate the SKU/FNSKU/internal-item mapping before aggregation.
4. Recalculate the unit roll-forward by SKU and disposition.
5. Run the variance ladder; assign each exception an amount, owner, cause, evidence, and due date.
6. Add separately reconciled in-transit, 3PL, return, and office stock to the company total.
7. Join supported cost layers and calculate value independently from unit differences.
8. Post approved COGS, transfer, write-down, and correction entries with workpaper references.
9. Have a reviewer tie closing units and value to the inventory subledger and general ledger.

How do I know the FBA reconciliation is finished?

• Opening units equal the prior signed close.
• Every SKU and disposition satisfies the movement equation.
• Inbound and outside-FBA units are included once, not twice.
• SKU mappings and unit conversions are version-controlled.
• Quantity and value variances are separately visible.
• Lost, damaged, found, removed, and reimbursed events are not netted blindly.
• Closing value ties to the inventory subledger and general ledger.
• Every remaining exception has evidence, owner, risk level, and resolution date.

When should I involve an accountant or inventory specialist?

Escalate material unexplained shrinkage, repeated inbound shortages, commingled or bundled stock, consignment, multiple legal entities, foreign-currency cost layers, tax/book differences, and potential impairment. Amazon operations data cannot by itself determine legal ownership, financial-statement classification, tax treatment, or the recoverability of a reimbursement claim.

Caigeek can help when the inputs include Amazon ledger exports, shipment and reimbursement files, the SKU master, purchase costs, outside-location reports, and the general ledger. A useful output is a unit roll-forward, ownership bridge, value reconciliation, exception register, proposed journals, and reviewer package—not a plug posted to make the account equal one Amazon screen.

Frequently asked questions