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

e-Factura ANAF for WooCommerce is a plugin for shops in Romania that sell on WooCommerce and 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 — the way accounting programs do it, but without a SaaS in between and without a monthly subscription. The upload index, the ANAF status and the answer ZIP with the Ministry of Finance seal are kept with the order.

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 in the developer profile on anaf.ro with the callback URL the plugin shows. Invoices are in RON only.

How it was tested, honestly. The plugin was tested on a local WooCommerce store with ANAF answers simulated from the official API documentation (upload, stareMesaj, descarcare, uploadb2c) and the examples of Romania’s Ministry of Finance. Every XML from the test orders — B2B, B2C, a seller not registered for VAT, credit notes — passed the official ANAF validator (UBL 2.1 XSD + CIUS-RO 1.0.9 schematron). We have not run it against the live ANAF, test or production, yet: that needs the certificate of a Romanian company. Start in the TEST environment with your company 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 plugin builds the invoice from the WooCommerce order data and from the VAT settings you choose: categories for lines without VAT, the non-VAT-payer mode, “TVA la încasare”, B2C reporting, foreign buyers. These are your accountant’s decisions — show them the settings before switching to PRODUCTION.

What the admin gets

• WooCommerce → e-Factura: the “Invoices”, “SPV messages”, “Settings” and “Licence” tabs.
• Invoice register: number, order, buyer with CUI, total, ANAF status, upload index or the rejection text; status filter and search. Links to the details, XML, the ANAF answer ZIP and the PDF (Pro).
• “Send / check now” sends the queue and checks the statuses at once, without waiting for cron.
• Notices at the top of the admin: rejected or undelivered invoices, no ANAF connection, a connection that is about to end.

Every order has an “e-Factura” box: invoice number, status (“Accepted by ANAF”, “Rejected by ANAF”, queued), upload index and links to the XML and ZIP. An order without an invoice gets a “Send to e-Factura” button. The order notes record each step: invoice created, uploaded with its index, accepted or rejected with the reason.

A rejected invoice is visible at once: in the register, on the order and in a notice at the top of the admin, next to the error text from the ANAF answer ZIP (for example BR-RO-111 about the county code). Once the order is fixed, “Rebuild and send” rebuilds the invoice with the same number, which never reached the buyer; one you do not need is closed with “Discard”.

What the buyer sees

The checkout gets the “CUI / CIF (for an invoice to a company)” and “Trade register no.” fields and, while WooCommerce hides its own Company field, “Company name (for the invoice)”. Without a CUI the order is an ordinary one. With a CUI the plugin checks the check digit (with or without the RO prefix), and a CNP typed into the CUI field is refused with a hint. A CUI without a company name does not pass. Works on the classic and the block checkout.

ANAF requires the sector (SECTOR1–SECTOR6) for an address in Bucharest. A Bucharest buyer without a sector in the City field is asked to add it, for example “Sector 3” — otherwise ANAF itself would reject the invoice.

How it works — step by step

1. ANAF application. In the developer profile on anaf.ro you register an application for the “E-Factura” service with the callback URL from the plugin settings; ANAF gives you a Client ID and a Client Secret.
2. Connection. WooCommerce → e-Factura → Settings: Client ID and Client Secret, “Connect to ANAF”, choose the qualified certificate. “Check the connection” tests the token with a request to ANAF.
3. Seller. CUI, name, address, county (the sector for Bucharest), IBAN, VAT payer or not, the number series.
4. Checkout. A company buyer enters its CUI; a wrong CUI or a Bucharest address without a sector does not pass.
5. Order status. The order becomes “Completed” (or “Processing” — your choice): the plugin checks the data against the RO rules, builds the XML with the next number and queues it. No number is used up until the data passes the checks.
6. Sending. Action Scheduler uploads the XML to ANAF right away (upload), cron is the safety net. Then the plugin polls the state (stareMesaj) with a growing pause, within the ANAF rate limits.
7. Answer. Accepted — the ZIP with the invoice and the Ministry of Finance signature is kept with the order; rejected — the error text in the register and on the order.
8. Failures. ANAF down, a technical error or 429 — the invoice waits and is retried with the same XML; a “transmisa anterior” duplicate is tied to the original index.

Pro. A WooCommerce refund — by items or by amount — produces a 381 credit note referencing the invoice, sent to ANAF the same way. Orders without a CUI are reported through uploadb2c with the CNP (if the buyer gave it) or 13 zeros. EU buyers with a VAT number get category K, buyers outside the EU get G, both with extern=DA.

Under the hood

• UBL 2.1, CustomizationID CIUS-RO 1.0.1: 380 invoice and 381 credit note; the XML is frozen once built, so a retry sends the same file byte for byte.
• ANAF OAuth: authorization code on logincert.anaf.ro, token_content_type=jwt, a state against forged callbacks. The access token lasts 90 days and is renewed automatically 10 days before it ends; the refresh token lasts 365 days, then a new sign-in with the certificate. The Client Secret and the tokens are stored encrypted in the database (AES-256 with the site’s keys).
• RO e-Factura API: upload / uploadb2c, stareMesaj, descarcare, listaMesajeFactura and transformare (PDF) — within the ANAF limits on the number of requests.
• ANAF answers (signed ZIPs, error lists, SPV messages, PDFs) are kept in the site database since version 1.0.1, not in the uploads folder — no web server, nginx included, can hand them out by direct URL. Downloads go only through the admin with a capability check, the customer PDF with an order key and owner check.
• Locked numbering: two orders in the same second never get the same number; separate counters for TEST and PRODUCTION.
• Simulation mode: the CCEF_ANAF_MOCK constant in wp-config.php simulates ANAF answers in the TEST environment — to check the shop without a certificate.
• Deleting the plugin removes the tokens, crons and caches; the invoice register and the ANAF answers stay as accounting records. The CCEF_DELETE_DATA constant removes everything.

Installation

1. Plugins → Add New → Upload Plugin: choose efactura-anaf-for-woocommerce-1.0.1.zip and activate.
2. Register an “E-Factura” application in the ANAF developer profile with the callback URL from the plugin settings.
3. WooCommerce → e-Factura → Settings: Client ID and Client Secret, “Connect to ANAF”, the certificate, “Check the connection”.
4. Fill in the seller data and the number series (a series of its own if another program also issues invoices), keep the TEST environment.
5. Place a test order with a CUI and set it to “Completed” — within a minute the order shows the index and the ANAF status.
6. Show the VAT settings to your accountant and switch the environment to PRODUCTION.
7. For Pro: paste the licence key from the e-mail after payment or start the 7-day trial.