Peppol E-Invoicing Requirements in Ireland

The underlying standard: EN 16931

Every Peppol invoice is built on EN 16931, the European semantic standard for electronic invoicing, introduced under EU Directive 2014/55/EU for public procurement. EN 16931 defines the core data a valid invoice must contain — it doesn't dictate a file format on its own. On the Peppol network specifically, that data is expressed as Peppol BIS Billing 3.0, a UBL 2.1 XML syntax that implements EN 16931 with some additional Peppol-specific rules. A PDF, no matter how detailed, does not satisfy this requirement on its own — it isn't structured, machine-readable data.

Who these requirements apply to

Irish public bodies — central government departments, the HSE, county councils, and Education and Training Boards — have had to be able to receive EN 16931 e-invoices since 18 April 2019 (central government) and 18 April 2020 (sub-central), under S.I. 258/2019 transposing Directive 2014/55/EU. Suppliers are not legally required to send e-invoices to public bodies, but several bodies prefer or require structured or Peppol invoices, so check your contract and purchase order terms. If a buyer does ask for a Peppol invoice, these are the requirements it needs to meet. See our full Peppol invoice Ireland guide for more detail and how to find your buyer's Peppol ID.

Mandatory fields checklist

A Peppol BIS Billing 3.0 invoice should include:

• A unique, sequential invoice identifier
• Invoice issue date and payment due date
• Your (the supplier's) name, address, VAT number and Peppol identifier
• The buyer's name, address and Peppol identifier
• A buyer reference or purchase order (PO) number — Peppol BIS Billing 3.0 expects one, and public bodies usually require it
• Line-item descriptions, quantities, unit prices and the VAT rate applied to each
• A VAT breakdown by rate category — taxable amount and VAT amount per rate
• Invoice totals: net subtotal, total VAT, and amount payable
• Payment details, typically an IBAN, if payment is expected by transfer

Miss any of the required items, or format the VAT breakdown incorrectly, and the invoice can be rejected by an Access Point before it's even seen by a human — which is why hand-building UBL XML is a common source of delay for suppliers new to Peppol.

VAT-specific requirements

Irish Peppol invoices must apply the correct VAT category and rate to every line — 0%, 9%, 13.5% or 23% — rather than a single blended rate for the whole invoice. Each rate needs its own subtotal in the VAT breakdown. Revenue also requires invoice records, including the underlying VAT detail, to be retained for six years, so your generated UBL XML and PDF should both be kept on file, not just the summary shown to the buyer.

Delivery requirements

Meeting the format requirements is only half the job — the invoice also needs to reach the buyer's own Peppol Access Point for genuine network delivery, which means routing it through your own Access Point (or a provider that offers one). Where a recipient accepts a direct email instead of network delivery, the correctly formatted PDF can be sent that way — but the underlying UBL XML should still exist and meet every requirement above, since many buyers expect one or the other, and audits can ask for either.

How PeppolInvoice.ie handles this for you

Rather than tracking EN 16931 field rules and BIS Billing 3.0 formatting by hand, PeppolInvoice.ie collects the required information through a short form and generates a UBL 2.1 XML file built to EN 16931 / Peppol BIS Billing 3.0 — plus a matching PDF — automatically. VAT rates, identifiers and totals are calculated and placed where the standard expects them, so the file is ready to upload to your own Access Point. We recommend validating the file with your Access Point.

New to the process end-to-end? Our step-by-step guide to sending a Peppol invoice walks through it from account setup to delivery.