ERP Implementation Consultant, UK

Common reasons UK ERP rollouts run into trouble

UK ERP projects tend to falter in familiar places, and most of them sit in the space between the partner's scope and the business's daily work.

• VAT treated as configuration only. Tax codes are set up early, but nobody tests whether the codes actually feed the right boxes on the return until the first live quarter is due.
• Sage nominal codes copied wholesale. A chart of accounts that grew over many years, with departments and cost centers stuffed into account numbers, is moved across instead of being redesigned around dimensions.
• Bank files left until the end. The Bacs export or bank feed is assumed to work, then fails the bank's format checks the week before go-live.
• The SOW is not read by the business. Data cleansing, report building or user training turn out to be client tasks, and nobody has planned the time.
• Approval is informal. Designs are agreed in a call, not signed off, so disagreements resurface during testing.
• Payroll is forgotten. Even when payroll stays in its own software, the journal import and department mapping need building and testing.

None of these is unusual, and none requires a dramatic intervention. They need someone on the client side who owns the plan for each and checks progress weekly. If your project already shows several of these signs, ERP recovery describes how I reset a project that has drifted.

Working alongside a UK implementation partner

A good partner wants an organized client. Decisions arrive on time, requirements do not move every week and testing is done by people who know the processes. My role is to provide that organization without getting in the way of the partner's own methodology.

In practice, I hold a weekly session with the partner's project lead covering status, blockers and the decisions due that week. I keep a decision log that records the option chosen, the reason and who approved it. When a change request arrives, I check it against the agreed requirements, ask whether it is a genuine new need or a gap in the original design, and present it to your sponsor with the partner's estimate and the timeline impact. A short steering meeting covers the risks that need director-level attention.

I also read every design document with your process owners before it is signed. That is where many issues can still be fixed cheaply: a costing method chosen without the finance team, an approval route that bypasses a control your auditors expect, or an intercompany process that only works one way.

The partner keeps ownership of configuration and technical delivery. The business keeps ownership of what is acceptable. Keeping those roles apart is the main protection against a system that is technically finished but not fit for use. The general approach is described under ERP implementation.

Migrating from Sage, Xero and older UK systems

UK migrations most often start from Sage 50, a larger Sage product, Xero or QuickBooks, sometimes with a separate stock or job system alongside. Each has its own quirks, and the partner's import tools only work well once the data has been cleaned and mapped by people who understand it.

Early on, finance needs to decide how much history to bring across. Many businesses migrate opening balances and open items, and keep read-only access to the old system for history. Others bring in a period of summarized or detailed history for reporting. Your accountant should agree the approach, particularly where records must remain accessible for HMRC.

For each trial load I check:

• Nominal balances by company, agreed to the old trial balance at the cutover point.
• Open sales and purchase ledger items by document, including VAT on unpaid invoices where cash accounting or similar schemes apply.
• Stock on hand and its valuation per warehouse, tied back to the balance sheet.
• Customer and supplier records, including VAT numbers, bank details and payment terms.
• Fixed asset registers if depreciation moves to the new system.

Where departments or cost centers were embedded in account codes, I map old codes to new dimensions with the finance team so comparatives still make sense. The method is covered in more depth on ERP data migration and the ERP migration checklist.

Testing and timing a UK go-live

UAT for a UK business must cover more than raising an invoice. I write scripts from your real transactions and have business users run them: standard and zero-rated sales, a reverse charge supply where relevant, an import, a euro receipt with an exchange difference, a Bacs payment run accepted by your bank, a direct debit collection if you use them, and a complete month-end close. A test VAT return is produced from UAT data and compared box by box with what your accountant expects.

The go-live date then needs to work with the UK calendar:

• VAT periods. Switching at the start of a VAT period avoids a return assembled from two systems. If that is not possible, plan exactly how the split return will be prepared and checked.
• Financial year-end. Starting a new year in a new system keeps comparisons clean, though the people closing the old year and preparing for audit are the same people you need for cutover. Agree the trade-off with your finance director and accountant.
• Payroll. If payroll moves systems, a mid-year change brings year-to-date figures and RTI continuity into scope, so the payroll provider and your advisor need to be involved early.
• E-invoicing. If customers or future rules require structured e-invoices, test the connector and message flow before cutover rather than after.

My pages on UAT and go-live support go further into both.

Hypercare, the first VAT return and remote support

Go-live is the start of the hardest stretch, not the end of the project. During hypercare, a daily triage call with partner consultants and super users sorts genuine defects from training needs and from enhancement requests that belong in a later phase. Each issue has an owner and a target, and the sponsor receives a brief daily update.

A pair of milestones matters most. The first month-end close in the new system shows whether bank reconciliations, stock, receivables and payables hold together. The first live VAT return shows whether the tax code design really works. I work through both with your finance team and the partner, and anything that needs fixing goes into a stabilization backlog with proper estimates.

All of this runs remotely. Calls fall inside the UK working day, recorded walkthroughs let staff at other sites catch up, and daily logs are shared so everyone sees the same picture. On-site presence around go-live is possible by arrangement if your team would benefit from it.

If you are still choosing a system or a partner, the UK ERP selection consultant page explains how I run that stage. For the broader view, see ERP consulting in the UK, the freelance engagement models or the UK overview.