RO e-Factura E-Invoicing for Romania changelog
All notable changes to ANAF e-Factura for CS-Cart and Multi-Vendor (kv_ro_efactura) are documented here.
The format follows Keep a Changelog and the project uses Semantic Versioning.
[Unreleased]
Section titled “[Unreleased]”Fixed (release-gate audit 2026-11-07)
Section titled “Fixed (release-gate audit 2026-11-07)”- An upload that got no answer (timeout, 5xx) is never repeated blindly: the document is marked “upload sent, result not confirmed”, ANAF is asked (listaMesajeFactura + downloaded answer compared by invoice number) and the upload is repeated only when nothing was registered. Send again is refused when ANAF may already hold the document.
- Credit notes cannot exceed the invoice: one note per request token (double click), quantities are taken from what earlier credit notes left open, per-invoice lock.
- Vendors in Multi-Vendor cannot run the global queue or discard jobs; in owner mode they cannot create, send, correct or credit fiscal documents of the owner.
- The upload deadline shown is 5 calendar days (OUG 115/2023) in Europe/Bucharest, with a “confirm with your accountant” note.
- One invoice per order and a gapless number under concurrent status changes (per-order lock, row first, number and counter in one transaction); no invoice for cancelled, declined, failed or incomplete orders.
- Text is cut by characters (Romanian diacritics); CIUS-RO length limits applied (item name 100, note 300, party names 200).
- OAuth state parameter; status queries that keep failing stop with the ANAF text instead of polling forever.
- Icon added to the package.
[1.0.0] - 2026-11-07
Section titled “[1.0.0] - 2026-11-07”- CIUS-RO UBL 2.1 Invoice and CreditNote built from orders (VAT categories S, Z, E, O, K, G; prices with or without tax; discounts; shipping and surcharge lines; RON and other currencies with the VAT amount in RON; buyers with CUI or VAT id, EU and non-EU buyers, individuals).
- Validation before upload: official OASIS UBL 2.1 XSD, a subset of the EN 16931 / Romanian business rules, optional ANAF validator.
- ANAF OAuth (authorization code with the qualified certificate in the browser, refresh token rotation, manual token entry), upload, status polling, download of the signed ZIP answer attached to the order, ANAF error messages, XML and PDF downloads.
- Credit notes (full or partial, optional automatic credit on a chosen order status).
- Test and Live environments, gapless numbering per series, job queue with retries, log with CSV export, order list column, Multi-Vendor per-vendor company.
- Optional customer field “Company tax ID (CUI / VAT ID)”.