Electronic invoicing

Requirement

TicketBAI, also called TBAI, is the new invoice reporting model created and shared by the three Basque provincial councils (Álava, Vizcaya y Guipúzcoa) and the Basque Government.

According to the Basque Government’s Department of Economy and Taxation, the TBAI’s main goal is to “guarantee the declaration of all sales operations conducted by persons or entities that perform economic activities”. TicketBAI is a common project but it is adapted to each provincial council’s laws. It means that its implementation differs depending on the provincial council.

Generally, as of the compliance deadline, all sales must generate a file with tax information which must be submitted to the corresponding provincial council’s tax authority. Each sale must also generate an invoice with the TBAI code and TBAI QR code based on the reported file. The invoice must also include enough information so that final clients can cross reference the invoice to ensure them of its correct issuance.

The three regional tax authorities and the Basque government have embarked on a shared project to fight tax fraud through the implementation of TICKET BAI. This Project revolves around a set of new technical and legal obligations that will directly impact how businesses create invoices.

This initiative intends to establish more control and visibility into companies’ turnover and business activities, particularly those in the B2C sector.

M3 solution

Users can submit their invoices electronically in the required format using LSP.

For each issued invoice and regardless of the invoicing function that has been used, an invoice BOD is created by M3 and can be viewed by users in 'Invoice Header. Open' (CMS500). Then, the invoice BOD is published using ION to LSP. The invoice BOD is handled by LSP and converted into a TBAI output type file sent through the connectivity. For TBAI files that are generated from the Bizkaia region, a LROE240 report must be generated to send the TBAI files to the tax authorities.

Any response from the tax authorities as to whether the invoice was accepted or rejected is received by LSP and is returned to M3 using the ProcessInvoice BOD.

Depending on the region, a different output file type can be used for any correction or modification to previously sent invoices. For Alava and Gipuzkua regions, if the ProcessInvoice BOD contains a PartiallyAccepted or Rejected status, the issues indicated in the ProcessInvoice BOD needs to be resolved. After doing it, LSP re-sends the reports using the Zuzendu modification schema or Zuzendu correction schema, respectively. For TBAI files that are sent through LROE240 and resulted to a PartiallyAccepted or Rejected, this means that one or more TBAI files that have been sent are rejected. The issues indicated in the ProcessInvoice BOD of the rejected TBAI must be resolved. After doing it, the reports are resent by LSP using the LROE240 modification schema. The original identification and QR code are referenced.

The ProcessInvoice BOD updates the invoices in M3 Business Engine using the API INVBODMI.

Limitations

Credit Invoice without an original invoice is currently not handled.

Configuration guidelines

Program ID	Program name	Description or comment
CMS500	Invoice Header. Open	All created and recreated invoices are displayed. See NCR 11227 for details about the process. For details on the consumption of the ProcessInvoice BOD to enable feedback from external portals for eInvoicing, see NCRs 12061, 12200, 12201.

See "M3 configuration for electronic invoicing" in the Infor M3 Core Configuration Guide for Infor Localization Services Platform.