Every document on the Peppol network has a DocumentTypeId. This is a unique URN (Uniform Resource Name) that precisely indicates which format and profile the document follows. The DocumentTypeId is used for SMP registration (to indicate which documents an organisation can receive), for routing and for validation.

A DocumentTypeId looks complex at first glance but follows a fixed structure. Take the NLCIUS invoice DocumentTypeId as an example:

urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:nen.nl:nlcius:v1.0::2.1

This contains three parts:

The root namespace tells which XML schema is used. The customization tells which profile and country-specific implementation applies. The version refers to the UBL specification version.

The table below contains the most commonly used DocumentTypeIds for invoices and credit notes.

The eConnect PSB groups DocumentTypeIds into document families. When configuring SMP capabilities or querying document types via the API, you can use these family names as shorthand instead of full URNs.

Tip: via the PSB API you can use queryRecipientParty to query which DocumentTypeIds a receiver supports. This is useful for checking in advance whether your document can be delivered correctly.

Some formats are no longer valid on the Peppol network:

Note: if your invoices are being rejected with an error about an invalid CustomizationID, check whether you are still using a deprecated format. Upgrade to NLCIUS/SI-UBL 2.0 or BIS Billing V3.

More information about the complete code lists can be found in the Peppol BIS Billing specification at docs.peppol.eu/poacc/billing/3.0/.

• Peppol Party Identifiers per country
• Peppol BIS Billing V3
• NLCIUS: the Dutch standard
• NLCIUS with G-account
• Download XML sample files