ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

Ireland — PEPPOL pioneer, ROS Revenue Online Service

Ireland is one of Europe's PEPPOL pioneers for B2G. The Office of Government Procurement (OGP), an agency of the Department of Public Expenditure, has operated a central PEPPOL access point for every Irish public body since 18 April 2019 (Statutory Instrument 354 of 2019). The reference format is generic PEPPOL BIS Billing 3.0 without a national CIUS. For tax reporting, ROS (Revenue Online Service) remains the keystone of VAT filings. No domestic B2B mandate before ViDA implementation in 2030.

Regulatory timeline

  • 2000 — Revenue Online Service (ROS). The Revenue Commissioners launch ROS, one of Europe's earliest VAT e-filing portals. ROS remains the keystone of Irish tax reporting: VAT3 (VAT return), VIES, RTD (Return of Trading Details).
  • 13 October 2014 — eDocs migration to the Office of Government Procurement (OGP). The public-procurement function is centralised at the OGP, an agency of the Department of Public Expenditure, paving the way for centralised B2G e-invoicing.
  • 27 November 2014 — EU Directive 2014/55. Ireland transposes the e-invoicing in public procurement directive through Statutory Instrument 354 of 2019 (European Union (Electronic Invoicing in Public Procurement) Regulations 2019).
  • 18 April 2019 — Mandatory B2G. SI 354/2019 takes effect: every Irish public body must be able to receive an EN 16931-compliant electronic invoice. The OGP designates PEPPOL as the reference network and operates a central PEPPOL Access Point for the Government of Ireland.
  • 2020-2024 — Mass adoption of B2G PEPPOL. Over 90% of central public bodies and most HSE (Health Service Executive), Local Authorities and Education and Training Boards accept PEPPOL BIS Billing 3.0 invoices in production.
  • 14 February 2024 — Revenue B2B consultation. Revenue opens a public consultation "Modernising Ireland's administration of VAT": call for views on VAT modernisation, B2B e-invoicing and real CTC, ViDA 2030 alignment.
  • 1 July 2030 — ViDA cross-border DRR. Under "VAT in the Digital Age", Ireland will apply structured electronic invoicing and the Digital Reporting Requirement (DRR) for intra-EU B2B transactions. No earlier domestic B2B mandate is publicly known as of writing.

Deep dives — 10 dedicated pages

Ten dedicated pages drill into every dimension of the Irish e-invoicing and EDI ecosystem — the reforms and framework (OGP Peppol Authority B2G 2019, Revenue VAT modernisation, ViDA 2030 roadmap), the technical specifications (ROS e-filing, the unusually broad zero-rate VAT, PPSN/CRO identifiers), and the real-world B2B usage that dwarfs the local market: retail EDIFACT (Dunnes/Musgrave/Tesco), the pharma and medtech cluster (Pfizer/J&J/Boston Scientific/Medtronic), the US-tech multinationals (Apple/Intel/Google/Meta), and Ireland's role as the EU corporate domicile driving intra-group and transfer-pricing flows.

Reforms & framework

  • OGP — Irish Peppol Authority, B2G since 2019 · The Office of Government Procurement is the Irish Peppol Authority. eInvoicing Ireland programme, B2G receipt mandate since April 2019 (transposing 2014/55/EU, SI 258/2019). Peppol BIS Billing 3.0, private-operator model.
  • Revenue — VAT modernisation & B2B e-invoicing · Revenue 2023-2024 public consultation on VAT modernisation. No B2B mandate yet: phased, ViDA-aligned roadmap, cross-border digital reporting 2030, domestic to follow. A gradual approach distinct from the IT/PL big-bang.
  • ViDA Ireland 2030 — digital reporting · Ireland's ViDA trajectory: mandatory cross-border DRR from 1 July 2030, EC Sales List recapitulative statement abolished. Revenue aligns its VAT modernisation with this timeline. An optional domestic mandate may precede it.

Technical specs

  • ROS — Revenue Online Service, VAT e-filing · Revenue's digital tax portal, mandatory e-filing for nearly all taxable persons. Bi-monthly VAT3 return, annual RTD (Return of Trading Details), ROS digital certificates, SEPA direct debit payment.
  • VAT regimes — 23 / 13.5 / 9 / 0% · Standard 23%, reduced 13.5% (construction, energy), reduced 9% (newspapers, extended gas/electricity), zero 0%. Ireland's zero-rate list is unusually broad: food, children's clothing/footwear, oral medicines, books. Zero ≠ exempt.
  • Identifiers — PPSN, TRN, VAT number, CRO · PPSN (Personal Public Service Number), Tax Reference Number, Irish VAT number (IE + 7 digits + 1-2 letters), CRO number (Companies Registration Office), Peppol ICD 9935. Tax identity vs registry identity distinction.

Real-world B2B usage

Technical schema

