E-invoicing in Ireland: VAT modernisation, Peppol and the 2028 start

01Ireland’s position in autumn 2026

Revenue calls the programme VAT modernisation. Its published timeline has three phases. From 1 November 2028, VAT-registered businesses dealt with by Revenue’s Large Corporates Division issue structured e-invoices for domestic B2B supplies and report the invoice data to Revenue, and from the same date every business must be able to receive e-invoices. From 1 November 2029 the requirement extends to VAT-registered businesses trading B2B within the EU. In July 2030 the EU’s own cross-border rules under ViDA follow.

The public side moved earlier. Under the European Union (Electronic Invoicing in Public Procurement) Regulations 2019, S.I. No. 258 of 2019, contracting authorities must receive and process e-invoices that follow EN 16931, and Ireland uses Peppol to deliver them. The Office of Government Procurement currently performs the Peppol Authority function for Ireland; Revenue has said it intends to take that role on from 1 January 2027. Belgium, for comparison, has required domestic B2B e-invoicing since January 2026, as its federal e-invoicing site (opens external site) explains.

02What qualifies as an e-invoice

For these purposes an e-invoice is structured data: a file a system can process without anyone reading it, built on the semantic model of the European standard EN 16931. A PDF does not qualify, and neither does a scan or a Word file, however it is sent. Revenue’s timeline says so explicitly. A structured invoice may carry a PDF copy for people to read, but the data is the invoice.

The Peppol specification of EN 16931 is Peppol BIS Billing 3.0, in UBL syntax, and it is what Irish public buyers receive. Revenue will publish the technical detail of the B2B exchange and the reporting; build on EN 16931 now and keep the channel and reporting format configurable until those specifications are final.

03How Peppol operates

Peppol is a set of specifications plus an international network for business documents, governed by OpenPeppol, a non-profit based in Brussels, with a Peppol Authority in each participating country. It uses a four-corner model. Your finance system (corner one) passes the invoice to your access point (corner two). That access point delivers it to your customer’s access point (corner three), which hands it to the customer’s system (corner four). Before delivery, the sending access point looks the receiver up in the network directory, the Service Metadata Locator, which refers to a Service Metadata Publisher, to confirm the receiver is registered and which document types it accepts.

The practical effect is large: one agreement with one access point provider gives you every participant on the network, whatever provider they chose. Many ERP and accounting packages bundle an access point; specialist providers cover higher volumes and documents beyond invoices, such as purchase orders and credit notes.

• Registration: your organisation is listed with its identifier and the documents it can accept. A missing or incorrect entry is a common reason invoices never land.
• Validation: access points test each invoice against the Peppol BIS Billing 3.0 rules and reject failures before they reach the customer.
• Delivery status: the network confirms technical receipt. Business replies such as accepted, queried or paid are separate messages, and only work where both sides support them.

04Who is affected, and when

Large corporates go first on issuing, but the receiving requirement reaches every business on 1 November 2028. An owner-managed firm that never sends a structured invoice before 2029 still has to accept them from its large suppliers on that date. Suppliers to public bodies should also check their contracts: individual contracts may set their own invoicing terms. Revenue has said it will publish more detail on the second and third phases.

05How the EU rules fit around Ireland

Two EU instruments shape national schemes. Directive 2014/55/EU (opens external site) obliges public contracting authorities to accept EN 16931 e-invoices; S.I. No. 258 of 2019 is Ireland’s transposition, which is why public buyers moved first here as elsewhere. The VAT in the Digital Age package (ViDA), including Council Directive (EU) 2025/516 (opens external site), was adopted on 11 March 2025 and has been in force since 14 April 2025. It lets Member States mandate domestic e-invoicing without first seeking an EU derogation, makes e-invoicing and digital reporting compulsory for intra-EU B2B supplies from 1 July 2030, and requires national real-time reporting systems to converge on the EU model by 1 January 2035.

Until then each country sets its own pace and architecture: Peppol in some, a national clearance platform in others, mixtures elsewhere. An Irish group that also invoices in other Member States needs one integration design with several outputs.

06Preparing the ERP: what decides success

A first Peppol invoice can go out the same day you connect. Moving your whole invoice volume across with no manual handling is a design job. The work lies in master data, validation, inbound handling and archiving; the network itself is the easy part.

• Fix master data early. Each customer needs a correct identifier, VAT number and address, and each item a unit of measure and VAT category that map to the codes in the standard. Check whether customers are registered before you send, and keep checking, since firms change providers.
• Validate inside your own process. Apply the access point’s business rules before sending, so a failed invoice is fixed in the ERP rather than discovered weeks later by a customer still waiting for it.
• Plan for receiving first. From November 2028 every business must accept e-invoices, so inbound handling is where most Irish firms start. Structured invoices can be matched automatically to supplier, purchase order and goods receipt, with only mismatches sent for approval. Paper or PDF invoices that still arrive, for instance from suppliers outside the EU, can be brought into the same flow through document capture.
• Keep the structured original. The file you sent or received is the invoice. Store it unchanged with the delivery evidence for the statutory retention period, and make sure it can be found and read during a Revenue audit.
• Watch the flow. Failed deliveries, rejections and invoices awaiting approval belong on a dashboard with a named owner, not in a shared mailbox.

In Odoo, Peppol sending and receiving is available, so preparing an owner-managed business is mostly configuration, data clean-up and approval routing. For a multinational’s Irish operation on SAP, the choice is usually SAP’s own document compliance tooling or a link to an external access point, and either way the VAT reporting to Revenue belongs in scope. Where several ERPs, a webshop and a group system all invoice, a shared integration layer keeps formats, validation and monitoring together.

07A plan towards November 2028

1. 01Map your invoice flows. Which systems send and receive invoices and credit notes, for which countries and through which channels, including webshops, subscriptions and intercompany billing.
2. 02Pick the access point model. Built into the ERP, a specialist provider, or a shared integration layer for several systems, judged on volume, document types and countries.
3. 03Clean the master data. Identifiers, VAT numbers, units and VAT categories for customers, suppliers and items.
4. 04Get receiving working. Every business must be able to accept e-invoices from November 2028; build matching, approval and posting, with exceptions routed to staff.
5. 05Test with your main trading partners. Exchange live invoices with your largest customers and suppliers before the switch, and see how their systems handle yours.
6. 06Archive and monitor. Keep structured originals and delivery evidence, and assign an owner to failed messages.
7. 07Design for reporting to Revenue. Shape the data flows so invoice data can also be reported once Revenue’s specifications are final, and so the 2029 and 2030 phases are an extension, not a rebuild.

08Points to follow

• The passage of Finance Bill (No. 2) 2026 and Revenue’s technical specifications for exchange and reporting.
• The transfer of the Peppol Authority role from the OGP to Revenue, intended for 1 January 2027.
• Revenue’s further detail on the 2029 phase and the national rules for ViDA in July 2030.
• New versions of Peppol BIS Billing 3.0 and of the validation rules your access point enforces.

These rules are still moving, in Ireland and in most markets around it. Put a date on any internal note about them, and recheck Revenue’s pages before each design decision.