Peppol BIS and OGCIO: B2G e-invoicing in Ireland
How the OGCIO mandate, the EU eInvoicing Directive 2014/55/EU and the Peppol BIS Billing 3.0 specification fit together — and what a supplier to the Irish State has to do to be paid.
The OGCIO Peppol mandate (2019)
Ireland's central rules for receiving electronic invoices in the public sector are set by the Office of the Government Chief Information Officer (OGCIO), part of the Department of Public Expenditure. Following the European Directive on e-invoicing in public procurement, OGCIO mandated that central Government Departments and their agencies must be able to receive structured e-invoices via the Peppol network from 2019 onwards, with sub-central contracting authorities (local authorities, voluntary bodies, the wider public service) following on a phased basis. The mandate is not a one-day switch but a steady migration: paper and PDF remain technically tolerable for legacy contracts, but Peppol-delivered structured invoices are the channel that contracting authorities expect and recommend to suppliers tendering for new awards.
Directive 2014/55/EU: the European frame
The Irish mandate transposes the European eInvoicing Directive — Directive 2014/55/EU on electronic invoicing in public procurement — which obliges every contracting authority in the EU to be able to receive and process e-invoices that conform to the European semantic standard EN 16931. The Directive is deliberately format-neutral: any syntax (UBL 2.1, UN/CEFACT CII) is acceptable as long as the content carries the EN 16931 core elements. In practice, Peppol BIS Billing 3.0 has become the dominant pan-European profile and is the choice adopted by OGCIO for Ireland. A supplier delivering a Peppol BIS invoice is, by construction, compliant with the European standard.
Peppol BIS Billing 3.0: the technical profile
Peppol BIS Billing 3.0 is a Business Interoperability Specification published by OpenPeppol that pins down the EN 16931 model into a concrete UBL 2.1 document, with its own validation rules and code lists. Every Peppol-compliant invoice carries the supplier and customer identifiers, the line items with quantities and unit prices, VAT per rate and the totals — fields a receiving system can book automatically without re-keying. The profile evolves through versioned releases; software that supports the current Peppol BIS Billing produces invoices that any compliant Irish Government receiver can read.
Government Departments and contracting authorities
All central Government Departments are connected to Peppol and able to receive Peppol BIS Billing 3.0 invoices: the Department of Finance, the Department of Public Expenditure, NDP Delivery and Reform, the Department of Health, the Department of Education and so on. The HSE and large semi-State bodies have followed. At sub-central level the picture is more granular — local authorities, voluntary organisations, education and training boards and the smaller public bodies have been migrating in waves. When you bid on eTenders for a public contract, the tender documentation now routinely specifies that invoicing will be by Peppol and gives you the Peppol Participant ID of the contracting authority.
How a supplier delivers a Peppol BIS invoice
From the supplier's point of view the operation is the same regardless of which Department is on the other side. Your invoicing software produces the invoice as a Peppol BIS UBL document carrying the buyer's Peppol Participant ID (often derived from the State's Department or Body identifier scheme), then hands it to your access point on the Peppol network. The four-corner model takes over: your access point locates the buyer's access point through the Peppol Directory, delivers the document, and returns a transport-level message receipt. The buyer's finance system books the invoice straight from the structured data — no scanning, no OCR, no manual re-entry.
Where ROS fits — and where it doesn't
It is worth being precise about what Peppol is, and what it is not. Peppol BIS is the delivery channel and document standard for getting a structured invoice into a Government buyer's finance system. ROS, the Revenue Online Service, is a separate system: it is where the supplier files their own VAT3 return and other Revenue obligations on the same invoices, but Revenue does not sit in the middle of the Peppol exchange itself. A supplier issuing Peppol BIS invoices to the State still files VAT3 through ROS as usual, with the same Irish VAT rates and the same periodicity. The two systems serve different sides of the same transaction.
Bidding for State contracts in the Peppol era
If you tender on eTenders for State contracts and are awarded business, the practical question on day one of delivery is whether you can issue a Peppol BIS invoice. Many large central buyers will not accept PDFs by email any longer, and where they still tolerate them, payment cycles for Peppol invoices are noticeably faster because the document is booked automatically and routed for approval without manual handling. Being Peppol-ready is therefore both a compliance question (the OGCIO mandate) and a commercial one (faster payment, fewer rejections, fewer queries from the buyer's accounts payable team).
Accepted invoicing channels
Frequently asked questions
Is sending Peppol BIS legally required to invoice the Irish State?
The OGCIO mandate requires Government Departments and their agencies to be able to receive Peppol BIS invoices; the symmetrical obligation on suppliers depends on the specific tender and contract. In practice, new State contracts now routinely specify Peppol BIS as the invoicing channel, and a supplier that cannot send Peppol BIS is at a real disadvantage when bidding on Government work.
Do I have to register with OGCIO to send Peppol invoices?
No. You connect through a Peppol access point — your invoicing software provider, in most cases — and the access point handles the technical registration on the Peppol network. The Government Department you are invoicing is identified through its Peppol Participant ID, which is published or supplied with the tender documents.
How does this relate to Revenue and ROS?
Peppol BIS delivers the invoice to the State buyer; Revenue and ROS are about your own VAT and tax returns on the same invoices. Sending a Peppol invoice to a Department does not change how you file VAT3 through ROS — you continue to report Irish VAT as usual, with the rates and dates Revenue specifies.
What is a Peppol Participant ID?
It is the addressing scheme on the Peppol network — the equivalent of an email address but for legal entities. Each Government Department, agency or business that receives Peppol invoices has a Participant ID (typically based on a recognised identifier scheme such as VAT or a registered Department number). Your access point uses this ID to locate the recipient through the Peppol Directory.
What happens if I have an existing PDF invoicing flow with a Department?
Legacy flows are tolerated for the duration of the legacy contract, but the trend is clearly toward Peppol BIS as the universal channel. When the contract is re-procured under the new framework, Peppol BIS will be the expected invoicing route, and migrating in advance is the easier path. Most modern invoicing platforms support both PDF (for the human eye) and Peppol BIS (for the State's finance system) in parallel.