EN 16931 (UBL), no CIUS
- Format id:
en16931-ubl - Countries: EU-wide
- Status: in active use
- Parser:
ublfamily, converts to canonical JSON
Bare EN 16931 or an unknown CIUS of it. Accepts the 2017 and 2026 specification identifiers.
Where you will receive it
Section titled “Where you will receive it”- BG:
en16931-ubl/-cii,peppol-bis3. No exchange mandate yet; B2B proposed for 2028. - EE:
e-arve,en16931-ubl,peppol-bis3. Since Jul 2025 buyers can require e-invoices. e-arve files can hold several invoices. - FR:
facturx,fr-ctc-ubl,fr-ctc-cii,en16931-ubl/-cii. All businesses must receive from 1 Sep 2026. Factur-X BASIC WL accepted until Sep 2027. CII D22B.
Mapping notes for the ubl parser family
Section titled “Mapping notes for the ubl parser family”- Phase 1. Covers: Peppol BIS 3 + self-billing, XRechnung UBL, NLCIUS, CIUS-RO, CIUS-PT, HR-CIUS, OIOUBL 3, UBL.BE, PINT, BIS 2 (best-effort), OIOUBL 2. One parser, profile-specific rules on top. Invoice vs CreditNote element names differ (
InvoicedQuantity/CreditedQuantity). UBL 2.1 CreditNote has no rootcbc:DueDate: readcac:PaymentMeans/cbc:PaymentDueDate, and accept a rootcbc:DueDateonly as a fallback with a warning (it appears in some XRechnung test files).
The same parser family handles the formats listed in Build order and mapping notes.
Check it
Section titled “Check it”- Drop a EN 16931 (UBL), no CIUS file into the browser converter to get canonical JSON; nothing is uploaded.
- Conformance checklist: fixtures, real samples, mapping source and validation for this format.
- Output shape: canonical-invoice.v1.schema.json.