Revenue Ireland Digital Reporting: Practical Steps Before ViDA
Revenue Ireland digital reporting: practical 2026 steps for SMEs and exporters to align with ViDA, EN 16931 and Peppol BIS Billing 3.0 well before deadline.
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 (typically
0088GLN or0188CRO for Irish entities). - 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.
ROS — what changes, what stays
| ROS today | After ViDA |
|---|---|
| VAT3 manual returns | Continues; supplemented by digital reporting |
| Manual PDF upload for some flows | Largely retired; structured exchange replaces it |
| Direct debit, ROS payments | Unchanged |
| Customer-by-customer reconciliation | Real-time-ish: report at issuance |
ROS is not going anywhere. It will gain a "view of digital reporting" surface in time, but the underlying structured data flows over Peppol-aligned infrastructure.
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 — see our XRechnung readiness checklist).
- 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. Irish customers typically reach Sprint 5 readiness in three months when the master data is healthy.
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: EU Council ViDA package; Revenue eBrief releases; Peppol BIS Billing 3.0 specification; OpenPeppol directory.
Frequently asked questions
- What is digital reporting under ViDA?
- Digital reporting under ViDA is the requirement to transmit structured transactional data about each cross-border intra-EU B2B invoice to the issuer's home tax authority within two business days of issuance, using the EN 16931 semantic model.
- Will Revenue replace ROS?
- No. Revenue Online Service remains the taxpayer interface; the digital reporting layer is fed from the same structured invoice data exchanged on Peppol, with Revenue ingesting the report through a back-end channel.
- How early should we start?
- Three to five sprints in 2026 for issuance and inbound on Peppol BIS Billing 3.0. Add another sprint for digital-reporting hooks once Revenue publishes the technical specification. Finish ahead of the 2028 phase-in to avoid stacking with year-end and other regulatory work.
- Do small Irish suppliers need a Peppol Access Point?
- Yes if they want to keep selling to large public-sector and corporate buyers that already require Peppol. The Access Point can be operated by a service provider rather than self-hosted.
- How does this interact with Northern Ireland?
- NI uses the GB VAT regime under the Windsor Framework but follows EU rules for goods. The participant identifier scheme and the VAT scheme on the invoice must reflect that nuance — get it wrong and Revenue or HMRC will reject downstream.
About Dr. Syed Raza
Dr. Syed Raza is an IT Enterprise Architect at ClayDesk LLC and leads the GoRoute platform. He works across Peppol Access Point and SMP infrastructure, PINT jurisdictions (Oman, AU/NZ, EU, JP, MY, SG), and national CTC regimes, translating regulatory detail into production-grade e-invoicing systems.
Building on Peppol?
GoRoute is a certified Peppol Access Point & SMP. Book a demo or read the docs to get started.