Skip to content
IBT-031

Seller VAT identifier (TRN)

The 15-digit VAT registration number, required on a tax invoice.

Field 15 in the tax-invoice list: a seller registered for VAT gives its registration number. Rule IBR-134-AE requires it on every type except 480 and 81, and IBR-132-AE expects 15 digits starting with 1 and ending with 03.

The guidelines (Appendix 6) warn that a Corporate Tax TRN or any other tax-type TRN does not go here; a seller not registered for VAT gives its TIN in IBT-032 instead.

IdentifierIBT-031
Path in the document/Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID='VAT']/cbc:CompanyID
Cardinality0..1 (required by IBR-134-AE except on 480 and 81)
Data typeIdentifier
Applies toTax invoice

In JooDax

Built

JooDax requires the number on the taxed types (380 and 381) and writes it under the VAT scheme, refusing its absence (field 15). For a party in the UAE it checks the shape IBR-132-AE asks: 15 digits, starting with 1 and ending with 03. The module is not yet wired to the programs’ invoices, and its output has not been through the official Schematron or an ASP’s validation.

crates/jdx-einvoice-ae/src/lib.rs

Related fields

Fields — E-invoicing in the UAE (PINT AE)

Sources

  1. UAE Electronic Invoice Mandatory Fields (vV 1.1) — Ministry of Finance, United Arab Emirates
  2. PINT AE Billing 1.0.4 – Invoice transaction, syntax binding (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
  3. PINT AE Billing 1.0.4 – AE specific PINT rules (jurisdiction aligned rules) (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
  4. UAE Electronic Invoicing Guidelines (vV 2.0) — Ministry of Finance, United Arab Emirates

Checked on: 4 November 2026. What concerns JooDax is taken from the programs’ own code.