Skip to content

Fatal

BR-RO-L1018: Charge reason on the whole invoice, 100 characters at most

In short

Fatal: fails the selected checks.

BR-RO-L1018 means the reason on a charge that applies to the whole invoice is longer than 100 characters. The check measures the reason code field, so fix it by putting only a short code in it and moving any longer wording to the reason text.

On this page

What it means

The reason for a charge on the whole invoice must not be longer than 100 characters. The rule text names the charge reason (BT-104), but the test measures the charge reason code (BT-105), the AllowanceChargeReasonCode element in UBL. It applies to each charge on the whole invoice, not to discounts or to charges on a single line.

Why it matters

Romania's rules for RO e-Factura set this limit and a breach is fatal. Codes on the standard list are only a few characters long, so a failure usually means free text was typed into the code field. The file is rejected until it is corrected.

How to fix it

In your invoicing software, open the charge on the whole invoice, such as freight or packaging, and look at its reason. Choose a code from the UNTDID 7161 list, such as FC for freight, or leave the code out and use the reason text (BT-104) alone. Put any longer explanation in the reason text, not in the code.

The rule as published

Numarul maxim permis de caractere pentru Motivul taxei suplimentare la nivelul documentului (BT-104) este 100. #The allowed maximum number of characters for the Document level charge reason (BT-104) is 100.

Business terms: BT-104

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-L1018 still fails, and which other rules do.

Updated 6 November 2026