ERP implementation: Phases, timelines, and pitfalls UK finance teams need to plan for

ERP implementations that hit their business goals almost always have finance team fingerprints on the early decisions: reporting requirements and data quality locked down before design starts, and close processes tested before anyone is ready to go live. If you're leading a mid-market finance team at a company with 50 to 1,500 employees across multiple entities, ERP implementation is one of the highest-stakes projects you'll face. It's also one of the hardest to recover from when your team isn't leading the early calls.

This is general guidance for UK finance teams, not legal, tax, or implementation advice. ERP decisions depend on your specific circumstances, so consult a qualified accountant or implementation adviser before acting on the information covered here.

What is ERP implementation?

ERP implementation is the project of replacing or introducing an enterprise resource planning system across your organisation. For your finance team, it touches every process, from accounts payable and order-to-cash through to management reporting and VAT submission. That's around 30 processes to map before configuration even begins, according to ICAEW research, and each one you don't document properly becomes a potential failure point later in the project.

If you're implementing in 2026 or 2027, overlapping regulatory changes, including Making Tax Digital and FRS 102 lease accounting, raise the stakes on how you design and configure the system.

What are the seven phases of ERP implementation?

The seven phases are discovery and planning, design, development and configuration, data migration, testing, go-live, and post-go-live stabilisation. Recognised vendor methodologies differ in naming and sequencing, but they converge on this broadly similar structure.

We'll focus on the phases where your finance team has the most leverage. Development and configuration is typically implementation-partner-led. Data migration, which finance teams do own, is covered in the pitfalls section below because it's where more projects fail than succeed.

Discovery and planning

You gather requirements, establish project governance, form the implementation team, and create a formal project plan. Your finance team's job here is to map every current financial process, document statutory reporting obligations across IFRS, UK GAAP, VAT, and Making Tax Digital, and nominate finance super users who'll champion the system internally.

Data quality is the most underestimated risk at this stage. Finance teams too often defer data work to later phases, which creates significant delays when issues surface mid-implementation. Gathering reporting requirements upfront shapes every design decision that follows, so consider this the single highest-value activity your team can contribute here.

Design

This is where you document how your organisation will run its processes in the new system. For finance, the single most important decision in this phase is usually the chart of accounts (CoA) design. Getting it right now matters more than almost any other choice you'll make during the project. A well-designed CoA can deliver benefits comparable to a complete reimplementation, which gives you a sense of how much rides on this one decision.

If you operate across multiple European entities, you'll need to make an explicit, documented decision between local statutory convenience and group-level reporting consistency.

Testing

You lead User Acceptance Testing (UAT), where users check that the system works in real finance scenarios. That means running your accountants through every end-to-end workflow they'll rely on after go-live, from invoice processing and payment runs to bank reconciliation, month-end journals, and VAT returns. It also means testing every integration point between the ERP and your accounting software, bank feeds, and upstream spend management tools. The accountant who processes 200+ payables a month needs to be confident the new system handles their specific workflow before anyone signs off.

For higher-risk implementations, parallel running adds another layer of assurance. That means running both the legacy and new systems simultaneously for a defined period so you can compare outputs directly.

Your formal UAT sign-off is the gateway condition for go-live. Testing should be completed before production deployment, full stop. If UAT hasn't signed off, the system isn't ready.

Go-live and stabilisation

Going live in the final week of any month, any quarter-end, or any year-end close period introduces exactly the kind of chaos the new system was supposed to eliminate. The first week of a new month isn't much safer either. Close typically spills into those opening days, so the genuinely lightest reporting window for most finance teams sits mid-month. Month-end and year-end financial statements take precedence over all other business operations for finance teams, so build go-live around that mid-month window.

Go-live is a milestone, not the finish line. Configuration adjustments, workflow refinements, and user support needs typically continue for months afterwards. Plan for that rather than treating go-live as the end of the project.

How long does ERP implementation realistically take?

Timelines are where expectations and reality diverge most sharply. The Panorama 2024 report puts the median ERP implementation at 15.5 months across all organisation sizes. That's a global figure, and whilst no UK-specific benchmark from an authoritative body is available to narrow it down, multi-module configurations, data migration complexity, and change management all extend timelines, meaning complex real-world deployments often run longer than planned.

Panorama Consulting Group's data also shows that around 58% of ERP projects complete within their expected timeline. About 28% finish slightly late, and 11% significantly late. The leading cause of delay shifted from technical issues in 2023 to resource constraints and staffing limitations in 2024. Some degree of overrun is normal, so build it into your project plan from the start.

Timeline overruns matter because they compound every risk in the project. And the most common risks, covered next, are the ones your finance team is best positioned to prevent.

