What is changing and when?
Revenue is replacing a VAT reporting system that has been largely unchanged since 1972. Instead of periodic returns built from aggregate sales and purchases, businesses will issue structured electronic invoices to their customers and report a subset of that invoice data to Revenue in real time. Revenue calls it the most significant modernisation of Ireland's VAT system since VAT was introduced here over fifty years ago, and it is not an Irish initiative alone: it is Ireland's route to complying with the EU's VAT in the Digital Age package, adopted on 11 March 2025 as Council Directive (EU) 2025/516.
The rollout has three phases. Revenue set them out in VAT Modernisation: Implementation of eInvoicing in Ireland, published on 8 October 2025, and maintains a running version on its VAT modernisation timeline.
| Phase | Date | Who has to issue | What they issue |
|---|---|---|---|
| One | 1 November 2028 | VAT-registered large corporates | Structured e-invoices plus real-time reporting, domestic B2B |
| Two | November 2029 | VAT-registered businesses in cross-border EU B2B trade | The same domestic obligation, extended |
| Three | 1 July 2030 | All EU Member States, cross-border EU B2B | Full ViDA e-invoicing and digital reporting |
Two things about that table matter more than the rest of this page.
The first is the line that sits underneath all three phases in Revenue's own diagram: all businesses need to be enabled to receive e-invoices from suppliers. Revenue's large corporates page puts a date on it. From 1 November 2028, all businesses in Ireland are required to be able to receive structured e-invoices. Your smallest client is caught by that sentence on the same day as the largest company in the country. They are not caught as an issuer, and the difference between those two obligations is the single most useful thing you can explain to a client this year.
The second is that only Phase One carries a confirmed day of the month. Revenue has published 1 November 2028 in plain words. For Phase Two it has published November 2029, with no day named at the time of writing, and advisers who quote 1 November 2029 are making a reasonable inference rather than citing Revenue. Phase Three is the ViDA date, 1 July 2030.
What is not changing is worth saying out loud, because it is the first thing an anxious client asks. Revenue states that these changes relate solely to invoicing and reporting processes, and that tax rates, payment requirements and liability calculations remain unchanged. Nobody's VAT bill moves because of this. What moves is how the invoice is built, sent and reported.
Who is caught in each phase?
Phase One is narrower than the phrase "large corporates" suggests, and it is defined by who manages the file rather than by size. Revenue's test, confirmed in a press release on 10 February 2026, is that a large corporate is a VAT-registered business whose tax affairs are managed by Revenue's Large Corporates Division, and that is established or has a fixed establishment in Ireland. There is no turnover figure in the e-invoicing rule itself. If you want a rough proxy, the group turnover threshold for Large Corporates Division is €350 million, up from €190 million, with some cases managed there on sector grounds instead, and Revenue sets that out in its Cooperative Compliance Framework manual. Treat the €350 million as an indicator only. The rule is the division, not the number.
You will not have to work out which of your clients qualify. Revenue has said it will write to large corporates to notify them of their inclusion in Phase One. If a client receives that letter, the date on their calendar is real and they are in the first cohort.
Phase Two, in November 2029, extends the domestic obligation to VAT-registered businesses engaged in cross-border EU B2B trade, the ones benefiting from the 0% VAT arrangements on intra-EU supplies. Revenue's reasoning is that these businesses need to be familiar with the domestic system before the EU-wide one becomes mandatory, and there is a commercial edge to it: under ViDA, businesses trading across EU borders need these systems in order to keep access to those 0% arrangements.
Phase Three, from 1 July 2030, is the ViDA layer itself, applying across every Member State to cross-border EU B2B transactions.
Read those three phases carefully and a gap appears. A purely domestic Irish business, not managed by Large Corporates Division and doing no intra-EU B2B trade, is not named as an issuer in any published phase. It is still caught by the receive obligation from 1 November 2028. That is the correct answer to give a small client who asks whether this applies to them, and it is more precise than the answer most of them will read online, which is that everyone must be e-invoicing by 2030.
What does a structured e-invoice actually mean?
A structured e-invoice is not a nicer PDF. Revenue is explicit about this. The ViDA Directive requires e-invoice structures to comply with European Standard EN 16931 using structured data formats that enable automatic processing, and current practices including issuing PDF invoices or scanned paper invoices will no longer satisfy VAT compliance requirements. Revenue repeats the point in a footnote: issuing PDF invoices or scanned paper invoices will not satisfy ViDA requirements.
The distinction is machine-readability. A PDF is a picture of an invoice. A human can read it, and software can guess at it, but the guessing is the part that goes wrong. A structured e-invoice is a data file, ordinarily XML, in which the supplier VAT number, the line items, the tax rates and the totals each sit in a defined field with a defined meaning. The receiving system does not interpret it. It reads it.
EN 16931 is the European standard that defines those fields. It is a semantic data model rather than a single file format, which is why two invoices can both be valid EN 16931 documents and still look different in a text editor. The European Commission's eInvoicing documentation sets out the compliance criteria and the core data model, along with the subsets, known as Core Invoice Usage Specifications, that a country or sector may layer on top without breaking the core rules.
Two practical consequences follow, and both belong in a conversation with a client.
Scanning stops being a compliance activity. If a practice's current answer to invoice handling is that documents are scanned, OCR'd and keyed, that pipeline is being fed by a format that will no longer count for the transactions inside scope. The scanning does not disappear overnight, because invoices outside the mandate will keep arriving as PDFs for years, but it stops being the direction of travel.
Receiving is a systems question, not a filing question. Being able to receive a structured e-invoice means having something that can accept the file, validate it against the standard and put it somewhere useful. For most small businesses this will arrive as a software update from whoever supplies their accounts package. The practice's job is to know which clients have a supplier who will ship that update and which do not.
On how invoices will actually travel between businesses, be careful with what you read. Revenue has said the new system will use existing technical infrastructure including the Peppol framework, already used in Irish public sector e-invoicing, and that it is working with the Office of Government Procurement as Ireland's Peppol authority. Revenue has also said it will consult industry experts to evaluate the mechanisms for effective e-invoicing and reporting. Several software vendors already describe a specific Peppol exchange model as settled for Ireland. Revenue's own published material does not go that far yet, and detailed technical specifications are still to come.
What does this mean for your clients?
For most clients in a general practice, the honest summary is one sentence: you almost certainly will not have to issue structured e-invoices in 2028, and you will have to be able to receive them.
That framing is worth protecting, because the alternative framing is already circulating and it causes two expensive mistakes. The first is panic buying, where a client with fifteen invoices a month is sold an enterprise compliance platform for a 2028 obligation they do not have. The second is the mirror image, where a client hears that it only affects large corporates, tunes out entirely, and misses the receive obligation that genuinely does apply to them on the same date.
Three groups on your client list deserve a note on the file now.
Clients who supply large corporates. When a Phase One business starts issuing structured e-invoices in November 2028, its suppliers and customers are on the other end of that transaction. A client selling into a Large Corporates Division business will feel the change through their customer's procurement requirements, and probably earlier than the legal date, because large businesses test with real suppliers before a deadline rather than on it.
Clients trading into the EU. These are the Phase Two population, and they carry the sharpest commercial risk on this page, because the 0% VAT treatment on intra-EU supplies is tied to operating the new systems.
Clients on old or bespoke systems. A client on a supported cloud accounting product will receive this as an update. A client on a desktop package three versions behind, or on something a contractor built for them in 2011, will not. That is the group to identify in 2026, because the lead time is measured in years and the conversation is unpleasant if it starts in 2028.
What should a practice do in 2026 rather than 2028?
Nothing you buy in 2026 will still be the right purchase in 2028, because Revenue has not published its technical specifications yet and has committed to doing so well in advance of each phase. So the 2026 work is not procurement. It is knowing your own book.
Segment the client list into issuers and receivers. Three columns. Managed by Large Corporates Division. Trades B2B into the EU. Neither. The third column is most of the list and their only obligation on current information is to receive. This is an afternoon's work with the data you already hold, and it turns a vague national deadline into a specific number of client conversations.
Ask every software supplier one question in writing. What is your roadmap for EN 16931 structured e-invoicing and Irish real-time reporting? Keep the replies. The quality of the answer tells you more about which clients are exposed than any assessment you could run yourself, and a supplier with no answer in 2026 is a supplier to be nervous about in 2028.
Fix the invoice data you already have. Structured invoicing is unforgiving about fields that a person would have quietly corrected. Missing or wrong customer VAT numbers, inconsistent unit descriptions, tax codes applied by habit rather than by rule: all of it survives in a PDF process and none of it survives validation against a standard. Cleaning it is useful in its own right and it is the cheapest preparation available.
Decide who owns this internally. One named person who reads Revenue's updates and reports at the partner meeting. Revenue has committed to further guidance and engagement through the Tax Administration Liaison Committee and its own channels, so the information will arrive. Somebody has to be reading it.
Write the client-facing note once. Most of your clients will ask the same question, and the answer differs only by which of the three columns they fall into. Draft three short versions now.
What not to do in 2026. Do not buy a compliance platform against unpublished specifications. Do not tell clients that everyone must be e-invoicing by 2030, because it is not what Revenue has published. Do not treat the receive obligation as a technicality.
How does this connect to invoice processing automation?
Most invoice processing automation sold today is built to solve a document problem. An invoice arrives as a PDF or on paper, and a system reads it, extracts the fields, guesses at the ones it cannot read, matches the result to a purchase order and sends the exceptions to a person. It works, and it is genuinely valuable now. It is also an answer to a question the mandate slowly removes.
When an invoice arrives as structured data, the extraction step disappears. There is nothing to read, because the fields are already fields. What remains is the part that was always the real work: deciding whether the invoice is right. Is this what we agreed. Does it match what was delivered. Is the VAT treatment correct. Is this supplier who they claim to be. Should it be paid now.
That has a direct bearing on what a practice should build between now and 2028. Automation aimed at reading documents is depreciating. Automation aimed at judging transactions is not, and it works on both formats: a structured invoice gives it cleaner input, and a PDF invoice still needs the same decisions after extraction. The mixed period is going to be long, because invoices outside the mandate keep arriving in the old formats, so anything built now has to handle both.
Our position on this has not changed because of the mandate. Automate the handling, keep the judgment with a person, and measure the change against a baseline you agreed before you started. The mandate does not alter what should stay human. It removes some of the mechanical work earlier than most practices expect, and it puts a legislated date on a rebuild that many were planning to do eventually anyway.
If you want to talk through where your own book sits, that conversation is the opportunity review, and it starts with your client list rather than with software.