What UNCL1001 Is
UNCL1001 is the UN/EDIFACT code list for document and message names. In PINT-AE, the invoice type code — the field that distinguishes a standard tax invoice from a credit note or debit note — is drawn from this list. It appears in the XML element cbc:InvoiceTypeCode for invoices and cbc:CreditNoteTypeCode for credit notes.
The full UNCL1001 list contains dozens of document types. PINT-AE restricts the permitted values to a small UAE-relevant subset. Using any code outside this subset will fail schematron validation and the document will be rejected by the ASP.
Permitted Values in PINT-AE
| Code | Document Type | PINT-AE Element |
|---|---|---|
| 380 | Commercial Invoice (Tax Invoice) | cbc:InvoiceTypeCode |
| 381 | Credit Note | cbc:CreditNoteTypeCode |
| 383 | Debit Note | cbc:InvoiceTypeCode |
| 386 | Prepayment Invoice | cbc:InvoiceTypeCode |
| 875 | Self-Billed Invoice | cbc:InvoiceTypeCode |
| 876 | Partial Invoice | cbc:InvoiceTypeCode |
Code 380 is the standard commercial tax invoice — the most common type. Code 381 is used for Electronic Credit Notes. Code 386 is specific to prepayment invoices issued before the final supply. Code 875 applies where the buyer issues the invoice on behalf of the supplier (self-billing arrangement under Article 5 of MD 243).
Why This Matters Operationally
Many ERP systems generate their own internal document type codes and map them to output formats during export. If the mapping is not configured specifically for PINT-AE, the wrong UNCL1001 code — or a proprietary code with no UNCL1001 equivalent — will be written into the XML. The ASP schematron validation will reject the document.
A common error is using code 389 (self-billed credit note) or 384 (corrected invoice), neither of which is permitted in PINT-AE. ERP output mapping must be audited against the permitted PINT-AE subset before go-live.
Special Scenarios
Prepayment invoices (386): Where a supplier receives an advance payment before delivering goods or services, a prepayment invoice is issued at the time of receipt. The final invoice, issued upon completion of the supply, must reference the prepayment invoice. Both documents flow through the Electronic Invoicing System.
Self-billing (875): Under Article 5 of MD 243, a buyer may issue Electronic Invoices on behalf of a supplier subject to prior agreement. The invoice carries code 875 and the buyer's ASP is responsible for transmission. The compliance obligation remains with the supplier.
Credit notes (381): An Electronic Credit Note is used to reduce or cancel a previous Electronic Invoice. It must reference the original invoice via the cac:BillingReference element. A credit note cannot be issued as a standalone document without referencing a prior transaction.
ERP and IT Configuration Requirements
- Map every internal document category (standard invoice, credit memo, debit memo, prepayment, self-bill) to the corresponding UNCL1001 code from the permitted PINT-AE subset.
- Validate that the correct XML element is used —
cbc:InvoiceTypeCodefor 380/383/386/875/876 andcbc:CreditNoteTypeCodefor 381. - Ensure credit note transactions carry a
cac:BillingReferenceto the original invoice UUID and sequential number. - Prepayment invoice workflows must be configured to generate a linking reference on the final invoice.
- Reject any internal document type that has no valid PINT-AE UNCL1001 mapping — do not default to 380.