· 4 min read
e-Factura without copy-paste: automating your SPV invoices
Still logging into SPV every day to download invoices and retype them? Here is what you can automate and where a person stays in control.
If your company works with Romanian e-Factura, you know the routine: log into SPV, look for new invoices, download the XML and PDF, then key everything into the accounting system. e-Factura automation takes the repetitive part off your plate. Incoming invoices land where they belong, and you only look at the ones that don't match.
What manual SPV work looks like today
For many companies, e-Factura brought cleaner data but not less work. A typical flow looks like this:
- someone signs into SPV, the ANAF portal, with a digital certificate;
- they check for new messages and download invoices one at a time;
- they unzip the files and render a PDF so the invoice is readable;
- they email everything to the accounting team;
- the accountant retypes the lines into SAGA, WinMentor or another system.
Each step takes only a few minutes. The problem is that it repeats for every invoice, every day. And a wrong VAT rate or a missed invoice usually shows up only at month-end close.
What you can automate in the e-Factura flow
The good news: almost everything repetitive can run without anyone touching it.
- Automatic SPV invoice download. A service connects to ANAF through the official authorization and checks for new invoices on a schedule. Nobody has to log in and look.
- Reading the invoice. Data is pulled straight from the XML: supplier, tax ID, line items, quantities, prices, VAT and totals.
- Matching against orders. Each invoice is compared with the purchase order or goods receipt in your ERP. If prices and quantities match, it moves on.
- Export to accounting. Validated data goes to SAGA, WinMentor, SmartBill or your ERP, via API or import files.
- Alerts on differences. A changed price, a duplicate invoice or a new supplier triggers a notification instead of a month-end surprise.
- A clean archive. The original XML and the generated PDF are stored on your side, searchable by supplier or date.
Why SPV's XML is easier to automate than a PDF
Romanian e-invoices use the UBL format, an XML file with a standard structure. Every piece of information sits in a specific field, so nothing has to be guessed from an image.
That is a big difference from scanned invoices or PDFs sent by email. Those need OCR and AI to extract the data, and the output needs closer review.
A few things still take some thought. Your supplier calls a product one thing; your item master uses a different code. An AI model can suggest the match based on past invoices. A person confirms it once, and from then on it applies automatically.
A person stays in control of the exceptions
Automation doesn't mean every invoice gets booked without anyone seeing it. You set clear rules up front:
- the invoice matches the order on price and quantity: it is booked automatically;
- the price differs from the order: it waits for your approval;
- a new supplier or an unverified tax ID: it goes to a person for review.
For your accounting team, this means reviewing instead of retyping. Their time goes into exceptions and analysis, not into copying numbers from one screen to another.
What we learned building ProBill
ProBill is our own invoicing platform, built around e-Factura. It has sent more than 1 million invoices to SPV so far. That experience left us with a few rules we apply to every project:
- Automatic retries. ANAF services can be slow or temporarily unavailable, so the flow has to retry on its own.
- Readable error messages. A validation error needs a plain explanation so people know what to fix.
- A full audit trail. For every invoice you can see when it was downloaded, what was checked and who approved it.
We bring the same experience to our document processing projects, including for international groups that need SPV data in a group-wide ERP. You can see more examples in our case studies.
How to get started with e-Factura automation
- Count how many invoices you receive per month and from how many suppliers.
- Decide where the data needs to go: accounting software, ERP or both.
- Set the rules: what goes through automatically and what needs approval.
- Run a one-month pilot and measure how many exceptions show up on your own documents.
Not sure where to begin? A short audit shows what is worth automating first. And if e-Factura is only one of your repetitive flows, take a look at process automation.
How many invoices is your team still typing by hand? Tell us what documents you receive and where they need to go, and we'll show you what the automated flow would look like.