Skip to content

Fatal

BR-RO-L1016: Payment means text must be 100 characters or fewer

In short

Fatal: fails the selected checks.

BR-RO-L1016 means the text that describes how the invoice is to be paid (BT-82) is longer than 100 characters. Fix it by shortening the text to a few words, or by leaving it out, since the payment means code already says how to pay.

On this page

What it means

The free text that explains the payment method (BT-82) must not be longer than 100 characters. In UBL it is the name attribute on the payment means code, and the check applies to every payment means block in the file. The code itself (BT-81) is not what is counted.

Why it matters

This is a Romanian rule for RO e-Factura and it is fatal. The check fails and the file is rejected until the text is shortened.

How to fix it

In your invoicing software, look for the payment method or payment means description on the invoice. Shorten it to a few words, such as 'Bank transfer', or clear it, because the payment means code stays in the file either way. Move longer payment instructions into the payment terms.

The rule as published

Numarul maxim permis de caractere pentru Explicatii privind instrumentul de plata (BT-82) este 100. #The allowed maximum number of characters for the Payment means text (BT-82) is 100.

Business terms: BT-82

Where this rule applies

Rule set Version
CIUS-RO UBL Invoice 1.0.9 1.0.9
CIUS-RO UBL Credit Note 1.0.9 1.0.9
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether BR-RO-L1016 still fails, and which other rules do.

Updated 6 November 2026