Troubleshooting
“Test connection” fails
Section titled ““Test connection” fails”- “The ANAF authorisation is missing or expired”: click Authorise with ANAF again (the access token lasts 90 days and is renewed with the refresh token, which lasts 365 days).
- Check the mode: Test calls
api.anaf.ro/test, Live callsapi.anaf.ro/prod. - A 400 answer at the token step means the Client ID or secret is wrong, or the authorisation code was not used within about a minute: authorise again.
- ANAF refuses the login if the callback address differs from the registered one by even one character, or is not https.
- A 403 answer on the message list means the certificate’s user has no SPV rights for the CIF you entered.
- The Log shows the answer (masked). Your server must reach
logincert.anaf.roandapi.anaf.roover HTTPS (outgoing port 443) and have a current CA bundle.
Nothing happens after an order changes status
Section titled “Nothing happens after an order changes status”- Check Settings > General > Enable, the status setting and the license status bar.
- Open Jobs: queued jobs wait for cron. If the counts never change, run the command from the settings page by hand once.
- Orders of buyers abroad, or individuals when set to Skip, are skipped on purpose; use Create e-invoice on the order to override.
The invoice is Waiting for connection or seller data
Section titled “The invoice is Waiting for connection or seller data”Complete the seller data on the Connection page and authorise with ANAF; the next cron run queues it.
The invoice shows Error with “Local validation failed”
Section titled “The invoice shows Error with “Local validation failed””The add-on stopped the invoice before sending it because the schema or a rule check failed (for example a county that is not an RO-xx code, or a missing RON exchange rate). Fix the cause and use Send again.
The invoice is Rejected by ANAF
Section titled “The invoice is Rejected by ANAF”The messages of ANAF are shown on the order tab and in the log. Common causes are an invalid buyer identifier, a county or Bucharest sector that ANAF does not accept, and tax category mistakes. Correct the data and use Send again (same number), or, if ANAF accepted an earlier version, issue a credit note and a new invoice.
Uploaded but never accepted
Section titled “Uploaded but never accepted”ANAF can take minutes to hours. The add-on checks after 2, 5, 15, 60 and 180 minutes and then every hour from cron. If it stays Uploaded for more than a day, check the Log and the messages in your ANAF SPV.
The cron address answers “Forbidden”
Section titled “The cron address answers “Forbidden””The key in the address is wrong. Copy the address again from the settings page.
Still stuck
Section titled “Still stuck”Contact us through https://cs-cart.kaviolabs.com with the add-on version, the CS-Cart version and the relevant log lines (secrets are masked automatically).