Romania e-Factura
Romania RO e-Factura CIUS-RO UBL 2.1 + ANAF SPV BYOK submission: B2B/B2C clearance, CUI/CIF validation, load index polling, download status
Romania e-Factura
CIUS-RO UBL 2.1 & ANAF SPV submission for Odoo — B2B and B2C clearance, control index & status on every customer invoice
Connect Odoo to Romania's national RO e-Factura system operated by ANAF through the Spatiul Privat Virtual (SPV). Customer invoices and credit notes are generated as the Romanian CIUS-RO UBL document, uploaded to ANAF, and the returned load index, download ID and validation status are stored on the move — ready for Romania's fully-enforced 2026 e-invoicing mandate.
CIUS-RO UBL 2.1 generation
Invoice and credit note built to the Romanian EN 16931 customisation (CIUS-RO 1.0.1), with the mandatory seller and buyer county (judet) as ISO 3166-2:RO codes, RON document currency, RON tax accounting currency on foreign-currency documents, and the 19% / 11% / 9% / zero / exempt / reverse-charge VAT categories.
ANAF SPV submission (BYOK)
Upload, status polling and document download over the documented ANAF e-Factura REST API using your own OAuth2 token. Test and production endpoints are editable; requests retry with exponential backoff and every call is logged. The load index and download id are captured automatically.
B2B + B2C 2026 scope
Handles the standard B2B clearance flow and the B2C self-billing flow (anonymous consumer with the conventional CUI placeholder), selectable per move. Foreign-buyer documents are routed with the ANAF external marker.
Real CUI / CIF validation
The official ANAF mod-11 control-digit algorithm (key 753217532) validates the Romanian fiscal code on company and partner, with RO VAT prefix handling, so typos are caught before a wasted ANAF round-trip.
Business-rule validation & onboarding
A Romania rule set layered on an EN 16931 core checks the seller CUI, county code, RON currency, VAT categories and credit-note referencing before upload. An onboarding wizard sets the fiscal code, county and BYOK SPV token in one place, and an optional batch upload + status cron keeps the 5-working-day transmission window covered.
Compatible with Odoo 18, 19 & 20
Built on the shared e-Invoice Core Engine. Bring-your-own-key credentials: your OAuth2 tokens and fiscal code are stored solely on your own database and are never sent anywhere except the ANAF SPV endpoint you configure.
Screenshots
Posted Ro Customer Invoice W
Customer Invoices List Filte
Update date: 2026-07-02
User guides (PDF)
Related modules
Romania e-Transport
ANAF RO e-Transport (UIT) declarations for high-fiscal-risk goods: stock.picking glue, SPV BYOK token, CUI checksum, QR
Romania e-Transport International
ANAF RO e-Transport international extension: border crossing point (PCV), customs office, MRN / customs declaration refs, foreign-party transit declarations and intl UIT validation
Romania e-TVA Recon
Romania ANAF e-TVA pre-filled VAT return reconciliation vs the Odoo D300: fetch the pre-fill, rebuild D300 boxes from posted moves, flag discrepancies, prepare the response