UK: 
USA:
ERPEnterprise resource planning (ERP) is a type of software that organisations use to manage main business processes. migrations are often driven by the need for better data, improved controls and long-term scalability. Yet one critical area is still too often treated as an afterthought, tax.
When tax is not properly considered during an ERP migration, the consequences can be expensive, time-consuming and difficult to unwind. What may feel like a technical implementation decision today can quickly turn into a compliance and operational risk tomorrow.
Tax touches more of your ERP than you think
Indirect tax, in particular, is embedded across multiple processes within an ERP system, including order-to-cash, procure-to-pay, inventory, billing, and reporting. If tax requirements are not designed into these processes from the outset, the system may technically go live, but it will not operate correctly in the real world.
Common issues include incorrect tax determination, inconsistent treatment across jurisdictions, missing data required for tax engines and reporting structures that do not support compliance obligations. These problems rarely surface immediately, but once transaction volumes increase, they become far more visible and far more costly.
Fixing tax after go-live isn’t simple
One of the biggest misconceptions during ERP projects is that tax can be “fixed later”. In reality, post-implementation remediation often requires reworking core data structures, reconfiguring integrations and, in some cases, reversing design decisions that the wider system now depends on.
This typically leads to additional project spend, unplanned delays and disruption to business as usual. Worse still, errors that have already occurred may expose the business to audit risk, penalties and reputational damage.
Automation does not remove the need for tax design
Many ERP programmes rely on tax automation solutions to handle complexity. While tax engines are powerful tools, they are only as effective as the data and processes that feed them.
Without proper tax involvement during migration, automation can simply scale incorrect logic at speed. Product taxability, jurisdiction mapping and transaction flows all need to be carefully aligned with the ERP design to ensure automation delivers the intended benefit.
The real cost is often hidden
The true cost of ignoring tax during an ERP migration is rarely limited to system fixes. It often shows up later as increased manual intervention, workarounds in spreadsheets, delayed close processes and a heavier compliance burden for already stretched teams.
Over time, this erodes confidence in the system and undermines the very objectives the ERP migration was meant to achieve.
Bringing tax in early
When tax is involved from the start of an ERP migration, it becomes a design enabler rather than a risk. Early involvement allows tax requirements to be built into process design, data structures and integrations, reducing rework and supporting smoother delivery.
It also ensures that tax technology, whether embedded in the ERP or delivered through third-party solutions, is configured to support the business as it operates today and as it scales in the future.
Investing in the ERP
ERP migrations are major investments. Ignoring tax during the process can turn that investment into a long-term liability.
By treating tax as a core part of ERP design rather than an afterthought, organisations can reduce risk, avoid costly remediation and ensure their new system delivers real, sustainable value.
If you’re planning or already underway with an ERP migration and want to understand how tax should fit into the process, it’s worth addressing it sooner rather than later.
Whether you’re implementing an ERP for your own organisation or delivering an ERP programme on behalf of a client, having the right tax expertise involved from the outset can make a material difference, and that’s where we can help.
