How to Connect Amazon to Xero: A UK Seller's Guide

If you sell on Amazon and keep your books in Xero, the monthly reconciliation is usually where it falls apart. Amazon doesn't pay you per order — it pays a net lump sum every fortnight or so, after deducting a long list of fees, refunds and reserves. Try to force every order into Xero and you'll drown in entries that match nothing in your bank account.

This guide explains the right way to connect Amazon (Seller Central and FBA) to Xero for UK sellers: why per-order is wrong, how settlement-based journals work, how to handle Amazon's fees, refunds and reserves, the VAT rules that genuinely catch people out (including marketplace facilitator rules and OSS/IOSS), and when an off-the-shelf tool beats a custom build.

Why per-order syncing is the wrong model

The most common mistake is pushing every Amazon order into Xero as its own invoice or sales receipt. A seller doing, say, 50 orders a day would generate around 1,500 entries a month — none of which reconcile against the bank, because Amazon never pays you order by order.

What actually lands in your bank is a settlement disbursement: typically every 14 days, Amazon nets your gross sales against selling fees, FBA fees, refunds, advertising, storage, loan repayments and reserves, then pays out whatever's left. That single deposit can represent thousands of orders and dozens of fee types.

So the goal isn't to mirror orders in Xero. It's to record, per settlement, a summary that equals the disbursement — so reconciliation becomes a one-click bank match rather than a forensic exercise.

Per-order detail only makes sense for low-volume, high-value sellers (bespoke or B2B wholesale) who genuinely want order-level records in the ledger. For everyone else, summarised is correct.

Settlement-based journals: the correct approach

The right model is to post one summarised journal (or summary invoice) per Amazon settlement period. Each journal breaks the settlement into its component lines, and the net total ties out to the bank deposit.

A well-structured settlement journal in Xero includes lines for:

• Gross sales (product revenue), ideally split by VAT rate and by marketplace
• Shipping income charged to buyers
• Promotional rebates and discounts
• Amazon selling fees (referral/commission fees)
• FBA fulfilment fees (pick, pack and ship)
• FBA storage and long-term storage fees
• Advertising spend (Sponsored Products and similar)
• Refunds and the associated fee adjustments
• Reserves held back and reserves released
• Subscription and other Seller Central fees

When all of that nets to the figure Amazon actually paid you, the bank line matches and reconciliation takes minutes.

Fees must be recorded gross, never netted off sales

This is the rule that protects both your reported turnover and your VAT. Record sales at the gross amount the buyer paid, and post Amazon's fees as separate expenses. If a £40 sale is quietly recorded as roughly £34 because the referral and FBA fees were netted off, your turnover is understated and your VAT figures can be wrong. The disbursement clears everything against the bank — but each line has to exist in its own right first.

Reserves: the line that trips everyone up

Amazon frequently holds back a reserve — a portion of your balance retained against potential refunds or A-to-z claims — and releases it in a later settlement. Ignore reserves and your Xero balance won't match the disbursement, leaving you chasing a difference that never resolves.

The clean pattern is an Amazon reserve clearing account in Xero. Reserve held in one settlement posts to that account; reserve released in the next reverses it. At any point, the clearing account balance equals the money Amazon is holding but hasn't paid you. If it drifts to a figure that makes no sense, something in the mapping is wrong — which makes it a useful early-warning signal.

The same clearing-account logic applies to Amazon lending repayments if you've taken Amazon finance: the repayment is deducted from your disbursement and needs its own account, not a reduction of sales.

VAT: the UK and cross-border details that matter

VAT is where Amazon-to-Xero setups quietly go wrong, because the rules differ by where the buyer sits and where your stock is held.

Marketplace facilitator rules — Amazon often collects the VAT

Since the post-Brexit reforms, Amazon acts as the deemed supplier (marketplace facilitator) and collects and remits UK VAT itself on certain sales — notably goods sold by overseas sellers to UK customers, and imported consignments not exceeding £135 sold to UK buyers. On those transactions Amazon charges and accounts for the VAT, so you must not also account for output VAT on them, or you'll pay it twice.

The practical consequence: your settlement data contains a mix of sales where you owe the VAT and sales where Amazon already handled it. Your Xero mapping has to separate the two. Lumping everything into standard-rated output VAT is the classic, expensive error. A UK-established seller holding UK stock and selling to UK buyers generally still accounts for their own VAT — but verify your exact position with your accountant, because it hinges on establishment and stock location.

EU sales — OSS and IOSS

If you sell to EU consumers (for example via Pan-European FBA or EFN):

• OSS (One Stop Shop) covers intra-EU distance sales of goods already inside the EU. VAT is charged at the destination country's rate and reported via a single OSS return.
• IOSS (Import One Stop Shop) covers imports into the EU not exceeding €150 sold to consumers.
• Where Amazon is the deemed supplier, it may collect the EU VAT instead.

Each of these maps to a different Xero tax treatment. If you sell across borders, this needs deliberate mapping rather than a default rate.

Refunds reverse VAT

A refund isn't just negative revenue — it reverses the output VAT on the original sale (and adjusts the related fees). Make sure your setup handles refunds as proper reversals, not as a plain expense, or your VAT return will be overstated.

A good principle: what Amazon charged or collected and what Xero records must agree, line for line.

