Amazon UK Seller VAT Invoices to Excel for VAT Return Prep

Preparing a UK VAT return from amazon.co.uk activity means drawing on four separate document streams inside Seller Central: the VAT Calculation Report (VCR) for per-order sales VAT data, Tax Document Library Sales Invoices for the audit-grade per-order PDFs, Tax Document Library Seller Fee Tax Invoices for the input VAT on Amazon's own fees, and the Settlement Report (Flat File V2 or XML) for reconciling those figures to the bank deposit. Since 1 August 2024, UK-established sellers have received their fee invoices from Amazon EU SARL UK Branch, carrying UK VAT at 20% and recoverable in Box 4, in place of the pre-2024 Luxembourg reverse-charge entries from Amazon Services Europe S.à r.l. Whether Amazon or the seller is liable for the output VAT on any given order is decided by the UK online marketplace rules: under the £135 consignment threshold, or where the seller is overseas, Amazon is the deemed supplier, and the seller still counts the sale in their Box 6 turnover figure.

There is no native bulk download for the per-order Sales Invoices. That single friction, the reason so many sellers and bookkeepers end up looking for a way to move the amazon uk seller vat invoice to excel themselves, is the one Seller Central does not solve for you. The route from those four documents to a return-ready spreadsheet, and from the spreadsheet to an MTD submission, is the rest of this article.

Each stream carries different content and lands on a different part of the return.

The VAT Calculation Report (VCR) is produced monthly as a CSV for sellers enrolled in Amazon's VAT Calculation Service. Each row is one VAT event, typically one order or one refund, with a taxable amount, a VAT amount, a marketplace facilitator flag, a B2B flag, and the ship-from and ship-to country. For UK-domestic sales the VCR feeds Box 1 (output VAT) and Box 6 (net turnover); where any EU dispatch slipped into the quarter, Box 8 picks up the value of those goods.

The Tax Document Library Sales Invoices are per-order PDFs issued either by Amazon (where it is the deemed supplier under the online marketplace rules) or by the seller through Amazon's invoicing service. These are the audit-grade evidence file. HMRC's expectations on what each PDF must show, from VAT registration number through tax-point date and per-rate VAT subtotal, are covered in detail in the article on what HMRC requires on a UK VAT invoice. The seller is required to retain them whether or not they are the entity that issued them.

The Tax Document Library Seller Fee Tax Invoices are Amazon's invoices to the seller for FBA fees, referral fees, monthly subscription, and any other non-advertising fee. These are the source of input VAT and feed Box 4 (input VAT recoverable) and Box 7 (purchases, net of VAT). The change of issuing entity on 1 August 2024 changed the journal that posts these invoices, which is the subject of its own section below.

The Settlement Report is produced bi-weekly as a Flat File V2 or XML, joining orders, refunds, fees, and the net disbursement to the seller's bank account. It is not, strictly, a VAT document. Its role in a return-prep workflow is reconciliation, tying the VAT figures derived from the VCR and the fee invoices back to the deposits the seller can actually see in their bank.

One further document is worth naming briefly so it is not confused with the rest. The AVTR (Amazon VAT Transactions Report) carries cross-border stock movements for sellers whose inventory crosses EU member-state borders. For a UK-domestic seller it adds nothing the VCR does not already give, and it is out of scope here; the Pan-EU FBA workflow that depends on the AVTR sits in its own article.

The extracted data from all of this ends up, eventually, in Making Tax Digital compatible bookkeeping or bridging software. That is the constraint the spreadsheet design later in the article has to satisfy: not only must Box 1, Box 4, Box 6, and Box 7 figures fall out cleanly, but the columns have to survive an import into Xero, QuickBooks, Sage, FreeAgent, or a bridging tool without losing the link back to the underlying invoice.

The online marketplace rules: which sale Amazon declares and which one you do

Since 1 January 2021 the UK has operated an online marketplace VAT regime that re-routes certain sales so the marketplace, not the seller, accounts for the output VAT. The seller still books the revenue and still counts the gross sale in their own turnover for VAT purposes; what changes is whose return the VAT itself lands on. Until each row of the VCR is classified against this regime, no Box figure is reliable.

