| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2871 |
| Technical Name |
l10n_ro_efactura_gb |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2871 |
| Technical Name |
l10n_ro_efactura_gb |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
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
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
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module