Source: PINT-AE BIS Invoice v1.0.2 Schematron

Rule at a Glance

ID Severity Context (XPath)
BR-01 Fatal (error) ubl:Invoice
Series reference: BR-01  |  Schematron ID: ibr-001

Classification

Syntax & Integration — This rule validates a structural routing field that identifies the document specification, not a business data field drawn from the transaction itself.

What the Rule Is Checking

BR-01 requires that every invoice document contains a non-empty cbc:CustomizationID element at the invoice header level. In PINT-AE BIS Invoice v1.0.2, the only permitted value for this element is the full PINT-AE specification identifier string. The rule fails — fatally — if the element is absent or carries an empty value.

This is BT-24 in the PINT-AE data model. It appears as the first substantive field in the UBL XML structure, immediately after the namespace declarations.

Why This Rule Exists

The Specification Identifier tells the receiving system — and the UAE Peppol Access Point — which business rules apply to this document. Without it, a receiving system cannot determine whether to validate the document against PINT-AE, EN 16931, or another specification. In a multi-standard Peppol network, omitting BT-24 creates routing ambiguity that can cause valid invoices to fail downstream processing.

In the UAE context, the FTA and accredited service providers (ASPs) use BT-24 to confirm that a document is a PINT-AE compliant invoice before applying UAE-specific validation rules. A document without BT-24 will be rejected before any business-content validation occurs.

Standard / Code List

BT-24 must carry exactly this value for UAE tax invoices transmitted via the PINT-AE network:

urn:peppol:pint:billing-1@ae-1

For UAE credit notes (document type code 381), the same CustomizationID value applies. The Peppol Document Type Identifier (transmitted separately in the envelope) distinguishes invoice from credit note at the access point level — BT-24 itself is identical for both.

UAE Data Example

PASSES ✓
<cbc:CustomizationID>urn:peppol:pint:billing-1@ae-1</cbc:CustomizationID>

FAILS ✗ — Element absent:
<!-- No cbc:CustomizationID present -->

FAILS ✗ — Wrong specification (EN 16931 value):
<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>

FAILS ✗ — Empty element:
<cbc:CustomizationID></cbc:CustomizationID>

What Your ERP / IT Team Must Ensure

  • The UBL mapping layer must hardcode BT-24 as urn:peppol:pint:billing-1@ae-1 for all outbound UAE e-invoices — this value should never be sourced from a configuration table or user input.
  • Where an ERP system generates multiple Peppol document variants (e.g., EU PEPPOL BIS 3.0 for European entities and PINT-AE for UAE entities), the CustomizationID must be set per-entity based on the Peppol profile, not globally across all output.
  • Any XSL transformation or middleware that wraps ERP output into UBL must preserve BT-24 and must not strip it during namespace normalisation.
  • ASP integration tests should verify BT-24 presence and exact string match before submitting to the Peppol network. A mismatch will produce a BR-01 fatal error at the schematron validation stage.

Related Rules

BR-02 (Invoice number), BR-03 (Invoice issue date), BR-04 (Invoice type code), Peppol Document Type Identifiers for UAE