NextERP Documentation
ROEN

e-Factura, e-Transport and SPV · Article 04

Common e-Factura errors

Applies to Odoo 19 · 20

The messages below appear in Odoo when an invoice is sent to e-Factura (the Romanian national e-invoicing system) or when the ANAF response is retrieved. Some are checks made by Odoo before sending (nothing goes to ANAF), others come from SPV (Spațiul Privat Virtual, the taxpayer's private online space at ANAF). The exact message may contain the name of the partner or field instead of the ellipsis.

Odoo checks before sending

These messages appear in the send window; the invoice does not reach ANAF until you correct them.

Message in Odoo Cause What to do
"The field … is required on …." A field is missing from the company's or the customer's address (county, city, street), including for foreign customers Fill in the field on the indicated partner
"The following partner's city name is invalid: …. If partner's state is București, the city name must be 'SECTORX', …" Customer in Bucharest with the city "București" Enter the sector as the city (Sector 1 … Sector 6)
"Each invoice line should have at least one tax." An invoice line has no tax Add the tax, including for exempt or reverse-charge lines
"Romanian access token not found. Please generate or fill it in the settings." The company is not connected to SPV Generate the token, as in Connecting to SPV
"The invoice has already been sent to the SPV." The invoice is already in the Sent or Validated status Do not resend it; fetch the status. For corrections, issue a credit note

Responses from SPV

Message in Odoo Cause What to do
"Access token is unauthorized." / "Access token is forbidden." Token expired or revoked, or the certificate has no rights on the company's CUI (the Romanian tax identification number) Generate the token again, with the certificate of the person registered in SPV for the company
"You reached the limit of requests. Please try again later." The number of requests accepted by ANAF was exceeded Try again later
"Timeout while sending to SPV. Use Synchronise to SPV to update the status." SPV did not return the index in time; the invoice stays Not indexed Do not resend; use Synchronize with ANAF
"This invoice was refused by the SPV for the following reason: …" The invoice does not meet the CIUS-RO validation rules Correct the data indicated in the reason and send again

How to read a refusal reason

The refusal reason is written in the invoice history and usually starts with the code of the broken rule (for example a BR-RO rule of the national format). The code points to the wrong element: the address, the tax code, the tax or the totals. After the correction, the refused invoice can be sent again directly, with Send: the old file is detached on refusal.

For an invoice that has stayed Not indexed for more than 3 days, synchronization marks it Refused, without a reason. Check in SPV whether the invoice arrived and, if not, resend it.

Documentation by the NextERP team.