What are the most common ERP implementation pitfalls?

Gartner strategy research reports that 75% of ERP strategies aren't strongly aligned with overall business strategy. For finance teams, the consequences of poor strategy alignment show up in four areas.

Budget overruns from unscoped technology

Around two in five organisations exceed their planned ERP budget, according to Panorama Consulting Group's 2024 data. The leading cause is additional technology needs that weren't scoped at project initiation. Among organisations that significantly exceeded budget, only a third had used technology assessment services beforehand.

For UK mid-market companies, year-one total investment is often presented in broad ranges by providers, but the integration, staffing, and post-go-live costs that drive overruns are frequently excluded. The gap between a vendor's initial quote and the actual total cost of ownership is where finance teams are most commonly caught off guard. Consider building 10% to 20% contingency above the vendor's initial estimate, earmarked specifically for integration work, change management, and the first three months of post-go-live support.

Data migration and chart of accounts failures

Finance owns the data migration, not your implementation partner. An ICAEW evaluation (2019) makes this explicit: the client is responsible for the data itself. That means identifying everything to be migrated, from open AP and accounts receivable (AR) balances and fixed asset registers through to historical transactions and customer and supplier master data.

Supplier master data in particular often needs to be cleaned and imported as part of AP implementation. You'll lead the cleansing effort, remove duplicates, correct coding errors, and validate the migrated trial balance against your source system. That sign-off is yours alone.

What makes this especially difficult is that fixing data problems post-implementation often means a full remediation programme to unpick the issues and redo the work. That's painful, costly, and entirely avoidable with earlier intervention.

A related risk sits in how different teams define the same data. Revenue may mean bookings to your sales team, recognised revenue under IFRS 15 or FRS 102 to your finance team, and cash received to your accounting team. Resolve the conflicts before the chart of accounts configurations are migrated, not after.

Month-end close disruption

An ERP transition can leave your finance team unable to close the books, reconcile cash, or produce auditable accounts. The most thoroughly documented UK example is Birmingham City Council, whose ERP implementation exceeded its original budget by at least £90m, with financial control failures persisting across three consecutive financial years. The Grant Thornton audit found the council struggled to understand its cash position and produce auditable accounts, noting that the level of risk inherent in the solution was not properly understood.

Inadequate change management and strategy misalignment

The people side of an ERP transition is where many projects quietly unravel, even when the technical side is well managed. Finance team members may feel threatened that technology adoption could lead to job losses, and CFOs need to confront this early in the process. Generic train-the-trainer programmes frequently miss finance-specific edge cases. Multi-entity consolidation adjustments, multi-currency revaluations, and period-end accruals all require targeted training that standard programmes rarely cover, which leaves AP clerks, management accountants, and treasury staff underserved.

What UK regulatory requirements affect ERP implementation in 2026 and 2027?

The pitfalls above are difficult enough in a stable regulatory environment. If you're implementing during 2026 or 2027, four overlapping regulatory pressures make them harder, because each one directly affects how the ERP needs to be configured. Getting any of them wrong creates compliance exposure you'll be fixing post-go-live.

Making Tax Digital

MTD for VAT is already mandatory for VAT-registered businesses. HMRC is progressively extending digital record-keeping requirements, with MTD for Income Tax Self Assessment rolling out from April 2026 and the scope widening through 2028. If your ERP implementation doesn't account for MTD-compliant data formats and quarterly reporting capabilities, you risk retrofitting them later.

GDPR and data protection

ERP data migration involves employee payroll data, customer financial records, and supplier payment data, all categories of personal data under UK GDPR. You'll need to complete a Data Protection Impact Assessment (DPIA) covering migrated data before the move.

Under UK GDPR, penalties for serious breaches can reach up to £17.5 million or 4% of annual global turnover, whichever is higher. The Data Use and Access Bill, introduced in October 2024, will amend UK GDPR requirements further, so confirm your data migration approach against the latest guidance before go-live.

FRS 102 lease accounting changes

FRS 102 lease accounting changes effective January 2026 require ERP reconfiguration. Under the revised standard, lessees must recognise most leases on the balance sheet as right-of-use assets with corresponding liabilities. That means your ERP needs new asset categories, amortisation schedules, and disclosure reports that may not exist in your current configuration.

A survey by IRIS Software Group and KPMG, presented at an ICAEW webinar, found that of 500 in-house accountants surveyed in the UK, many were still assessing the impact and hadn't completed the system changes needed to comply. If you operate EU subsidiaries applying IFRS, you'll face similar requirements under IFRS 16, which has mandated on-balance-sheet lease recognition since 2019.

