Summary

  • VAT invoices must be issued as e-invoices from 1 April 2029; possible digital reporting is a separate, undecided policy track.
  • HMRC is asking whether selected data could serve defined purposes. Its consultation does not send every invoice or every field to the tax authority.

Britain has put a date on the invoice format. It has not put a date on a new tax-data feed. That distinction is the whole story.

From 1 April 2029, VAT invoices will have to be issued as e-invoices. Buyers and suppliers will exchange structured invoice data electronically. The government’s separate consultation, published on 28 October and open until 20 January 2027, asks what further use might be made of that data. It is an invitation to test a case, not an announcement that HMRC will receive every invoice.

The consultation defines digital reporting as possible access to selected e-invoice data for defined purposes. It says any such arrangement would require separate policy decisions. There is no preferred reporting model, detailed data specification or legislation in the document. The format mandate is scheduled; the state’s access rights are still a question.

That difference is easy to blur because structured data makes reuse look effortless. Once an invoice is machine-readable, someone can imagine sending a copy to the tax authority, matching it against a return or using it to flag a repayment. But a data format answers how systems exchange information. It does not answer who may retrieve a field, under what authority, for which purpose, for how long, or how an error gets corrected.

HMRC is asking about practical gains. Better data might help a business spot a tax mistake earlier, reduce repeated information requests, support faster and more targeted VAT repayment checks, or enable new software services. Each is a proposed benefit to investigate. The consultation supplies no measured saving or outcome. A prompt that prevents an error could help both sides; a data feed that produces another query for the same records could simply give administration a cleaner way to ask twice.

That is why the burden question matters as much as the technology. The consultation asks about costs for businesses, software providers and government, and whether smaller firms, particular sectors or organisations on legacy systems would face different effects. It also asks whether existing software, Peppol or EDI routes could provide selected information without forcing businesses to re-enter it. A route that works for a large finance platform may still leave a small supplier paying for an adapter, a support contract and time to reconcile exceptions.

HMRC has asked for evidence on these differences; the public material does not quantify them.

The same document puts privacy and commercial confidentiality on the table: data minimisation, access controls, corrections, retention and deletion, transparency, accountability and governance. Those are not accessories for a later technical team. They define whether the arrangement is a bounded service or a broad new reporting layer. If a field is collected for one purpose, who can reuse it? Who sees it? Can a business inspect the record HMRC relied on? How quickly can a mistake be corrected before it prompts a repayment hold or another intervention? The consultation raises these questions without yet answering them.

The wider-government case needs a tighter boundary still. HMRC says broader public-sector use would involve aggregated data, clear purpose, governance and safeguards. Aggregation can reduce exposure, but it does not define a purpose by itself. A proposal still has to identify the function, the minimum data needed and the people allowed to act on it.

There are two policy clocks now. The e-invoicing roadmap plans a technical-standards consultation for Spring 2027. It expects detailed invoice requirements to be developed between October 2027 and April 2028, with at least 12 months’ notice before the April 2029 requirement. The digital-reporting consultation runs alongside that work but may only lead to options, another consultation and then a separate decision. The invoice clock is counting down; the access clock has not started.

The useful test for any eventual proposal is plain: name each field, purpose and recipient; show the access, correction and retention rules; publish the net cost by business type; and identify which duplicate reports or manual requests disappear. If the new channel adds data delivery while the old paperwork survives, the promised simplification has failed its first test. A common invoice standard is a rail. It is not a warrant to board every carriage.

Official sources: HMRC’s digital-reporting consultation; the e-invoicing implementation roadmap.