Amazon settlement reconciliation: from settlement report to bank deposit

An Amazon settlement is a marketplace statement rather than a payout file. It contains sales, referral fees, fulfilment fees, storage charges, refunds, reimbursements and adjustments, covering a defined settlement period, and the net figure is what reaches the bank.

The reconciliation problem is that almost none of those components map one-to-one onto ledger accounts, and the settlement period rarely aligns with the accounting period.

Why the bank deposit and the sales figure never agree

• Multiple fee typesdeducted inside the settlement, each belonging to a different expense account.
• Reimbursements and adjustmentsthat are neither sales nor refunds and need their own treatment.
• Settlement periods that straddle month-end, so one statement covers two accounting periods.
• Reserves and holdsthat delay a portion of funds beyond the settlement.
• Multi-marketplace activity, where several regions settle separately and sometimes in different currencies.

The automatable part

Decomposing a settlement into its components, allocating them to accounts by rule, splitting a straddling settlement on a defined basis and matching the net against the bank deposit are all mechanical operations that follow the same logic each period. Reserve treatment and unusual adjustments stay with a person.

Cross-period activity is exactly the case the reference build flags rather than silently matching into the wrong month.

Marketplace settlement structures change over time. Where specific behaviour matters to a build, we verify it against current vendor documentation at implementation time.

When standard software is enough

Standard connectors are often the right solution for standard workflows. If the connector posts activity correctly and the clearing account returns to zero without investigation, there is nothing here worth building. Keep the software you have.

When custom automation may be justified

The case for a custom reconciliation layer depends on recurrence, not on frustration. It is worth looking at when the same exception patterns return every close, several sources have to agree before the balance resolves, and meaningful staff time goes into work that follows repeatable rules.

If you want a structured answer rather than an opinion, the Fit Score scores one workflow against recurrence, effort, source complexity, rule repeatability and portfolio reuse. It runs in your browser and takes a couple of minutes.