Is OIOUBL the same as PEPPOL?

No, but they are close. Both are UBL 2.1 and EN 16931-compliant; OIOUBL is the Danish national profile with its own CustomizationID and rules.

Which OIOUBL version is current?

OIOUBL 3.0 (2021), which aligns the Danish profile with EN 16931. Earlier OIOUBL 2.x predated the European standard.

What syntax does OIOUBL use?

OASIS UBL 2.1 XML - the same syntax as PEPPOL BIS and XRechnung-UBL.

Can I convert OIOUBL to PEPPOL?

Yes. Both are UBL 2.1 / EN 16931, so the conversion mainly changes the CustomizationID and applies the PEPPOL rules; the invoice data transfers cleanly.

What is OIOUBL?

OIOUBL is the Danish national e-invoice profile, built on UBL 2.1 and conforming to EN 16931. Version 3.0 (2021) aligns Denmark with the European semantic standard.

Open a OIOUBL file in the viewer → See every business term, a visual preview and the raw XML.

Country: Denmark 🇩🇰
Syntax: UBL 2.1
Version: 3.0 (2021)

Key facts

CustomizationID urn:cen.eu:en16931:2017#compliant#urn:fdc:digst.dk:2021:oioubl:3.0.
UBL 2.1 syntax.
Used for Danish public-sector invoicing; maintained by the Danish Agency for Digitisation.

OIOUBL and EN 16931

OIOUBL is the Danish national e-invoice profile, built on OASIS UBL 2.1. Denmark was an early adopter of UBL-based public invoicing; the earlier OIOUBL 2.x predated EN 16931. Version 3.0 (2021), maintained by the Danish Agency for Digitisation (Digitaliserings- styrelsen), aligns the profile with the European standard, so an OIOUBL 3.0 invoice is also an EN 16931 invoice.

Its CustomizationID, urn:cen.eu:en16931:2017#compliant#urn:fdc:digst.dk:2021:oioubl:3.0, declares EN 16931 compliance constrained by the Danish OIOUBL 3.0 ruleset.

OIOUBL, PEPPOL and Nemhandel

Both OIOUBL and PEPPOL BIS are UBL 2.1, EN 16931-compliant profiles - they differ in their CustomizationID and national rules, not their syntax. Denmark exchanges invoices over Nemhandel, the national infrastructure, which interoperates with the PEPPOL network. In practice a Danish receiver may accept OIOUBL or PEPPOL BIS; the documents look very similar because they share the UBL structure and the European semantic model.

Converting OIOUBL

Because OIOUBL 3.0 sits on the same UBL 2.1 syntax and EN 16931 model as PEPPOL BIS and XRechnung-UBL, converting between them is largely a question of swapping the CustomizationID and applying the target profile’s rules - the business data carries over cleanly. Facturus reads and writes OIOUBL 3.0, so it can act as the Danish endpoint of a cross-border conversion.

Frequently asked questions

Is OIOUBL the same as PEPPOL?: No, but they are close. Both are UBL 2.1 and EN 16931-compliant; OIOUBL is the Danish national profile with its own CustomizationID and rules.
Which OIOUBL version is current?: OIOUBL 3.0 (2021), which aligns the Danish profile with EN 16931. Earlier OIOUBL 2.x predated the European standard.
What syntax does OIOUBL use?: OASIS UBL 2.1 XML - the same syntax as PEPPOL BIS and XRechnung-UBL.
Can I convert OIOUBL to PEPPOL?: Yes. Both are UBL 2.1 / EN 16931, so the conversion mainly changes the CustomizationID and applies the PEPPOL rules; the invoice data transfers cleanly.

Do more with Facturus

Convert a file XRechnung, Factur-X, PEPPOL, FatturaPA, UBL, CII - any direction, EN 16931. Validate against EN 16931 Upload an invoice and get the compliance report - no conversion. Identify a file Not sure what you have? Detect the format or check a PDF instantly.