Etoolio

PINT AE Data Dictionary

Free PINT AE data dictionary. Search every UAE e-invoice business term (BT) and group (BG) with its cardinality and UBL 2.1 XML path, the core mandatory fields, and where the TRN and PINT AE identifiers go.

Updated

76fields
26core mandatory
22business groups
UBLΒ 2.1ENΒ 16931 model

76 fields

required optional repeatable
BG-1Invoice information/Invoice
BT-1
Invoice number
1..1
BT-2
Invoice issue date
1..1
BT-3
Invoice type codeUN/ECE 1001 code, e.g. 380 (commercial invoice), 381 (credit note).
1..1
BT-5
Invoice currency codeUsually AED for domestic UAE supplies.
1..1
BT-6
VAT accounting currency codeAED when the invoice currency differs, so VAT is shown in AED.
0..1
BT-7
Value added tax point date
0..1
BT-9
Payment due date
0..1
BT-10
Buyer reference
0..1
BT-13
Purchase order reference
0..1
BT-19
Buyer accounting reference
0..1
BT-20
Payment terms
0..1
BG-2Process control/Invoice
BT-23
Business process typeFixed for PINT AE: urn:peppol:bis:billing
1..1
BT-24
Specification identifierIdentifies the PINT AE profile: urn:peppol:pint:billing-1@ae-1
1..1
BG-3Preceding invoice referencecac:BillingReference/cac:InvoiceDocumentReference
BT-25
Preceding invoice numberRequired on credit notes to reference the original invoice.
1..1
BT-26
Preceding invoice issue date
0..1
BG-4Invoice notecbc:Note
BT-22
Invoice note
0..n
BG-5Invoice periodcac:InvoicePeriod
BT-73
Invoicing period start date
0..1
BT-74
Invoicing period end date
0..1
BG-7Sellercac:AccountingSupplierParty/cac:Party
BT-27
Seller name
1..1
BT-28
Seller trading name
0..1
BT-29
Seller identifier
0..n
BT-30
Seller legal registration identifier
0..1
BT-31
Seller VAT identifierCarries the seller's 15-digit UAE Tax Registration Number (TRN).
0..1
BT-34
Seller electronic addressPeppol participant ID for routing; scheme 0235 is used for the UAE.
1..1
BG-8Seller postal addresscac:PostalAddress
BT-35
Seller address line 1
0..1
BT-37
Seller city
0..1
BT-39
Seller country subdivisionThe Emirate, e.g. Dubai, Abu Dhabi.
0..1
BT-40
Seller country codeAE for the United Arab Emirates (ISO 3166-1).
1..1
BG-9Seller contactcac:Contact
BT-43
Seller contact email address
0..1
BG-10Buyercac:AccountingCustomerParty/cac:Party
BT-44
Buyer name
1..1
BT-46
Buyer identifier
0..1
BT-47
Buyer legal registration identifier
0..1
BT-48
Buyer VAT identifierBuyer's 15-digit UAE TRN, required for B2B supplies to a registered business.
0..1
BT-49
Buyer electronic addressBuyer's Peppol participant ID (scheme 0235 for the UAE).
1..1
BG-11Buyer postal addresscac:PostalAddress
BT-50
Buyer address line 1
0..1
BT-52
Buyer city
0..1
BT-55
Buyer country codeAE for a domestic UAE buyer.
1..1
BG-13Delivery informationcac:Delivery
BT-69
Actual delivery date
0..1
BT-70
Deliver to location identifier
0..1
BT-75
Deliver to city
0..1
BT-78
Deliver to country code
0..1
BG-16Seller tax representative partycac:TaxRepresentativeParty
BT-63
Seller tax representative VAT identifier
1..1
BG-17Payment instructionscac:PaymentMeans
BT-81
Payment means type code
1..1
BT-83
Remittance information
0..1
BG-18Credit transfercac:PaymentMeans/cac:PayeeFinancialAccount
BT-84
Payment account identifierThe IBAN of the account to be paid.
1..1
BG-20Document level allowancescac:AllowanceCharge [ChargeIndicator=false]
BT-92
Document level allowance amount
1..1
BT-95
Document level allowance VAT category code
1..1
BG-21Document level chargescac:AllowanceCharge [ChargeIndicator=true]
BT-99
Document level charge amount
1..1
BT-102
Document level charge VAT category code
1..1
BG-22Document totalscac:LegalMonetaryTotal
BT-106
Sum of invoice line net amount
1..1
BT-107
Sum of allowances on document level
0..1
BT-108
Sum of charges on document level
0..1
BT-109
Invoice total amount without VAT
1..1
BT-110
Invoice total VAT amount
0..1
BT-112
Invoice total amount with VAT
1..1
BT-113
Paid amount
0..1
BT-114
Rounding amount
0..1
BT-115
Amount due for payment
1..1
BG-23VAT breakdowncac:TaxTotal/cac:TaxSubtotal
BT-116
VAT category taxable amount
1..1
BT-117
VAT category tax amount
1..1
BT-118
VAT category codeS = standard 5%, Z = zero-rated, E = exempt, O = out of scope.
1..1
BT-119
VAT category rate5 for standard-rated UAE VAT; 0 for zero-rated.
0..1
BT-120
VAT exemption reason text
0..1
BG-25Invoice linecac:InvoiceLine
BT-126
Invoice line identifier
1..1
BT-127
Invoice line note
0..1
BT-129
Invoiced quantity
1..1
BT-130
Invoiced quantity unit of measureUN/ECE Rec 20 code, e.g. EA (each), HUR (hour), KGM (kilogram).
1..1
BT-131
Invoice line net amount
1..1
BG-29Price detailscac:InvoiceLine/cac:Price
BT-146
Item net price
1..1
BT-149
Item price base quantity
0..1
BG-30Line VAT informationcac:Item/cac:ClassifiedTaxCategory
BT-151
Invoiced item VAT category code
1..1
BT-152
Invoiced item VAT rate
0..1
BG-31Item informationcac:InvoiceLine/cac:Item
BT-153
Item name
1..1
BT-154
Item description
0..1
BT-155
Item seller's identifier
0..1
BT-158
Item classification identifier
0..n

