Native ANAF e-Invoicing in the ERP — pushed to SPV for every issued or received invoice
4softerp has e-Invoicing built natively into ANAF SPV: signed UBL-XML transmitted at issuance from the sales module, received invoices pulled and linked to the goods-receipt note and journals, statuses monitored, ANAF index kept in each company's file.
The full e-Invoicing cycle, inside the ERP flow
Automatic submission at issuance
Every invoice issued from the sales module or via API goes to SPV immediately with UBL-XML validation against the current ANAF schema.
Automatic pull of received invoices
Invoices received in SPV enter the ERP automatically, with OCR on the attached PDF, matching against the purchase order and goods-receipt note, and posting into the purchase journal.
Real-time customer CUI validation
The partner CUI is validated live against ANAF before issuance — no rejections for inactive supplier.
Status monitoring and retries
Errors, retries, cancellations — all visible inside the ERP, no need to enter SPV manually.
ANAF index in the electronic file
For every invoice the ERP keeps the SPV index, the XML file and the receipt for the 10-year audit window required by the Tax Code.
e-Invoicing isn't a separate app bolted onto accounting. In 4softerp, the moment you confirm a delivery or issue an invoice is the same moment it transmits to SPV and posts into the journal — one flow, across any number of companies, with no duplicated documents.
Frequently asked questions about ANAF e-Invoicing
Put ANAF e-Invoicing on autopilot, integrated in the ERP
One cloud ERP issues, transmits to SPV, receives and posts to the journal — live in 1–2 weeks, data in the EU/GDPR.