Peppol E-Invoicing Requirements in Ireland
"Peppol e-invoicing requirements" covers more than just using the network — it means hitting a specific data standard, format and set of mandatory fields. Here is exactly what that means in practice, and a checklist to confirm you meet it.
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
Since January 2024, any business supplying goods or services to an Irish public sector body — central government departments, the HSE, county councils, or Education and Training Boards — must submit invoices that meet these requirements. This applies regardless of business size: sole traders, SMEs and large enterprises are all held to the same standard. See our full Peppol invoice Ireland guide for who exactly is covered and which hub to invoice.
Mandatory fields checklist
A compliant Peppol invoice must 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, where one was issued
- 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 these, or format the VAT breakdown incorrectly, and the invoice can be rejected by the recipient's 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 correctly structured UBL 2.1 XML file — plus a matching PDF — automatically. VAT rates, mandatory identifiers and totals are calculated and placed exactly where the standard expects them, so the output is ready to upload to an Access Point or send directly.
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.
Generate a requirements-compliant invoice
Every field, format rule and VAT breakdown handled automatically — free for your first invoice.
Get started free