Revenue Ireland Digital Reporting: Practical Steps Before ViDA

Why this guide

The ViDA roadmap shapes what Ireland will do. This guide covers how an Irish finance and IT team gets from today's PDF-and-email reality to a ViDA-ready posture, in five concrete sprints. It is the practical companion to our Ireland ViDA roadmap.

We assume your starting point is: ROS in place, accounts on a mid-market or enterprise ERP, some BIS exchange happening for B2G but most B2B still on PDF.

The five-sprint plan

Sprint 1 — Master data

Most digital-reporting failures are master-data failures, not technical failures. Spend the first two weeks here.

• VAT identifier on every customer and supplier (Irish, GB, EU).
• CRO numbers for every Irish counterparty.
• Currency codes, country codes, IBAN format, BIC where required.
• Endpoint identifier scheme decided per counterparty. For Irish entities that is 9935, the Irish VAT number — the only Irish scheme in the Peppol code list; there is no CRO scheme.
• Tax category codes on every product / service line.

Sprint 2 — Outbound issuance

Generate Peppol BIS Billing 3.0 from your ERP for a single test customer. Validate against:

• UBL 2.1 XSD
• EN 16931 baseline Schematron
• Peppol BIS 3.0 Schematron

Then expand to your top 50 customers.

Sprint 3 — Inbound reception

Subscribe to a certified Access Point and publish your participant on the OpenPeppol SML through your provider's SMP. Confirm:

• AS4 endpoint reachable.
• Inbound document persisted in structured form.
• AP/ERP routing produces a posted invoice in the AP module.
• Receipts (MLR) sent back to the supplier.

Sprint 4 — Validation and exception handling

A robust pipeline distinguishes:

• Schematron error — reject and notify.
• Schematron warning — pass and log.
• AS4 transient failure — retry with backoff and idempotency.
• Permanent delivery failure — dead-letter and alert.

We cover the common patterns in invoice validation errors you can prevent and how does e-invoicing work.

Sprint 5 — Reporting hook

When Revenue publishes the digital reporting specification, the data is already in your system in structured form. Add the report emitter as a separate consumer of the invoice event stream — do not hard-couple it to either AS4 send or AP receive.

What changes under the Bill

ROS is not going anywhere. How the reporting data reaches Revenue has not been published: Revenue says it will use existing infrastructures including the Peppol framework, but the channel, the data fields and the specifications are still to come.

A specific watch list for cross-border Irish flows

• Ireland → EU member states: EN 16931 + Peppol BIS 3.0 + the receiver's national CIUS where applicable (e.g. XRechnung for German federal buyers — handled automatically by the multi-country e-invoicing API).
• Ireland → GB: Peppol BIS 3.0 stays; GB VAT scheme on the invoice; HMRC's MTD for VAT continues separately.
• Ireland → US / non-EU: No mandate today, but Peppol global reach continues to expand. Build issuance once and route flexibly.

What to avoid

• Treating digital reporting as an extra return. It is a continuous data feed, not a quarterly form.
• Letting different teams own master data, issuance, and reporting. They are one project.
• Building a custom SMP. The Peppol SMP is a specification, not a Saturday-afternoon project. Use a certified provider.

What we ship at GoRoute

GoRoute is a certified Peppol Access Point and SMP operator (POP000991) with Peppol BIS Billing 3.0 in production.

To see Ireland alongside the rest of the 2026/2027/2028 timeline, jump to the e-invoicing mandates 2026 tracker. To start with the regulatory frame, the Ireland ViDA roadmap is the companion piece.

Book a demo and we'll size the project against your data.

Sources: Council Directive (EU) 2025/516 (ViDA); Finance (No. 2) Bill 2026, section 51, as initiated on 19 October 2026; Revenue, Implementation of eInvoicing in Ireland (8 October 2025); Revenue eBrief releases; Peppol BIS Billing 3.0 specification; OpenPeppol directory.