TRTrackmeshflow
Guides › Buyer's Guide

Cloud ERP in the UK: Making Tax Digital, 2029 E-Invoicing, Costs and Go-Live Timelines

UK VAT filing already has to be digital, and mandatory B2B e-invoicing is planned for April 2029. Here's what to require from a cloud ERP now, what it costs, and how long go-live takes.

Trackmeshflow editorial team · November 2026 · 9 min read

What a UK Finance Team Should Demand From a Cloud ERP Now

If you're choosing a cloud ERP for a UK entity, two dates matter. The first has passed: Making Tax Digital (MTD) for VAT has applied to every VAT-registered business since April 2022. The second is coming. The government has announced mandatory e-invoicing for VAT invoices between businesses, and to the public sector, from April 2029. A system you sign for now will probably still be live when that rule starts, so test it against both.

A sound cloud ERP UK shortlist has to clear four checks:

  • MTD for VAT filing built in. The ERP submits returns to HMRC through the API, with no spreadsheet steps in between.
  • UK VAT logic that holds up in practice. That covers Northern Ireland goods rules, the domestic reverse charge and postponed import VAT.
  • A credible plan for structured e-invoicing. In practice that means Peppol.
  • UK GDPR-compliant data transfer terms. These must cover the hosting region, support staff and sub-processors.

The same checks apply to a multinational adding a UK subsidiary to a global instance. Many group ERPs handle UK VAT well. Some only handle it on paper. The sections below show how to tell them apart.

Advertisement

Making Tax Digital ERP Compliance: What 'Compatible' Has to Mean

Under MTD for VAT, businesses keep digital records and file returns through software that connects to HMRC's API. Every step between the source transaction and the submitted return must be a "digital link." Retyping a figure, or copying and pasting one, breaks the chain. A Making Tax Digital ERP setup that exports to Excel, adjusts the numbers, then uploads through bridging software can be compliant if the links stay digital. It's still the weakest point in most setups, because one manual paste undoes it.

Ask vendors to show these in a live demo, not on a slide:

  • Submitting directly from the ERP to HMRC, including authorizing the HMRC connection and renewing it.
  • Viewing VAT obligations and payment liabilities from HMRC inside the system.
  • Drilling down from each of the nine VAT return boxes to the transactions behind it.
  • Posting adjustments and errors from earlier periods with an audit trail, so late corrections stay inside the digital chain.
  • Sending the fraud-prevention headers HMRC requires on API calls.

Microsoft Dynamics 365 Business Central, Sage Intacct, Oracle NetSuite, Acumatica and SAP's cloud editions all offer UK MTD for VAT functionality, either built in or through a localization add-on. The difference is in the detail. Ask who maintains the connector, whether it costs extra, and how quickly it was updated the last time HMRC changed its API.

UK VAT Scenarios That Expose Generic Localizations

Most failures don't happen on standard-rated domestic sales. They happen on edge cases that generic tax engines simplify. Test these in a sandbox with your own transaction types:

  • Northern Ireland. Under the Windsor Framework, goods moving to and from Northern Ireland follow EU VAT rules. That means the XI VAT number prefix, separate tax codes and separate reporting. Distributors shipping from Great Britain into Northern Ireland or the EU need this to work properly.
  • Domestic reverse charge for construction services. Invoices need the correct wording, and the customer accounts for the VAT. Construction firms also need Construction Industry Scheme (CIS) deductions, which are usually handled by a partner add-on.
  • Postponed VAT accounting on imports. Import VAT is declared on the return instead of being paid at the border. The ERP has to reconcile this against HMRC's monthly statements.
  • Partial exemption and capital goods scheme adjustments for groups with mixed activities, such as property, finance or healthcare.
  • VAT groups and multiple VAT registrations across several entities.

If a vendor answers any of these with "configurable," ask to see it configured. A partner with several UK go-lives behind them should be able to demonstrate each one without a long preparation.

