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.

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.

Revenue phases the B2B rollout: large corporates from 1 November 2028, VAT-registered businesses in intra-EU trade and those in the Large Corporates Division on 1 January 2028 from 1 November 2029, and the EU ViDA cross-border obligation from 1 July 2030. The 2028 and 2029 dates are set out in the Finance (No. 2) Bill 2026, which was still going through the Oireachtas when read on 22 October 2026.

Last verified against the European Union (Electronic Invoicing in Public Procurement) Regulations 2019 (S.I. No. 258 of 2019, made 12 June 2019 and in operation from that day under section 16(3) of the Interpretation Act 2005) on irishstatutebook.ie, the Office of the Revenue Commissioners' Implementation of eInvoicing in Ireland, 2026 Update (published 21 October 2026), its eInvoicing Hub (the Implementation phases and Large Corporates Phase One pages), and the Finance (No. 2) Bill 2026 on oireachtas.ie on 22 October 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.

• Generate Irish Peppol invoices via standard: "peppol-bis" (profile peppol), addressed with the Irish VAT endpoint scheme (IE:VAT, Peppol EAS 9935).
• Validate Peppol BIS UBL against the full EN 16931 + Peppol BIS 3.0 Schematron (peppolVersion in the response). Parse reads its fields and runs no rules.
• Validation depth on the Peppol path is Authority-checked: Beliq asserts verdict parity against OpenPeppol’s own unit-test corpus (335 cases) plus its published example invoices. The pinned Peppol BIS Schematron carries no Irish national rule family, so the shared corpus is the only suite that applies. It exercises some of the pack’s rules and not others: what the test suites cover gives the count. A calendar-enforced re-check watches for any future all-Ireland CIUS or mandate phase change. See how verification works for the tier definitions and the verificationTier field that reports them.

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.

Today you send Beliq’s UBL output through your chosen Access Point (BYOC). Managed delivery over Peppol is in build. Authority oversight: Office of Revenue Commissioners + Office of Government Procurement.

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.

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
    }
  }'

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").

• Quickstart
• Authentication
• Peppol BIS format reference
• Format overview
• Generate API
• Validation artifacts, Peppol BIS Schematron
• EC eInvoicing in Ireland
• Revenue: Implementation of eInvoicing in Ireland, 2026 Update (PDF)