BR-RO-01:Romanian CIF/CUI required
Romanian invoices must include the tax identification code (CIF/CUI).
Engine Classification
Business data required · Explicit input workflow · No assumptions made
Required input: Romanian Tax ID (CIF/CUI)
What is BR-RO-01?
BR-RO-01 is a fatal validation rule defined in the peppol-bis-3 specification (ROU national rules). It validates the CompanyID element under Party > PartyTaxScheme in the UBL invoice XML.
When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.
Target path: XPath: /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID
Why This Error Matters
Romanian e-Factura system requires valid CIF for processing.
BR-RO-01 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
Validator Behavior
- ·Causes invoice rejection
- ·Rejected by PEPPOL Access Points
- ·Error returned: BR-RO-01
- ·Specification: peppol-bis-3
How to Fix It
Get CIF/CUI
Romanian tax ID (2-10 digits)
Add RO prefix
Format: RO + number
Validate
Check CIF control digit
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Missing or empty element triggers cbc:CompanyID error --> <cbc:CompanyID></cbc:CompanyID>
<!-- Provide the required value --> <cbc:CompanyID>VALID_VALUE</cbc:CompanyID>
Technical Reference
XPath: /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyIDCode Example
<cac:PartyTaxScheme>
<cbc:CompanyID>RO12345678</cbc:CompanyID>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:PartyTaxScheme>Common Causes
- ·Missing RO prefix
- ·Invalid format
- ·CIF not registered
Seeing this in production? The API handles BR-RO-01 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
Romanian invoices must include the tax identification code (CIF/CUI).
Add Romanian CIF/CUI with RO prefix. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, BR-RO-01 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.
Many instances of BR-RO-01 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including romanian cif/cui required.
BR-RO-01 is commonly seen in exports from Romanian e-invoicing systems. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
Last updated: 18 January 2026
Handle BR-RO-01 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.