marks the core mandatory fields. This is a working reference to the PINT AE model, which inherits its business terms from ENΒ 16931 / Peppol BIS BillingΒ 3.0. The binding source is the UAE Ministry of Finance / FTA PINT AE specification β€” always validate and submit through your Accredited Service Provider (ASP).

Every PINT AE invoice field, in one searchable place

The PINT AE data dictionary is the definitive list of the fields a UAE e-invoice can carry β€” each identified by a business term code (BT), grouped into business groups (BG), with a cardinality that says how many times it may appear and a UBL 2.1 XML path that says exactly where it lives in the file. PINT AE (Peppol International Invoice β€” Arab Emirates) doesn't invent these fields from scratch: it inherits the semantic model from the European standard EN 16931 and Peppol BIS Billing 3.0, then pins down UAE-specific rules on top β€” the 15-digit Tax Registration Number, the AED accounting currency, and a fixed specification identifier. This reference lets you search any of those fields by name, by code, or by XML element in seconds.

What is PINT AE built on?

Three layers stack up. At the base, EN 16931 defines the meaning of an invoice β€” the ~130 business terms every compliant e-invoice in Europe and beyond shares. Peppol BIS Billing 3.0 maps those terms onto UBL 2.1 XML and adds the rules for exchanging them over the Peppol network. PINT AE is the UAE country specialisation of that model, published for the Ministry of Finance and Federal Tax Authority mandate. Because the layers are inherited, the BT and BG codes you see here are stable and portable β€” learn them once and they apply across every Peppol jurisdiction.

Which fields are mandatory?

A minimal valid invoice is smaller than most people expect. The always-required core is: the invoice number (BT-1), issue date (BT-2), type code (BT-3) and currency (BT-5); the two PINT AE identifiers (BT-24 and BT-23); the seller's name, electronic address and country (BT-27, BT-34, BT-40); the buyer's name, electronic address and country (BT-44, BT-49, BT-55); at least one invoice line with its quantity, unit, net amount, price, item name and VAT category (BT-126, BT-129, BT-130, BT-131, BT-146, BT-153, BT-151); a VAT breakdown (BT-116 to BT-119); and the four document totals (BT-106, BT-109, BT-112, BT-115). Toggle the Core mandatory filter above to isolate exactly these.

