e-Factura automation means a software flow that picks up invoices directly from your invoicing software, validates them, automatically submits them to Romania's national e-invoicing system RO e-Factura (via SPV, the tax authority's Virtual Private Space portal) and archives the responses from ANAF (the Romanian tax agency) — no manual uploads, no forgotten invoices, no validation errors discovered too late. In short, you eliminate all the repetitive SPV work.
The e-Factura context in Romania: where we are in 2026
In short: the RO e-Factura system has become the official channel for transmitting invoices in Romania, mandatory for B2B relationships since 1 July 2024 and for B2C since 1 January 2025, according to the ANAF calendar currently in force. If you issue invoices, they must reach SPV in the standardized electronic format, within the legal deadlines.
This means almost every Romanian business — from sole traders and micro-enterprises to companies with thousands of invoices per month — deals with the same process: the invoice is issued, converted to XML (the UBL standard used by RO e-Factura), uploaded to SPV, validation is awaited, and the ANAF response (upload index, error messages, the signed invoice) must be tracked and stored.
We will not go into thresholds, exact deadlines or fine amounts here — these can change through legislation, and it is your accountant's or tax advisor's job to confirm them. What does not change is the mechanics of the process: invoices must reach SPV correctly and on time. And that mechanics can be fully automated.
The real pains of working with SPV manually
Direct answer: the problem is not the e-Factura system itself, but the fact that many companies operate it manually — and manual means lost time, human error and compliance risk. Here is what we hear most often from companies that contact us:
- Repetitive manual uploads. Someone exports the XML from the invoicing software, logs into SPV with a certificate or token, uploads the file, notes the index. Dozens or hundreds of times a month. At 5 minutes per invoice, 200 invoices means over 16 hours of purely mechanical work.
- Validation errors discovered late. SPV rejects invoices for invalid tax IDs, wrong client fiscal codes, non-compliant units of measure, incomplete addresses or XML structure problems. If nobody checks the responses daily, the error surfaces when the legal deadline is almost gone.
- Lost or unsent invoices. The invoice issued on Friday afternoon never gets uploaded. The responsible colleague is on holiday. Nobody has a clear list of "what was sent and what was not". The lack of a central log is one of the most frequent sources of trouble.
- Painful reconciliation. At month end, accounting must reconcile three sources: the invoicing software, the SPV messages and the bank statement. Without automation, this happens by eye, in Excel, with the inherent risk of misses.
- Supplier invoices, ignored. e-Factura works both ways: incoming invoices also arrive in SPV. Many companies download them sporadically, manually, and lose visibility over their expenses.
All these pains share the same root: a mandatory digital process operated by hand. The solution is not "more attention" — it is removing the manual step.
What an automated e-Factura flow actually looks like
Direct answer: an automated flow connects your invoicing software to SPV through a chain of software steps — fetch, validate, submit, archive, notify — that runs on its own, on a schedule or instantly when an invoice is issued. Here is the anatomy of such a flow, as we build it:
1. Integration with the invoicing software (SmartBill, Oblio, FGO)
Most Romanian companies already use SmartBill, Oblio or FGO. All three expose APIs through which an external system can read issued invoices, their statuses and client data. The automated flow polls the API every few minutes or receives notifications on issue, so no invoice depends on a manual export anymore. We covered this type of connection in our article on SmartBill API integration — the same principles apply to Oblio and FGO.
2. Validation before submission
This is where the most time is saved. Before the invoice goes to ANAF, the flow automatically checks the data that most often causes rejections: the client's tax ID (including lookups in public registries), the XML structure required by RO e-Factura, mandatory fields, VAT rates. An error caught locally is fixed in minutes; one discovered after an SPV rejection takes hours or days.
3. Automatic submission to SPV
The flow authenticates the application with the ANAF system (through the OAuth mechanism provided for e-Factura), uploads the XML and stores the upload index. It then periodically checks the status: validated, processing or rejected. Everything a human used to do by logging into SPV now happens in the background, around the clock, including Friday evenings and holidays.
4. Archiving and a complete log
Every submitted invoice, every ANAF response, every signed XML is saved automatically — in the cloud (Google Drive, S3) or on your own server — with a central log: what was sent, when, with what status. During an audit or reconciliation, everything is one click away, not scattered across inboxes and local folders.
5. Smart notifications
The flow stays silent when everything works and speaks only when needed: a rejected invoice, a validation error, a new invoice received from a supplier, or a daily summary by e-mail or Slack. The team stops checking SPV "out of reflex" — the system reports the exceptions on its own.
n8n automation vs. custom integration: which to choose
Direct answer: for small and medium volumes with a single invoicing tool, an n8n flow is the fastest and cheapest path; for high volumes, complex business logic or integration with your own ERP, a custom integration (dedicated code) is the right investment. We use both, depending on the situation.
| Criterion | n8n flow | Custom integration |
|---|---|---|
| Implementation time | Days, up to 1–2 weeks | A few weeks, depending on complexity |
| Indicative cost | A few hundred – 1,500 EUR | 2,000 – 6,000 EUR |
| Best suited for | SMEs, small/medium volumes, one invoicing tool | High volumes, own ERP, complex business logic |
| Maintenance | Easy — the flow is visual and quick to adjust | Needs a developer, but more robust at scale |
| Extensibility | Good — hundreds of ready-made integrations | Unlimited — any specific requirement |
The n8n flow is built on an open-source automation platform you can host on your own server, so invoice data does not pass through third-party services. We connect existing nodes (HTTP, e-mail, Google Drive) with e-Factura-specific logic and get a working flow quickly, easy to adjust later. We wrote about the approach at length in our guide to n8n automations.
A custom integration means code written specifically for your business: a service that runs continuously, handles thousands of invoices per month, has automatic error recovery (retry with backoff), monitoring, a full audit log and connects to any internal system — ERP, CRM, data warehouse. It is the right solution when e-Factura is not an isolated task but a piece of the company's financial infrastructure.
To be honest: n8n is enough for many companies. We recommend a custom integration only when volume or complexity justifies it — and we say so directly in the first conversation. For a broader picture of what else can be automated beyond invoicing, read our complete guide to AI automations.
Not sure which option fits you? Write to us — we analyze your invoice volume and current process for free, then honestly recommend the cheaper option that gets the job done.
Indicative costs, no surprises
Direct answer: a simple e-Factura automation flow with n8n costs from a few hundred euros up to roughly 1,500 EUR, while a complete custom integration typically falls between 2,000 and 6,000 EUR — the final price depends on the number of connected systems and the validation logic required.
- Simple n8n flow (a few hundred – 1,500 EUR): fetching invoices from one tool (SmartBill, Oblio or FGO), basic validation, SPV submission, cloud archiving, e-mail notifications. Covers the needs of most SMEs.
- Complete custom integration (2,000 – 6,000 EUR): a dedicated service with advanced validations, handling of incoming supplier invoices, automatic reconciliation, a monitoring dashboard, internal ERP/CRM integration, an audit log and support for high volumes.
On top of that, possibly hosting (a small server for n8n costs a few euros per month) and an optional maintenance subscription. We publish prices because that is exactly how we would want to be treated as clients: no "request a quote" just to get a common-sense estimate. The final offer, of course, comes after we understand your specific process.
Implementation steps: how a project unfolds
Direct answer: a typical e-Factura automation project goes through five steps — analysis, access and authorization, flow construction, testing in the ANAF test environment, and go-live with monitoring — and takes from a few days to a few weeks.
- Analysis of the current process. Which invoicing software you use, how many invoices you issue and receive monthly, who currently handles SPV, where errors appear most often. A 30–60 minute conversation, usually enough.
- Access and authorization. Together we set up API access to the invoicing software and register the application with the ANAF system for e-Factura (the OAuth authorization process, based on the company's certificate). The bureaucratic step — we guide you end to end.
- Building the flow. We implement fetching, validation, submission, archiving and notifications, in stages, with checkpoints at every step.
- Testing in the test environment. ANAF provides a test environment for e-Factura; we run real scenarios there — correct invoices, invoices with intentional errors, high volumes — until the flow handles every case correctly.
- Production and monitoring. We start the flow on real invoices, in parallel with the manual process for the first period, then hand over: documentation, team training and, if you want, ongoing maintenance.
Frequent mistakes to avoid
Direct answer: the most expensive mistakes in e-Factura automation are missing error handling, ignoring incoming invoices, not archiving ANAF responses, and testing directly in production. We see them often in flows built in a hurry:
- A flow with no error handling. The happy path is easy; the real value lies in what happens when the invoicing API does not respond, when SPV is unavailable or when an invoice is rejected. Without retries, a replay queue and alerts, automation creates false confidence — more dangerous than the manual process.
- Ignoring the receiving direction. Supplier invoices also arrive in SPV. A complete flow downloads them, archives them and forwards them automatically to accounting.
- Not archiving the responses. The upload index and the ANAF-signed XML are your proof of transmission. If the flow does not store them systematically, you will reconstruct the history by hand during an audit.
- Testing directly in production. Invoices submitted to SPV have real effects. Every flow must first be validated in the ANAF test environment.
- Tokens and certificates left to expire. Authorizations have validity periods. A serious flow monitors expiry and warns in advance, instead of silently stopping one Monday morning.
- Automating a broken process. If client data is incomplete in the invoicing software, automation just delivers errors faster. Data cleanup is part of the project.
Conclusion: SPV should not be a full-time job
e-Factura has become a permanent reality for Romanian businesses. You can treat it as a daily manual chore or as a background process that runs on its own, correctly, with a complete log and alerts only when they matter. The difference is a one-time investment, usually between a few hundred and a few thousand euros, that pays for itself within months from the time saved alone — not even counting the compliance risks avoided.
We build both fast n8n flows and complete custom integrations, with code you own and transparent pricing from the first conversation. Contact us and, after a short analysis, we will tell you honestly which option makes sense for your invoice volume — and exactly what it would cost for you.
Frequently asked questions
Is automatic submission of invoices to SPV legal?
Yes. ANAF provides official interfaces (APIs) precisely so that software applications can submit invoices on the company's behalf, based on an authorization made with the company's certificate/identity. The major invoicing tools use the same mechanism.
Does the automation work with my invoicing software?
Most likely, yes. SmartBill, Oblio and FGO have public APIs we work with frequently, and most ERPs and management tools offer some form of export or API. If you use something else, we check for free before any commitment.
How long does implementing an automated e-Factura flow take?
A simple n8n flow is usually working within a few days to 1–2 weeks. A complete custom integration takes a few weeks, depending on the number of connected systems and the complexity of the validations. Testing in the ANAF test environment is included in both cases.
What happens if ANAF rejects an invoice?
The flow detects the rejection, stores the error message and notifies you immediately (e-mail, Slack) with the exact reason. Automatically correctable errors can be configured for resubmission; for the rest, you receive all the information to fix things quickly, within the legal deadline.
Do I still need an accountant if I automate e-Factura?
Yes — automation removes the mechanical work of uploading and tracking, not the tax expertise. Your accountant remains responsible for the fiscal correctness of the invoices; in fact, the flows we build make their work easier, because they receive clean, complete, neatly archived data.