‹ Back

With mandatory e-invoicing due to take effect in the UK from April 2029, organisations are beginning to consider what the changes might mean for their finance systems and processes.

 

For universities and charities, the questions may be broader than simply how to issue and receive invoices. There may be different types of income to consider, from research and commercial activity to grant funding, alongside relationships with overseas suppliers, partners and funders.

 

Before considering the practical implications, it is worth understanding some of the terminology.

 

 

What is an e-invoice?

At first glance, an e-invoice might sound like any invoice that is created or received electronically. In practice, there is an important distinction between an electronic copy of an invoice and a structured e-invoice.

 

A PDF invoice sent by email is electronic in the everyday sense, but it is essentially a digital image or document. Someone may still need to read the information, enter it into a finance system and process it.

 

A structured e-invoice is different. It contains invoice information in a standardised digital format that can be exchanged directly between systems and processed automatically.

 

For example, rather than receiving a PDF and manually entering the supplier name, invoice number, date, VAT amount and total, a finance system can receive those fields as structured data and use them in its normal processing workflow.

 

This is the distinction that matters for the future UK mandate. The intention is to move towards structured invoice data that can be exchanged and processed consistently, rather than simply replacing paper invoices with PDFs.

 

 

How does e-invoicing work?

The basic principle is straightforward: invoice information is created in one system, transmitted electronically and received by another system in a format that it can understand.

 

Imagine a university purchasing equipment from a VAT-registered UK supplier.

1. The supplier creates an invoice in its finance or accounting system.
2. The invoice is converted into the agreed structured format.
3. It is transmitted through an e-invoicing network.
4. The university receives the invoice data into its own finance system.
5. The invoice can then be validated, matched to the purchase order and processed for payment.

 

The aim is to reduce the need for manual intervention and make the exchange of invoice information more consistent.

 

This does not mean that every invoice will automatically be approved and paid. Organisations will still need appropriate checks and controls, including purchase order matching, approval workflows and verification of supplier details.

 

The technology supports the process, but the organisation still needs to decide how that process should operate.

 

 

What is Peppol?

One of the terms appearing frequently in discussions about e-invoicing is Peppol.

 

Peppol is an international framework that allows organisations using different finance and accounting systems to exchange electronic documents, including invoices, using common standards and network arrangements.

 

The UK government has confirmed that Peppol will be the core interoperability framework for the UK’s e-invoicing regime.

 

The important point is that Peppol is not itself a finance system or an accounting package. It provides a common way for different systems to communicate with one another.

 

For example, a university using Oracle Fusion should be able to exchange a structured invoice with a supplier using a completely different finance system, provided the relevant systems and service providers support the required standards.

 

This is particularly relevant for organisations with large and varied supplier bases, where it would be impractical to establish a separate technical connection for every trading relationship.

 

 

What is an access point?

You may also come across the term access point.

 

An access point is a service that connects an organisation to the Peppol network. It handles the technical requirements for sending and receiving documents in accordance with the network's standards.

 

In practice, most organisations will not need to connect directly to Peppol or manage the network themselves. Their finance system or e-invoicing software provider may provide this functionality, either directly or through an integrated service provider.

 

The important consideration will be whether the organisation's chosen software and provider can support the future UK requirements and exchange invoices with the systems used by its suppliers and customers.

 

 

What does interoperability mean?

Interoperability is simply the ability of different systems to exchange information and use it correctly.

It is a fundamental part of making e-invoicing work at scale.

 

Most organisations do not use exactly the same finance software as their suppliers and customers. A university might use Workday or Oracle Fusion, while a supplier uses SAP, Unit4 or a specialist accounting package.

 

Without common standards, each system may structure and interpret invoice information differently. This can create the need for bespoke integrations, manual intervention and additional reconciliation.

 

A common framework such as Peppol is intended to address this by providing agreed standards for the way invoice information is structured and exchanged.

 

It does not mean that every organisation needs to use the same software. Instead, it allows different systems to communicate using a shared approach.

 

 

Does this apply to grant claims?

This is an important distinction for universities and charities, where income can come from a range of sources, including research grants, charitable funding and other forms of external support.

 

The UK mandate is concerned with VAT invoices. It does not mean that every request for payment or claim for funding will need to be issued as an e-invoice.

 

A genuine grant, where funding is provided without any specific goods or services being supplied in return, is generally outside the scope of VAT. In those circumstances, the grant claim is not a VAT invoice and would not ordinarily fall within the UK mandatory e-invoicing requirement.

 

However, the description given to a payment is not decisive. Some arrangements described as grants may, in substance, involve the provision of goods or services in return for payment. The VAT treatment depends on the nature of the arrangement and whether there is a supply for VAT purposes.

 

For organisations with significant grant income, research funding or collaborative arrangements, it will therefore be important to understand which income streams involve VAT supplies and which do not.

 

 

What about cross-border transactions?

The UK implementation roadmap makes clear that the domestic mandate will not require e-invoices for cross-border transactions. The reason is that VAT invoices are not required under the relevant UK invoicing rules for these transactions.

 

However, that does not mean international e-invoicing can be ignored.

 

Other countries are developing or introducing their own e-invoicing and digital reporting requirements. For example, the EU's VAT in the Digital Age (ViDA) reforms include digital reporting requirements for cross-border B2B transactions from July 2030. EU Member States can also introduce mandatory domestic e-invoicing under certain conditions.

 

For universities and charities with overseas suppliers, research partners, subsidiaries or other international relationships, this creates an additional consideration.

 

Even where a transaction is outside the scope of the UK mandate, an overseas organisation may be subject to requirements in its own country. Equally, an international customer, supplier or funding partner may introduce e-invoicing as a contractual requirement, even where there is no specific legal obligation applying to the UK organisation.

 

It may therefore be worth considering international e-invoicing requirements as part of wider finance systems planning, rather than treating the UK mandate in isolation.

 

 

E-invoicing and digital reporting: are they the same thing?

Another term that is likely to become more familiar is digital reporting.

 

Although closely related, e-invoicing and digital reporting are not the same thing.

 

E-invoicing concerns the electronic creation and exchange of invoice information between organisations.

 

Digital reporting concerns the reporting of transaction or invoice data to a tax authority or another relevant body.

 

The two can be linked. For example, a country may use the information generated through e-invoicing to support tax reporting or compliance monitoring. However, introducing mandatory e-invoicing does not automatically mean that every invoice will be reported to HMRC in real time.

 

The UK government has begun exploring the potential future use of structured invoice data through a separate consultation. No decision has yet been made to introduce additional digital reporting requirements as a result.

 

 

What does this mean for your organisation?

Understanding the terminology is a useful starting point, but the real challenge will be understanding how e-invoicing fits into the organisation's existing systems and processes.

 

For universities and charities, this may involve more than the accounts payable team. Considerations could include:

• Procurement: how suppliers are selected, onboarded and supported to exchange invoices electronically.
• Accounts payable: how incoming invoices are received, validated, matched and approved.
• Accounts receivable: how invoices are generated and issued to customers, including commercial customers and other institutions.
• Tax: how VAT treatment is determined and reflected in invoice data.
• Finance systems: whether existing ERP platforms and integrations can support the required standards.
• Research and funding: distinguishing grant claims from transactions that represent supplies for VAT purposes.
• International activity: understanding requirements that may apply through overseas trading relationships or contractual arrangements.

 

The introduction of mandatory e-invoicing is an opportunity to look beyond the technical requirement and consider whether existing processes are working as effectively as they could.

 

Getting the technology right will be important, but so will understanding the tax rules, the underlying data and the processes that connect different parts of the organisation.