The 2029 UK E-Invoicing Mandate: What's Settled and What Isn't

The UK e-invoicing mandate announced at the 2025 Autumn Budget will require VAT invoices between UK businesses, and to the public sector, to be issued as structured electronic files from April 2029. Government publications point to a decentralized model in which invoices travel between accredited service providers, with Peppol as the expected framework. HMRC is publishing details in stages, and legislation and technical specifications may still change. Treat specifics as provisional until they appear in law.

A few points are reasonably clear:

  • Invoices will need to be machine-readable and structured. A PDF attached to an email won't qualify.
  • Your ERP will need to send and receive invoices through a certified access point, either the vendor's own or a third party's.
  • Accounts payable changes as much as accounts receivable. You'll receive structured invoices that should match automatically against purchase orders and goods receipts.

Other points are open: whether real-time or periodic reporting to HMRC is added later, how invoice rejection and correction will work, and what transition arrangements smaller businesses get. Belgium, Germany, Poland and France have each set their own rules. Don't assume the UK will copy any one of them.

Peppol UK Readiness Checks for Your RFP

Peppol is already used in the UK for some public-sector purchasing, and it's the most likely basis for the 2029 rules. Put these questions in your RFP:

  1. Is the vendor, or a named partner, a certified Peppol access point provider? Is the service bundled into the subscription or priced per document?
  2. Does the ERP generate and validate UBL invoices and credit notes against current Peppol BIS Billing specifications, plus any UK-specific rules once published?
  3. Can inbound Peppol invoices go straight into automated three-way matching, without being converted back into PDFs?
  4. Does the vendor already support live e-invoicing in other countries, such as Belgium, Poland, Malaysia or Saudi Arabia? A track record elsewhere is the best evidence of delivery in the UK.
  5. Will the vendor commit contractually to delivering UK mandate compliance in the standard product, with no extra licence fee?

Question five matters most. E-invoice transaction fees are a growing line in renewal negotiations, so get the commitment agreed while you still have leverage.

UK GDPR ERP Data Transfers: Where Your Records Actually Go

An ERP holds personal data on employees, customer contacts, supplier contacts and sometimes payroll. Under UK GDPR, a transfer to a country outside the UK needs an adequacy regulation or an approved safeguard. Access by a support engineer in another country counts. The Data (Use and Access) Act 2025 adjusted the test for transfers, but the core obligations remain.

For UK GDPR ERP data transfers, check the following:

  • Hosting region. Ask whether UK data centers are available, and whether that's standard or a premium option. Hyperscaler-hosted ERPs on Azure, AWS and Google Cloud commonly offer UK regions. Other vendors may host in Ireland, the Netherlands or Germany, which UK adequacy rules generally cover for the EEA.
  • Support and sub-processor access. Many vendors run follow-the-sun support from the US, India or the Philippines. Each flow needs a basis: the UK–US Data Bridge for certified US recipients, or the International Data Transfer Agreement or UK Addendum to the EU standard contractual clauses elsewhere.
  • Transfer risk assessments. Ask whether the vendor will supply the information you need to complete one.
  • Breach notification deadlines in the data processing agreement that leave you time to meet the 72-hour reporting window to the Information Commissioner's Office (ICO).

Groups that also operate in the EU, the Gulf or India should map every jurisdiction's rules onto one processing agreement. Patching them together after signing creates gaps. Have your data protection officer or counsel review the final terms.

Typical Costs and Timelines by Company Size

The figures below are typical 2026 market ranges in USD. Contracts vary widely with modules, user numbers, discounting and partner rates. UK pricing is usually quoted in GBP and won't convert at parity. Confirm current figures with vendors and implementation partners.

