e-Factura is not optional, and doing it by hand does not scale past a few invoices a week. The integration turns filing into a side effect of completing an order: the invoice is generated in the RO_CIUS format, submitted to the ANAF SPV, and followed until ANAF answers. The answer is the part that matters — an upload is not a filing until it has been accepted, and a rejection reason is the only thing that tells you what to correct.
← All technologies
— e-Factura
Invoices filed while you sleep.
Romania’s mandatory e-invoicing wired into your shop, so an invoice is built, submitted to ANAF and tracked without anyone opening the SPV.
What we build
01
SPV connection
OAuth credentials and the qualified certificate configured against the ANAF SPV, in production and test.
02
RO_CIUS generation
Invoices built in the UBL 2.1 RO_CIUS structure, with the VAT and party fields ANAF validates.
03
Automatic submission
Filing triggered by order completion, with the upload index stored against the order.
04
Status & rejections
Every answer surfaced in your own admin, rejection reason included, so corrections are quick.
Why us for e-Factura
- Filing becomes part of the order flow, not a month-end job
- The ANAF answer is tracked — an upload is not treated as a filing
- B2B and B2C flows, plus credit notes, handled the same way
- Direct to ANAF, or through SmartBill or Oblio if you already use one
- Built into the shop you already run, not a second system to check
— FAQ
Frequently asked questions
Still uploading invoices by hand?
Tell us what your shop runs on and who does your accounting — we will scope the e-Factura work.