What Is PINT-AE BIS v1.0.2?

PINT-AE BIS v1.0.2 is the UAE's mandatory electronic invoice standard, derived from the Peppol International (PINT) billing specification. It defines the exact structure, mandatory fields, code lists, and validation rules that every electronic invoice issued in the UAE must comply with from 1 January 2027 (large enterprises) and 1 July 2027 (all other businesses in scope).

PINT stands for Peppol INTernational — a family of technical specifications created by OpenPeppol to allow countries to customise invoice formats while maintaining interoperability across the global Peppol network. The "AE" suffix designates the UAE-specific jurisdiction layer applied on top of the international PINT core.

The Three-Layer Architecture

Understanding PINT-AE requires understanding how it is constructed. There are three layers:

Layer 1 — UBL 2.1. The underlying XML grammar is OASIS Universal Business Language version 2.1. Every PINT-AE invoice is a UBL 2.1 XML document. UBL defines the element names, structure, and namespace (urn:oasis:names:specification:ubl:schema:xsd:Invoice-2).

Layer 2 — PINT Core. OpenPeppol defines a set of business rules — what fields are mandatory globally, what code lists must be used, and how amounts must be calculated. This layer ensures that a PINT-AE invoice can be read by any Peppol-connected system worldwide.

Layer 3 — UAE Jurisdiction-Aligned Rules. The UAE Ministry of Finance adds its own mandatory fields and validation rules on top of the PINT core. These rules are encoded in two schematron files: PINT-UBL-validation-preprocessed.sch (PINT core rules) and PINT-jurisdiction-aligned-rules.sch (UAE-specific rules). These schematron files contain 302 validation rules in total.

What the Standard Governs

PINT-AE BIS v1.0.2 governs every aspect of a compliant UAE electronic invoice:

  • Which XML elements are mandatory, conditional, or optional
  • Which code lists must be used for country codes (ISO 3166), currency codes (ISO 4217), unit of measure codes (UNECE Rec 20), payment means codes (UNCL4461), and invoice type codes (UNCL1001)
  • How VAT category codes (S, Z, E, O) must be applied at line and document level
  • How the Participant Identifier — constructed as 0235: followed by the 10-digit TIN — must be formatted for both supplier and buyer
  • How monetary amounts, tax totals, and line extensions must be calculated and reconciled
  • What transaction type flags (B2B, B2G, self-billing) must be declared

Scope and Applicability

PINT-AE BIS v1.0.2 applies to electronic invoices and electronic credit notes exchanged between businesses (B2B) and between businesses and government entities (B2G) in the UAE. Consumer-facing transactions (B2C) are outside its scope. The standard applies regardless of VAT registration status — it is anchored to Corporate Tax registration, covering approximately 640,000 registered entities.

The standard covers invoices, credit notes (document type code 381), and self-billed invoices (document type code 389). Each has a distinct transaction profile within the PINT-AE specification.

Why This Matters for ERP and Finance Teams

PINT-AE BIS v1.0.2 is not a PDF form or a reporting format — it is a machine-readable XML schema enforced by automated schematron validation at the Accredited Service Provider (ASP) level. An invoice that fails any fatal rule will be rejected by the ASP before it reaches the buyer. There is no manual override path.

ERP systems must be configured to produce PINT-AE-compliant XML output. This means mapping every mandatory field in the ERP transaction to the correct UBL 2.1 element, applying the correct code list values, and ensuring calculation accuracy to the decimal place. The schematron rules that enforce all of this are examined individually in the PINT-AE Rule series on this site.

Global Equivalents

The PINT methodology is used across multiple jurisdictions. Singapore uses PINT-SG, Australia and New Zealand use A-NZ PINT, and the EU uses EN 16931 (a related but distinct standard). Because PINT-AE is built on the same PINT core, UAE businesses transacting internationally through the Peppol network have a structural advantage: the invoice format is interoperable without transformation at the schema level.