Romanian mandatory e-invoicing (RO e-Factura) requires every B2B and B2G Sales Invoice to be issued as a CIUS-RO compliant UBL 2.1 XML, uploaded to the ANAF SPV (Spațiul Privat Virtual), and cleared with a Ministry of Finance ID and seal within the legal deadline — with late or missing submissions carrying real penalties. Stock ERPNext gives you a clean Sales Invoice DocType and a general-purpose print/PDF pipeline, but it has no native concept of ANAF UBL generation, OAuth token exchange with the SPV, upload/status polling, or the D406 SAF-T structure that ANAF expects. Finance teams end up rekeying invoices into a government portal or a third-party bridge, which breaks the audit trail and does not scale.

ECOSIRE builds a dedicated Frappe app (for example ecosire_ro_efactura) that lives inside your ERPNext bench and wires directly into your existing sales flow. We add the fiscal fields Romania needs — CUI/CIF, RO VAT registration status, county and SPV identifiers, CIUS-RO document type codes — as custom fields and child DocTypes rather than parallel spreadsheets. hooks.py doc events on Sales Invoice on_submit generate the UBL XML from your real invoice data (parties, tax breakdown per VAT rate, unit codes, currency), validate it against the CIUS-RO business rules, and hand off to a background job. A queued scheduler task and whitelisted server methods handle the ANAF OAuth2 flow, upload the document to the SPV, and then poll for the clearance ID and download the signed response, writing every step back to a dedicated E-Factura Submission DocType so status is visible and re-tryable from the ERPNext UI.

On the reporting side we build the D406 SAF-T (Standard Audit File for Tax) export as a Frappe report/DocType that assembles the required master data and General Ledger movements into ANAF's XML schema for the reporting period, with validation and a downloadable file for submission. Where your operation moves goods, we scope the app to be e-Transport ready — the UIT declaration data model and the same SPV integration pattern — so that capability can be switched on without a second integration effort. Everything is exposed through role-profile-gated permissions (e.g. an "E-Factura Manager" role), client scripts for one-click resubmission on the Sales Invoice form, and the Frappe REST API / whitelisted methods so upstream systems can trigger issuance programmatically.

Because this is build-to-order, we start from your actual chart of accounts, VAT setup, invoice volume and edge cases rather than a fixed template. After a short scoping call we confirm the exact document types, tax scenarios and SPV credentials in play, then build against Frappe/ERPNext v15 and v16. Typical delivery is one working week from confirmed scope. You receive the installable source, a UAT pass on your staging bench, and a post-go-live support window — no rekeying into the ANAF portal, and a compliance path that stays inside ERPNext.