Three operative cases decide whether the sale belongs to the seller's return or to Amazon's.

The first case is consignments of £135 or less imported from outside the UK and sold to a customer in Great Britain through an online marketplace. HMRC's guidance on VAT for overseas goods sold to UK customers using online marketplaces is unambiguous on this: where consignments of goods with a value of £135 or less are sold to customers in Great Britain through an online marketplace, the online marketplace is liable for the VAT. The seller invoice shows zero VAT, Amazon declares the £135-or-under VAT on its own return, and the seller does not. This is the amazon marketplace facilitator £135 vat split that catches every UK seller who imports stock direct-to-customer through an Amazon-handled FBA or Merchant fulfilment route.

The second case is goods already in the UK at the point of sale where the seller is not UK-established. Establishment is a status question, not a stock question: it covers whether the seller has a fixed presence in the UK from which the supply is made. Where the seller is overseas but the inventory is in a UK fulfilment centre, Amazon is the deemed supplier regardless of the £135 threshold. UK-established sellers are unaffected by this rule, but the moment a seller's establishment status is ambiguous, the per-row treatment in the VCR is the controlling answer.

The third case is the default one. UK-established sellers with stock in the UK selling to UK customers above £135, and any other scenario the marketplace rules do not capture, charge and remit UK VAT in the normal way. Amazon issues the per-order Sales Invoice on the seller's behalf (or the seller issues it themselves through Amazon's invoicing service), and the row carries the seller's VAT rate and amount.

The Box 6 consequence is where most return-prep errors actually live. Even where Amazon is the deemed supplier and the seller invoice shows zero VAT, the gross value of the sale still counts towards the seller's Box 6 net turnover figure. This is operationally counter-intuitive: there is no VAT to account for, but the sale is not invisible to the return either. Marketplace-facilitator sales mis-posted as out-of-scope or excluded entirely produce an understated Box 6, which is one of the more reliable triggers for an HMRC enquiry on an Amazon seller's return.

The VCR exposes the classification through six operative columns that drive every pivot: taxable amount, VAT amount, marketplace facilitator flag, B2B flag, ship-from country, and ship-to country. The pivot logic, applied per row, is short enough to commit to memory. Where the facilitator flag is Y, the row contributes the gross value to Box 6 only. Where the facilitator flag is N, the ship-to is UK, and the VAT amount is positive, the row contributes the VAT to Box 1 and the gross value to Box 6. Where the B2B flag is Y and the ship-to is an EU VAT-registered customer, the row is a zero-rated intra-community supply and contributes the gross value to Box 6 only, with the customer's VAT number on file as proof. Refunds and credit notes appear as negative-amount rows and flip the signs on the same contributions.

Northern Ireland adds a wrinkle the VCR exposes but does not resolve. NI follows the Windsor Framework for movements of goods, which means a GB-stocked seller shipping to a customer in NI is not always inside the same online marketplace facilitator treatment as a GB-to-GB sale. The ship-from country and ship-to country fields are how the classification surfaces in the data; the rules themselves sit under the Northern Ireland Protocol guidance from HMRC, which is the right place to send the reader rather than reproducing the framework inline. The practical takeaway for return prep is that GB-to-NI rows deserve a manual review pass, especially where the underlying goods were originally sold to the seller from outside the UK.

The August 2024 fee billing change and the new posting routine

For roughly fifteen years, UK-established Amazon sellers received their fee invoices, FBA fees, referral fees, monthly subscription, and the rest, from Amazon Services Europe S.à r.l. in Luxembourg. The invoices showed no VAT. The bookkeeping treatment was the Amazon Services Europe Luxembourg VAT reverse charge UK posting: the seller booked both an output and an input VAT entry on the value of the imported service, with a net effect of zero on the VAT liability but with all four operative boxes touched. From 1 August 2024 that changed. UK-established sellers were migrated to billing by Amazon EU SARL UK Branch, the same trading group's UK-registered branch, and the invoices now carry UK VAT at the standard 20% rate. The same monthly fee from Amazon produces a materially different journal entry.

The cleanest way to see the change is to take a single £100 fee and post it under both regimes.

