What Peppol Document Type Identifiers Are

Every document transmitted over the Peppol network carries a Document Type Identifier (DTI). This is a structured string that tells the receiving ASP exactly what kind of document is arriving and which specification version it conforms to. It is not a field inside the invoice XML — it is part of the Peppol transport envelope, carried in the AS4 messaging layer.

The DTI determines which schematron rules the receiving ASP applies to validate the document. A mismatched DTI — for example, sending a PINT-AE invoice with a PINT-SG (Singapore) document type identifier — will either fail validation or route incorrectly.

UAE Document Type Identifiers

The UAE has registered two primary document type identifiers with OpenPeppol for the PINT-AE standard:

Document TypeDocument Type Identifier
Tax Invoice (PINT-AE)urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:peppol:pint:billing-1@ae-1::2.1
Credit Note (PINT-AE)urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2::CreditNote##urn:peppol:pint:billing-1@ae-1::2.1

The @ae-1 segment is the UAE country extension identifier. It signals that this document follows the UAE-specific customisation of the PINT billing specification, rather than the Singapore (@sg-1), Japan (@jp-1), or other national extensions.

Process Identifier

Alongside the Document Type Identifier, Peppol transport also requires a Process Identifier that identifies the business process being executed. For UAE Electronic Invoicing the process identifier is:

urn:peppol:bis:billing

Both identifiers are configured at the ASP level — suppliers do not typically encode them manually. However, when testing end-to-end connectivity or configuring direct API integrations with an ASP, both values must be specified correctly in the transport headers.

Why Businesses Need to Understand This

While ASPs handle DTI configuration in most production setups, there are three scenarios where enterprise teams need to understand DTIs directly. First, when performing end-to-end connectivity testing against a test SMP/SML, the correct DTI must be specified in test tool configuration. Second, when an organisation operates its own Peppol access point as its ASP, the DTI must be registered in the SMP for each participant. Third, when troubleshooting a document delivery failure, the AS4 transport logs will reference the DTI — and an incorrect DTI is a common root cause.

ERP teams integrating directly with an ASP API (rather than routing through a middleware layer) must also ensure that API calls specify the UAE DTI, not a generic Peppol billing DTI or a DTI from another jurisdiction.

Relation to the PINT-AE Schematron

The PINT-AE schematron validation rules are version-locked to the @ae-1 specification. A document transmitted with the correct DTI will be validated against the full PINT-AE rule set — 302 rules covering mandatory fields, code list conformance, and UAE-specific business rules. Documents transmitted with an incorrect DTI may bypass country-specific rules and fail at a later reconciliation stage.

ERP and IT Configuration Requirements

  • Confirm with your ASP that they have registered the UAE DTI (@ae-1) for your Participant Identifier in the Peppol SMP.
  • In test environments, specify the full UAE Document Type Identifier string — not a shorthand or generic Peppol billing reference.
  • If operating a self-managed access point, register both the invoice and credit note DTIs for each UAE entity.
  • When reviewing AS4 transport logs for delivery failures, check the DTI in the message header as a first diagnostic step.
  • Do not reuse DTI configurations from other Peppol jurisdictions (Singapore, EU) for UAE transactions — the country extension suffix differs.

Related Posts