Saga + e-Factura SPV: automated B2B workflow without manual uploads
After 1 July 2024, all B2B invoices must be pushed to the SPV. Here is how Azuvio automates XML generation, validation, and submission, leaving Saga to handle only the accounting.
Ionut Mihaescu — Full Stack Developer Azuvio · 2026-05-08 · 7 min · ERP & Integrations
e-Factura SPV — mandatory, but painful for SMEs
Since 1 July 2024, all B2B invoices in Romania must be pushed to the SPV (the Romanian tax authority's Private Virtual Space) in XML UBL 2.1 RO_CIUS format. Deadline: 5 working days from issuance. Penalty: 1,000-10,000 RON per invoice not submitted.
The problem with the typical Saga workflow
Your external accountant receives monthly invoices from you (PDF or Excel). They enter them into Saga, generate the SPV XML, and manually upload it to the ANAF portal. Problems:
15-30 day lag between issuance and submission — a guaranteed penalty
SPV validation errors (wrong VAT ID, missing CPV code, unbalanced VAT totals) — rejected invoices
Lack of audit trail — who uploaded it, when, and with what ANAF response ID
Internal FTE cost — someone must check the status of each invoice in the SPV
The automated workflow with Azuvio over Saga
The Saga + Azuvio connector works as follows:
1. Order enters the OMS (eMAG, B2B portal, field agent, etc.)
2. Invoice is generated in Azuvio with all RO_CIUS fields validated
3. SPV XML is pushed automatically to ANAF via API (oAuth2), with retries for temporary errors
4. ANAF response ID is saved on the invoice (complete audit trail)
5. Daily XML/CSV export to Saga for accounting — marked as «SPV submitted, with upload ID»
What the accountant does
They open Saga and see the imported invoices with the status «SPV: OK» plus the upload ID. No more uploading, no more status checking. Saga contains exactly what is needed for the trial balance and statutory reporting. See also the e-Factura glossary.
Handling SPV errors
When ANAF rejects an invoice (inactive VAT ID, invalid CPV code), Azuvio holds it in a «manual review» queue with the exact error message. The operator corrects and resubmits. Saga does not see the invoice until it is valid in the SPV — no accounting pollution.
Measurable benefits
A company with 400 B2B invoices/month reduced:
SPV upload time: from 8h/month (manual) to 0 (automated)
ANAF penalties: from ~3,000 RON/month (delays) to 0
SPV rejection rate: from 6% to <0.5%
Conclusion
e-Factura should not be an accounting task. It is an operations task, resolved at the source. Saga only receives the clean result. See also the Saga connector, the EDI pillar, and the ERP coexistence doctrine.