Item name
The name of the goods or service on the line.
Field 50 in the tax-invoice list and field 48 in the commercial list.
To tell goods from services the guidelines point to the item type (BTAE-13) with G, S or B; with G an item classification code is required, with S a service accounting code (IBR-184-AE and IBR-185-AE). The guidelines say HSN codes are optional for now.
| Identifier | IBT-153 |
|---|---|
| Path in the document | /Invoice/cac:InvoiceLine/cac:Item/cbc:Name |
| Cardinality | 1..1 |
| Data type | Text |
| Applies to | Tax invoice and Commercial invoice |
In JooDax
BuiltJooDax writes the name and refuses its absence (naming it field 50, the tax-invoice number). It writes no item type or classification codes. 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.