Marcel Bolosh, the finance minister, acknowledged the problem, namely that some invoices were multiplying, and gave his subordinates a week’s time to resolve it. But the blame was also placed on the users. Meanwhile, companies that offer accounting software, the most important in the Romanian market, have reported what the problems are. All are important and absolutely all are caused by the Ministry of Finance.

The error and problem text was published by Saga Software, one of the companies offering these solutions, with support from two others: FGO and Tdec.

What technical problems does e-Invoice have?

We take 12 points from the mentioned text in full:

1. A newly created company that appears in the ANAF database creates problems for its suppliers. In particular, if I invoice a newly formed company, although this is found in the MF database search, it is identified in the VAT register. When sending an invoice to it, an error of the type “CUI identified in the invoice …. = DOES NOT EXIST” is generated.

Yes, Mr. Minister, it’s funny! The electronic invoicing system says that there is no company in all MF/ANAF databases. When a colleague from Oradea first pointed out this error to me, and we tried to determine how and when it appears, I could not believe it. Today we also received confirmation from other external sources, from TDec and FGO users, confirming the same situation. The colleague from Oradea is waiting for a response from ANAF to the message sent through SPV. I wonder what they will say, if they say anything.

2. Errors in the generation of the OAuth code (this code is special, which after its generation allows the transfer of taxpayer invoices, without the actual presence of a digital certificate, after the generation of this code) – in recent days These errors seem to have reduced the time when they are gone – but logic tells us so – most of the errors appeared during their generation, and now most likely the number of generations or re-generations has decreased, so the probability of errors has also decreased.

3. errors of web services – they randomly stop, do not function for a short time. They seem to decrease, but due to the fact that they are temporarily stopped or changed completely opaquely, they create problems.

4. Incorrect errors related to the formatting of invoices. The same invoice without any changes can be sent a second time without any problems. is one of the most common and frequent mistakes when invoices are automatically sent via API. For example, the known error “unknown element (‘Account’) in namespace”. This is a false positive error.

5. Changing the format of the answer list or other changes to them during a request through web services is a bug reported only once by one source.

6. When updating a digital certificate, the e-Invoice system does not see the data of the new certificate, even if authentication in the spv is possible manually. It takes at least a day for the system to see the updated certificate data. Appears more and more often. The sad thing is that in ANAF in SPV they can enter manually. But they are unable to send the invoice in e-Invoice for at least a few hours, even if they have confirmation from ANAF that their digital certificate has been updated.

7. Lack of required details when rejecting calls – same token/certificate works in some companies and not in others, even if they are authorized in the same SPV.

8. No paging and call blocking capabilities – their documentation says they block calls if there are too many and return an error code to stop the automatic billers. It actually returns not what the documentation says, but something else. According to official statements, they accept 100 bills per minute. The reality is that a maximum of 60 (ie one per second) can be sent to ensure that they are sent correctly.

9. The MF e-Invoicing Guide states that additional documents can be attached to invoices sent in this way – the documentation does NOT contain any specification on how to do this. There is no example of this. Someone try using the MF invoice creation page and see if they can add anything to it!

10. The web service call allows you to download a daily limit of only 500 bills/responses/index. What does it mean? If you issue 600 invoices and receive 10 invoices, only 500 of the 610 invoices will be uploaded! Not all. What is an aberration. I’m starting to understand Vodafone people. I was told that the error returned indicated that for more than 500 a new endpoint must be called. What to watch: there are no documents on it!

11. there were errors during the online validation of e-invoice XML (in online confirmation web services) and when generating online PDF files from these XMLs. Temporarily fixed, appears randomly.

Separately from the above, from those who primarily use TDec, as well as from other users of other platforms, we have received messages regarding this aspect:

12. The use of the https://www.anaf.ro/uploadxml/ program misleads users as they believe that PDF invoices generated by the ANAF website can be considered original/official, contrary to the provisions of Article 3 paragraph (3) from the ORDER to the MOF ORDER No. 1365/2021: “[…] The original copy of the electronic invoice is considered to be an XML-type file accompanied by an electronic signature of the Ministry of Finance, which is provided to the issuer, respectively the recipient, in the RO e-Invoice system in zip form. archive file”.

So, the Ministry of Finance faces several problems, not only those announced by the Ministry of Finance. It is true, these days people from CNIF are working non-stop, as confirmed to HotNews.ro by various sources from the Ministry of Finance. Many of these problems should not have existed. Some may still appear, but not so many.