settlement report total does not match the marketplace payout by 1,204.55" error on the Amazon settlement import

TL;DR

The settlement report and the payout are related but not the same number: Amazon disburses most of a settlement while holding a reserve, rolls unavailable amounts into the next cycle, and sometimes splits one settlement across two disbursements. A 1,204.55 gap is usually the reserve or a rolled amount, not lost money. Rebuild the comparison properly: take the settlement report total, subtract the reserve or unavailable balance Amazon shows on the settlement, and compare the remainder with the disbursement for that settlement identifier, allowing for the settlement that straddles two payouts. Import on settlement groups, not on payout totals, and book the reserve as a receivable from Amazon so the difference has a home instead of breaking the import every cycle.

"settlement report total does not match the marketplace payout by 1,204.55" error on the Amazon settlement import

Use this when

• An Amazon settlement import is rejected or parked because its total differs from the bank payout by a four-figure amount.
• Amazon shows a reserve, unavailable balance or account-level hold for the period.
• Settlements close mid-cycle so one settlement feeds two disbursements.

Not for this skill when

• Individual order lines are missing from the settlement report. That is a report generation or API problem, not a payout comparison problem.
• The gap equals FBA fees or advertising charges you have not recorded. Record the charges; the payout comparison method is fine.

Steps

1. Download the settlement report and the payments disbursement detail for the same settlement identifier from Seller Central. Verify: both documents for the exact settlement are in hand
2. Reconcile the settlement in layers: gross sales and fees to the settlement total, then settlement total minus reserve and unavailable amounts to the disbursement. Verify: each layer's difference is quantified and the 1,204.55 is located in a layer
3. Confirm the reserve or rolled amount in the Amazon payments dashboard and note when Amazon schedules its release. Verify: the withheld amount and its expected release cycle are confirmed from Amazon's own figures
4. Adjust the import to post by settlement group with a reserve receivable line, instead of forcing settlement total to equal payout. Verify: the import accepts the settlement and the reserve sits as a receivable balance
5. Reconcile the bank deposit to the disbursement and clear the reserve when Amazon releases it in a later settlement. Verify: bank, settlement and reserve balances all agree across the two cycles

Variant phrasings

Amazon settlement report total does not match payout reserve

The verbatim mismatch with its usual cause.

Amazon settlement vs disbursement difference unavailable balance import

The layer-by-layer phrasing.

marketplace settlement reconciliation reserve receivable accounting

The accounting treatment search.

Compatibility: Amazon Seller Central settlement and disbursement reports (flat file and API) imported into ERP and marketplace accounting tools, all marketplaces with reserve policies.

Why it happens

Marketplaces protect themselves against refunds and chargebacks by settling sales in one calculation and paying out in another, holding a reserve against future claims. Accounting imports built on the naive assumption that settlement equals payout therefore fail on a predictable cadence, and the failure amount wanders with sales volume. The money is not missing; it is sitting in Amazon's reserve, visible in their dashboard, waiting for an accounting design that represents it.

Edge cases / pitfalls

• New seller accounts and policy changes raise reserve rates without notice; a growing gap can be a higher reserve, not an error.
• Currency conversion on cross-border disbursements adds a second, smaller difference layer; separate it from the reserve.
• Year-end cut-off needs the reserve receivable agreed to Amazon's statement, or the balance sheet understates assets.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstHYu7lwZAMzx9jq5GXLrHQ