Seller tax registration identifier (TIN)
The 10-digit TIN, given by a seller not registered for VAT.
In the commercial-invoice list, field 15 is the seller tax registration identifier: a seller without a TRN gives its TIN. Rule IBR-148-AE expects ten digits shaped 1XXXXXXXXX, and IBR-177-AE requires IBT-031 or IBT-032.
It goes in a second PartyTaxScheme whose scheme is not VAT; the syntax binding says "use TAX code". The guidelines confirm this covers persons registered for Corporate Tax but not for VAT.
| Identifier | IBT-032 |
|---|---|
| Path in the document | /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID!='VAT']/cbc:CompanyID |
| Cardinality | 0..1 (IBT-031 or IBT-032 required, IBR-177-AE) |
| Data type | Identifier |
| Applies to | Commercial invoice |
In JooDax
BuiltJooDax writes the TIN when there is no TRN and accepts it on a commercial invoice instead of a TRN, under the scheme TAX (see IBT-031-1), and checks its shape: ten digits starting with 1 (IBR-148-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.