The tools: A2X and Link My Books vs custom

There's no single best method — it depends on volume, marketplaces and how unusual your tax position is. Here's an honest comparison.

Approach	Best for	Strengths	Weaknesses
Dedicated apps (A2X, Link My Books)	Most UK Amazon sellers	Settlement-level journals; fees, refunds, reserves and VAT split out; accountant-friendly	Monthly fee scales with volume; ceiling on custom logic
Native / cheap connectors	Very small, single-marketplace sellers	Cheap or free; quick	Often per-order; weak on reserves, fees and facilitator VAT
Zapier / Make	Light glue, alerts, edge cases	Flexible; no code	Per-event by default; won't reconcile settlements; costly at volume
Custom integration	High volume, multi-channel, bespoke tax	Exactly your rules; consolidates channels; scales	Build and maintenance cost; only worth it past real complexity

Dedicated apps

For most UK sellers, A2X or Link My Books is the pragmatic starting point. Both fetch each Amazon settlement, break it into a summarised journal split by sales, fees, refunds, reserves and tax, and post it to Xero so the total matches your disbursement. Both have UK-aware VAT logic, including marketplace facilitator handling — which is exactly the part cheap connectors miss.

The trade-off is a monthly fee that scales with order volume, and a limit on how much bespoke logic you can apply. When evaluating any tool, ask specifically how it handles reserves, marketplace facilitator VAT, refunds and multiple marketplaces — that's where the weaker options fall down.

Zapier or Make

Zapier and Make are great for lightweight glue — a Slack alert on a big order, or drafting something from a specific event. They're the wrong tool for the core accounting job: they fire per event and can't reconstruct a batched settlement, so they recreate the per-order mess. Use them as glue, not as your ledger sync. We weigh this up in our guide to Zapier vs Make vs custom integration.

Custom integration

A custom build talks directly to Amazon's Selling Partner API (SP-API) and the Xero API, applying exactly your rules: how to summarise, which clearing accounts to use, how to map facilitator vs self-accounted VAT, and how to fold Amazon in alongside other channels. More on when that's worth it below.

Reconciling to Amazon disbursements

The test of any setup is simple: does each Xero settlement entry reconcile to the penny against the matching bank deposit?

A robust pattern uses an Amazon clearing account (plus the reserve clearing account above). Sales, fees and refunds post to clearing; the disbursement moves the net from clearing to your bank. The clearing balance represents earned-but-unpaid money — a built-in sanity check.

Mind the timing boundary: settlement periods rarely align with calendar months, so a settlement can straddle a VAT quarter or year end. Good tools let you allocate the journal to the right period; if you're reconciling by hand, watch this at quarter ends.

When is a custom integration worth it?

Off-the-shelf tools cover the common cases well. A custom build earns its keep when you outgrow them:

• High volume, where per-settlement app pricing hurts or summarisation needs to be smarter than the tools allow.
• Multiple channels — Amazon plus Shopify, eBay, a B2B portal or EPOS — needing consolidated, consistent posting into one Xero file. Our guides on syncing Shopify and Xero and connecting Stripe to Xero cover the sister problems.
• Complex cross-border VAT across UK, OSS and IOSS that no single connector maps cleanly.
• Operational coupling — the same pipeline feeding inventory, COGS or a reporting warehouse.

A custom integration writes clean, settlement-matched entries on your exact rules. The cost is real — design, build and maintenance — so it makes sense once the cost of getting it wrong (double-counted VAT, hours of reconciliation, margin you can't see) outweighs the build. As an indicative UK market guide only, a focused Amazon-to-Xero build commonly sits in the low-to-mid five figures depending on marketplaces and complexity — treat that as a range to sanity-check quotes against, not a price.

There's often a sensible middle path: use A2X or Link My Books for the standard flow, and add a small custom piece only for the edge case it can't handle.

A practical rollout checklist

1. Map your accounts first — sales (by VAT rate), Amazon fees, FBA fees, advertising, refunds, plus an Amazon clearing account and a reserve clearing account.
2. Choose settlement-based summaries, not per-order, unless you're genuinely low-volume.
3. Pick the lightest tool that fits — usually A2X or Link My Books for the core flow.
4. Confirm fees post separately and sales stay gross.
5. Verify VAT mapping, especially splitting marketplace-facilitator sales from self-accounted ones, plus any OSS/IOSS.
6. Check one full settlement reconciles to the penny against the bank disbursement, including reserves.
7. Test a refund end to end, including the VAT reversal.
8. Run a parallel month before you trust it, and document the setup for your accountant.

How APIwise can help

Connecting Amazon to Xero is rarely the hard part — getting it to reconcile cleanly is, with fees split out, reserves tracked, VAT correctly split between what you owe and what Amazon already collected, and disbursements matching your bank to the penny. As the UK's API and AI integration specialists, we're vendor-neutral: if A2X or Link My Books is the right answer for you, that's exactly what we'll say. If your volume, marketplaces or VAT position genuinely call for a custom build, we'll scope and price it up front, fixed. You can read more about how we work as a Xero integration specialist.

The simplest next step is our fixed-price Integration Health Check — we review how your systems connect today, find the gaps and risks, and give you a clear, costed plan, as part of our API integration work. Book your Integration Health Check and make your Amazon-to-Xero reconciliation something you never think about again.