Romania CIUS-RO Format: Technical Requirements for RO e-Factura

Romania's CIUS-RO (Core Invoice Usage Specification - Romania) is a national customization of UBL 2.1 aligned with the European standard EN 16931. The format defines over 100 data fields with strict ANAF validation rules — invoices failing validation are rejected immediately and must be corrected and resubmitted within the 5-day deadline.

What Is CIUS-RO?

CIUS-RO includes: Base: UBL 2.

CIUS-RO is Romania's implementation of the European e-invoice standard, building on the EN 16931 semantic data model with Romanian-specific requirements:

• Base: UBL 2.1 XML following EN 16931 Core Invoice
• Extensions: Romanian tax identification (CUI/CIF), specific VAT categories, local business rules
• Validation: ANAF schema validation + 50+ business rules

What Are the Mandatory CIUS-RO Fields?

Seller Data

• CUI/CIF: Romanian tax identification number (validated against ANAF registry)
• Legal name: Must match ONRC (trade registry) registration
• Address: Full Romanian address including county (județ)
• Bank account: IBAN for payment

Buyer Data

• CUI/CIF: Buyer's tax ID (validated against ANAF)
• Legal name: Must match registration
• Address: Including county code

Invoice Data

• Invoice number: Sequential within seller's numbering system
• Issue date and delivery date
• Currency: RON for domestic; EUR or other for cross-border
• VAT breakdown: Per rate (19% standard, 9% reduced, 5% reduced)
• Line items: Description, quantity, unit price, VAT rate, amounts

Common ANAF Validation Errors

Common ANAF Validation Errors — CUI_INVALID: Tax ID fails checksum or not found in ANAF — Verify CUI at mfinante. gov.

Error	Description	Solution
CUI_INVALID	Tax ID fails checksum or not found in ANAF	Verify CUI at mfinante.gov.ro
SCHEMA_ERROR	XML doesn't conform to CIUS-RO XSD	Validate against official schema before submission
VAT_MISMATCH	VAT amounts don't match rate calculations	Recalculate with proper RON rounding
DUPLICATE	Invoice number already exists for this seller	Use unique sequential numbering per year
DEADLINE_EXCEEDED	Submission beyond 5-day window	Submit within 5 calendar days of issue date

How Invoicemonk Handles CIUS-RO

Invoicemonk generates CIUS-RO compliant UBL 2.1 XML automatically, validates against ANAF rules before submission, and handles CUI verification through the official ANAF API — ensuring first-submission acceptance.