PEPPOL support

Problem/Motivation

As of 1st January 2026 e-invoicing becomes mandatory in Belgium and the rest of the EU. The protocol uses PEPPOL access points.

The following schemas in UBL/XML are required:

1. Peppol BIS Billing UBL CreditNote V3 (busdox-docid-qns::urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2::CreditNote##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1)
2. busdox-docid-qns::urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2::CreditNote##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:selfbilling:3.0::2.1
3. Peppol UBL.BE Credit Note 3.0 (busdox-docid-qns::urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2::CreditNote##urn:cen.eu:en16931:2017#conformant#urn:UBL.BE:1.0.0.20180214::2.1)
4. Peppol BIS Billing UBL Invoice V3 (busdox-docid-qns::urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1)
5. busdox-docid-qns::urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:selfbilling:3.0::2.1
6. Peppol UBL.BE Invoice 3.0 (busdox-docid-qns::urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#conformant#urn:UBL.BE:1.0.0.20180214::2.1)

The following are advised, but not mandatory.

1. Peppol Invoice Response transaction 3.0 (busdox-docid-qns::urn:oasis:names:specification:ubl:schema:xsd:ApplicationResponse-2::ApplicationResponse##urn:fdc:peppol.eu:poacc:trns:invoice_response:3::2.1)
2. Peppol Message Level Response transaction 3.0 (busdox-docid-qns::urn:oasis:names:specification:ubl:schema:xsd:ApplicationResponse-2::ApplicationResponse##urn:fdc:peppol.eu:poacc:trns:mlr:3::2.1)

Steps to reproduce

Proposed resolution

Are there any plans to implement a feature so that invoices are converted to compliant UBL/XML and sent directly to a configured access point? This will become necessary as of 01/01/2026.

Remaining tasks

User interface changes

API changes

Data model changes