RO e-Factura (ANAF) error messages explained
When you send an invoice to RO e-Factura, ANAF's system answers in stages. The upload call returns an upload index or an error message, the status call then answers ok, nok or in prelucrare, and a nok comes with an error file listed as ERORI FACTURA. Most of these messages carry no code, so Klarbon lists them under its own short descriptions and links to the official API pages they come from. The validation errors name CIUS-RO and EN 16931 rules such as BR-RO-110, and each of those rules has its own page on Klarbon.
In short
What ANAF's RO e-Factura answers mean, from nok and ERORI FACTURA to upload errors such as a file over 10 MB, and what to do before you send the invoice again.
This list covers 43 messages from the official documents below. ANAF gives 33 of them no code, so Klarbon lists them under its own description. 9 have their own page; the others are explained in the table only.
Upload status (stareMesaj)
| Code | What it means |
|---|---|
| ok | Invoice processed RO e-Factura status ok means the invoice file was validated and processed by the system. Nothing to do. The answer, with the original invoice and the Ministry of Finance's signature, can be downloaded, and the invoice is also available to the buyer. |
| nok | Errors found, invoice not delivered |
| in prelucrare | Still being processed RO e-Factura status in prelucrare means the system has not yet finished processing the uploaded file. Check the status again later with the same upload index. |
| XML cu erori nepreluat de sistem | File refused at upload |
Types of answer in the message list
| Code | What it means |
|---|---|
| ERORI FACTURA | Answer with the errors found |
| FACTURA TRIMISA | Invoice sent and validated RO e-Factura answer type FACTURA TRIMISA is delivered after an invoice you sent was validated: it holds the original invoice with the Ministry of Finance's signature. Nothing to fix. Download it within 60 days if you need the signed copy. |
| FACTURA PRIMITA | Invoice received RO e-Factura answer type FACTURA PRIMITA is an invoice you received as the buyer from a seller who sent it through RO e-Factura. Nothing to fix. Download it within 60 days; after that it is archived and released on request. |
| MESAJ CUMPARATOR PRIMIT | Message from the buyer, received RO e-Factura answer type MESAJ CUMPARATOR PRIMIT is a message from the buyer to the issuer of an invoice, as received. Read the message, then answer the buyer as you agreed with them. |
| MESAJ CUMPARATOR TRANSMIS | Message from the buyer, sent RO e-Factura answer type MESAJ CUMPARATOR TRANSMIS is a message from the buyer to the issuer of an invoice, as sent. Nothing to fix. Review the message if you need to follow up with the invoice issuer. |
Upload errors
| Code | What it means |
|---|---|
| File larger than the size limit | |
| File does not match the UBL or CII structure | |
| CIF in the request is invalid | |
| Unknown value for the standard parameter RO e-Factura answers with this message when the standard parameter of the request has a value the service does not accept. Send one of the accepted values. The software that calls the service sets it. | |
| Invalid value for the extern parameter RO e-Factura's upload service answers with this message when the extern parameter is present with a value other than DA. Send extern=DA only for a buyer outside Romania who has neither a CUI nor a NIF, or leave the parameter out. | |
| Invalid value for the autofactura parameter RO e-Factura's upload service answers with this message when the autofactura parameter is present with a value other than DA. Send autofactura=DA for an invoice the buyer issues on the supplier's behalf, or leave the parameter out. | |
| Invalid value for the executare parameter RO e-Factura's upload service answers with this message when the executare parameter is present with a value other than DA. Send executare=DA only for such an invoice, or leave the parameter out. | |
| CIF not in the enforcement register RO e-Factura's upload service answers with this message when executare=DA is sent but the CIF is not in the RO e-Factura register for enforcement. Leave executare out unless an enforcement body submits the invoice on behalf of the debtor; otherwise check the CIF sent. | |
| XML file missing from the request RO e-Factura's upload service answers with this message when the request does not include an XML file. Attach the XML file to the request and send it again. |
Status, list and download request errors
| Code | What it means |
|---|---|
| A required parameter is missing RO e-Factura answers with this message when a required parameter of the request is missing. Send the request again with every required parameter filled in. | |
| Upload index is not a whole number RO e-Factura's status service answers with this message when the id_incarcare sent is not a whole number. Send the upload index exactly as the upload call returned it. | |
| No invoice with this upload index RO e-Factura's status service answers with this message when no invoice is found for the id_incarcare given. Ask for the status again with the correct upload index. | |
| Number of days is not a whole number RO e-Factura's message list service answers with this message when the zile parameter is not a whole number. Send zile as a whole number and try again. | |
| Number of days outside 1 to 60 RO e-Factura's message list service answers with this message when the zile parameter is not between 1 and 60. Ask for 1 to 60 days. | |
| A list parameter is not a valid number RO e-Factura's paginated message list answers with this message when startTime, endTime or pagina is not a number or has a value the system does not accept. Send the times in milliseconds, such as 1646037374000, and a page number, then try again. | |
| Start of the period more than 60 days ago | |
| End of the period is not later than its start RO e-Factura's paginated message list answers with this message when endTime is not later than startTime. Send an endTime later than startTime. | |
| End of the period in the future RO e-Factura's paginated message list answers with this message when endTime is later than the moment of the request. Send an endTime no later than the time of the request. | |
| Unknown value for the filter RO e-Factura's message list services answer with this message when the filtru parameter has a value other than E, T, P or R. Send E, T, P or R, or leave filtru out to get the full message list. | |
| Page number higher than the number of pages RO e-Factura's paginated message list answers with this message when pagina is higher than the total number of pages. Ask for a page within the total. | |
| No messages in the period RO e-Factura's message list services answer with this message when there are no messages in the requested period. Widen the period within the last 60 days or leave out the filter, then ask for the list again. | |
| More than 500 messages: use pages RO e-Factura's simple message list answers with this message when the list holds more than the 500 messages allowed on one page. Use the paginated list, listaMesajePaginatieFactura, and read it page by page. | |
| Download id is not a whole number RO e-Factura's download service answers with this message when the id sent is not a whole number. Send the id exactly as the message list gives it. | |
| No invoice for this download id RO e-Factura's download service answers with this message when no invoice is registered for the id given. Download with the id from the message list. |
Validation and seal check messages
| Code | What it means |
|---|---|
| R_BT_32_cui | Seller CUI incorrect |
| Signature not confirmed for these files | |
| Signature confirmed RO e-Factura's signature check answers with this message when the invoice XML and the signature file were validated: the signature is authentic and belongs to the invoice. Nothing to do. The XML invoice with its signature counts as the original document. | |
| Signature check request incomplete or invalid RO e-Factura's signature check answers with this message when at least one of the two files was not uploaded or is not an e-invoice XML file. Upload both files and run the check again. |
Rights, limits and technical errors
| Code | What it means |
|---|---|
| No SPV rights for any CIF RO e-Factura answers an upload, status or message list call with this message when the person or application calling it has no rights in SPV for any CIF. Use a certificate registered in SPV as a representative of the company, or have that right registered first. | |
| No SPV rights for this CIF RO e-Factura answers an upload or message list call with this message when the caller has no rights in SPV for the CIF given. If the CIF sent is wrong, correct it. Otherwise, use a certificate that represents this CIF in SPV, or have the right of representation registered. | |
| No right to query this upload RO e-Factura's status service answers with this message when the caller has no right to query the upload index given. Use the correct upload index and a certificate authorised to query it, then ask for the status again. | |
| No right to download this answer RO e-Factura's download service answers with this message when the caller has no right to download the answer. Download with a certificate that represents that CUI in SPV. | |
| Daily call limit reached RO e-Factura answers with this message when a daily limit on calls has been reached, for RASP uploads, status queries, message lists or downloads. Wait until the next day before calling again. If you need higher limits, ANAF asks you to write through the contact form in SPV or on anaf.ro; repeatedly ignoring the limits can get API access blocked. | |
| Technical error in the service RO e-Factura's services answer with this message when a technical error occurs, giving a reference after Cod. Try again later. If it keeps happening, contact ANAF and quote the reference given after Cod. |
Read the official document
- eFactura: Serviciu de upload al facturii (upload, uploadb2c) Source: eFactura: Serviciu de upload al facturii (upload, uploadb2c), version 1.0 (2025-02-03), published by Ministerul Finanțelor, read on 8 November 2026.
- eFactura: Serviciu de stare mesaj al facturii (stareMesaj) Source: eFactura: Serviciu de stare mesaj al facturii (stareMesaj), version 1.0 (2021-11-02), published by Ministerul Finanțelor, read on 8 November 2026.
- eFactura: Serviciu de listare mesaje (listaMesajeFactura, listaMesajePaginatieFactura) Source: eFactura: Serviciu de listare mesaje (listaMesajeFactura, listaMesajePaginatieFactura), version 1.0 (2024-01-27), published by Ministerul Finanțelor, read on 8 November 2026.
- eFactura: Serviciu de descarcare al facturii (descarcare) Source: eFactura: Serviciu de descarcare al facturii (descarcare), version 1.0 (2021-11-02), published by Ministerul Finanțelor, read on 8 November 2026.
- eFactura: Serviciu de validare pentru sintaxa UBL Invoice si CreditNote (validare) Source: eFactura: Serviciu de validare pentru sintaxa UBL Invoice si CreditNote (validare), version 1.0 (2022-10-28), published by Ministerul Finanțelor, read on 8 November 2026.
- XML Signature Validation API: API pentru validarea semnăturilor la facturile electronice Source: XML Signature Validation API: API pentru validarea semnăturilor la facturile electronice, version 1.0 (2024-09-03), published by Ministerul Finanțelor, read on 8 November 2026.
- Prezentare servicii web pentru Sistemul național privind factura electronică RO e-Factura Source: Prezentare servicii web pentru Sistemul național privind factura electronică RO e-Factura, version 2025-02, published by Ministerul Finanțelor, read on 8 November 2026.
- Limite la apelarea API eFactura Source: Limite la apelarea API eFactura, version 2024-03-25, published by Ministerul Finanțelor, read on 8 November 2026.
- Ghid privind utilizarea sistemului național de facturare electronică RO e-Factura Source: Ghid privind utilizarea sistemului național de facturare electronică RO e-Factura, version 2024-02-21, published by Ministerul Finanțelor, read on 8 November 2026.
Klarbon explains each code in its own words; the official wording is in the document linked above.
Frequently asked questions
Why do most RO e-Factura messages have no code?
ANAF's API documentation lists the messages its services return as plain Romanian text, without codes. Klarbon describes each one in its own words, and the paste box on the rejection codes page recognises the message; the exact wording is in the official pages linked below.
What is the difference between nok and XML cu erori nepreluat de sistem?
With nok the system found errors and did not process the file. You can download an answer with the errors and the Ministry of Finance's signature, but the invoice does not reach the buyer. XML cu erori nepreluat de sistem means the file was already refused at upload, and the error came back as the answer to the upload call.
Where do I find the error file?
In the list of answers, under the type ERORI FACTURA. Downloading it gives a ZIP with two XML files: one with the errors found and one with the Ministry of Finance's electronic signature.
How long can I download answers?
Invoice files and error messages can be downloaded for 60 days from when they are published in the system. After that they are archived and released on request, and the RO e-Factura guide explains how to ask for documents to be posted again.
Where do these messages come from?
From the RO e-Factura API descriptions, the web services presentation and the user guide published by the Ministry of Finance on mfinante.gov.ro, read on 8 November 2026. ANAF gives most of these messages no code; Klarbon's headings are its own descriptions, not ANAF's wording.