Company profileTypical platformsAnnual subscriptionImplementation (one-off)Go-live timeline
Small: 10–50 users, one UK entityBusiness Central, Sage Intacct, Acumatica, NetSuite$15,000–$60,000$30,000–$120,0003–6 months
Mid-market: 50–250 users, 2–5 entities, some trade with Northern Ireland or the EUNetSuite, Business Central, Acumatica, Unit4, IFS$60,000–$250,000$150,000–$600,0006–12 months
Large: multiple countries, UK as one entity among manySAP S/4HANA Cloud, Oracle Fusion, Dynamics 365 Finance, Infor$250,000–$1M+$600,000–$3M+12–24 months

The biggest cost drivers are data migration, the number of integrations (warehouse management, e-commerce, banks, payroll, transport management), add-ons for construction or Northern Ireland, and a Peppol access point if it isn't bundled. Ask your partner to price UK tax localization testing as its own line, so it doesn't get squeezed when the schedule tightens.

Sequencing Go-Live Around April 2029

Plan backwards from the mandate. If you go live by mid-2027, you have nearly two years to switch on Peppol, test with your main customers and suppliers, and fix how accounts payable handles exceptions. Go live in late 2028 and any slippage collides with the deadline.

A hypothetical worked example: a Midlands distributor has 60 users, ships into Northern Ireland and has two EU customers. It signs in Q1 2027. The schedule looks like this:

  • Months 1–3: design, including VAT code design for XI and GB flows.
  • Months 4–7: build and data migration.
  • Months 8–10: a parallel run covering one full VAT quarter, filing from both old and new systems and comparing totals box by box.
  • After that: Peppol receiving goes live in 2028, then sending, ahead of the mandate.

Two rules help. Never go live in the last month of a VAT quarter. And keep the old system readable for at least six years, the usual UK retention period for VAT records.

Red Flags and a Decision Rule for UK Buyers

Walk away from a vendor, or push back hard, if you hear any of these:

  • "MTD is handled by an export file" when you want direct submission from the ERP.
  • No named UK partner with several completed UK go-lives in your sector.
  • A 2029 e-invoicing roadmap with no contractual commitment and no live e-invoicing in other countries.
  • A data processing agreement that lists sub-processors "available on request" without saying which countries they're in.
  • Per-invoice pricing with no cap at renewal.

The decision rule: shortlist only vendors that can submit a VAT return from the system, demonstrate your three hardest VAT scenarios, and name their Peppol access point. Then compare total five-year cost. HMRC guidance keeps changing, and your position on Northern Ireland, partial exemption or CIS depends on your circumstances, so ask a UK-qualified tax adviser to confirm your setup before go-live.

Quick answers

Do I need a new ERP to comply with Making Tax Digital for VAT?

Not necessarily. MTD for VAT requires digital records and an unbroken chain of digital links to HMRC-recognized filing software, and bridging tools can provide that for older systems. If you're replacing your ERP anyway, choose one that submits directly to HMRC, because spreadsheet steps are where errors and audit questions tend to arise.

Is the 2029 UK e-invoicing mandate definitely using Peppol?

Government publications point to a decentralized model built on the Peppol framework with accredited service providers, but legislation and detailed specifications may still change. An ERP that already supports Peppol is the lowest-risk choice either way. Check the latest HMRC guidance before you finalize contracts.

Can our cloud ERP data be hosted outside the UK?

Yes, provided each transfer has a lawful basis under UK GDPR. The EEA is generally covered by adequacy regulations, certified US recipients can be covered by the UK–US Data Bridge, and other countries usually need the International Data Transfer Agreement or the UK Addendum. Remote support access counts as a transfer, not just the hosting location.

We're a non-UK group adding a UK subsidiary. Can our global ERP handle it?

Often it can, through the vendor's UK localization pack, but test it against your actual UK transactions, especially Northern Ireland goods movements, the domestic reverse charge and postponed import VAT. Confirm that MTD submission and future Peppol support cover the UK entity specifically, and get local tax advice on registration and filing obligations.

Written by the Trackmeshflow editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.