ERP Implementation UK: Scope, Costs and Go-Live Planning

ERP implementation UK projects follow the same broad method as anywhere else, but a UK SME also has to fit the work around HMRC deadlines, digital VAT records, payroll reporting and UK GDPR. Those obligations do not pause while a new system is being configured, so they belong in the scope, the budget and the go-live date from the first planning meeting.

The practical problem is that these touchpoints are easy to treat as “the accountant’s side” until late in the project. A VAT quarter split across two systems, a payroll cutover in the wrong week or a supplier contract that is silent on where data is stored can all create work that nobody budgeted for. This guide focuses on those UK-specific decisions. For the general phases of discovery, build, testing and rollout, see our ERP implementation guide.

VAT, payroll and record keeping checks belong in the implementation plan, not after go-live. Illustrative photograph, not an OpsMavix client.

Image credit: Kelly Sikkema, Unsplash License. No edits.

Key Takeaways

• Decide early which UK records the ERP will hold: VAT, payroll, stock, CIS or none of them.
• Making Tax Digital for VAT requires digital records and digital links, so test the full route to HMRC.
• Plan how old VAT and company records stay accessible for the required retention periods.
• Treat the implementation partner as a processor under UK GDPR and put the required terms in the contract.
• Time go-live around VAT quarters, payroll dates and financial year end, not just partner availability.
• Budget for internal staff time and contingency as well as software and partner fees.

In this guide:

• 1. Set the UK Scope Before Choosing Software
• 2. Build a Realistic Budget for a UK SME
• 3. Plan Making Tax Digital for VAT From Day One
• 4. Keep VAT and Company Records Accessible
• 5. Protect Personal Data During Migration
• 6. Time Go-Live Around VAT Quarters and Year End
• 7. Choose a UK Implementation Partner
• 8. Ask the Right Data Residency and Contract Questions
• Frequently Asked Questions
• How OpsMavix Can Help

1. Set the UK Scope Before Choosing Software

Decide what the ERP will be the record for

A UK SME rarely moves every regulated process into one system on day one. Some businesses keep their accounting package and connect the ERP to it; others move the ledger as well. Payroll is often handled by a separate provider. Each choice changes which compliance tasks the implementation must prove.

Write down, for each area below, whether the new ERP will create the record, receive it from another system or have nothing to do with it.

Separate entities and registrations

If the group has more than one company or VAT registration, list them. Ask suppliers to demonstrate how each entity keeps its own VAT records, numbering and reporting. A system that handles one company well may need extra configuration, or extra licences, for several.

Keep packaged and custom options open

Packaged ERP and accounting software can meet UK requirements well when the business fits its standard processes. Configuration or a focused integration may be enough when the existing finance system already works. A custom application or full custom ERP can suit distinctive operations, but still needs a clear plan for VAT records and HMRC submissions. Our bespoke ERP software UK guide covers that build or buy decision in more depth.

2. Build a Realistic Budget for a UK SME

List every cost line, not just the licence

Software subscriptions are usually the most visible number, but they are rarely the whole cost. A useful UK budget separates external spend from internal time and shows VAT treatment clearly.

For a closer look at quote drivers, see what moves the ERP price.

Hypothetical worked budget

The figures below are hypothetical and exist only to show the structure. They exclude VAT. Whether you can reclaim VAT on these costs depends on your own VAT position, so ask your accountant.

In this hypothetical case, internal time adds about a quarter to the external budget. Leaving it out does not make the cost disappear; it simply moves it into overtime, delayed month-end work or rushed testing.

Before accepting quotes, check that each one states what counts as a change, that subscriptions cover the entities you need, and that migration tasks are split clearly between the partner and your team.

3. Plan Making Tax Digital for VAT From Day One

Understand what MTD for VAT requires

HMRC says all VAT-registered businesses should now be signed up for Making Tax Digital for VAT. Its record keeping guidance says you must keep some VAT records digitally and, if you use more than one piece of software, the link between them must be digital.

