Romanian companies now carry two heavy, deadline-driven obligations at once: every B2B and B2G invoice must clear the ANAF SPV e-Factura channel in the CIUS-RO UBL format, and the SAF-T D406 declaration must be filed on the ANAF schema on a monthly or quarterly cadence plus the annual run. Odoo's native l10n_ro gives you the Romanian chart of accounts, VAT tax groups (19/9/5%) and base_vat validation, and account_edi provides an EDI framework — but out of the box there is no CIUS-RO document builder, no OAuth2 handshake with SPV, no inbound document fetch, and nothing that assembles the D406 XML. Teams end up exporting to spreadsheets, hand-uploading to the ANAF portal, and reconciling errors after the fact.

This is a build-to-order app that ECOSIRE designs, builds, and installs specifically for your Odoo database. We extend account.move with the fields, compute/@api.depends methods and state machine needed to generate valid CIUS-RO UBL 2.1 XML directly from your posted invoices, then submit it to the ANAF SPV over OAuth2, poll for the signed response, and store the returned index and signed document against the invoice. Inbound e-Factura documents are pulled from SPV and turned into draft account.move vendor bills with your mapped taxes and accounts, so accounts payable starts from a matched draft rather than a PDF. Every submission, download, error message and ANAF status lands on the mail.thread chatter so finance and auditors share one timeline.

The SAF-T D406 side reuses the same posted ledger. We build the D406 monthly/annual XML export against the current ANAF schema, driven by mapping tables (regular Odoo models with ir.model.access.csv and record rules) that translate your accounts, taxes, products and units of measure into the codes ANAF expects — so the declaration reflects your real chart rather than a generic template. A dedicated test-vs-production environment switch lets you validate the full round trip against the ANAF test endpoint before any live filing, and an optional e-Transport (UIT) declaration hook can be scoped in for goods movements. Everything is delivered as a proper Odoo module: __manifest__.py with pinned dependencies (account, account_edi, base_vat, l10n_ro), XML/OWL views, QWeb status reports, security rules, and automated actions for scheduled submission and status polling, all callable over XML-RPC/JSON-RPC for integration.

Because it is built to order, there is no instant download — after a short scoping call we confirm the exact e-Factura profiles, D406 mapping depth and environments in writing, then build and hand over on staging for UAT before go-live. Typical delivery is 2 to 4 weeks from confirmed scope. Pricing starts from $599 (indicative, single-company base scope); multi-company groups, deeper D406 mapping, e-Transport, and custom integrations increase the quoted scope.