Old journal (pre-1 August 2024). Amazon Services Europe S.à r.l. invoices £100, no VAT. The fee is a service received from outside the UK and falls under the reverse-charge rules. The bookkeeping entry increases Box 1 by £20 (notional output VAT on the imported service), increases Box 4 by £20 (matching input VAT recovered), increases Box 6 by £100 (value of the service received, included in net turnover under reverse-charge convention), and increases Box 7 by £100 (purchase, net of VAT). The £20 in Box 1 and the £20 in Box 4 cancel each other out, so the cash effect on the return is zero, but the four-box footprint is real and an HMRC return will not balance if any of them is missed.

New journal (from 1 August 2024). Amazon EU SARL UK Branch invoices £100 net, £20 UK VAT, £120 gross. The fee is now a UK-domestic supply with UK input VAT. The bookkeeping entry increases Box 4 by £20 (input VAT recoverable in the normal way) and increases Box 7 by £100 (purchase, net of VAT). Box 1 and Box 6 are not touched, because the seller is the recipient of a domestic supply, not the maker of one. The cash effect on the return is a £20 input-VAT recovery, not zero.

The most common post-migration error, and the reason every bookkeeper preparing an Amazon seller's return after August 2024 needs a fresh template, is continuing to post the new UK-VAT-bearing invoice as a reverse-charge entry. The mechanical consequence is double-counting: Box 1 picks up a £20 output entry it should not, Box 6 picks up a £100 turnover line it should not, and Box 4 records £40 of input rather than £20. On a quarter of £50,000 of Amazon fees, the error overstates Box 1 by £10,000 and turnover by £50,000. Bookkeepers running an out-of-date posting template against the new supplier name on the invoice are the audience for this paragraph. The fix is to read the issuer name on the PDF: "Amazon EU SARL UK Branch" means the post-migration journal applies, "Amazon Services Europe S.à r.l." means the reverse-charge journal still does.

Sellers using Xero typically post Amazon fee invoices either by manually creating a draft bill against the PDF or by routing the PDF into Xero through one of the data-capture integrations. The same posting decision applies once the bill is in the system: tax rate "20% (VAT on Income)" became "20% (VAT on Expenses)" for the new entity, and Xero's reverse-charge tax codes drop out of the workflow for UK-established sellers. The general workflow on converting PDF supplier invoices into Xero bills covers the upstream capture step that puts the bill in front of the posting decision.

Which entity invoices a given seller is determined by the seller's establishment, not by the marketplace they are selling on. EU-established sellers, including UK companies that have set up an EU establishment for stock-holding reasons, continue to receive Luxembourg-issued invoices from Amazon Services Europe S.à r.l. and continue to operate the reverse-charge journal.

One scope note before moving on. The August 2024 change applied to FBA, referral, and subscription fees. It did not apply to Amazon Sponsored Ads, which are invoiced separately from Amazon Online UK Ltd and have always carried UK VAT for UK sellers. Sponsored Ads invoices have their own reconciliation workflow, covered in the Amazon Sponsored Ads invoice reconciliation workflow, and they should sit on a separate posting line from the Tax Document Library fee invoices in the bookkeeping system.

Three routes from Amazon's documents to a return-ready spreadsheet

Choosing how to actually get a quarter's worth of Amazon documents into a working spreadsheet comes down to two questions: how many orders the seller is processing, and what audit posture they want to maintain. Three routes are credibly in use among UK sellers and their bookkeepers, and each one has a volume band where it fits and a band where it stops fitting.

Route 1: manual download from the Tax Document Library, combined with Power Query. The seller (or bookkeeper) navigates to the Tax Document Library in Seller Central, opens each per-order VAT invoice PDF, parses or OCRs the file, and pastes the resulting line into Excel for pivoting. Power Query takes care of the consolidation step once the files are in a folder. The fit is honest: this works for low-volume sellers, broadly up to around 100 orders per month, and for one-off historical recovery of a closed quarter. The pain point is equally honest. At 500 to 5,000 orders per month the manual route consumes hours per quarter, because each PDF takes several clicks to retrieve through the Seller Central UI and the Tax Document Library does not offer a quarter-wide selection. Practitioner threads on the Amazon Seller community report 3 to 5 minutes per invoice as the realistic UI cost.