Where do the UAE-specific values go?

  • Specification identifier (BT-24 / CustomizationID): urn:peppol:pint:billing-1@ae-1 β€” the value that marks a document as PINT AE.
  • Business process (BT-23 / ProfileID): urn:peppol:bis:billing.
  • Seller TRN (BT-31): the seller's 15-digit Tax Registration Number, in cac:PartyTaxScheme/cbc:CompanyID under the VAT scheme.
  • Buyer TRN (BT-48): the buyer's TRN, required for B2B supplies to a VAT-registered business.
  • Currency (BT-5): normally AED; if you invoice in another currency, VAT must still be shown in AED via BT-6.
  • Country (BT-40 / BT-55): AE; the Emirate goes in the country subdivision (BT-39).

How to read a cardinality

Cardinality is written as min..max. 1..1 means the field is required exactly once; 0..1 means optional, at most once; 0..n means optional and repeatable; 1..n means required and repeatable (an invoice must have at least one line, BG-25, but may have many). A field is only truly mandatory when both it and its parent group are present β€” an optional group such as Delivery (BG-13) can be left out entirely, but if you include it, its required children apply.

From reference to a real file

This dictionary tells you what each field means and where it belongs; when you're ready to produce or check an actual document, use the UAE E-Invoice (PINT AE) generator and validator to build a structurally correct UBL invoice from a simple form, or paste an existing XML to see which core fields are missing. Both tools run entirely in your browser β€” nothing you type is uploaded, which matters for financial data. For the mandate timeline and who has to comply when, the generator's deadline tab estimates your PINT AE go-live date based on your business size.

A working reference, not the binding spec

Treat this as a fast lookup for building, learning and debugging β€” not as the legal source. The authoritative definitions, code lists and business rules are published by the UAE Ministry of Finance and Federal Tax Authority as the PINT AE specification, alongside the OpenPeppol PINT AE package. When it's time to send real invoices, an Accredited Service Provider (ASP) performs the full Peppol schema and business-rule validation and handles transmission over the network.

Good to know

PINT AE Data Dictionary, frequently asked questions

What is the PINT AE data dictionary?

It is the list of every business term (BT) and business group (BG) that a UAE PINT AE e-invoice can contain, each with its cardinality (how many times it may appear) and its UBL 2.1 XML path. PINT AE inherits this semantic model from EN 16931 and Peppol BIS Billing 3.0, adding UAE-specific rules such as the Tax Registration Number (TRN) and the PINT AE specification identifier.

Which fields are mandatory in a PINT AE invoice?

A minimal valid invoice needs its core fields: invoice number (BT-1), issue date (BT-2), type code (BT-3), currency (BT-5), the PINT AE specification and process identifiers (BT-24, BT-23), seller and buyer name, electronic address and country (BT-27/34/40, BT-44/49/55), at least one line (BT-126, BT-129, BT-130, BT-131, BT-146, BT-153, BT-151), a VAT breakdown (BT-116 to BT-119) and the document totals (BT-106, BT-109, BT-112, BT-115). Use the 'Core mandatory' filter to see them all.

What are the PINT AE CustomizationID and ProfileID?

The specification identifier (BT-24, CustomizationID) is urn:peppol:pint:billing-1@ae-1 and the business process (BT-23, ProfileID) is urn:peppol:bis:billing. These two values tell the Peppol network that the document follows the UAE PINT AE profile.

Where does the UAE TRN go in the XML?

The seller's 15-digit Tax Registration Number is carried in the Seller VAT identifier (BT-31), and the buyer's TRN in the Buyer VAT identifier (BT-48), both mapped to cac:PartyTaxScheme/cbc:CompanyID under the VAT tax scheme. The Emirate goes in the country subdivision (BT-39) and the country code (BT-40/BT-55) is AE.

Is this the official specification?

No. This is a fast, searchable working reference to help you build and debug invoices. The binding source is the UAE Ministry of Finance / Federal Tax Authority PINT AE specification and the OpenPeppol PINT AE package. Always validate and submit through your Accredited Service Provider (ASP).