Buyer tax scheme code
The scheme of the buyer’s tax identifier; the default is VAT.
Field 25 in the tax-invoice list; the default is VAT.
Rule IBR-133-AE makes the scheme codes in the invoice VAT, the one exception being the seller tax registration identifier (IBT-032). The PINT AE model has no buyer counterpart to IBT-032.
| Identifier | IBT-048-1 |
|---|---|
| Path in the document | /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyTaxScheme/cac:TaxScheme/cbc:ID |
| Cardinality | 1..1 (when IBT-048 is present) |
| Data type | Code |
| Applies to | Tax invoice |
In JooDax
BuiltJooDax writes VAT with the buyer’s TRN. It never writes a buyer’s TIN in a tax scheme, since the PINT AE buyer has no place for it: a buyer’s TIN is its address (IBT-049). 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)
- PINT AE Billing 1.0.4 – Invoice transaction, semantic model (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
Checked on: 4 November 2026. What concerns JooDax is taken from the programs’ own code.