Skip to content

Fatal

BR-RO-020_1: Invoice type code must be 380, 384, 389 or 751

In short

Fatal: fails the selected checks.

BR-RO-020_1 means the invoice type code is not one of the four codes the Romanian rules allow on an invoice: 380, 384, 389 or 751. Fix it by setting the code that fits the document, usually 380 for a normal invoice.

On this page

What it means

In an invoice document, the invoice type code (BT-3) must be exactly one of 380 (invoice), 384 (corrected invoice), 389 (self-billed invoice) or 751 (invoice with information for accounting purposes). The official text also lists 381 (credit note), but the test for an invoice document does not accept it. A credit note is a separate document type with its own check, BR-RO-020_2.

Why it matters

The type code tells the recipient what kind of document this is.

How to fix it

In your invoicing software or XML, check the invoice type code (BT-3, cbc:InvoiceTypeCode in UBL). A normal invoice is 380. Use 384 only for an invoice that corrects an earlier one, 389 for a self-billed invoice and 751 for an invoice providing information for accounting purposes. If you meant a credit note, use a UBL CreditNote document with cbc:CreditNoteTypeCode set to 381.

Once the file is corrected, check it again for free: Check an e-invoice

Or fix the invoice in a form and download the corrected file, for 1 credit: Fix a rejected e-invoice Beta

The rule as published

Codul tipului facturii (BT-3) trebuie sa fie unul dintre urmatoarele coduri din lista de coduri UNTDID 1001: 380 (Factura), 389 (Autofactura), 384 (Factura corectata), 381 (Nota de creditare), 751 (Factura - informatii în scopuri contabile). #The invoice type code (BT-3) must be one of the following codes in the UNTDID 1001 code list: 380 (Invoice), 389 (Self-invoice), 384 (Corrected invoice), 381 (Credit note), 751 (Invoice - information for accounting purposes).

Business terms: BT-3

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

Updated 7 November 2026