`BR-RO-001`

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

RO e-Factura (CIUS-RO)Error

The specification identifier (BT-24) is not the CIUS-RO value. RO e-Factura accepts exactly urn:cen.eu:en16931:2017#compliant#urn:efactura.mfinante.ro:CIUS-RO:1.0.1 — version 1.0.0 has not been accepted since 29 December 2022, and a plain EN 16931 or Peppol identifier is rejected outright. This is the first thing ANAF checks, so a wrong value here hides every other problem in the document.

Field: document.specification_id (BT-24)
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

ANAF accepts only the current CIUS-RO version in BT-24: …CIUS-RO:1.0.1. Templates from 2021 still carry 1.0.0 and are rejected.

Fails this rule

<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:efactura.mfinante.ro:CIUS-RO:1.0.0</cbc:CustomizationID>

Passes

<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:efactura.mfinante.ro:CIUS-RO:1.0.1</cbc:CustomizationID>

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-001?lang=en