01What actually gets automated, step by step
The document itself generates from the order or job data that already exists, so nobody retypes a client's name, address or line items a second time. VAT calculates against the correct rate automatically rather than by memory, which is where manual invoicing quietly produces errors that surface months later at an audit. For Romania specifically, the invoice has to become a UBL 2.1 XML file, get submitted through the ANAF API, and the validation response, accepted or rejected, has to write back into the business's own records without someone checking a portal by hand every time.
- The document generates from data that already exists, nothing retyped
- VAT calculates against the correct rate automatically, not from memory
- For Romania: UBL 2.1 XML, submitted via ANAF, validation written back automatically
02What still needs a person
Automation handles the invoice that follows the standard rule, it does not handle the client who negotiates a discount after the fact, a disputed line item that needs a phone call to resolve, or a one-off exception that breaks the usual pricing logic. A good invoicing automation is built to recognise when a case falls outside its rules and flag it for a person rather than forcing it through and producing a wrong document with real legal weight behind it, since an invoice is not an internal note, it is a legal and tax record.
- A negotiated discount or disputed line still needs a human decision
- A good system flags the exception instead of forcing it through
- An invoice carries real legal and tax weight, unlike an internal note
Quoting, VAT and gapless invoicing running as one system
ATP Spedition runs three logistics lines at once, courier, moving and freight, each with its own tax and e-invoicing rules, and PROOF48 built quoting, VAT calculation, gapless invoicing and e-Factura submission as one connected system rather than three separate manual processes. Romanian e-Factura and e-Transport were treated as first-class requirements from the start, not bolted on afterward, because a logistics business cannot afford an invoice sequence with a gap in it or a submission the tax authority rejects.
See the build: ATP SpeditionQuestions, answered
Does invoicing automation work for a business that is not in Romania?
The VAT and document generation logic applies broadly. The e-Factura submission piece specifically is Romania's own system; a business elsewhere would automate against whatever its own tax authority requires instead.
How much manual work does this realistically save?
It depends on volume, and PROOF48 does not publish a blanket hours-saved figure because it varies too much by business to be honest as a single number. What is consistent is that retyping the same order data twice disappears.
Where PROOF48 fits
Invoicing automation removes the repetitive parts: document generation, VAT calculation and, in Romania, e-Factura submission and validation. It does not remove judgment calls like a negotiated discount or a disputed line. ATP Spedition runs all three logistics lines on one connected system built this way.
Cosmin Tiu · Founder, PROOF48
Cosmin has worked in online marketing and software development since 2018, and has built with AI every day since January 2023. He still writes code from scratch daily, in Python, React, Rust and C#. PROOF48 ships business websites in 48 hours and invoices afterwards, so every opinion on this blog was paid for in real builds, not in theory.