The closely-related failure mode on this route is the amazon vat invoice missing for order case: the seller pulls up a known order in the Tax Document Library and finds no VAT invoice attached. Common causes are the order pre-dating the seller's VAT registration, the buyer not having a VAT-eligible address on file, the order falling under the marketplace facilitator rules with the Amazon-issued invoice listed under a different tab, or Amazon's invoicing service issuing the document with a delay of several days after dispatch. The practical fallback in each case is the same: derive the row from the VCR for that order, treat the VCR row as the source of truth for the VAT figures, and flag the row in the working spreadsheet so the audit-grade PDF can be retrieved later if the seller is asked to produce it.

Route 2: VAT Calculation Report with an Excel pivot. For sellers enrolled in Amazon's VAT Calculation Service, the VCR is already a per-order CSV with the VAT figures, the marketplace facilitator flag, the B2B flag, and the country fields needed for the Box derivation. The workflow is to download the monthly VCRs for the quarter, stack them in Excel, add a small set of helper columns for the contribution logic in the previous section, and pivot. This is the cleanest workflow for a disciplined VCS-enrolled seller who is comfortable in a CSV-only flow and does not need the per-order PDFs in front of them for return prep.

The limitation is the audit posture. The VCR does not produce the audit-grade per-order PDFs that an HMRC inspection would expect to see, and the question of how to retain those PDFs in parallel is where the amazon tax document library bulk export problem reappears. The Tax Document Library does offer a batch-download utility, but Seller Central documentation variously cites 7-day and 3-month windows for the per-batch cap, and there is no single-action quarter-wide bulk download for the per-order sales invoices. A VCS-enrolled seller running Route 2 typically ends up running a slow background process to pull the parallel PDFs for retention, even though the return-prep figures themselves come straight from the VCR.

Route 3: batch extraction of the Tax Document Library PDFs into a consolidated spreadsheet, joined to the VCR for the facilitator-split derivation. For high-volume sellers (typically a few hundred orders per month and up) and for multi-client bookkeepers who are preparing several Amazon returns each quarter, the cost-effective path is to treat the folder of Tax Document Library PDFs as the input and produce the working spreadsheet directly. The per-order sales invoices and the seller fee tax invoices share a folder, the extraction pulls the VAT-relevant fields from both, and the resulting spreadsheet joins back to the VCR on order ID for the facilitator-split flags.

This is the route where AI invoice data extraction fits naturally as a tool. The product is designed around exactly this shape of job: a folder of mixed PDFs, a natural-language prompt describing what to extract and how to structure the output, batch processing of up to 6,000 files per session, and a structured Excel or CSV output where every row carries a reference back to the source file and page. A bookkeeper running quarter-end for three Amazon clients can drop each client's Tax Document Library folder into a session, apply a saved prompt that produces the column set the return prep needs, and end the session with three return-ready spreadsheets in a fraction of the time the manual route would consume per client. The product produces the per-order rows reliably, with the audit reference back to the source PDF, but the return-prep judgement calls still sit with the seller or the bookkeeper: facilitator split classification, NI Protocol treatment of GB-to-NI movements, B2B reverse-charge treatment, and retrospective credit notes are all the seller's call rather than the tool's.

The working spreadsheet schema your quarter needs to produce

A return-ready spreadsheet for a UK Amazon seller's quarter converges the four document streams into a single sheet with one row per VAT event. The column set below is the working schema; everything in the rest of the article either populates a column or filters on one.

