Every Amazon payout arrives in the bank account as one lump sum, and it would be convenient if that number meant something simple, like revenue. It doesn’t. That deposit is the end result of gross sales, minus fees of several kinds, minus refunds, minus reserves, minus advertising costs, minus VAT on fees, plus reimbursements, all netted together. Book it as sales and the books start drifting from the first settlement.
For UK Amazon sellers, the stakes are higher than a messy P&L. Amazon now reports gross sales data directly to HMRC. The figures in the seller’s tax return need to hold up against what HMRC already knows. And since August 2024, VAT on most seller fees is charged directly by Amazon rather than handled through the reverse charge mechanism. Sellers who haven’t adjusted their Amazon accounting treatment are sitting on unreclaimed input VAT without realising it.
This article covers how Amazon settlement reconciliation works, where it goes wrong, and what a proper setup looks like in Xero with A2X.
The Struggle With Amazon Settlement Reports Reconciliation
Amazon Seller Central offers several reports, and none of them agree with each other. Run four different reports for the same month and you will get four different sales figures. The reasons are structural, not errors on Amazon’s part.
The sales dashboard shows revenue before VAT and refunds with no fees deducted. It is not a reliable figure for accounting purposes. Business Reports record ordered product sales at the point of order placement, which means they include cancelled and pending orders that may never complete. Fees do not appear. Refunds show by refund date rather than by original order date.
Transaction reports (also called date range reports) get closer to reality. They record individual transactions based on shipment date, only counting shipped orders, and they include fees. But they are not the reconciliation source either.
Settlement Reports are. The Flat File V2 settlement report reflects actual money movement. Amazon generates one roughly every 14 days at disbursement. It breaks out gross sales, fees by type, refunds, reserves, reimbursements, advertising spend deductions, and the net deposit. This is what hits the bank. This is the starting point for reconciliation.
But the settlement report alone does not give the full picture. The VAT transactions report captures VAT detail that settlement data does not include. And settlements only contain released transactions — money Amazon has actually disbursed. Revenue earned but held under delivery date-based reserve policies (DD+7, for example) or on Amazon Business invoiced orders sits in deferred status until Amazon releases it. That can be days or weeks after shipment. For limited companies on accrual accounting, revenue needs to be recognised when earned, not when the cash arrives. Amazon’s Transaction Report in the Reports Repository covers both deferred and released transactions by posted date, making it a necessary third source. A2X pulls settlement and VAT transactions data automatically and has a separate feature for accruing deferred transactions into the correct period, though it needs to be enabled. Managing all three sources manually is where most sellers or their accountants lose the thread.
How Poor Settlement Reconciliation Affects Amazon Sellers
When settlement components are not broken out properly, the consequences compound over time.
Margin visibility disappears. If fees are not separated by type, there is no way to see what Amazon is charging per order, per category, or per marketplace. Product-level margin analysis becomes guesswork.
VAT on seller fees goes unreclaimed. Since August 2024, Amazon charges 20% UK VAT directly on most seller fees. If the accounting treatment was never updated, that VAT is being deducted from settlements but not appearing as reclaimable input VAT on returns. The money leaves the business and doesn’t come back.
HMRC has the gross figures. Online marketplaces are legally required to report gross sales data to HMRC. The number HMRC holds is gross revenue, not the net deposit that lands in the bank. A seller tracking turnover from net deposits could be understating their reported revenue relative to what HMRC already knows.
VAT threshold calculations break. Turnover for VAT registration purposes is based on gross revenue, not net payouts. Sellers using net deposits to judge whether they are approaching the threshold are working from the wrong number.
The books cannot support scrutiny. Due diligence for funding, investment, or exit requires accounts that can be traced back to source data. A single “Amazon income” line with no fee breakdown does not survive that process.
How Proper Amazon Settlement Report Reconciliation Works
There are two valid approaches to reconciling Amazon payouts. The first is the clearing account method. It is a manual process: the seller or their accountant posts each settlement component to a clearing account in the accounting software and matches the result against the bank deposit. The second is A2X, which pulls settlement and VAT transaction data directly from Seller Central and posts it to Xero automatically, matching the data to payouts without the manual step.
Both methods land the same components in the same places in the chart of accounts. The difference is how they get there.
The Clearing Account Method
A clearing account sits between Amazon and the bank in the accounting software. Each component of a settlement posts to it: revenue on one side, fees, refunds, reserves, and other deductions on the other. When the bank deposit arrives, the clearing account balance should match the deposit amount and zero out.
This is the manual approach. Without A2X or a similar tool, the seller or accountant is doing this work by hand for every settlement.
How Each Settlement Component Should Be Posted
Each line item in the settlement belongs in a specific place in the chart of accounts. Gross sales post to a revenue account. Fees post to their respective expense accounts, broken out by type rather than lumped into a single “Amazon fees” line. Referral fees, FBA fulfilment fees, storage fees, and subscription fees each go to their own account. Refunds post as contra-revenue, reducing the sales figure rather than sitting as an expense. VAT on fees posts with the correct tax code.
In the clearing account method, all of these post against the clearing account so the net balance can be matched to the bank deposit. The account structure itself, where each component lands, applies regardless of whether the work is done manually or through A2X. A2X posts to the same account types. But this section describes the manual process.
What a Non-Zero Balance Tells You
When the clearing account does not zero out after the bank deposit is matched, something is missing or miscoded. A reserve that was not coded as a receivable. A currency conversion difference that was not accounted for. A loan repayment deducted by Amazon but not recorded. An entry posted to the wrong period.
This is where the manual method starts to break down. Spotting a non-zero balance is one thing. Knowing how to investigate and resolve the underlying cause is another. Many business owners and non-specialist accountants get stuck at exactly this point. They either don’t know to monitor the clearing account balance in the first place, or they see the mismatch and cannot trace it back to its source.
For sellers processing multiple settlements per month across more than one marketplace, the volume of manual work and the skill required to troubleshoot discrepancies makes the clearing account method increasingly impractical.
A2X does not use clearing accounts in this way. It works differently, and its approach is covered in the section below.
The Reconciliation Problems We Often See in Practice
When Elver E-Commerce Accountants onboard a new client, the accounting setup that comes with them usually contains some version of the same errors. These are the patterns that show up repeatedly, and they are a large part of why scaling Amazon sellers benefit from working with a specialist.
Inbound Freight Lumped in With FBA Fees
Inbound freight, the cost of shipping stock from the factory or supplier to Amazon’s FBA warehouse, is a stock cost. It belongs in cost of goods sold. FBA fulfilment fees, what Amazon charges per order to pick, pack, and ship to the customer, are a selling expense. They belong in operating costs.
Both are deducted from Amazon payouts rather than billed separately, which is why they get lumped together. But the effect of that is material. Misallocating inbound freight to selling expenses understates COGS. Gross margins look higher than they are. And because inbound freight volumes fluctuate with stock replenishment cycles rather than order volume, margins become volatile in ways that don’t reflect the actual trading performance.
Settlements That Cross Month-End
Amazon’s settlement cycle runs roughly every 14 days. It does not align with calendar months. A settlement can easily span the last week of one month and the first week of the next. If the full settlement posts to the month the deposit lands in, revenue and costs shift between periods. Monthly P&L figures become unreliable and VAT return accuracy is compromised, particularly when the cutoff falls across a VAT quarter boundary.
Reserves Recorded as Costs
Amazon holds reserves for various reasons: new seller accounts, high refund rates, or policy reviews. A reserve is not a fee. It is money Amazon is holding temporarily. It will either be released in a future settlement or applied against claims.
When reserves are coded as an expense, the P&L takes a hit that doesn’t represent an actual cost. When the reserve is released, it appears as unexplained income. The net effect is artificial P&L movement that obscures the real trading position.
Advertising Spend Hidden in the Net Deposit
PPC advertising costs are often deducted directly from settlements. Without a dedicated account mapping, that spend disappears into the net deposit figure. There is no visibility on how much was spent on advertising in a given period, and ROAS calculations cannot be done from the accounting data alone.
The ad spend exists in the settlement report, broken out as a separate line item. The problem is not that Amazon hides it. The problem is that without proper mapping, the accounting software treats it as part of the undifferentiated net figure.
Multi-Marketplace Settlements in a Single Account
A seller on Amazon .co.uk, .de, and .fr receives separate settlements for each marketplace. Each has its own currency, its own fee structure, and its own VAT treatment. Posting all of them through a single clearing account and a single set of revenue and expense accounts makes it impossible to see which marketplace is profitable and which is not. VAT treatment is different for UK and EU marketplaces. Combining them means the VAT codes on the resulting entries will be wrong for at least one jurisdiction.
Refunds Posted as Expenses
A refund reverses a sale. It should reduce revenue and reverse the associated output VAT. When refunds are posted as an expense instead, revenue stays overstated and output VAT remains on a transaction that no longer exists. Gross margins, refund rates, and product-level performance all read incorrectly.
Automating Settlement Reconciliation With A2X
A2X connects to Amazon Seller Central, fetches each settlement file when Amazon generates it, and also pulls the VAT transactions report. It combines both data sources to build the full picture. The settlement report alone does not contain all the VAT detail needed for accurate posting. The VAT transactions report fills that gap. This is one of the key reasons manual reconciliation from settlement files alone falls short.
A2X breaks each settlement into its component parts: gross sales, fees by type, refunds, taxes collected, reimbursements, and other adjustments. It summarises those components into a single invoice or journal entry per settlement rather than posting per order, which would overload Xero with thousands of individual transactions.
That summary posts to Xero, mapped to the correct accounts in the chart of accounts. Revenue goes to the revenue account. Each fee type goes to its own expense account. Refunds go to contra-revenue. Each line gets the correct VAT code based on the mapping configuration. When the bank deposit arrives in Xero’s bank feed, it matches the A2X-posted invoice for one-click reconciliation.
A2X also splits settlements that span two calendar months so each month’s P&L is accurate. It supports multi-marketplace setups, generating separate summaries for .co.uk, .de, .fr and so on. Sales can be grouped by SKU, product type, or posted as a lump sum. Multi-currency is handled with conversion happening in Xero. There is an auto-posting option so settlements flow through without manual approval each time.
Where Human Oversight Is Still Needed
A2X handles the heavy lifting on data extraction and posting. It does not replace the accountant’s judgment on mapping, compliance, and anomaly detection.
Initial mapping configuration. A2X suggests default mappings, but someone needs to verify they match the seller’s chart of accounts and VAT situation. A wrong mapping means wrong books, automated at speed. This is the accountant’s job during setup.
Reacting to Amazon billing changes. When Amazon changed its VAT treatment in August 2024, A2X updated its defaults. But existing accounts needed manual review to confirm the new mappings were applied. A2X flags changes. It does not force-update a live configuration. Someone has to act on it.
Catching anomalies. Unreleased reserves, unexpected reimbursements, miscoded Amazon-initiated adjustments, new fee types Amazon introduces without warning. A2X posts what Amazon gives it. If Amazon miscategorises something in the settlement file, A2X passes it through. A human needs to review the output and spot when something doesn’t look right.
VAT return accuracy. A2X feeds Xero the right data if the mappings are correct, but it does not file the VAT return or verify the return before submission. The accountant still needs to review it. For multi-marketplace sellers where UK, EU, and zero-rated transactions all need separate treatment, submitting without that review is how errors get filed.
Inventory and COGS. A2X does not handle stock valuation or inbound freight allocation. It posts what Amazon reports in the settlement. COGS and margin analysis require separate processes.
Advertising reconciliation. PPC spend deducted from settlements will appear in A2X if it is part of the settlement data. Standalone advertising invoices billed separately are not pulled in. The seller or accountant needs to reconcile ad spend independently.
Deferred transactions. A2X can accrue held-back revenue into the right period, but the feature is off by default. Someone needs to enable it, map the asset account per marketplace, and set the opening balance.
A2X is the tool. The accountant is the judgment layer that configures and monitors it.
Structuring Your Accounts for Amazon Data
The chart of accounts needs to be built for the data that Amazon generates, not for simplicity. A generalist setup with a single “Amazon income” line and fees lumped into one account will not support settlement reconciliation. The components cannot be matched, the VAT codes cannot be applied correctly, and the resulting figures will not survive any serious review.
The structure needed includes a clearing account per marketplace (for sellers using the manual method), separate revenue accounts where needed, expense accounts broken out by fee type (referral fees, FBA fulfilment fees, storage fees, subscription fees, advertising), contra-revenue for refunds, and a receivable for reserves.
Each account needs the correct VAT code assigned. UK marketplace fees carry 20% VAT. EU-related fees may still attract reverse charge treatment depending on fulfilment location, but are generally subject to UK VAT. Advertising has its own treatment. The VAT detail is covered in the section below. The point here is that the chart of accounts structure determines whether the data can flow correctly. Get the structure wrong and no amount of reconciliation effort will produce accurate books.
Restructuring the chart of accounts is one of the first things Elver does during onboarding. It is foundational work that everything else depends on.
Amazon Settlement Reconciliation and UK VAT
From 1 August 2024, Amazon moved fee billing from Amazon Services Europe S.à r.l. (ASE), based in Luxembourg, to Amazon EU S.à r.l. (AEU), which has a UK branch. Because AEU has a UK establishment, it charges 20% UK VAT directly on fees. Before this change, fees were subject to the reverse charge mechanism. Sellers didn’t pay VAT upfront to Amazon. Their accountant self-accounted for it on the VAT return, with output and input VAT cancelling out and no cash impact.
This is not new information for most sellers. The change is nearly two years old. But Elver still sees clients whose A2X mappings and accounting treatment were never updated. The practical result is months of input VAT that was charged and deducted from settlements but never reclaimed on VAT returns.
The fees now subject to direct 20% UK VAT include FBA fulfilment fees for orders shipped from a GB warehouse, referral and merchant seller fees, subscription fees for the Professional Selling Plan, and storage fees.
FBA fees for orders shipped from outside a GB warehouse are zero-rated. Advertising fees are not affected by this change. UK advertising was already billed from the UK at 20% VAT before August 2024. EU advertising remains reverse charge.
VAT is deducted from settlements upfront, reducing the net payout. VAT-registered sellers reclaim it on their return, but there is a timing gap between the deduction and the reclaim. Non-VAT-registered sellers cannot reclaim it. Their fee costs increased by 20%.
The A2X Mapping Change
Fee transactions that were previously mapped as “Reverse Charge Expense” should now be mapped as “20% VAT on Expenses.” A2X updated its default mappings when the change took effect. Sellers or their accountants need to verify the configuration was applied correctly to their account.
This is not a blanket switch across all fees. EU-related fulfilment fees, for example orders fulfilled from warehouses outside the UK, still attract reverse charge treatment in some scenarios. A2X does not always distinguish these automatically. A manual adjustment journalled over the A2X postings is often required to get the VAT on EU fulfilment fees correct. This is one of the reasons sellers need an ecommerce-specialist accountant reviewing the output rather than relying on A2X defaults alone.
The Backlog Reclaim Opportunity
Sellers who did not update their mappings or accounting treatment after August 2024 may be sitting on unreclaimed input VAT. The VAT was charged by Amazon and deducted from settlements. But if it was still coded as reverse charge in Xero, it will not appear as reclaimable input VAT on their returns.
The opportunity is not a retrospective claim in the traditional sense. It is correcting the coding going forward and amending prior returns where VAT was missed. The fee invoices that document the VAT charged are in Seller Central under Reports, then Tax Document Library. These invoices are the documentation required to support the input VAT claim.
UK and EU Marketplace Fees in Xero
The Xero chart of accounts needs correct VAT codes per account, with separate treatment for UK and EU marketplace fees. UK fees carry 20% VAT. EU fees may carry reverse charge or zero-rated treatment depending on the specific fee and fulfilment location. Combining them under a single VAT code will produce incorrect returns.
How Often Should Amazon Sellers Reconcile Their Settlements?
There is a timing constraint. Amazon releases the VAT transactions report on the 4th of the following month, so a full reconciliation can only be completed after that date. Per settlement reconciliation (matching the bank deposit against the A2X posting or clearing account) can and should happen as settlements arrive. But the VAT layer needs the monthly report before it can be finalised. Leaving reconciliation for a full quarter creates a different problem. Discrepancies stack, the detail behind individual settlements fades, and the work required to untangle it grows out of proportion to the time elapsed. A quarterly catch-up typically produces an approximation rather than accurate books.
How Elver Handles Amazon Settlement Reconciliation
Elver uses Xero and A2X as the core of every Amazon client’s accounting setup. The chart of accounts is structured for ecommerce data from the start. A2X mappings are configured and reviewed by the ecommerce accountant team. VAT compliance is handled in-house with a single point of contact rather than referred to a third party.
The work described in this article is what Elver E-Commerce Accountants do for scaling Amazon brands as part of an ongoing service.
If your books don’t reflect what your business is doing, book a discovery call and we’ll tell you what we’d change.
