eliDocs
/
Country Guides

Ireland

Irish B2B + B2G e-invoicing with Beliq, Peppol BIS 3.0 UBL, EAS 9935, and the Revenue submission boundary.

Ireland’s e-invoicing landscape uses standard Peppol BIS Billing 3.0 UBL (EN 16931) directly. There is no country-wide national CIUS. Sector-specific CIUSes exist for Central Government, Department of Education ETBs, and Local Government per the EC eInvoicing-Ireland page, but Beliq does not implement sector overlays. Authority: the Office of Revenue Commissioners.

So an Irish invoice in Beliq is a Peppol BIS invoice with Irish parties (EAS 9935). See the Peppol BIS format reference for the full element layout.

Mandate timing

Ireland’s public sector has received Peppol e-invoices for years. B2B issuing phases in later under the Revenue.ie VAT Modernisation roadmap, starting with large corporates and paired with real-time reporting.

DateWhat changes
12 June 2019Public-sector bodies must be able to receive and process EN 16931 e-invoices over Peppol.
November 2028Large VAT-registered corporates must issue B2B e-invoices with real-time digital reporting; every business must be able to receive.

The B2B rollout is phased under the Revenue.ie VAT Modernisation roadmap (October 2025): large corporates from November 2028, all VAT-registered businesses in intra-EU trade from November 2029, and full convergence with EU ViDA in July 2030.

Last verified against the Office of the Revenue Commissioners' VAT Modernisation eInvoicing roadmap (October 2025) and the European Commission eInvoicing country page on 9 July 2026. Official source.

If you already issue B2G invoices to Irish public-sector buyers, you are in scope today. For the dates beliq tracks across every covered country, see the mandate calendar.

What Beliq does today

  • Generate Irish Peppol invoices via standard: "peppol-bis" (profile peppol), addressed with the Irish VAT endpoint scheme (IE:VAT, Peppol EAS 9935).
  • Validate and parse Peppol BIS UBL against the full EN 16931 + Peppol BIS 3.0 Schematron (peppolVersion in the response).
  • Compliance status for ireland_peppol is supported; it rides the fully-verified Peppol BIS pipeline (9 OpenPeppol positive examples + 227 negative test cases). Ireland adds no country-wide rules, so there is no Ireland-specific corpus; that is recorded as a tracked gap with a quarterly re-check for any future all-Ireland CIUS or mandate phase change.

What Beliq does not do (Peppol transmission boundary)

Ireland’s network is the Peppol Network. Beliq is not a Peppol Access Point. It does not:

  • Transmit invoices over Peppol or register you as a Peppol participant.
  • Operate the 4-corner exchange on your behalf.
  • Implement sector-specific CIUSes (Central Government / ETBs / Local Government). If a sector buyer requires their CIUS, your Access Point provider routes accordingly.

You send Beliq’s UBL output through your chosen Access Point (BYOC). Beliq’s job ends at a correct, Peppol-valid document. Authority oversight: Office of Revenue Commissioners + Office of Government Procurement.

Integration architecture (Beliq vs Peppol Access Point)

Concern In Beliq today Outside Beliq (your stack / partner)
Peppol BIS 3.0 UBL invoice XML Generate, Validate, Parse —
Peppol Network transmission (4-corner) Not offered, see boundary above Your Access Point provider
Sector-specific CIUS (Central Gov / ETBs / Local Gov) Not offered Your Access Point provider

Generating an Irish Peppol invoice

Address both parties with the Irish VAT endpoint scheme (IE:VAT, EAS 9935) via the peppol block. Provide either a buyerReference or an orderReference (Peppol requires one). The simpler alternative is to omit the peppol block and pass a vatId (IE…) + address.countryCode: "IE"; Beliq then derives the IE:VAT scheme (9935) automatically.

generate-ireland-peppol.sh
curl -X POST https://api.beliq.eu/v1/generate \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "standard": "peppol-bis",
    "profile": "peppol",
    "output": "xml",
    "invoice": {
      "number": "2026-0001",
      "issueDate": "2026-06-03",
      "currencyCode": "EUR",
      "buyerReference": "IE-PO-7711",
      "seller": {
        "name": "Test Seller Ltd",
        "vatId": "IE1234567T",
        "peppol": { "schemeId": "9935", "id": "IE1234567T" },
        "address": { "street": "1 Sample Street", "city": "Dublin", "postalCode": "D02 XY00", "countryCode": "IE" }
      },
      "buyer": {
        "name": "Test Buyer Ltd",
        "vatId": "IE9876543W",
        "peppol": { "schemeId": "9935", "id": "IE9876543W" },
        "address": { "street": "2 Example Road", "city": "Cork", "postalCode": "T12 AB00", "countryCode": "IE" }
      },
      "lines": [
        {
          "description": "Professional services",
          "quantity": 1,
          "unitCode": "C62",
          "unitPrice": 100.00,
          "lineTotal": 100.00,
          "vatRate": 23,
          "vatCategoryCode": "S"
        }
      ],
      "taxSummary": [
        { "vatCategoryCode": "S", "vatRate": 23, "taxableAmount": 100.00, "taxAmount": 23.00 }
      ],
      "totalNetAmount": 100.00,
      "totalTaxAmount": 23.00,
      "totalGrossAmount": 123.00
    }
  }'

Validation behaviour

On /v1/validate and /v1/generate, Irish invoices run the full EN 16931 + Peppol BIS 3.0 Schematron; failures carry the relevant BR-* / PEPPOL-* rule id. The response reports profileDetected: "peppol" and a peppolVersion. CreditNote payloads are supported (documentType: "creditnote").

Further reading