Amazon settlement reconciliation: matching disbursements to your ERP when the reserve hides the rest

Here is the part that changes everything: with Amazon, you are not reconciling sales against a deposit. You are reconciling a settlement report against itself. A seller in r/FulfillmentByAmazon described the usual mess — "Orders get shipped, payments come in but when it's time to reconcile, things just don't line up. Delays, mismatched payouts, and manual back-and-forth every week." The thread's top answer was a link to a Discord server. So here is the actual method. Amazon's deposit is short and late on purpose — it nets out referral and FBA fees, holds back a reserve, and pays on a two-week clock. The settlement report already foots to that deposit. Your job is to prove the part it keeps — the reserve — and show it carries into the next report. Do that, and the chaos becomes one number you can name.

Why your Amazon disbursement never matches your sales

Three structural facts make the gap permanent, and all three are normal. A disbursement is a batch over a settlement period, not a single sale — Amazon takes a window of activity and wires you one number. Amazon subtracts its cut first: referral fees, FBA fulfillment and storage fees, refunds, and advertising spend all come out before the money moves. And it holds back a reserve. A bookkeeper running four marketplaces in r/Accounting summed up the feeling exactly — "Amazon holds reserves and releases them on some schedule only Amazon understands." It is less mysterious than that, but the instinct is right: a chunk of your money is parked, on purpose.

The reserve comes in two layers, and it helps to name them. First is the standard delivery-date reserve: Amazon now holds an order's funds until seven days after delivery — DD+7. Amazon's own migration notice, quoted in r/FulfillmentByAmazon, spelled out why: "Moving your reserve setting to DD+7 provides time for you to accrue fees and other costs before disbursement." A seller on that thread put the cash-flow cost plainly — "this will add 8 to 14 days to cash flow planning." Second is the account-level reserve, a dynamic hold for estimated returns and claims that can, in a bad month, swallow the whole payout. A seller in r/FulfillmentByAmazon watched it happen: "Amazon is now saying my entire balance is for the account level reserve and no payment is being made." Neither reserve means money is lost. Both mean the deposit is always smaller than the period's sales — so reconciling one against the other directly is a fight you cannot win.

The settlement report is the source of truth — read it that way

Before any matching, internalize one fact a seller stated in an Amazon-to-Xero thread in r/AmazonSeller: "On the Amazon side your books are/should be based on your Amazon settlement reports. These are final and do not change." That is the whole game. The settlement / Payment Date Range report in Seller Central is the ledger — not your order export. It lists every financial event in the period: orders, refunds, referral fees, FBA fees, storage, ad charges, reserve movements, and the disbursement, and it foots to the net Amazon paid. Reconcile against your order count or your gross sales and you will never tie. Reconcile against the settlement report and it ties by construction — because Amazon built it to.

The fix: one Amazon clearing account, settlement by settlement

The method is the same clearing-account model that makes every marketplace tie out, applied to Amazon's specific line items. A clearing account is a holding account for money that is earned but not yet settled to cash. Open one — Amazon Clearing — and route everything through it. Book gross sales as revenue through the account. Post every deduction the settlement report lists — referral fees, FBA fees, refunds, ad spend, chargebacks — to that account. When the disbursement lands, it clears most of the balance. What is left is the reserve, and it is supposed to be there. (For the Shopify-specific version of the same gross-versus-net gap, see why Shopify deposits never match your sales.)

Per settlement period, into Amazon Clearing
-------------------------------------------
1) Sales (gross):
   Dr  Amazon Clearing             gross sales
       Cr  Sales revenue                        gross sales

2) Deductions from the settlement report:
   Dr  Referral fees (expense)     referral fees
   Dr  FBA fees (expense)          fulfillment + storage
   Dr  Refunds / contra-revenue    refunds
   Dr  Advertising (expense)       sponsored ads spend
       Cr  Amazon Clearing                      fees + refunds + ads

3) Disbursement (cash):
   Dr  Bank                        net disbursement
       Cr  Amazon Clearing                      net disbursement

Amazon Clearing balance after posting
   = gross - (referral + FBA + refunds + ads) - net disbursement
   = the amount Amazon held back

   should equal:  delivery-date (DD+7) reserve
                + account-level reserve
                + any settled disbursement still in transit
   anything beyond that is your exception

The reserve is not a mystery — prove it with a roll-forward

This is the part every thread skips. An accountant in r/AmazonSeller asked the exact right question and got no real answer: "I am an accountant in a small company so I need details not high level overview. How do I reconcile the Account Level Reserve?" Here it is. Amazon's settlements are continuous — each report opens with the prior period's ending reserve and closes with a new one. So you do not hunt for the reserve; you roll it forward. Beginning reserve, plus what was newly held this period, minus what was released, equals the ending reserve — and that ending number must equal the reserve shown at the top of the next settlement. If it ties, the reserve is proven, not guessed.

Account-level + DD+7 reserve roll-forward
-----------------------------------------
  Beginning reserve        (top of THIS settlement report)
+ Amounts newly reserved   (orders delivered < 7 days ago; account-level holds)
- Amounts released         (prior reserves now disbursed)
= Ending reserve           (must equal the reserve line at the TOP of the NEXT report)

  Ending reserve == next report's beginning reserve  -> reserve proven
  Ending reserve != next report's beginning reserve  -> that gap is your exception

