ICAEW.com works better with JavaScript enabled.

How to build a digital tax system that works for everyone

Author: Ed Saltmarsh

Published: 16 Nov 2026

Person working on laptop

Digitalising the tax system one initiative at a time risks leaving gaps that won’t be fixed. Ed Saltmarsh explains why a coherent digital infrastructure is vital to build a better tax system in the UK.

So far in our How to build a better tax system campaign, we have identified five critical pillars to building a better tax system; looked at what is wrong with UK tax policymaking and how to reform it; explained why HMRC must change to succeed; set out how the tax profession could be improved; and outlined how pressure can be reduced on the tax tribunals. In our latest paper, summarised below, we focus on the UK’s digital infrastructure.

Background

The UK is digitalising its tax system initiative by initiative without a published blueprint for how it fits together, or how it interacts with other government systems: build first, connect later and hope the joins hold. That is primarily a failure of governance rather than of technology: no one is accountable for the space between the digital systems.

In our latest paper, we make three connected arguments.

  • First, the tax system needs a common architecture for its data and identity, published and applied to every future initiative. It should set out who holds what data and how it should move, so that taxpayers provide data only once, third-party data can be challenged, and everyone who needs particular data can access it.
  • Second, that architecture cannot stop at HMRC’s boundary, because much of the data the tax system depends on is held elsewhere. That means the architecture must address not only how data moves between systems, but its quality, who is responsible for it and how taxpayers and agents can challenge errors.
  • Third, when government requires taxpayers to interact with it digitally, it takes on obligations of its own: to the users of software it has in effect mandated, to agents acting on behalf of taxpayers and to those who cannot easily go digital.

Defining ‘digital infrastructure’

Digital infrastructure can mean almost anything, so this chapter draws a boundary around three areas:

  • the digital systems taxpayers and businesses run for their own purposes;
  • HMRC’s internal use of technology; and
  • the interaction layer between the two, which covers identity verification, filing software, application programming interfaces (APIs) and the communications passing between government and taxpayers.

This chapter is primarily concerned with the third area and its effect on taxpayers and their agents. HMRC’s internal systems are the subject of the first pillar in this series, which covers HMRC’s administration, including how it governs and uses the data it holds.

HMRC remains the most important single actor in the tax system’s digital infrastructure, and much of this chapter is about it, but it is not the only one. Taxpayers and their agents also have to deal with Companies House, HM Land Registry, the Department for Work and Pensions, Defra, Border Force, the devolved tax authorities and others, often crossing between several systems in a single transaction. A chapter confined solely to HMRC would therefore miss much of the friction taxpayers actually experience

Why now?

There are several major changes curently under way that rely on the same foundations: how taxpayers are identified, how they access services securely, how agents act on their behalf and how data moves between systems. They include:

  • Making Tax Digital (MTD) for income tax, which became mandatory from 6 April 2026 for sole traders and landlords with qualifying income of more than £50,000, with lower thresholds following in April 2027 and April 2028;
  • GOV.UK One Login, which began replacing Government Gateway for new HMRC users in February 2026, with existing users to be moved across gradually and arrangements for agents and organisations still to be settled;
  • Mandatory e-invoicing for business-to-business and business-to-government VAT invoices, which takes effect from April 2029, with a detailed implementation roadmap published at budget 2026; and
  • increased use of AI, on both sides at once: HMRC is beginning to use it to review what taxpayers provide, while taxpayers, agents and software providers are beginning to use it to prepare what they submit.

All of these developments may make sense on their own terms. The risk is that each is designed and delivered as though it were the only thing happening. The prize for getting this right is considerable. With the right data, in the right format, reliably linked to the right taxpayer, HMRC could help taxpayers get things right first time by pre-populating returns and flagging likely errors before filing. It could also target its enquiries more precisely, asking specific questions of those who need to answer them and leaving compliant taxpayers alone.

Five design principles

Our recommendation has two parts. First, government should adopt a set of design principles for the tax system’s digital infrastructure, meaning every system through which taxpayers and agents deal with the tax system, whichever body runs it. Second, it should establish a mechanism for holding future initiatives to those principles.

