The difference from a PDF, in one line
A PDF is a picture of an invoice. A structured e-invoice is the invoice as data.
Both contain the same information as far as a person is concerned. The difference is what a computer can do with them without guessing. In a PDF, the supplier VAT number is ink in a particular position, and software has to find it, read it and hope. In a structured e-invoice it is a field, labelled, in a known place, with a known format. Nothing is inferred.
That is the entire point of the change. Revenue describes e-invoicing as the electronic transmission of structured invoices through an end-to-end digital process, and it is explicit that the current practice of issuing PDF invoices or scanned paper invoices will not satisfy the new requirements.
An emailed PDF is not an e-invoice under these rules. Neither is a scanned paper invoice, a photographed one, or a PDF with an XML file attached out of courtesy rather than as the actual invoice.
What EN 16931 is
EN 16931 is the European standard that defines what an electronic invoice must contain. Revenue states that the ViDA Directive requires e-invoice structures to comply with European Standard EN 16931, using structured data formats that enable automatic processing.
The useful thing to understand about it is that EN 16931 is a data model rather than a file format. It defines the meaning of each element, the supplier, the customer, the line items, the tax rates, the totals, the payment terms, and the rules that govern them. It does not dictate one single file that every invoice must look like. That is why two invoices can both be valid EN 16931 documents and still differ when you open them.
The European Commission's EN 16931 documentation sets out the core data model and the compliance criteria, along with Core Invoice Usage Specifications, which are permitted subsets that a country or an industry can define on top of the core without breaking its rules.
In practice you will not be writing XML. Your accounting software will produce a compliant file, or it will not, and that is the question to put to your supplier.
Why Ireland is requiring it
Structured invoicing is the foundation of real-time reporting. Once the invoice is data, a subset of that data can be sent to Revenue as the transaction happens rather than aggregated into a periodic return months later. Revenue is introducing both together: from 1 November 2028, VAT-registered large corporates must issue e-invoices and report to Revenue in real time for domestic B2B transactions.
Ireland's rules sit under the EU's VAT in the Digital Age package, adopted on 11 March 2025. Revenue has noted that until now Ireland has been one of very few EU Member States not yet operating or rolling out mandatory e-invoicing.
What it changes for a business
Sending. If you are inside the scope of a phase, your system has to produce a compliant file and get it to the customer through whatever channel is specified.
Receiving. Every business in Ireland must be able to receive structured e-invoices from 1 November 2028, whether or not it has to issue them. Receiving means your system can accept the file, validate it against the standard and do something useful with it, not that somebody can open it.
Data quality. This is the part that surprises people. Structured invoicing validates fields that a PDF process quietly tolerates. A missing or mistyped customer VAT number, a tax code applied by habit, an inconsistent unit description: in a PDF workflow a person fixes these without anyone noticing. Against a standard, they fail. Cleaning up invoice master data is the cheapest preparation available and it is useful whether or not the dates move.
Scanning and OCR. If your current invoice handling depends on reading documents, that capability is aimed at a format the mandate is retiring for in-scope transactions. It will still be needed for years, because invoices from businesses outside the phases keep arriving as PDFs, but it stops being the direction of travel.
How the invoices will actually move
Less is settled here than vendors suggest, and it is worth being careful.
Revenue has said the new system will use existing technical infrastructure including the Pan-European Public Procurement Online framework, known as Peppol, which is already used in Irish public sector e-invoicing. One point is often misstated here: the 2019 regulations (S.I. 258/2019) oblige public bodies to receive and process structured e-invoices, and they did not apply to sub-central bodies until 18 April 2020. They place no obligation on suppliers to issue them, so business-to-government e-invoicing has never been compulsory for the supplier. Revenue is working with the Office of Government Procurement, Ireland's Peppol authority. Revenue has also said it will consult industry experts to evaluate the mechanisms for effective e-invoicing and reporting, and that it will publish detailed technical specifications well in advance of each phase.
Several software vendors already describe a specific Peppol exchange model as decided for Ireland. Revenue's own published material does not go that far. Until the specifications are out, treat the transport question as open and be wary of anything sold on the basis that it is closed.
What to do about it now
Ask your accounting software supplier one question in writing: what is your roadmap for EN 16931 structured e-invoicing and Irish real-time reporting. Keep the answer. A supplier with no answer in 2026 is the thing to worry about, not the format itself.
Then clean the invoice data you already hold, because that work is needed regardless and it does not depend on any specification Revenue has yet to publish.
For the dates and who is caught by each phase, see when does Irish e-invoicing start. For what all of this means for an accounting practice and its clients, see Ireland's e-invoicing mandate and your practice.