e-Factura ANAF for OpenCart — RO e-Factura invoices to ANAF (SPV) straight from orders

e-Factura ANAF for OpenCart is a module for shops in Romania on OpenCart 4 that have to report their invoices to the national RO e-Factura system (SPV) of the ANAF tax authority. It turns an order into an electronic invoice in UBL 2.1 under the Romanian specification CIUS-RO 1.0.1 and sends it to the ANAF API itself, through your own OAuth application — without an accounting SaaS in between and without a monthly subscription. The upload index, the ANAF status and the signed answer of the Ministry of Finance are kept with the invoice.

What you need. A company registered in SPV; a qualified digital certificate of a person with SPV rights for the company’s CUI; your own ANAF application for the “E-Factura” service, registered on the ANAF portal with the callback URL the module shows. OpenCart 4.0.2+ or 4.1.

How it was tested, honestly. The module was tested on local OpenCart 4.1.0.3 and 4.0.2.3 stores (mysqli and pdo database drivers) with ANAF answers simulated from the official API documentation (upload, stareMesaj, descarcare, uploadb2c) and the examples of Romania’s Ministry of Finance: installation with the standard Installer, guest checkout, B2B and B2C invoices, credit notes, EUR with the BNR rate, an EU buyer, a rejection and a resend. The XML of the test orders passed the official ANAF validator (UBL 2.1 XSD + CIUS-RO 1.0.9 schematron); the offline validator cannot identify an EU buyer (extern=DA), that document passed the XSD and the schematron. We have not run the module against the live ANAF, test or production, yet: that needs the certificate of a Romanian company. Start in the TEST environment during the 7-day Pro trial — if ANAF answers differently from its documentation, we fix it promptly.

Responsibility for the content of the invoice stays with the shop. The module builds the invoice from the OpenCart order data and from the VAT settings you choose: categories for lines without VAT, the non-VAT-payer mode, “TVA la încasare”, B2C reporting, the BNR rate for currencies. These are your accountant’s decisions — show them the settings before switching to PRODUCTION.

What the admin gets

• Extensions → Modules → e-Factura ANAF: the “Invoices”, “Settings”, “Tools” and “Licence” tabs.
• Invoice register: number, order, buyer with CUI, total and currency, status (“In SPV”, “Rejected by ANAF”, “Not delivered”), upload index or the ANAF message; filter and search. “Send queued invoices now” sends the queue at once.
• Invoice page: the XML, the signed ANAF answer, a check and a PDF through the public ANAF services, “Regenerate and send” for a rejected invoice.
• Notices at the top of the module: no connection or an expired one, invoices that have not reached SPV for a while.

The order page in the admin gets an “e-Factura” panel: the buyer’s tax number with the check result, a field to correct the CUI for the invoice (the customer’s data is not changed) and the order’s invoices with their ANAF status. A rejected invoice shows the error list from the ANAF answer; once fixed — “Regenerate and send” with the same number.

Uncertain uploads. If ANAF does not answer after an upload has started (a timeout), the module never resends the invoice blindly — that could create a duplicate in SPV. The invoice becomes “Not delivered”, and “Send again as it is” sends the same XML after you have checked in SPV that the first one did not arrive.

What the buyer sees

The standard OpenCart checkout gets a “CUI / CIF (company)” field — an ordinary OpenCart custom field (Customers → Custom Fields) that the module creates with a button in the settings. It is optional: without a CUI the order is an ordinary one, a company with a CUI gets an invoice in RON. “14399840”, “RO14399840” and “RO 14399840” are all accepted.

A Romanian CUI with a wrong check digit does not pass: the error appears under the field, and the order cannot be placed until the number is fixed. VAT numbers from other EU countries and foreign tax numbers are accepted.

How it works — step by step

1. ANAF application. In the developer section of the ANAF portal you register an application for the “E-Factura” service with the callback URL from the module settings; ANAF gives you a Client ID and a Client Secret.
2. Connection. Settings → Connection to ANAF: Client ID and Client Secret, “Connect with ANAF”, choose the qualified certificate, “Check the connection”.
3. Seller. CUI, name, address, county or Bucharest sector, VAT payer or not, the number series; the “Create the CUI field” button.
4. Order status. The order gets the status you chose (for example “Complete”): the module builds the XML with the next number and queues it.
5. Sending. The invoice is uploaded to ANAF right after the status change; the OpenCart scheduler checks the queue every hour, and for faster statuses add a hosting cron with the address from the “Tools” tab every 5 minutes.
6. Answer. Accepted — status “In SPV”, the index and the signed ANAF answer on the invoice; rejected — the error list and “Regenerate and send”.
7. Failures. ANAF down — the invoice waits in the queue and goes later; an uncertain upload waits for your decision.

Pro. The “Refunded” status (or one you choose) produces a full 381 credit note referencing the invoice; a partial credit note is created by hand by lines or by amount. Orders without a CUI are reported through uploadb2c with the CNP (an optional field of its own) or 13 zeros. EU buyers with a VAT number get category K, buyers outside the EU get G, both with extern=DA. Orders in EUR, USD and other currencies get an invoice with the BNR rate and the VAT total in RON.

Under the hood

• UBL 2.1, CustomizationID CIUS-RO 1.0.1: 380 invoice and 381 credit note; counties coded as ISO 3166-2:RO, Bucharest sectors as SECTOR1–6.
• ANAF OAuth: authorization code on logincert.anaf.ro, token_content_type=jwt, a state against forged callbacks. Tokens and the Client Secret are stored encrypted; the encryption key lives in the shop’s storage folder.
• RO e-Factura API: upload / uploadb2c, stareMesaj, descarcare within the ANAF limits — polling with a growing pause, the answer is downloaded once.
• ANAF answers are kept in the shop database, not as files in the site folder: they cannot be opened by a direct URL, downloads go only through the admin.
• OpenCart events (order status change, checkout, order panel) and an OpenCart scheduler task — no core files are edited.
• Log cc_efactura.log in the shop’s log folder, viewable in the “Tools” tab.
• Uninstall: without “Delete data” the invoice register and counters stay for your accounting; with “Delete data” the CUI/CNP fields created by the module are removed too.

Installation

1. Extensions → Installer → Upload: cc_efactura.ocmod.zip, then Install.
2. Extensions → Extensions → Modules → e-Factura ANAF → Install → Edit.
3. Register an “E-Factura” application on the ANAF portal with the callback URL from the “Settings” tab.
4. Paste the Client ID and Client Secret, “Connect with ANAF”, sign in with the certificate, “Check the connection”.
5. Fill in the seller data, click “Create the CUI field”, switch invoicing on, keep the TEST environment.
6. Place a test order with a CUI and set it to “Complete” — the invoice appears in the register with its ANAF status.
7. Show the VAT settings to your accountant and switch the environment to PRODUCTION. For Pro — the key from the e-mail after payment or the 7-day trial.