What Is UNCL4461?
UNCL4461 is the UN/EDIFACT code list for payment means — the codes that identify how a payment is, or is expected to be, made. The code list is maintained by UN/CEFACT as part of the EDIFACT standard suite. In PINT-AE electronic invoicing, a subset of UNCL4461 codes is used in the payment means element (cac:PaymentMeans/cbc:PaymentMeansCode) to declare the payment method applicable to the invoice.
The UAE Subset: 9 Permitted Codes
The PINT-AE specification does not permit the full UNCL4461 code list. Only the 9 codes included in the UAE-specific genericode file (UNCL4461.gc) are valid. Submitting any other UNCL4461 code will result in a fatal validation error at the ASP.
| Code | Name | Description |
|---|---|---|
| 1 | Instrument not defined | Payment method is not legally defined or is to be agreed separately between the parties. |
| 10 | In cash | Payment by currency (including bills and coins) in circulation, including checking account deposits. |
| 20 | Cheque | Payment by a pre-printed form on which instructions are given to an account holder to pay a stated sum to a named recipient. |
| 21 | Banker's draft | Issue of a banker's draft in payment of the funds. |
| 30 | Credit transfer | Payment by credit movement of funds from one account to another. |
| 49 | Direct debit | The amount is to be, or has been, directly debited to the customer's bank account. |
| 54 | Credit card | Payment made by means of credit card. |
| 55 | Debit card | Payment made by means of debit card. |
| 68 | Online payment service | Payment will be made or has been made by an online payment service. |
Is Payment Means Mandatory?
The payment means element is optional in PINT-AE — an invoice can be submitted without it and will not fail validation on that basis alone. However, where payment terms or settlement instructions are provided (e.g. bank account details, payment due date), best practice is to include the payment means code to give the buyer and the FTA a machine-readable indicator of the payment method. Many commercial contracts also require it for accounts payable automation at the buyer's end.
How to Map Common UAE Payment Methods
Bank transfer / IBAN payment is the dominant B2B settlement method in the UAE. This maps to code 30 (credit transfer). Invoices that include IBAN and bank details in the payment means block should carry code 30.
Online payment gateways (PayTabs, Network International, Stripe, etc.) map to code 68 (online payment service).
Post-dated cheques, still used in UAE commercial practice particularly for rent and trade credit, map to code 20 (cheque).
Cash payments in B2B contexts should use code 10. Note that the UAE has regulatory cash payment thresholds under AML legislation — the payment means code on an electronic invoice does not substitute for compliance with those requirements.
ERP Configuration Considerations
- Map every payment method code currently used in the ERP to one of the 9 permitted UNCL4461 values
- For payment methods that do not map cleanly, use code 1 (instrument not defined) rather than leaving the element empty or using an invalid code
- Confirm that the PINT-AE XML output places the payment means code in
cac:PaymentMeans/cbc:PaymentMeansCode, not in a narrative text field - Where bank account details are included in the invoice, ensure the payment means code is 30 to maintain internal consistency
- Test the full range of payment scenarios — including mixed-payment and advance-payment invoices — against the schematron before go-live
Advance Payments and Prepayments
The UAE Electronic Invoicing Guidelines V1.1 (Appendix 5) includes specific guidance on advance payments and retention. Where an invoice references a prior advance payment, the advance payment amount is typically reflected in the invoice document-level allowance or in a preceding prepayment document — not through the payment means code. The payment means code describes how the remaining balance is expected to be settled, not the history of prior payments.