Ireland aligns firmly with PEPPOL BIS Billing 3.0 for B2G; no proprietary national format (contrary to France Factur-X, Germany XRechnung or the Netherlands NL-CIUS). For tax reporting, ROS remains the reference platform.

  • PEPPOL BIS Billing 3.0 (UBL 2.1) — EN 16931 profile used without a national CIUS. The OGP explicitly recommends the generic PEPPOL profile.
  • iSPeed / iSpeed-IFS — historical FEI Ireland (Financial Executives Ireland) initiative for a national EDI format. Largely superseded by PEPPOL since 2019, with residual presence in some public sectors.
  • ROS XML (VAT declarative) — Revenue's proprietary schema for VAT3, VIES, RTD returns: not an invoice format but an aggregated post-fact declarative format.
  • TIN/VAT-IE: Tax Identification Number in the form IE + 7 digits + 1 or 2 letters (or IE + 9 digits for numbers issued since 2013).
  • PEPPOL schemeID: 9935 for IE:VAT.
xmlie-peppol-bis-snippet.xml
<?xml version="1.0" encoding="UTF-8"?>
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
         xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
         xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
  <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>
  <cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>
  <cbc:ID>IE-2026-0142</cbc:ID>
  <cbc:IssueDate>2026-05-19</cbc:IssueDate>
  <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
  <cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
  <cac:AccountingSupplierParty>
    <cac:Party>
      <cbc:EndpointID schemeID="9935">IE1234567T</cbc:EndpointID>
      <cac:PartyTaxScheme>
        <cbc:CompanyID>IE1234567T</cbc:CompanyID>
        <cac:TaxScheme>
          <cbc:ID>VAT</cbc:ID>
        </cac:TaxScheme>
      </cac:PartyTaxScheme>
      <cac:PartyLegalEntity>
        <cbc:RegistrationName>Ediverse Demo Eire Ltd</cbc:RegistrationName>
      </cac:PartyLegalEntity>
    </cac:Party>
  </cac:AccountingSupplierParty>
</Invoice>

Submission flow

The Irish B2G flow follows the PEPPOL 4-corner model: the seller submits via their access point, which routes via SML/SMP to the OGP access point (receiving for all central public bodies), then internal routing to the final recipient (HSE, Department, Local Authority).

textie-peppol-b2g-flow.txt
┌──────────────┐    ┌──────────────┐    ┌──────────────┐    ┌──────────────────┐
│ Seller IE    │──> │ Access Point │──> │ OGP Access   │──> │ Public body      │
│ (UBL ERP)    │    │ seller (C2)  │    │ Point (C3)   │    │ (HSE, Local, …)  │
└──────────────┘    └──────────────┘    └──────────────┘    └──────────────────┘
                          PEPPOL SML/SMP routing               C4 recipient

On the tax-reporting side, the seller files a VAT3 return monthly (or bi-monthly above the threshold) on ROS, and a VIES return quarterly for intra-EU sales. Annual Return of Trading Details (RTD) at year end. No per-invoice reconciliation on the Revenue side as of writing: VAT control is aggregated by rate.

For domestic B2B, no mandate: voluntary PEPPOL flows are spreading on the back of B2G traction (suppliers equipped to sell to the state also equip their B2B). EDIFACT EANCOM persists in retail (Musgrave, Tesco Ireland) and pharma.

Validation

Common pitfalls

  1. Two-format VAT-IE pattern. Legacy IE VAT numbers follow IE\d{7}[A-Z]{1,2} (e.g. IE1234567T, IE1234567AH); numbers issued since 2013 follow IE\d{8}[A-Z] (e.g. IE1234567TA). PEPPOL Schematron rules that only allow the first pattern reject the new numbers: review upstream regex validation.
  2. No national CIUS. Ireland has not published a national CIUS: use generic PEPPOL BIS Billing 3.0. Forcing a CIUS-XYZ from another EU country (XRechnung DE, RO_CIUS RO, etc.) triggers BR-CO-15 rejections at the OGP access point.
  3. IE VAT rates: 0 / 9 / 13.5 / 23%. The "hospitality" 9% rate (restaurants, hotels) and the "reduced" 13.5% rate (construction, electricity, gas) are often confused. See Revenue TDM Part 03-01-01.
  4. Brexit cross-border NI. Northern Ireland (NI) stays in the EU VAT-goods regime but exits on services. Dublin → Belfast flows need a VAT-XI (prefix XI) and not a regular VAT-GB for goods. ERPs that map NI to GB on destination trigger VIES rejections.
  5. ROS Digital Cert vs PEPPOL. ROS requires a digital certificate issued by Revenue (the "ROS Cert"); PEPPOL uses access point certificates issued by OpenPEPPOL AISBL. The two are not interchangeable: signing a PEPPOL payload with a ROS Cert produces an invalid signature rejected by SMPs.