• OrderID — Amazon's order identifier, the join key between the VCR, the Tax Document Library PDFs, and the Settlement Report.
• OrderDate — date of the order, used to allocate the row to a VAT period.
• MarketplaceID — A1F83G8C2ARO7P for amazon.co.uk; non-UK marketplaces carry their own ID and need separate treatment in the pivot.
• BuyerCountry — the ship-to country, controlling Box 6 versus Box 8 allocation and the NI Protocol flag.
• ShipFromCountry — the country the inventory was dispatched from, controlling the deemed-supplier determination and the cross-border classification.
• FacilitatorFlag — Y or N, taken from the VCR; the single most important field on the row for Box-by-Box classification.
• B2BFlag — Y or N, taken from the VCR; identifies zero-rated intra-EU B2B supplies that count in Box 6 but not Box 1.
• NetAmount — net of VAT in the seller's reporting currency (GBP for UK return prep).
• VATRate — typically 20%, 5%, or 0%, but credit notes and certain product categories carry their own rates.
• VATAmount — VAT charged on the row in GBP; zero where Amazon is the deemed supplier.
• GrossAmount — net plus VAT, the figure that contributes to Box 6 turnover.
• CurrencyCode — the currency the original transaction was settled in, relevant where the seller is operating across amazon.de, amazon.fr, amazon.it, or amazon.es in addition to amazon.co.uk.
• FXRateToGBP — the rate applied to translate a non-GBP transaction into GBP, recorded at the row level for audit trail.
• VATBox1Contribution — the £ amount the row adds to Box 1 (output VAT), derived from FacilitatorFlag and VATAmount.
• VATBox4Contribution — the £ amount the row adds to Box 4 (input VAT recoverable), populated where the row is a fee invoice and zero otherwise.
• VATBox6Contribution — the £ amount the row adds to Box 6 (net turnover), derived from GrossAmount with the facilitator and B2B treatment applied.
• VATBox7Contribution — the £ amount the row adds to Box 7 (purchases, net of VAT), populated for fee-invoice rows.
• AmazonVATInvoiceNumber — the invoice number on the per-order PDF or on the Tax Document Library fee invoice.
• AmazonDocumentPDFFilename — the filename of the audit-grade PDF retained by the seller, the link back to the source evidence on inspection.

A handful of the columns are non-obvious enough to flag. ShipFromCountry and BuyerCountry together drive both the Northern Ireland classification and the EU-spillover treatment, and a row that carries one but not the other is not safely classifiable. FXRateToGBP matters where the seller is making sales on amazon.de or amazon.fr without a separate currency-of-supply conversion already applied to the VCR; HMRC accepts a published-rate or sale-date convention provided it is consistent. AmazonDocumentPDFFilename is the column that connects the spreadsheet row back to the audit-grade evidence file the seller is required to retain, and it earns its place by surviving an HMRC enquiry six years later, when the rest of the bookkeeping system may have moved on.

The contribution-column convention is worth stating explicitly. Storing the Box 1, Box 4, Box 6, and Box 7 contributions per row, rather than computing them at pivot time, means the spreadsheet survives later corrections without breaking the formula trail. A refund or credit note becomes a new row with negative contributions in the relevant columns; the quarter total falls out by summing each contribution column across rows in the period.

The non-VCS seller path and the boundary cases at the edge of UK-domestic

A meaningful slice of UK Amazon sellers do not run on VCS. Some decline enrolment because their accountant prefers to manage invoicing externally, generating per-order VAT invoices outside the Amazon flow and treating Amazon's documents only as a transactional log. Others, particularly smaller UK-domestic-only sellers, see the VCS configuration overhead and the seller-side responsibilities as not worth the return on a clean home-country footprint. Either way, the non-vcs amazon seller vat return uk workflow has to build from the documents these sellers actually have, because the VAT Calculation Report is not one of them.

The substitute is two reports in combination. The Settlement Report under Reports → Payments carries the per-transaction lines, joining sales, refunds, and fee deductions to each fortnightly disbursement. The Date-Range Transactions Report under Reports → Payments → Date Range Reports gives the same data with arbitrary period boundaries, which is what a quarter-end usually needs. Together they reproduce most of what the VCR would have supplied at the transaction level, with one structural difference. Where VCS sellers receive the VAT rate and amount per row from Amazon, non-VCS sellers carry the VAT rate from the product configuration in Seller Central. Each ASIN has a VAT rate setting that Amazon applies at the point of sale, and the return-prep workflow has to trust that catalogue setting unless the seller has a parallel record of what VAT was actually charged. Data hygiene on the product catalogue, in particular for products that have moved between zero-rated, reduced-rate, and standard-rate categories, is the gating issue on this path.

