Any business that invoices in Romania
Bye-bye,retyping invoices.
An order is typed once. The invoice, the e-Factura upload and the late-payment reminder follow without you.
- Any business that invoices
- Live in 3 weeks
- Your invoicing tool stays
Twenty-three orders from last week, one invoicing tool, and an e-Factura upload waiting for each one of them.
Month end: two evenings or one report?
Drag the handle
The same month end, after
- 08:12Issued from the orderLast week's orders become invoices in one click. Nobody retypes a line.
- 10:30Uploaded and checkedEach invoice's e-Factura file is built and uploaded, with the upload index saved next to it.
- 12:45Less to get wrongThe price comes from the order and the client data from the client record.
- 16:00Reminders that go outAn overdue invoice sends its own reminder. The dashboard shows who owes what.
- 18:30Month endThe end of the month is a report, not two evenings.
A month end, before
- 08:12RetypingEvery order is typed again into the invoicing tool, line by line, by the one person who knows how.
- 10:30The uploadEach invoice goes to ANAF's e-Factura by hand. One comes back rejected for a missing tax code.
- 12:45The mistakeA wrong unit price on invoice 0418. A credit note, a new invoice, a new upload.
- 16:00Who has not paid?Overdue invoices live in someone's memory and a spreadsheet nobody trusts.
- 18:30Still invoicingThe end of the month means two evenings of invoicing.
A service company with eight people and a busy end of the month. The company is invented, like every name on this page.
Month end, itemised (example numbers)
The bad day · receipt
- retyping orders as invoices7about 100 invoices a month × 4 minuteshours a month
- before a late payer is chased15when reminders depend on someone rememberingdays
- spent on month-end invoicing2in this exampleevenings a month
The first line, a month210 lei
Example figures for a company like this one. The audit measures yours.
One order in. Invoice, upload and reminder out.
An order is entered once. The invoice, its e-Factura file and the reminder for a late payment follow from it on their own.
- 1Order
- 2Invoice
- 3e-Factura
- 4Payment
- 1
Order
Recorded once, where the orders already live
- 2
Invoice
Issued from the order, with the right VAT and the right client data
- 3
e-Factura
The UBL file is built and uploaded to ANAF's SPV
- 4
Payment
Paid is marked paid; overdue gets a polite reminder on its own
Try the autopilot
Run the autopilot on the new orders: watch the invoice, the e-Factura XML and the upload happen, then send the reminder for an overdue invoice.
Try this
- 1Run the autopilot on the new orders
- 2Open the e-Factura XML of an invoice
- 3Send the reminder for an overdue invoice
By hand, one more hire, or this
- Cost to startRetyping it yourself:NothingHire another person:A new salaryThis autopilot:€3,500, one time
- Retyping an order as an invoiceRetyping it yourself:Every line, by handHire another person:Every line, by themThis autopilot:Never
- The e-Factura uploadRetyping it yourself:By hand, each oneHire another person:By hand, each oneThis autopilot:Built and sent for you
- Who chases the late payerRetyping it yourself:Your memoryHire another person:Whoever remembersThis autopilot:A reminder, on its own
- A client having a hard monthRetyping it yourself:You, if you noticeHire another person:Someone who talks to themThis autopilot:Only if you mark them
- The last day of the monthRetyping it yourself:Evenings of invoicingHire another person:Fewer eveningsThis autopilot:A report
How we build it
The audit, 2 hours
We follow one order from arrival to payment with you and find every place it is typed twice.
The build, 3 weeks
Connected to your invoicing tool (SmartBill, Oblio, FGO) or ANAF's API, and to where the orders already live.
Handover
We run a real month end together and fix what it shows.
The stack
Your invoicing tool (SmartBill, Oblio, FGO) or ANAF's API, connected to where the orders already live. Invoices and data stay in your own accounts.
Ops Sprint
€3,500
one-time · live in 3 weeks
- A 2-hour operations audit
- One automation live in 3 weeks
- Handover and a short training
Running costs (messages, the AI model, hosting) are yours and stated up front. The 2-hour audit is the first step and costs €500, credited in full if you go ahead within 30 days. If you stop there, the written map is yours.
It’s for you if
- You invoice in Romania, and every invoice goes through e-Factura.
- One person knows how month end works, and you’d rather it wasn’t only them.
- You use SmartBill, Oblio or FGO, or you’re happy to work straight with ANAF.
- You want a late payer reminded without writing the awkward email yourself.
It’s not for you if
- Head office picks your invoicing system. Then it isn’t ours to change.
- You send a handful of invoices a month with no repeated admin. The tool you have is enough.
- You’d rather not sign a written data agreement. We don’t build without one.
Fair questions
Do we need a new invoicing tool?
Usually not. We connect the one you have; the audit tells you if it cannot be connected.
Is the e-Factura file valid?
In a real build it comes from your invoicing tool, or is checked against ANAF's validator before upload. The demo shows a teaching sample.
Will reminders annoy our clients?
You write the wording and choose when they go. A client you mark as an exception never gets one.
On the last working day of the month, you close the laptop at six with every invoice already uploaded.
We follow one order with you from arrival to payment and leave a written map: what to automate, what it saves, what it costs.
Or pick a time for a free intro call