Last reviewed: September 8, 2026
One settlement is one payout, and one payout is one journal entry. The figure Amazon deposits is what is left after product revenue, marketplace tax, referral fees, FBA fees, storage, ads, promotions, refunds, reserves and currency conversion have pulled in opposite directions. This page shows that entry in full, names the account every line type goes to, and gives the posting steps for QuickBooks Online and for Xero.
The numbers are sample data. The mapping was reviewed with practicing ecommerce bookkeepers and checked against real settlement files, and account names are editable, so nothing here forces you off your own chart of accounts.
Download the sample journal (CSV)The entry is dated the last posted date in the settlement and balances by construction: debits equal credits, and the balancing line is the deposit itself. Everything above the clearing row says where the money went, and the clearing row is what reaches the bank. For where the amounts come from, start with the settlement report itself.
| Account | Type | Debit | Credit |
|---|---|---|---|
| Amazon Sales | Income | 10,800.00 | |
| Amazon Sales Tax Collected conditional | Liability | - | |
| Amazon Reimbursements conditional | Other income | - | |
| Amazon Referral Fees | Expense | 1,670.00 | |
| Amazon FBA Fees | Expense | 2,470.00 | |
| Amazon Storage & Service Fees | Expense | 110.00 | |
| Amazon Advertising conditional | Expense | - | |
| Amazon Promotions conditional | Expense | - | |
| Amazon Clearing Account | Bank / asset | 6,550.00 |
Read it as 10,800.00 of product revenue, 4,250.00 of Amazon fees, and 6,550.00 landing in the bank. Nothing is collapsed into one net income line: once fees are netted into revenue neither figure can be checked again. The clearing account is what you reconcile against the actual bank transfer.
Amazon does not book money by account. It writes an amount-type and an amount-description on every row, and mapping those two strings to an account is the whole job. Fifteen categories cover it, in the order they are written into the entry, each with its default account and the memo that travels on the line.
| Category | Default account | Memo on the line |
|---|---|---|
| Sales / principal | Amazon Sales | Product sales (principal) |
| Shipping income | Amazon Shipping Income | Shipping income, net of chargebacks |
| Gift wrap income | Amazon Gift Wrap Income | Gift wrap income, net of chargebacks |
| Tax collected | Amazon Sales Tax Collected | Marketplace tax collected |
| Reimbursements | Amazon Reimbursements | FBA reimbursements |
| Referral (commission) | Amazon Referral Fees | Referral / commission |
| FBA fees | Amazon FBA Fees | FBA fulfilment fees |
| Storage / service | Amazon Storage & Service Fees | Storage / service fees |
| Ads (in settlement) | Amazon Advertising | Sponsored ads (in settlement) |
| Refunds | Amazon Refunds | Refunds / returns |
| Promotions | Amazon Promotions | Promotions / coupons |
| Reserve (held or released) | Amazon Reserved Balance | Reserve held or released |
| Disbursement / transfer | Amazon Payable / Disbursement | Payable to Amazon / disbursement |
| FX / rounding adjustment | Amazon FX / Rounding Adjustment | FX / rounding adjustment |
| Other | Amazon Other | Other settlement items |
| Balancing line | Amazon Clearing Account | Net deposit to clearing/bank |
A category with a positive net is credited and a negative one debited, so one rule handles both a fee and its refund. When the whole settlement nets negative, the clearing line flips to a credit.
The fee glossary lists every line type and where it belongs, from Principal and Commission through to reserves and VAT. It is validated against 161,344 real settlement lines from US, UK, German and Indian sellers, with every line classified.
Four rows in the entry above are conditional: marketplace-collected tax, FBA reimbursements, ads billed inside the settlement, and promotions. They appear only when those lines exist in the file. When they do not, the row is left out entirely rather than posted as 0.00.
A zero line claims the category was looked at and came to nothing. An omitted line says the file held nothing of that kind. A US seller in a facilitator state and a UK seller filing their own VAT produce entries with different rows, and both are correct. Any account whose net movement is under half a cent is dropped on the same rule.
A refund or reversal of X nets back into X's own account with its own sign. That rule, validated with a practicing bookkeeper, keeps each family of charges in one home account instead of scattering into a refunds pile nobody can interpret.
The trap is in the file itself. Every row carries both a transaction-type (Order, Refund, Transfer) and an amount-type (ItemPrice, ItemFees, Promotion). A rule that reads Refund off the transaction sends a refunded Principal away from Sales, and the entry still balances, which is why the mistake survives: a balanced entry can still be split wrongly.
Three of the fifteen categories move money without being income or expense, and each gets its own account so it can never reach a margin figure.
On the clearing account: if your business has no account-level reserve, you can skip it and debit the bank directly. One bookkeeper noted Amazon now holds deferred transactions for high-turnover accounts instead of an account-level reserve, which changes how the deposit is timed and means some sellers find no reserve line at all. Since account names are editable, either setup works.
Cost of goods is a second, separate entry, posted only if you supply a cost per unit. Amazon does not know what your goods cost, so nothing in the settlement can tell you.
| Account | Type | Debit | Credit |
|---|---|---|---|
| Cost of Goods Sold | Expense | 4,370.00 | |
| Inventory Asset | Asset | 4,370.00 |
On reimbursements: Amazon pays you what it decided the unit was worth, which is rarely what it cost you, and SkuSum cannot tell the two apart because a settlement file carries no cost of its own. Which account is correct depends on how you value inventory, and the two answers are not competing opinions. Under periodic inventory, purchases less closing stock, the lost unit is already absorbed: it is not in closing stock, so its cost has fallen into COGS with no explicit write-off to net against, and a contra account would relieve the same cost twice. Other income is correct there. Under perpetual inventory, where the unit is written off as a discrete event at the point of loss, the reimbursement nets against a cost recognised in that same entry, and a contra account against cost of goods sold is correct. SkuSum defaults to Other income because it cannot know which method your books are on, and the account name is editable, so change it if you keep perpetual inventory. Every reimbursed SKU is flagged in the review bucket so you can compare the credit against your own cost. A2X defaults to an income account too. This page argued only for the contra account until 2026-09-09, when a practicing bookkeeper and the seller who made that case both landed on the method distinction above.
COGS is only as complete as the seller's cost file. A SKU with sales but no cost row would silently understate COGS and overstate profit, so every such SKU is flagged in the review bucket before export instead of being assumed to be zero.
On cost basis: v1 uses one landed cost per unit. A practicing bookkeeper's note is that unit cost drifts as you replenish, so a date-wise SKU cost log with FIFO gives a more reliable inventory valuation over time. Dated cost logs are on the roadmap; for now the single cost per unit is explicit and auditable.
These account and detail types were reviewed with a practicing ecommerce bookkeeper. They are a starting point, not a rule, and account names are editable so you can match any chart of accounts.
| Account | QBO account type | QBO detail type |
|---|---|---|
| Amazon Sales | Income | Sales of product income |
| Amazon Shipping Income | Income | Sales of product income |
| Amazon Gift Wrap Income | Income | Sales of product income |
| Amazon Sales Tax Collected | Other Current Liabilities | Sales tax payable |
| Amazon Reimbursements | Other Income | Other miscellaneous income |
| Amazon Referral Fees | Expense | Shipping, freight and delivery |
| Amazon FBA Fees | Expense | Shipping, freight and delivery |
| Amazon Storage & Service Fees | Expense | Shipping, freight and delivery |
| Amazon Advertising | Expense | Advertising and promotional |
| Amazon Refunds | Income (contra) | Discounts and refunds given |
| Amazon Promotions | Income (contra) | Discounts and refunds given |
| Amazon Clearing Account | Bank | Cash on hand |
| Cost of Goods Sold | Cost of goods sold | Supplies and materials |
| Inventory Asset | Other current asset | Inventory |
Shipping and gift wrap get their own income accounts because Amazon reports them as separate revenue lines, and each chargeback nets inside its own account rather than becoming a fee.
One bookkeeper flagged that promotions can sit as contra income rather than an expense, so both appear above under the same detail type. The tool books the debit either way; the account classification is your call in QBO.
Unknown line types hard-block the export. Amazon invents new line types regularly, and a tool that pushes an unrecognised line into a catch-all produces books that balance and are wrong. The export stops, the exact rows appear in the review bucket, and you decide. Custom mappings are allowed only for types the mapping does not already know, and every custom-mapped line is disclosed in the review bucket and in the export trailer.
Two questions stay separate: the journal ties out to the deposit while individual SKU margins may still be flagged for review. Both states are shown explicitly, instead of letting a balanced journal imply that every SKU number is final.
The entry above is correct by hand, and it is what SkuSum builds automatically: it reads your settlement file in your browser, nothing uploaded and no Amazon login, writes the settlement-id into the journal reference, omits the rows your file does not have, and refuses to export while a line type is unrecognised. Run your own file and compare it against the split you would have made.
If you run Amazon clients and review the mapping against your real practice, in writing whenever suits you, you get free lifetime access and a say in what gets built first. A one line note on any of the five is enough.