VAT Notice 700/22 sets out the detail. It explains that a business can keep its electronic account across more than one piece of software, that a digital link is an electronic transfer of data without manual intervention, and that HMRC does not consider copy and paste to be a digital link. It also lists the digital records required, including the time of supply, value and VAT rate for supplies made, and the time of supply, value and input tax claimed for supplies received.

Map the route from ERP to HMRC

HMRC provides a software finder for record keeping and bridging software. Ask any supplier claiming MTD support which product submits the return and how that link is maintained.

MTD checklist for the implementation

• Name the system that will submit VAT returns after go-live.
• Confirm VAT codes and rates in the new system match your current treatment.
• Check that every transfer between systems is automatic, including corrections.
• Run a trial VAT return from test data and reconcile it to the transaction list.
• Agree who authorises the new software with HMRC and when.

If any owners are sole traders or landlords, note that HMRC’s Making Tax Digital for Income Tax guidance applies from 6 April 2026 where qualifying income exceeds £50,000, and from 6 April 2027 above £30,000. That is a separate obligation from the company’s VAT records.

4. Keep VAT and Company Records Accessible

Know the retention periods

HMRC guidance says you must keep VAT records for at least 6 years, or 10 years for records relating to the One Stop Shop or Mini One Stop Shop schemes. For limited companies, gov.uk says company records must be kept for 6 years from the end of the last financial year they relate to, or longer in some cases, such as assets expected to last more than 6 years or transactions covering more than one accounting period.

An ERP implementation often migrates only open balances and recent history. That is reasonable, but the older records still need a home that people can search and that will last as long as the retention period.

Decide where each record type will live

Plan the legacy system exit

Before cancelling an old subscription, test that exported files can be opened and searched without the old software, and check the cost and duration of any read-only access. If company records are lost, gov.uk says you must do your best to recreate them and tell your Corporation Tax office, so prevention is far easier.

5. Protect Personal Data During Migration

Treat the partner as a processor

When an implementation partner handles your customer, supplier or employee data, it will usually act as a processor on your behalf. The ICO’s guidance on what a controller and processor contract must include lists terms such as processing only on documented instructions, confidentiality, appropriate security, prior written authorisation for sub-processors, help with data subject rights and breaches, deleting or returning data at the end of the contract, and allowing audits.

Limit personal data in test environments

The ICO’s guidance on data protection by design and by default asks organisations to consider data protection from the planning stage of any new system, use only the personal data they need, restrict access and consider anonymising or pseudonymising data. It also says a DPIA is required where processing is likely to result in a high risk to people’s rights and freedoms.

In practice, that means asking whether testers really need live employee or customer details. Masked or sample data is often enough for most test scripts, with live data limited to final reconciliation by named people.

Ask where migration files, test copies and live ERP data will be stored and who can access them. Illustrative photograph, not an OpsMavix client site.

Image credit: Taylor Vick, Unsplash License. No edits.

Migration data protection checklist

1. A signed contract with the partner covers the processor terms the ICO lists.
2. The partner has named any sub-processors, including hosting providers.
3. Migration files are transferred securely and deleted when no longer needed.
4. Test environments use masked data where practical.
5. Access to live data during migration is limited to named people.
6. Your privacy information and records of processing reflect the new system.
7. You have considered whether a DPIA is needed and recorded the decision.

6. Time Go-Live Around VAT Quarters and Year End

Avoid splitting a VAT quarter without a plan

Most businesses submit a VAT return every 3 months, and gov.uk says the deadline for online submission and payment is usually one calendar month and 7 days after the end of the accounting period. Going live at the start of a VAT period keeps each return in one system. Going live mid-quarter is possible, but the return then needs figures from both.

Hypothetical worked example: a VAT quarter split across two systems

A hypothetical company has a VAT quarter from 1 January to 31 March and goes live on its new ERP partway through. All figures are hypothetical.

Under the gov.uk rule above, the return for a quarter ending 31 March would usually be due by 7 May. The finance team must combine both systems’ figures, reconcile them to transaction lists and keep the digital link requirements in mind for how the combined figures reach the submitting software. Your accountant should confirm the approach before the cutover date is fixed.

Respect payroll and year-end dates

