`BR-RO-020_1`

RO e-Factura (CIUS-RO) · validation rule

RO e-Factura (CIUS-RO)Error

The invoice type code (BT-3) must be one of 380 (invoice), 381 (credit note), 384 (corrected invoice), 389 (self-billed invoice) or 751 (invoice information for accounting purposes). RO e-Factura narrows UNTDID 1001 to those five; a code EN 16931 allows, such as 386 (prepayment invoice), is rejected here.

Field: document.type_code (BT-3)
Rule set: RO e-Factura (CIUS-RO)
Rule-set version: CIUS-RO 1.0.1 (ro16931-ubl-1.0.9, in force 2024-06-05) · in force since 2026-09-07 · Rule-set changelog
Who has to fix it: The sender

This is a property of the file you received, so it cannot be corrected on your side without changing the document — ask the supplier to reissue it.

Worked example · UBL

CIUS-RO narrows BT-3 to 380, 384, 389 and 751 (381 for credit notes); 326 (partial invoice) is valid EN 16931 but not accepted by ANAF.

Fails this rule

<cbc:InvoiceTypeCode>326</cbc:InvoiceTypeCode>

Passes

<cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>

Check your own invoice

Drop the file that failed. We parse it, run the official rule sets against it and list every finding with a fix — 20 invoices per day, no key, nothing stored.

Open the live demo

Same explanation over the API: GET /v1/rules/BR-RO-020_1?lang=en