What it means
The payment instructions (BG-16) have a payment means text (BT-82), a free-text description of how the invoice is paid, next to the payment means code (BT-81). In UBL it is the name attribute on the payment means code. The warning appears whenever that text is present.
Why it matters
This is a warning, so the invoice is not rejected. The code already tells the recipient how the invoice is paid, and software reads the code, not free text.
How to fix it
Keep the payment means code, such as 30 for a bank transfer or 58 for a SEPA credit transfer, and remove the description text. In your invoicing software, look at the payment method settings for a field that holds a description or name for the method. It is worth fixing if you want a clean check, and you can otherwise leave it.
The rule as published
The use of a payment means text (cac:PaymentMeans/cbc:PaymentMeansCode/@name) is not recommended Where this rule applies
| Rule set | Version |
|---|---|
| SI-UBL 2.0 / NLCIUS (invoice) | 2.0.3.13 |
| SI-UBL 2.0 / NLCIUS (credit note) | 2.0.3.13 |
| NLCIUS (CII) | 1.0.3.13 |
Check your file
Drop your e-invoice to see whether BR-NL-29 still fails, and which other rules do.
Related rules
- BR-NL-30 Leave out the bank account name
- BR-NL-31 Leave out the bank identifier on SEPA payments
- BR-NL-33 Avoid a second VAT total in another currency
- BR-NL-35 Leave out the VAT exemption reason code
- BR-NL-26 The seller's additional legal information is not recommended
- BR-NL-25 Dutch sellers should give a VAT number, not another tax number