Electronic invoice in Ireland
Decentralised model with e‑Invoicing Framework – Public authorities must accept
Ireland has gone from being, in Revenue's own words, one of very few EU member states not operating or rolling out mandatory e-invoicing, to having a published three-phase programme. Announced alongside the Budget 2026 speech, VAT Modernisation introduces mandatory domestic B2B e-invoicing with real-time reporting from November 2028 — described by Revenue as the most significant change to the Irish VAT system since the tax was introduced over fifty years ago.
The detail that gets lost in most summaries is on the receiving side. The phases decide who must issue. But every business must be able to receive a structured e-invoice from a mandated supplier — including businesses that are years away from any issuing obligation of their own. That is not an Irish embellishment; the ViDA Directive imposes it as a legal obligation on business customers. See The receive obligation.
Two eras. A light-touch B2G regime that has been running since 2019, and a phased B2B programme that starts in 2028.
The Office of Government Procurement takes the role on behalf of the Irish Government — the basis of the Peppol-first approach that persists today.
Contracting authorities in scope must receive and process EN 16931 invoices. Sub-central authorities followed from 18 April 2020. No supplier-side obligation was created.
Following the Budget 2026 speech, Revenue sets out the three-phase implementation of e-invoicing and real-time reporting, building on a public consultation opened in October 2023 whose findings were published in June 2024.
A deliberately small population, chosen because they are best placed to adapt and often already run comparable systems abroad. From this point all businesses need to be enabled to receive e-invoices.
The domestic obligation extends to all VAT-registered businesses engaged in cross-border EU B2B trade who benefit from the 0% VAT arrangements — giving them a year to work domestically before the EU regime arrives.
Structured e-invoicing and real-time reporting become mandatory for all cross-border EU B2B transactions across every member state. Irish businesses already on the domestic system transition into the EU obligations.
Phase 2 is widely misreported as "all VAT-registered businesses from November 2029". Revenue's wording is narrower and should be read literally: all VAT-registered businesses engaged in cross-border EU B2B trade who benefit from the 0% VAT arrangements. A purely domestic Irish business outside the Large Corporates Division is not brought in by Phase 2 on the published design.
Revenue's definition is cumulative. A business is in Phase 1 only if it meets all three limbs:
Note that this is an administrative test, not a turnover threshold — which is unusual, and convenient. Affected businesses will be told directly by Revenue rather than having to work out whether a numeric threshold catches them. If you are not sure whether a client is in scope, the question is which Revenue division handles them.
One consequence worth spelling out for cross-border traders: Revenue links continued access to the 0% VAT arrangements on intra-EU supplies to operating the new e-invoicing and reporting systems from July 2030. That is a commercial exposure of a different order from a filing penalty.
This is the part of the Irish programme that most businesses will discover too late. Revenue states it plainly: all businesses need to be enabled to receive eInvoices from suppliers. E-invoicing is an end-to-end digital process, and the ViDA Directive sets out a legal obligation for business customers to accept e-invoices from their suppliers.
So the phased rollout answers a narrower question than people assume. It tells you when you must issue. It does not exempt you from being able to receive when a mandated supplier starts sending — and in November 2028 that supplier will be one of the largest companies in the country, invoicing a long tail of smaller counterparties.
Practically, the receiving capability is the cheap half and the early half. Revenue says it is actively exploring options to make meeting this obligation as straightforward as possible for all businesses — but "as straightforward as possible" still means being reachable in a structured electronic format on a network, which is not something an accounts inbox does by itself.
Until 2028, the only live Irish obligation is the receiver-side B2G duty. S.I. No. 258/2019 requires contracting authorities and entities within the scope of the public procurement rules to receive and process EN 16931-compliant electronic invoices. It creates no supplier-side mandate — the Office of Government Procurement states directly that a supplier is not obliged to send an e-invoice to a public body.
Ireland's B2G experience since 2019 is not incidental to what happens in 2028. Revenue explicitly points to Peppol, already used by some Irish public bodies, as infrastructure that businesses can readily adopt — and is working with the OGP to prepare for the substantial growth in network usage the mandate will bring.
The future Irish system is best classified as continuous transaction control with real-time digital reporting — but not clearance. Revenue describes two operations happening in parallel: the supplier issues a structured e-invoice to the customer, and a subset of relevant data from that invoice goes to Revenue in real time.
A structured EN 16931 e-invoice, exchanged through the network. This is the commercial document and it goes directly to the buyer.
A subset of relevant invoice data, reported in real time. Key transaction details, not the whole document.
Not officially — and this matters for anyone designing against it. Revenue says the system will use various existing technical infrastructures, including Peppol, and is still consulting industry experts on the mechanisms for effective e-invoicing and reporting. Detailed technical specifications are to be published in advance of each phase. Reporting invoice data in parallel with a Peppol exchange could end up looking five-corner-shaped, but no formal C5 role has been announced.
EN 16931 is confirmed. Revenue states that e-invoice structures must comply with the European standard using structured data formats enabling automatic processing, and that current practices including issuing PDF invoices or scanned paper invoices will no longer satisfy VAT compliance requirements.
What is not yet fixed is the domestic profile. UBL 2.1 and UN/CEFACT CII D16B are the official EN 16931 syntaxes, and Peppol BIS Billing 3.0 is already in use in Irish B2G — but Revenue has not published the domestic B2B technical profile, so it would be premature to state that any one of them is mandated for every B2B participant.
The sensible build: treat EN 16931 and Peppol BIS Billing 3.0 as the baseline, and treat the Irish domestic validation and reporting profile as unfrozen until Revenue publishes its specifications. Anything more specific than that is guesswork dressed as a requirement.
Today, in ordinary B2B and B2C, a PDF is a perfectly normal invoice under the general VAT rules. In the B2G channel a standalone PDF is not an EN 16931 e-invoice. And for transactions caught by the future mandate, a PDF or a scanned paper invoice will not satisfy the requirement — which is the single clearest statement Revenue has made about the new regime.
The active Irish scheme in the Peppol electronic address code list is 9935 — Ireland VAT number, listed as IE:VAT. In a Peppol BIS Billing document it appears as the schemeID on the endpoint identifier:
There is no Ireland-specific Peppol scheme based on the CRO company registration number, unlike the national company-register schemes some other countries operate. The list does contain international schemes — 9913 for the Business Registers Network and 0088 for GLN, among others — but these should not be mistaken for an Irish CRO scheme.
When invoicing a specific Irish public shared service, check its own CIUS and identifier requirements separately: bodies such as the NSSO and the education and training sector may require additional business or process identifiers carried inside the invoice, over and above the endpoint.
Ireland's Peppol Authority is the Office of Government Procurement, which took the role on behalf of the Irish Government on 18 January 2018. Responsibility is split cleanly, and knowing which body owns which question saves time:
For B2G, Peppol is the official channel and the OGP describes it in the familiar connect-once, connect-to-all terms. For the future B2B regime, Peppol is clearly strategic and clearly expected to grow — Revenue and the OGP are preparing for exactly that — but Revenue has not declared Peppol the sole mandatory transport network for domestic B2B in 2028 or 2029.
One genuine simplification sits inside the programme and is rarely mentioned. Under ViDA, suppliers issue e-invoices within ten days of the transaction and digitally report specified data to their national tax authority — and the new system eliminates the reporting requirement of the monthly VIES returns.
For an Irish business trading intra-EU, that is a real removal of an existing monthly obligation, not just an addition of a new one. It is worth putting on the other side of the ledger when a client asks what all this costs them.
Ireland has no Peppol Authority Specific Requirements and no national accreditation layer comparable to the Slovak digitálny poštár. On current Peppol governance, a Service Provider certified in another EU country can serve Irish clients directly.
What remains is the ordinary OpenPeppol layer: the Service Provider Agreement, certification, AS4 messaging, PKI and certificate security, the relevant BIS profiles, addressing and SMP capability publication. Note also that being on an OGP public-sector procurement framework is a commercial arrangement — it is not an Access Point accreditation, and the two get conflated.
The open question for 2028. Whether Revenue will impose separate rules on providers handling the real-time reporting leg is not yet known — the legislative changes, operational processes and IT requirements are still in detailed analysis. Today's answer is "no accreditation"; that answer applies to the current Peppol B2G world, not necessarily to the reporting layer that does not exist yet.
An accountable person must retain all records relevant to the business for six years. Ireland then adds a rule that catches out businesses used to cloud-first archiving elsewhere in Europe.
The retrievability requirement is the one to design for. An archive that can only find an invoice by number or date does not meet it; retrieval by counterparty name has to be built in. Retain the XML, not merely a rendered PDF — from 2028 the structured document is the invoice.
No Ireland-specific penalty schedule for breaching the future e-invoicing and real-time reporting regime has been published. Revenue has said the legislative changes, operational processes and IT requirements are still in detailed analysis, with guidance and technical specifications to follow. So it would be wrong to state today that the sanction is a percentage of invoice value, that it applies per invoice, that a non-compliant invoice is automatically legally invalid, or that any syntax error destroys the deduction. None of that has been decided.
For B2G, S.I. No. 258/2019 contains no fixed monetary sanction on a supplier for sending paper or PDF — logically enough, since there is no supplier-side obligation to breach.
The Value-Added Tax Consolidation Act 2010 already provides, in the administrative consolidation of section 115(1)(a), a penalty of €4,000 for failure to comply with, among other things, Chapter 2 of Part 9 and related regulations — the chapter governing invoicing obligations. Care is needed here: that is not the same as saying €4,000 is already the established penalty for each breach of the 2028 regime. Future implementing legislation will determine which new duties are inserted into the VATCA and which penalty provisions attach to them.
Under the current regime a structured e-invoice is not the only documentary basis for reclaiming VAT. A VAT-registered person reclaiming VAT on goods and services used for taxable supplies must keep supporting records including a valid VAT invoice or the relevant Customs receipt. There is no published rule that "no structured e-invoice means no deduction".
Keep two things apart. The buyer's input VAT deduction is one question. The 0% VAT arrangements on intra-EU supplies are another — and it is the latter that Revenue expressly ties to operating the new systems from July 2030. Revenue is also clear that VAT Modernisation changes invoicing and reporting processes; rates, payment requirements and liability calculations are unchanged.
Two and a half years sounds generous until you notice how much of the specification is still open. What can be done now, without waiting for Revenue's technical documents:
The test is whether Revenue's Large Corporates Division manages the business, combined with VAT registration and Irish establishment. Revenue will notify affected businesses directly — but knowing early is better than being told.
Every business needs receive capability from November 2028 regardless of its own phase. It is the cheaper half and it has the earlier deadline.
Real-time reporting exposes the quality of what the ERP produces. Counterparty VAT numbers, line-level detail and tax treatment that survive a validator are the actual project — the transport layer is the easy part.
Baseline on the European standard and Peppol BIS Billing 3.0, and keep the validation and reporting layer configurable until Revenue publishes the domestic profile.
Ireland needs no accreditation and no local entity today. What it needs is a provider already running the standard the mandate will be built on:
9935, and on GLN or the Business Registers Network scheme where counterparties use themIreland has moved from laggard to a country with a firm, published plan. B2G remains a receiver-side duty on Peppol with no supplier mandate. Domestic B2B e-invoicing with real-time reporting arrives for Large Corporates Division companies in November 2028, extends to intra-EU traders in November 2029, and meets the EU regime on 1 July 2030.
Two things are settled: EN 16931, and the death of the PDF for mandated transactions. Two things are not: the domestic technical profile, and whether Peppol becomes the sole transport. Anyone selling certainty about the second pair is selling something Revenue has not published.
The obligation that arrives first is the one nobody is planning for. Whatever phase you fall into, you must be able to receive a structured e-invoice from November 2028. Start there.