Settlement reconciliation for FBA operators

Many sellers reconcile settlements only to confirm that deposits hit the bank. That is bookkeeping, not operating control. FBA settlement reconciliation should answer why margin moved, which fee categories changed, and whether Amazon owes money back.

Start by matching every settlement line to an operating object: order, refund, inventory adjustment, reimbursement, storage charge, inbound fee, removal, or reserve movement. Anything that cannot be mapped becomes an exception. Exceptions are where margin leaks hide.

Build a weekly close

Do not wait for month end. Weekly close is the right cadence because Amazon data changes often enough to matter, but not so often that the team drowns in noise.

The close should include:

• gross sales and referral fees by marketplace
• fulfillment fees by size tier
• refunds and return concessions
• storage, aged inventory, and inbound charges
• reimbursements opened, paid, denied, and pending
• reserve and transfer timing

The point is variance. Compare this week with the prior four-week average and explain material movement.

Reconcile at SKU level where possible

Account-level totals hide bad SKUs. If fulfillment fees rose 4 percent, was it mix shift, size-tier drift, or a real fee change? SKU-level reconciliation lets the operator act: fix a dimension issue, change price, change FBA/FBM routing, or stop replenishing.

Keep a case ledger

Every suspected overcharge should have a case status, evidence package, expected recovery, and deadline. Without a ledger, teams reopen the same issue, miss windows, or accept partial reimbursement without noticing.

Settlement reconciliation is where finance and operations meet. The best process produces fewer surprises and a prioritized list of actions, not a prettier spreadsheet.

Separate timing from true exceptions

Some settlement differences are only timing. A reimbursement may be approved in one week and paid in the next. A reserve movement may explain why the bank deposit does not match the gross settlement amount. Timing differences are normal, but they need expiration dates. If a line is marked as timing, record when it should resolve and automatically bring it back to the exception queue if it does not.

This keeps timing from becoming a junk drawer. Without an expiration rule, unresolved issues can sit under a harmless label until the claim window closes or the team forgets why the variance existed. A weekly close should make temporary explanations temporary.

Push fixes back to operations

The close should not end in finance. If a variance comes from size-tier drift, catalog and warehouse need the measurement data. If it comes from unexpected placement fees, inbound planning needs the selected option and actual charge. If it comes from return leakage, recovery and product teams need the SKU-level pattern.

Create a small handoff section in the close: issue, owner, expected action, dollar impact, and next review date. That handoff is what turns reconciliation into margin control. Otherwise finance explains the past while operations keeps creating the same future variance.

Make materiality rules clear

Not every variance deserves the same research depth. Define materiality rules before the close: small variances can be batched, repeat variances need root cause review, and high-dollar variances need immediate ownership. This keeps the close from becoming a hunt for every penny while still protecting meaningful margin.

Materiality should include pattern, not only dollar amount. A five-dollar variance repeated across hundreds of orders can matter more than one noisy adjustment. Track count, total value, and recurrence so the team can separate noise from systematic leakage. Review those rules quarterly as order volume, catalog mix, and operator capacity change. If the threshold is stale, the team will either ignore meaningful leakage or spend expensive time on immaterial noise. Write the threshold into the close notes.