HMRC says you must send a Full Payment Submission on or before your employees’ payday, and that reports for a new tax year cannot be sent before March. If the ERP will take over payroll, plan the switch around a pay run with spare time before it, and confirm how year-to-date figures carry across.

Financial year end is usually the busiest period for finance teams. Avoid scheduling go-live or final migration during year-end close and audit preparation unless the project is designed around it.

Include CIS only if it applies

If you work in construction and operate as a contractor under the Construction Industry Scheme, include subcontractor verification, deductions and monthly returns in testing. If CIS does not apply, leave it out of scope rather than paying for features you will never use.

7. Choose a UK Implementation Partner

Compare partner types fairly

Each can be the right choice. What matters is evidence that the people who will work on your project understand UK VAT, payroll interfaces and the data protection terms they will sign.

Ask for UK evidence, not general claims

• Demonstrate a trial VAT return from sample data in the proposed set-up.
• Show how a credit note, a VAT code change and a correction flow through to the return.
• Explain how payroll data reaches the ledger and who sends RTI submissions.
• Provide the draft processor contract terms and list of sub-processors.
• Describe the support model after go-live, including UK working hours cover.
• Confirm in writing how you will handle change requests and what they cost.

8. Ask the Right Data Residency and Contract Questions

Find out where data is stored and accessed

Many cloud ERP products store data outside the UK, or allow support staff outside the UK to access it. That is not automatically a problem, but it needs checking. The ICO’s brief guide to international transfers uses a three-step test: does UK GDPR apply, are you initiating the transfer to an organisation outside the UK, and is the receiver a separate legal entity.

If all three apply, the transfer needs to be covered by UK adequacy regulations, an appropriate safeguard such as the International Data Transfer Agreement or the Addendum together with a transfer risk assessment, or a valid exception. The ICO is clear that if no appropriate exception applies, the transfer must not be made.

Contract questions to ask every supplier

Where a full ERP is more than the business needs, an owned inventory automation system delivers the stock-and-orders core with a fixed price and no per-seat fees.

Frequently Asked Questions

What makes ERP implementation in the UK different?

The method is broadly the same, but UK businesses must plan around Making Tax Digital for VAT, VAT and company record retention, payroll RTI where payroll is in scope, and UK GDPR. These affect scope, testing and the go-live date.

Does a new ERP need to be MTD compatible?

Only if it holds VAT records or submits returns. If it passes transactions to an accounting package that submits, the link between the two must be digital. HMRC says copy and paste is not a digital link.

How long should we keep the old system’s records?

VAT records must be kept for at least 6 years, or 10 for One Stop Shop or Mini One Stop Shop records. Company records generally need keeping for 6 years from the end of the financial year they relate to, sometimes longer. Plan an archive before cancelling the old system.

When is the best time to go live?

Usually at the start of a VAT period, away from payroll dates and outside year-end close. Mid-quarter go-lives work, but the VAT return will need figures combined from both systems.

Is our implementation partner a processor under UK GDPR?

Usually, if it handles personal data on your instructions. The ICO lists terms the contract must include, such as documented instructions, security, sub-processor approval and deletion or return of data at the end.

Can our ERP data be hosted outside the UK?

It can, but check whether the restricted transfer rules apply and which mechanism covers the transfer. The ICO’s three-step test is a good starting point, and your contract should name the countries and sub-processors involved.

How much should a UK SME budget for ERP implementation?

There is no reliable single figure because scope varies widely. Build a budget from every cost line, add internal staff time and contingency, and compare quotes on the same scope.

How OpsMavix Can Help

OpsMavix can map how orders, stock, purchasing and finance records move through your business today, then define which records a new system should own and which should stay in your existing accounting or payroll tools.

That may involve connecting systems you already use, building an invoice approval workflow, an inventory automation system, a wholesale order management system or a project operations dashboard, or developing a full custom ERP where that fits. For a wider view of the options, see our operations management system guide.

Contact OpsMavix with a recent VAT return working file, a list of the systems that touch it and the handoff that causes the most rework. We can use that evidence to define requirements and a practical pilot.