BR-CL-16 in your own invoice? Upload the file and find every error in seconds.
What does BR-CL-16 mean?
Payment means in an invoice MUST be coded using UNTDID 4461 code list. The value must come from the prescribed code list; free or wrong codes are rejected by the standard.
Common causes of BR-CL-16
- A code was used that the prescribed code list does not contain.
- Typo or outdated code.
- Wrong upper/lower case in the code.
How to fix BR-CL-16
- Find the faulty spot in the XML. Open the XML of the invoice and go to field BT-81 along this XPath:
//ram:SpecifiedTradeSettlementPaymentMeans/ram:TypeCode - Apply the fix. Code the payment means (BT-81) with a code from UNTDID 4461, e.g. '58' (SEPA credit transfer), '59' (SEPA direct debit), '30' (credit transfer).
- Validate again. Save the file and validate it again to check that BR-CL-16 is no longer reported.
Concrete fix
Code the payment means (BT-81) with a code from UNTDID 4461, e.g. '58' (SEPA credit transfer), '59' (SEPA direct debit), '30' (credit transfer).
XPath
//ram:SpecifiedTradeSettlementPaymentMeans/ram:TypeCodeBefore / after: the XML example
This is the spot in question before and after the fix (Cross Industry Invoice, ZUGFeRD/Factur-X).
Wrong
<ram:SpecifiedTradeSettlementPaymentMeans>
<ram:TypeCode>99</ram:TypeCode>
</ram:SpecifiedTradeSettlementPaymentMeans>
Correct
<ram:SpecifiedTradeSettlementPaymentMeans>
<ram:TypeCode>58</ram:TypeCode>
</ram:SpecifiedTradeSettlementPaymentMeans>Frequent questions about BR-CL-16
How do I fix BR-CL-16?
Code the payment means (BT-81) with a code from UNTDID 4461, e.g. '58' (SEPA credit transfer), '59' (SEPA direct debit), '30' (credit transfer).
Related error codes
Check BR-CL-16 automatically
Instead of digging through the XML by hand you can validate your ZUGFeRD or XRechnung file online – upload the PDF or the XML and you get every error with rule ID, affected field, fix and XPath, as a readable report or as JSON through the API.