Electronic invoice ANAF: how to issue, submit and archive in RO e-Factura
In short: An ANAF electronic invoice is a UBL 2.1 XML file validated by the RO e-Factura system and electronically signed by the tax authority. A PDF sent by email is not an electronic invoice. EDIconnect generates the XML from your ERP, submits it through SPV, tracks its status and archives it for 10 years.
Key capabilities
- XML generated from the ERP: Invoices issued in the ERP become RO_CIUS-compliant UBL 2.1 XML automatically, with no re-keying.
- Submission through SPV: Automatic upload to the tax authority portal, with the upload index and response messages captured.
- Pre-submission validation: ANAF rules run locally, so syntax and business errors are fixed before a rejection happens.
- Status monitoring: Every invoice shows a clear state: processing, validated or rejected, with the exact reason.
- 10-year legal archiving: The signed XML is stored together with proof of submission and stays available for a tax audit.
- Inbound invoices: Supplier invoices are downloaded automatically and matched against purchase orders and receipts.
What makes an invoice valid
RO e-Factura accepts only XML files built on the European EN 16931 standard, localised for Romania through the RO_CIUS specification. Every mandatory field has its own validation rule: party identification, VAT numbers, tax rates, units of measure and payment terms.
Most rejections come from master data rather than amounts: wrong country codes, non-standard units of measure, missing VAT exemption reasons or incomplete addresses. Local validation before submission removes most of that work.
- Format: UBL 2.1 or CII XML, RO_CIUS compliant
- Submission: through SPV, with an upload index per invoice
- Response: signed invoice or an error list
- Archiving: 10 years of original XML plus proof of submission
The automated flow
In an automated setup, an invoice issued in the ERP is picked up within seconds, converted to XML, validated, signed and submitted. The status flows back into the ERP, so finance sees the invoice, the upload index and the ANAF response in one screen.
For inbound documents the flow reverses: invoices are downloaded from SPV, converted into the ERP format and matched with the order and the goods receipt, shortening time to payment approval.
Frequently asked questions
What exactly is an ANAF electronic invoice?
A UBL 2.1 XML file following the national RO_CIUS specification, submitted through RO e-Factura and signed electronically by ANAF. The PDF is only a visual rendering.
Do I still need a PDF or a paper invoice?
The legal document is the ANAF-signed XML. PDFs remain useful for communication with partners but do not replace the file in the system.
How long must the invoice be archived?
10 years, together with proof of submission. The archive must keep the original signed XML, not a converted copy.
What happens when an invoice is rejected?
ANAF returns an error file listing the broken rules. You fix the invoice and resubmit; the legal deadline does not change.
Can invoices be issued directly from the ERP?
Yes. EDIconnect connects to the ERP through a connector or API and turns invoices into valid XML without double entry.