In this article, we will find the most common errors of TicketBAI and their possible solutions. It should be noted that we are constantly improving, and it is possible that not all existing errors are identified in this article.

We can find the invoices and their status in TAX SETTINGS, by clicking on Files:



Once we access Files, the most important columns to review to manage errors are Command, Error Information, and Fiscal Status.

In the Fiscal Status column, we will see if the invoice is correctly sent , in error status , or if it has been resent/rectified and we can see what error it has in Error Information.

Finally, if we click on the order number, a window will open with the order information, and we will see which documents are associated with it:



Knowing which documents are associated with the order can be useful in case of having to correct an invoice with a corrective invoice, in this case, all invoices are listed there in order of creation.

In the example image, it can be observed that the original invoice is the first one, invoice X-7 rectifies the original, X-9 rectifies X-7, and finally X-11 rectifies the previous one, and it is the one whose status is correct in TicketBAI.

We can search for invoices that are in error status using the filter. By clicking on Filters, and in Error Information, we write a hyphen (-). There, all invoices containing Error Information will appear, we just need to look at the Fiscal Status column to know which ones are bad:



Important: Each opened order generates an invoice at the same moment, once the order is paid and closed, the invoice is signed and sent to TBAI, until the order is closed, the invoice is not signed or sent, as the process is not complete.


Taxation in test mode

  • Description: For some reason, the test mode has not been deactivated, and we have been working normally.

  • Solution: It is necessary to recreate the invoices so that they are sent to TBAI.


Code 6016

  • Description: If it is a corrective invoice of any type, the "SérieFactura" must be identified.

  • Solution: Check that all counters of the different invoices in the section COUNTERS have a unique prefix.
    Check that in the section CASHIERS, they have associated the counter with the Simplified Invoice and Returns. It is important that these counters do not coincide to avoid errors.
    Once these points have been checked, a case must be opened to REVO for review.


Code 2025

  • Description: The total amount must be equal to the sum of the taxable bases plus taxes, plus the equivalent remuneration taxes of the Subject NotExempt block, plus the sum of the taxable bases of the Subject Exempt block and the sum of the amounts.

  • Solution: Open a case to REVO for review.


Code 5016

This is an old bug that has already been fixed, if we find an invoice with this error, we just need to click on ZUZENDU MODIFY.


Code 005

  • Description: The file has already been received previously.

  • Solution: This error is purely informative. Click on the order and check if there are other associated invoices, now check the other invoices until finding the one that is uploaded correctly.

    Note: If you see that there is only one document, you must open a case to REVO for review.


Code 021

  • Description: The file to be modified must have been previously received in the system.

  • Solution: Open a case to REVO for review.