Your Amazon Deposit Doesn’t Match Your Sales—Here’s Why

Why Your Amazon Deposit Doesn’t Match Your Sales

An Amazon deposit can hit your bank for significantly less than the sales shown in Seller Central. That difference does not automatically mean money is missing. It reflects a more complicated flow of sales, fees, refunds, reserves, and timing differences that ecommerce businesses need to account for correctly.

The problem starts when the bank deposit is treated as the source of truth.

Amazon collects money from customers and later calculates the net amount payable to the seller. In between gross sales and the final deposit, Amazon can deduct fees, refunds, advertising expenses, and other amounts. Funds can also be held or deferred. As a result, the amount deposited into your bank is not the same thing as gross sales revenue.

The Ecom Clinic demonstrates the problem with anonymized customer data. In one example, booking an $11,012.61 deposit directly as sales would understate revenue by roughly $4,900 while also hiding Amazon costs. In another settlement example, sales total $2,947 while net proceeds are $1,459. The gap is where the financial details that help explain business performance live.

Amazon's settlement reports provide a way to investigate those details.

Seller Central's payment information can show sales, refunds, expenses, beginning balances, account-level reserves, and net proceeds. The more detailed settlement flat file goes further, including fields such as transaction type, amount type, amount description, posted date, and SKU. It can also provide details for returns and FBA fulfillment and storage fees.

The objective is not simply to match the bank deposit. It is to account for what created it.

A dedicated Amazon clearing account can help. Orders, refunds, fees, and related activity can flow through the clearing account before the final payout is matched against the bank. The basic reconciliation logic presented in the session is gross sales minus fees and refunds minus cash deposited, with the clearing account ultimately expected to reach zero once all relevant activity and timing differences have been accounted for.

Timing is especially important with Amazon.

Refunds can appear in a later settlement than the original transaction. Account-level reserves represent money being held rather than an ordinary P&L expense. Settlement periods can also cross month-end, creating problems when businesses post the entire settlement into the month when the payout arrives. For accrual accounting, the session emphasizes distinguishing the sales period from the settlement period so activity is reflected in the appropriate period.

Other mistakes can compound the problem. Posting synced orders and a settlement entry to the same income account can double count sales. Grouping every Amazon charge into one fee bucket can obscure how much is going toward advertising, fulfillment, storage, and other costs. Multi-currency activity can also create accounting issues when settlement currencies are handled incorrectly.

Amazon settlement reconciliation is therefore more than matching a deposit. It is about reconstructing the financial activity behind that deposit so your books reflect sales, costs, refunds, timing differences, and cash accurately.

Webgility helps automate this process by pulling Amazon settlement information and posting ecommerce data into QuickBooks. The session also demonstrates support for more granular order- and SKU-level accounting, helping businesses spend less time manually downloading, mapping, and investigating settlement data and more time using their financial information to make operational decisions.