Romanian e-invoicing
ANAF API integration for Romanian e-Factura
An ANAF API integration sends invoices to Romania's e-Factura system straight from your software, with no manual upload in the SPV portal. The software sends the XML, gets an upload index back and reads ANAF's response. DeviDevs invoices already go out through the API, and for your company we build the link between your billing software or ERP and ANAF.
Updated
What an e-Factura API integration does
- Generates the invoice as XML, in UBL 2.1 under the Romanian CIUS-RO rules.
- Checks the XML before it leaves, so a format mistake does not reach ANAF.
- Uploads the invoice through the e-Factura web services and keeps the upload index.
- Reads the invoice status and downloads ANAF's response.
The e-Factura submission deadline
An invoice has to reach the RO e-Factura system within five working days of its issue date. When invoices are uploaded by hand in SPV, a forgotten one can miss the deadline. An integration sends them as you issue them.
Authenticating with the ANAF API
The e-Factura API uses OAuth 2.0. You sign in on logincert.anaf.ro with your qualified digital certificate, and the software gets a token that it uses to upload invoices and renews on its own.
How DeviDevs invoices reach ANAF
- An invoice is issued with a person's approval, and the XML is generated and checked at issue.
- The upload goes through the API on a second yes from a person, and ANAF returns an upload index.
- When ANAF does not respond, the invoice waits in a queue and is not lost.
- If ANAF fails several times in a row, the system pauses and puts new invoices straight into the queue.
e-Factura integration with Saga, SmartBill or your ERP
We start from what your software offers: an API, an export or the database. If invoices come out of an ERP or an in-house app, we build their automatic submission to e-Factura so nobody copies data by hand anymore. We can start with an audit of the flow, so you know what is worth automating.
FAQ
What does an ANAF API integration mean?
Your software talks directly to the e-Factura web services: it uploads the invoice, reads its status and downloads the response, with no one logging into SPV.
How soon must an invoice be sent to e-Factura?
Within five working days of the invoice's issue date.
Can our billing software, such as Saga or SmartBill, be connected to e-Factura?
We start from what the software offers: an API, an export or the database. Once we have seen the flow, we tell you what link we would build and what stays in the software.
What happens if the agent gets an invoice wrong?
In our system an invoice is issued and uploaded only with a person's approval, and the XML is checked before it leaves. If ANAF rejects it at validation, the error comes back and the invoice does not go into the queue.
What exactly do you do: audit, documentation or implementation?
In steps: a scan of the flow, the diagnosis, building the integration and maintaining it. Prices are on the pricing page.
Related projects
Related services
Want your invoices connected straight to ANAF?
Tell us which billing software you use and where the data comes from. We will tell you what can be connected and how.
Write to us