Payment means code
The payment method (cash, card, transfer...) as a UNTDID 4461 code; optional.
The field is optional on every document, but when present it must come from UNTDID 4461 (BR-KSA-16, BR-CL-16), and each payment instruction must carry a code (BR-49). The data dictionary example is 30 (credit transfer).
PaymentMeans has a second job on notes: the reason for a credit or debit note (KSA-10) goes in its InstructionNote, so in practice a note carries this element even when the seller has no payment method to state.
| Identifier | BT-81 |
|---|---|
| Path in the document | /Invoice/cac:PaymentMeans/cbc:PaymentMeansCode |
| Cardinality | 1..n |
| Data type | Code |
| Applies to | Standard tax invoice and Simplified tax invoice |
| Group | BG-16 Payment instructions |
In JooDax
Partly builtThe programs write this element on credit notes only, always with code 10 (cash), because it is needed to carry the reason; the code does not reflect how the refund was actually paid.
crates/jdx-einvoice-sa/src/xml.rs
Applies to
| Tax invoice | Debit note | Credit note | Simplified | Simplified debit | Simplified credit |
|---|---|---|---|---|---|
| Optional | Optional | Optional | Optional | Optional | Optional |
Rules that check it
- BR-KSA-16 · If a payment means code is given, it must come from UNTDID 4461.
Related fields
Fields — E-invoicing in Saudi Arabia (FATOORA)
Sources
- Electronic Invoice XML Implementation Standard to the E-Invoicing resolution dated 2023-05-19 (v1.2) — ZATCA
- Electronic Invoice Data Dictionary to the E-Invoicing resolution dated 2023-05-19 (v1.2) — ZATCA
- الضوابط والمتطلبات والمواصفات الفنية والقواعد الإجرائية اللازمة لتنفيذ أحكام لائحة الفوترة الإلكترونية (قرار المحافظ رقم 62738 وتاريخ 1443/11/23هـ) (vfile dated 20230519 (decision 62738)) — ZATCA
Checked on: 4 November 2026. What concerns JooDax is taken from the programs’ own code.