A second issue for non-VCS sellers is that the marketplace facilitator classification is not surfaced as a flag the way the VCR exposes it. The seller has to derive it from the ship-from country, the seller's establishment status, and the consignment value, applied per row, against the operative rules in the marketplace section above. This is mechanical work once the rule logic is encoded as a formula, but it is the seller's responsibility to do it rather than Amazon's to flag it.

Boundary cases sit at the edge of a cleanly-UK-domestic quarter. They show up in most sellers' data at low volume, and they have to be classified rather than ignored.

• Occasional EU B2C sales below the €10,000 cross-border threshold. Where a UK-established seller makes occasional sales to consumers in EU member states and total cross-border sales for the calendar year are below the OSS-eligibility threshold of €10,000, the sales are treated as UK-domestic outbound for VAT purposes. They contribute UK VAT to Box 1 and gross to Box 6, with no OSS or member-state-specific filing implication. Once the threshold is crossed, the seller has to register for OSS or for VAT in each destination state, and the workflow becomes the Pan-EU one rather than this one.
• B2B sales to VAT-registered EU buyers. Where the buyer provides a valid EU VAT number that the seller has on file, the supply is zero-rated. The row contributes gross to Box 6 and zero to Box 1, with the customer's VAT number recorded against the order as the evidence that supports the zero-rating on inspection.
• Refunds and credit notes. Refunds issued in the same quarter as the original sale net cleanly against that quarter's Box 1 and Box 6 figures. Refunds issued in a later quarter against an earlier sale either adjust the original return (under the seller's accounting policy on retrospective adjustments) or land as a negative-contribution row in the current quarter; the contribution-column convention from the schema section makes the second approach straightforward to track.
• Import VAT on goods the seller is bringing into the UK from outside. Where the seller is importing stock to the UK, the import VAT due at the border is typically accounted for through Postponed VAT Accounting rather than paid up front and recovered later. The full mechanics of UK postponed VAT accounting for imports are out of scope for this article, but the rows the import generates (Box 1 entry for the postponed VAT, matching Box 4 entry for the recovery, Box 7 entry for the value of the goods) have to sit alongside the Amazon-sourced rows in the same working spreadsheet.

One scope marker before closing. Once a seller's stock crosses an EU member-state border, typically through Pan-EU FBA, the workflow leaves the territory this article covers. The Amazon VAT Transactions Report (AVTR) becomes the relevant document, OSS quarterly returns enter the picture for cross-border B2C sales above the €10,000 threshold, and the deemed-supplier rules under EU regulation operate alongside (and not always in parallel with) the UK marketplace rules. The Pan-EU article is the right destination for that workflow; everything in this one is the UK-domestic baseline that sits underneath it.

HMRC's six-year retention rule and Amazon's five-year archive

HMRC requires the seller to retain VAT records, including the underlying VAT invoices, for six years from the end of the relevant accounting period. Amazon's Tax Document Library retains downloadable VAT documents for approximately five years before they fall off the surface. The two windows do not line up.

The operational consequence is straightforward and easy to overlook. A seller who relies on Amazon's archive as their retention strategy will, in year six of any HMRC enquiry window, find that the per-order PDFs and the fee invoices for the period in question are no longer available through Seller Central. The seller is still required to produce them. There is no recovery path back into the Tax Document Library once the documents have aged out; the seller has to have retained them somewhere of their own. Self-retention is therefore not a best practice in the sense of a preferred convention. It is the only practice that satisfies the rule.

This is the durable reason periodic bulk extraction matters more than the per-quarter convenience suggests. The quarterly return is the proximate trigger that brings a seller into the Tax Document Library at all, and the working spreadsheet is the obvious deliverable from each visit. But the reason the practice has to be repeatable, and the reason the archive has to live in the seller's own systems rather than Amazon's, is the year-five-to-six gap. Every quarter the seller completes is a quarter whose PDFs need to be retained on the seller's side, indexed against the working spreadsheet that summarised them, and held against the possibility that HMRC asks for the underlying evidence in year six. The seller who treats Amazon's archive as their own storage is one inspection away from a problem.