Buyer VAT identifier (TRN)
The buyer’s VAT registration number, given on a tax invoice when the buyer is registered.
Field 24 in the tax-invoice list: buyers in the UAE registered for tax give their TRN. On a commercial invoice, the buyer’s legal registration identifier takes its place.
Rule IBR-135-AE asks for this number or the buyer identifier when the buyer’s address does not start with 1 and the invoice is not an export. For a foreign buyer, the guidelines say it is filled only if the buyer has a VAT number relevant to the transaction.
| Identifier | IBT-048 |
|---|---|
| Path in the document | /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID |
| Cardinality | 0..1 |
| Data type | Identifier |
| Applies to | Tax invoice |
In JooDax
Partly builtJooDax requires the buyer’s TRN on every tax invoice except with the predefined endpoints. That is stricter than the Ministry’s list, which asks it only of registered buyers: a buyer inside the system but not registered for VAT is refused by JooDax. For a buyer in the UAE it checks the TRN’s shape (IBR-132-AE). 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
- UAE Electronic Invoice Mandatory Fields (vV 1.1) — Ministry of Finance, United Arab Emirates
- PINT AE Billing 1.0.4 – Invoice transaction, syntax binding (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- PINT AE Billing 1.0.4 – AE specific PINT rules (jurisdiction aligned rules) (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- 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.