The cadence is what makes a sale and its cash land in different reports. A seller in that same thread confirmed the rhythm — "The automated disbursement is indeed every 14 days" — and Amazon's payment terms, as another seller quoted them, explain the seven-day piece: "Professional Sellers are paid every two weeks for orders delivered at least 7 days from the latest estimated delivery date." Tie periods to periods, not sales to days, and the timing stops looking like an error.

Reconcile an Amazon settlement, step by step

Same shape every period — only the report's date range changes. If a sync already posts these entries for you, the steps become a verification instead of data entry, which is exactly what you want to be doing.

1. Pull two files: the settlement report for the period (the summary and, if you want the detail on hand, the transaction view) from Seller Central, and your bank transactions.
2. Clean the exports first. A settlement ID or order ID that Excel autoconverted to a number, or a stray encoding mark in a product title, will silently break every match downstream — these are the CSV gotchas that quietly wreck a reconciliation. The settlement ID and order ID are the primary IDs the whole reconciliation joins on; protect them.
3. Foot the settlement report against itself: confirm beginning balance + sales − referral fees − FBA fees − refunds − ad spend ± reserve movement equals the disbursement Amazon says it paid. If Amazon's own report does not foot, stop — that is a data-pull problem to fix, not a books problem to force.
4. Post the summary to Amazon Clearing: gross to revenue, each deduction to its own expense or contra account, the disbursement from the bank — or let your tool post them and spot-check one period by hand.
5. Match the disbursement to a bank line on amount and date, or on settlement ID if the bank memo carries one. This is the cash-side tie covered in bank reconciliation, step by step.
6. Roll the reserve forward and confirm the ending reserve equals the next report's opening reserve. Then read the clearing balance: it should equal the reserve plus any settled disbursement still in transit. The remainder is your exception list — work only those rows.

A worked example: one settlement period

Say a two-week settlement. The summary breaks down like this, and the disbursement that hit your bank was 6,540:

Gross 12,000, minus referral fees 1,800, FBA fees 1,400, refunds 700, and ad spend 560, leaves 7,540 earned. Amazon held 1,000 of that in reserve, so 6,540 hit the bank — which matches the deposit. After all three entries post, Amazon Clearing is not zero; it holds 1,000. That 1,000 is the reserve, and it is supposed to be there. You did not lose it and you do not chase it. When the reserve releases next period, that disbursement clears it, and the balance returns to whatever the new reserve is. The reconciliation is done the moment you can say, in one sentence, what the balance is: it is the reserve.

When the settlement will not tie

When the leftover balance is bigger than your known reserve and in-transit, it is almost always one of a short list. A new seller in r/FulfillmentByAmazon hit the classic version — "the Disbursement Report and the Repository Report (which tracks unit-wise sales and realization) aren't lining up." The usual culprits:

• Deferred versus settled timing: an order is delivered but still inside its DD+7 window, so it is in the period's sales but not yet in the disbursement. That is in-transit, not an error — it belongs in the reserve and rolls forward.
• The report straddles month-end — earned in one month, paid in the next. Real timing residual; it lives in the in-transit bucket, not in an exception you chase.
• A fee or ad charge posted to the wrong account, so clearing never received the credit. The balance is off by exactly that amount.
• Multiple marketplaces (US, CA, MX, or the EU) settling in different currencies and converting at different rates — a real-looking gap that is just revaluation. That is its own discipline; see multi-currency reconciliation.
• A sync double-posted a settlement or dropped one — common when an integration "runs" but silently skips records. The dropped-record pattern is the same one in reconciling Shopify orders against your ERP.
• Two settlements with the same total, one unexplained — verify the IDs are distinct, because a near-duplicate the ID hides reads as a phantom exception.

What about A2X, Link My Books, Synder?

They automate exactly this — parse the settlement report and post the clearing-account entries so you do not key them by hand. A2X is the community default for posting Amazon settlements to QuickBooks or Xero; the others show up for specific stacks. It is a fair trade and often worth it. The reason to understand the method anyway is the one that seller named: your books are based on the settlement report, and those reports "are final and do not change," so a tool that posts entries you cannot read is a tool you cannot audit. Know what the reserve roll-forward should produce and you can check the tool instead of trusting it — which is also the first thing an auditor will ask you to show. The same logic carries to the ERP side, where the settlement totals have to agree with inventory and the GL in NetSuite and with the AR subledger.

Where this method tops out

One clearing account and a settlement-by-settlement roll-forward is the right tool for a seller on one or two marketplaces closing monthly or per settlement. It strains when you run many marketplaces and currencies at once, when you need daily cash visibility instead of period-end truth, or when an auditor wants the trail across thousands of order-level lines under each disbursement. The structure stays correct; reading it by hand stops scaling — the same way a spreadsheet does once partial payments and bundled deposits pile up. A workbook saves the answer but not the reasoning, and the reconciliation spreadsheet template only stretches so far across formats. Get the clearing account and the reserve roll-forward right first, and every later tool — or model — has something correct to check itself against.

← All writing