The five principles below are tests any new digital initiative should be able to pass:

  • One identity: The tax system has no consistent way to identify businesses. Yet a single business identifier, or a robust cross-government framework linking existing ones, could do more to resolve some of today’s hardest compliance problems than any new enforcement power aimed at taxpayers. It would also simplify life for the great majority of businesses that are trying to comply. Similar issues apply for individuals, where the use of an authoritative identifier could streamline the registration and agent authorisation processes.
  • Once, and only what is needed: The state should not ask a citizen for information it already holds. Further, the tax system should not be used to collect information that has no direct bearing on anyone’s tax liability. Every new data requirement should be published with a clear statement of its purpose and why it cannot be met from data that government already holds.
  • Agent parity by design: Digital services are typically designed around what an individual taxpayer needs, with agent access added later, if at all. The principle we propose is simple: if a client can do or see something digitally, their agent must be able to do or see it too, from the day the service launches.
  • Digital obligations require digital accountability: Once government requires taxpayers to interact through software, the quality of that software becomes part of the tax system’s own infrastructure. HMRC published its strategic approach to third party software in March 2026, with enhanced software standards and a delivery roadmap to follow. In our view, those standards should cover the accuracy and security of what a product submits as well as its connectivity, supported by a practical registration process and a test environment.
  • Trust in an automated system: As returns come to be prepared, checked or filed with the help of software and AI, a taxpayer’s ability to stand behind what has been submitted in their name depends on being able to see and understand what was done. We recommend that HMRC, working with developers, agents and taxpayers, and building on its software standards work, publish a framework for the assurance it expects around AI-assisted preparation and filing.

A common architecture

ICAEW’s central recommendation is that the government should publish a common architecture for the tax system’s data and identity and hold every new initiative to it. That architecture would have three parts:

  • a set of principles, agreed by convening a roundtable of the accounting and tax profession, the software industry, business representatives and groups representing taxpayers and citizens;
  • a named owner responsible for it; and
  • a map of what data exists, who holds it and how it flows. The map would not be another transformation roadmap, but would show every party in the system (taxpayer, agent, employer, software provider, HMRC, banks and other public bodies), how they interact and what data passes between them.

Without that, the other recommendations in this chapter risk being pursued as separate projects, in the way MTD, One Login and e-invoicing have been to date.

The government is not starting from nothing. HMRC already holds data on tens of millions of individuals and businesses – the first pillar of this series calls for it to build a comprehensive catalogue of that data – and cross-government API and data standards have existed for several years. What has not yet been published is a model others can design against, covering the relationships that cause the most friction, such as agent to client, business to individual and importer to declaration, and applied to new and legacy systems alike.

Our recommendations for government

  • Publish a common architecture for the tax system’s data and identity, including a map of what data exists, who holds it and how it flows between them.
  • Convene a roundtable of the profession, the software industry, business and taxpayer groups to agree the architecture’s principles and name its owner.
  • Settle which identifiers are authoritative for which purpose and how others are authorised to act on a taxpayer’s behalf, and make sure everyone the tax system deals with can obtain an identifier promptly and digitally.
  • Collect data only once and publish the purpose of every new data requirement and why existing data cannot meet it.
  • Give agents the same digital access as their clients, within the permissions each client grants, whichever government body runs the service.
  • Set standards for the accuracy and security of software that taxpayers are, in effect, required to use, and fund support for those who cannot go digital.
  • Publish a framework for the audit trail and assurance expected of AI-assisted returns.

Where this fits

Some practitioners argue for a more radical starting point: a moratorium on the current rules, an agreed opening position for every taxpayer and a clean slate from which to build a digital tax system. While a clean slate is a laudable idea, we do not think that it is realistic given the questions of fairness and transition it would raise. But the frustration behind it is real: digital transformation built on rules designed for a paper-based system will always be constrained by those rules, however good the technology on top. Our answer is to map what exists, publish the map and require what comes next to fit it, while treating each reform of the underlying rules as an opportunity to design them for a digital system.

The pillar papers in this series ask, one institution at a time, whether the foundations exist to deliver the kind of tax system the revised ten tenets describe. For digital infrastructure, the foundations are being laid, but initiative by initiative and without an agreed plan for how they fit together. We are not calling on government to build yet more infrastructure. We are calling on it to publish how what it is building fits together, to connect it and to make someone accountable for reviewing, improving and adapting it as technology advances. The alternative is to keep digitalising the tax system one initiative at a time, leaving gaps that are rarely fixed because the time and money needed to join them have run out.

Ed Saltmarsh, Tax Technical Manager – VAT and Customs Duties

Open AddCPD icon