Skip to content
IBT-047

Buyer legal registration identifier

The licence, ID or passport number identifying the buyer in law; required on a commercial invoice.

Field 24 in the commercial-invoice list, in place of the buyer’s tax number. Rule IBR-136-AE makes it required on types 480 and 81, as the guidelines confirm.

Otherwise IBR-149-AE asks for it when the buyer’s scheme is 0235 and the address matches neither 1XXXXXXXXX nor 9XXXXXXXXX. The guidelines say it and the buyer identifier IBT-046 are distinct fields, not interchangeable.

IdentifierIBT-047
Path in the document/Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID
Cardinality0..1 (required on 480 and 81 by IBR-136-AE)
Data typeIdentifier
Applies toCommercial invoice

In JooDax

Built

JooDax requires the identifier and its type on 480 and 81, requires the identifier whenever the buyer’s address is neither a TIN nor a 9XXXXXXXXX value (IBR-149-AE), and writes it on a tax invoice when present. 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.