BR-CL-16
Payment means in an invoice MUST be coded using UNTDID 4461 code list
What does this rule mean?
Payment means in an invoice MUST be coded using UNTDID 4461 code list
The value must come from a fixed code list.
Official rule message (standard)
Payment means in an invoice MUST be coded using UNTDID 4461 code list
Where the rule applies
Syntax: CII · UBL
The same rule, expressed twice: UBL and CII name the same fields with different paths. Running a CII file against the UBL rules is why you get errors that mean nothing.
UBL
cac:PaymentMeans/cbc:PaymentMeansCode
CII
ram:SpecifiedTradeSettlementPaymentMeans/ram:TypeCode
Technical test
The rule passes when this Schematron expression holds true:
((not(contains(normalize-space(.), ' ')) and contains(' 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 74 75 76 77 78 91 92 93 94 95 96 97 98 ZZZ ', concat(' ', normalize-space(.), ' '))))How to fix it
A wrong code-list value. A tool can suggest a valid code, but you confirm the correct one.
Choose a valid code — Beleggo proposes the nearest one.
Correct the affected entry in your XML, then re-check the invoice. Validation runs locally in your browser — your file never leaves your machine.
Check an e-invoice here
Drop an XML or ZUGFeRD PDF file here. Validation runs locally in your browser against EN 16931 — your file never leaves your machine.