EU e-invoicing mandates

If you have European operations, e-invoicing requirements are tightening. France is mandating structured e-invoicing on a phased schedule starting in 2026, with mid-market companies expected to follow in 2027. Germany, Spain, and Poland are each developing their own mandates on similar timescales.

Your ERP will need to generate compliant invoice formats, typically Factur-X, XRechnung, or Universal Business Language (UBL) depending on the country, and integrate with country-specific reporting platforms. Even if your operations are UK-only today, building e-invoicing capability into the ERP now is cheaper than retrofitting it after go-live.

How to protect your month-end close throughout implementation

So you're facing operational pitfalls that sink most projects, regulatory deadlines that narrow your margin for error, and a timeline that will almost certainly overrun. What can your finance team actually control?

Your first close in a new ERP is the moment everything gets tested for real. During the transition, you're temporarily losing control over the processes you already run to rebuild them in a system designed to work better. These measures help you maintain visibility while the switchover is happening.

Run a dress rehearsal close

Before go-live, simulate a full month-end close in the new system using migrated data. Run your team through AP invoice processing, asset depreciation runs, payment processing, and report outputs, then validate the results against your legacy system. Configuration gaps that only surface under real close conditions are far cheaper to fix here than during a live close.

Define parallel running exit criteria in advance

Set these before go-live, not after. For example, two consecutive month-end close cycles in which outputs from both systems reconcile within a defined materiality threshold. This is a decision your finance team needs to own, not one to leave to the implementation partner.

Plan a structured 90-day stabilisation period

Consider daily stand-ups with finance team leads in weeks one and two, with your implementation partner on-site for the full first month-end close. Every workaround should be documented formally. By month three, a formal post-implementation review measuring financial KPIs against pre-go-live baselines will give you a clear picture of where you are.

Protect spend data continuity

One of the fastest ways to introduce reconciliation gaps is losing visibility over day-to-day spend during the transition. Spend management tools that sit upstream of the ERP can help here by capturing transactions, coding them, and exporting clean data into your accounting system even while the ERP is being migrated. Spendesk integrates with accounting and ERP systems, so spend data can continue being exported into the ledger in a consistent format even when the underlying system is changing.

Niji, a French digital transformation consultancy of around 1,300 employees headquartered in Rennes, faced exactly this challenge while scaling rapidly across six French offices. Using Spendesk, they grew to 12x their original transaction volume while improving receipt recovery from 10% to near-complete, which meant their finance team wasn't choosing between growth and clean data during the transition.

What decisions during implementation matter most?

The difference between the two outcomes is usually visible early. ACCA research describes the divergence well: some finance functions adjust to technological change and end up with clean, accessible data supported by a lightweight digital core. Others remain heavily reliant on a burdensome ERP for month-end. Three decisions determine which path you're on. Data structure, process automation, and integration architecture each lock in choices that are expensive to reverse after go-live.

A successful ERP implementation protects the finance processes that matter after go-live. If your team can preserve clean data, maintain control over month-end, and avoid adding manual reconciliation work back into the process, you're in the first group. The phase where you have the most influence over that outcome is right now, while you're still planning.

If you're also planning how spend management should connect with a new or existing ERP, particularly across European entities with evolving e-invoicing and compliance requirements, Spendesk's integrations are worth exploring while you're still researching.

Frequently asked questions about ERP implementation

How long does ERP implementation take for a mid-market company?

For small and midsize businesses, implementation timelines commonly cited by industry advisers range from three to nine months. Panorama Consulting Group's 2023 and 2024 data shows a median project timeline of 15.5 months across all sizes. Some degree of overrun is the norm, so build it into your project plan.

How much does ERP implementation cost in the UK?

There's no single benchmark, and Panorama Consulting Group's data indicates that around two in five organisations exceed their planned budget, with unscoped technology needs as the leading cause. Costs vary widely by scope, number of users, integrations, and support requirements, so building contingency into your financial planning is advisable.

Should you choose a big-bang or phased ERP go-live?

Fewer than a quarter of organisations use a big-bang approach, according to Panorama Consulting Group. A phased rollout tends to be more manageable for mid-market finance teams, particularly if you operate across multiple entities or if your team can't sustain parallel running for more than two close cycles. Factor in your finance team's capacity and the complexity of your integration environment when deciding.

What should you test before ERP go-live?

Your finance team should lead UAT for every end-to-end financial scenario: invoice processing, payment runs, bank reconciliation, month-end journals, and VAT returns. Parallel running provides the highest assurance. Formal UAT sign-off from finance is a mandatory gate for go-live, and rushing this step is one of the most common contributors to post-go-live disruption.