b+ TicketBAI-BATUZ Monitor
The b+ TicketBAI-BATUZ monitor is a tool that allows you to view the posted documents for which TBAI records and/or LROE annotations have been generated.
Filter fields
By default, the following fields have been set for the search and filtering of results: Company, Accounting entry, Fiscal year, Accounting entry date, Posting date, Accounting period, Sending type and Accounting entry type.
However, it is possible to edit the field layout using the “Adapt filters” button to include and/or exclude fields from the default layout.
The b+ TicketBAI-BATUZ monitor organizes the results according to the Provincial Council to which it applies (Álava, Guipúzcoa and Vizcaya), as well as according to the status in which the registrations are (Accepted, Erroneous and Pending):
Accepted : Shows only results in “ Correct ” status.
Incorrect : Shows only results in “ Incorrect ” status.
Pending : Displays results whose processing has not yet been completed.
Navigability
Company: If you have the required role, clicking on the company code accesses the “Profit and Loss” account of the corresponding company. If you do not have the required role to view this account, a new SAP Cloud node will be opened.
Accounting entry: By clicking on the document number, a menu is displayed through which it is possible to navigate to the “Accounting entry management” application (Manage accounting entries: New version).
Detail: By clicking on any other data in the line other than “Company” or “Accounting Entry”, or by clicking the arrow, you access the detail view.
If the TBAI record or LROE annotation has been rejected, the status will be displayed as “Failed”.
When accessing the details, the reason for the rejection will be displayed in the “State Description” field and in the “Status History” section:
Attachments : In the “Attachments” section you will find the files generated from the accounting document, as well as the response XML obtained.
By clicking on these they will be downloaded automatically.
Features
The TicketBAI-BATUZ monitor has two (2) main functions: “Correct” and “Process.” These can be executed both from the monitor’s main screen and from the “Detail” view of each record/entry found in the TicketBAI-BATUZ (TicketBAI-LROE) monitor.
“Corregir” button
Allows the correction of records/entries that do not require the issuance of a corrective invoice (Substitute or Credit note).
Available from version 1.1.0 onwards.
The functionality of the “Corregir” button covers:
Invoices issued with certified software (TicketBAI invoices) subject to the TicketBAI regulations of the Provincial Councils of Álava and Gipuzkoa.
The correction is performed through the Zuzendu service provided by the Provincial Councils of Álava and Gipuzkoa for TicketBAI records of type “Creation”/”New” (Alta) with status “Incorrect,” “Accepted with errors” or “Correct,” as well as for TicketBAI records of type “Cancellation”/”Annulment” with status “Incorrect.”
Invoices issued with certified software (TicketBAI invoice) subject to the regulations of the Provincial Council of Bizkaia (BATUZ: TicketBAI-LROE) of type “Creation”/”New” (Alta) with status “Incorrect,” as well as the resubmission of LROE entries of type “Cancellation”/”Annulment” with status “Incorrect” corresponding to this subsection.
According to the LROE regulations of Bizkaia, the correction of rejected invoices under Subchapter “1.1 – Invoices issued with certified software” (TicketBAI invoices) can only be performed through Subchapter “1.2 – Invoices issued WITHOUT certified software.” For this reason, the correction functionality converts the original LROE entry of an invoice issued with certified software (FE 1.1) into an LROE entry corresponding to Subchapter “1.2 – Invoices issued without certified software” (FE 1.2). Once converted, it is sent to Subchapter 1.2 (Invoices issued without certified software), which allows the correction of LROE records/entries in status “Incorrect,” “Accepted with errors” and “Correct”.
If the invoice needs to be registered under Subchapter “1.1 – Invoices issued with certified software” of the LROE (Bizkaia) instead of Subchapter “1.2 – Invoices issued WITHOUT certified software,” the corresponding accounting document for the LROE FE 1.1 entry in status “Incorrect” must be canceled and reposted correctly to generate a new LROE FE 1.1 entry that can be received in status “Correct”.
Invoices issued WITHOUT certified software (FE 1.2) subject to the regulations of the Provincial Council of Bizkaia (BATUZ: LROE) of type “Creation”/”New” (Alta) with status “Incorrect”, “Accepted with errors” or “Correct,” as well as the resubmission of LROE entries of type “Cancellation”/Annulment” with status “Incorrect” corresponding to this Subchapter.
Received invoices subject to the regulations of the Provincial Council of Bizkaia (BATUZ: LROE) of type “Creation”/”New” (Alta) with status “Incorrect”, “Accepted with errors”, or “Correct,” as well as the resubmission of LROE entries of type “Cancellation”/”Annulment” with status “Incorrect” corresponding to this Subchapter.
Procedure for correcting TBAI records and/or LROE entries:
Select the documents to be corrected or modified and click the “Corregir” button.
Refresh the monitor by cliking the “Go” button.
Depending on the type of response received after the correction, the record/entry will be displayed in the corresponding tab (“Accepted” or “Erroneous”).
The document correction functionality (the “Corregir” button) is also available from the “Detail” view of the record/entry.
The document correction functionality includes the new files generated for the correction of the document in the “Attachments” section of the record’s “Detail” view.
Additionally, there is a new section called “Correcciones” (EN: Corrections) within the record/entry’s “Detail” view.
In this new section, the statuses obtained from each correction attempt are displayed, along with the returned error code and description, as well as chronological information about the correction.
The “Status History” section shows the status received on the first submission attempt (Original Flow), while the “Corrections” section displays the subsequent statuses obtained through the correction flows.
New Complementary Statuses
The correction functionality incorporates new complementary statuses that inform the user about the accounting situation of the document both in SAP and with the Tax Agency (AT/Hacienda Foral), indicating whether it has been canceled (Reversed) in either system.
The word “Obsoleto” (EN: Obsolete) in parentheses indicates that the accounting document is canceled (reversed) in SAP or is a cancellation (reversal) of a creation/new (Alta), and that a “Cancellation”/”Annulment” record is pending submission.
The word “Anulado” (EN: Canceled) in parentheses indicates that the accounting document is canceled/reversed in both systems, in SAP and at the Tax Agency/Hacienda Foral.
The following details the statuses that can be obtained for records/entries that have undergone cancellations/reversals in SAP:
→ “Creation”/”New” record/submission with status: “Incorrect” (Obsoleto)
Refers to a “Creation”/”New” record (Alta) that, for some reason, did not meet the minimum validations required for acceptance by the service provided by the Tax Agency/Hacienda Foral to which it was sent, but is additionally canceled/reversed in SAP (Column “Is reversed” marked as “Yes,” only for “Creation”/”New” record/entry (Altas) submissions) and has a generated “Cancellation”/”Annulment” record/entry that has not yet been sent.
Example:
→ “Cancellation”/”Annulment” record/submission (Baja) with status: “Incorrect” (Obsoleto)
Refers to a “Cancellation”/”Annulment” record (Baja) that, for some reason, did not meet the minimum validations required for acceptance by the service provided by the Tax Agency/Hacienda Foral to which it was sent. Additionally, this status indicates that the corresponding “Creation”/”New” record (Alta) that it cancels has not yet been received by the respective Tax Agency/Hacienda Foral.
Example:
A “Cancellation”/”Annulment” record (Baja) can only be returned by the Tax Agency/Hacienda Foral to which it was sent as either “Received” or “Rejected” (“Correct” or “Incorrect,” respectively).
→ “Creation”/”New” record/submission (Alta) with status: “Accepted with errors” (Obsoleto)
Refers to a “Creation”/”New” record (Alta) that met the minimum validations required for acceptance by the service provided by the Tax Agency/Hacienda Foral to which it was sent, but is additionally canceled in SAP (Column “Is reversed” marked as “Yes,” only for “Creation”/”New” record (Alta) submissions) and has a generated “Cancellation”/”Annulment” record/entry that has not yet been sent.
Example:
A “Creation”/”New” record/entry (Alta) in this status, “Accepted with errors (Obsolete)” indicates that it has a corresponding “Cancellation”/”Annulment” record/entry (Baja) that is still pending submission.
If the “Cancellation”/”Annulment” record/entry (Baja) is not sent, the “Creation”/”New” record (Alta) will remain valid for tax purposes at the Tax Agency/Hacienda Foral that received it, even though it is marked as “Is reversed” in SAP.
→ “Creation”/”New” record/submission (Alta) with status: “Correct” (Obsoleto)
Refers to a “Creation”/”New” record (Alta) that met all the required validations for acceptance by the service provided by the Tax Agency/Hacienda Foral to which it was sent, but is additionally canceled/reversed in SAP (Column “Is reversed” marked as “Yes,” only for “Creation”/”New” record (Alta) submissions) and has a generated “Cancellation”/”Annulment” record/entry that has not yet been sent.
Example:
A “Creation”/”New” record (Alta) in this status, “Correct” (Obsoleto)”, indicates that it has a corresponding “Cancellation”/”Annulment” record/entry (Baja) that is still pending submission.
If the “Cancellation”/”Annulment” record/entry is not sent, the “Creation”/”New” record (Alta) will remain valid for tax purposes at the Tax Agency/Hacienda Foral that received it, even though it is marked as “Is reversed” in SAP.
→ “Creation”/”New” record/submission (Alta) with status: “Accepted with errors” (Anulada)
Refers to a “Creation”/”New” record (Alta) that originally met the minimum validations for acceptance but has been properly canceled both in SAP and at the corresponding Tax Agency/Hacienda Foral.
Example:
The word “Anulada” (EN: Canceled) in parentheses indicates that the “Cancellation”/“Annulment” record/entry (Baja) was generated and received by the corresponding Tax Agency/Hacienda Foral, and therefore, the corresponding “Creation”/”New” record (Alta) is no longer valid for tax purposes, even though the “Creation” record/entry was previously received with error (Accepted with errors).
→ “Creation”/”New” record/submission (Alta) with status: “Correct” (Anulado)
Refers to a “Creation”/”New” record (Alta) that originally met all the required validations for acceptance but has been properly canceled both in SAP and at the corresponding Tax Agency/Hacienda Foral.
Example:
In this case, the word “Anulado” (EN: Canceled) in parentheses indicates that both the “Creation” and “Cancellation”/“Annulment” records/entries have been properly received by the corresponding Tax Agency/Hacienda Foral.
→ “Cancellation”/“Annulment” record/submission (Baja) with status: “Correct” (Canceled)
Refers to a “Cancellation”/“Annulment” record that has been properly generated and received by the corresponding Tax Agency/Hacienda Foral.
Correction Functionality Restrictions
The correction functionality (the “Corregir” button) is blocked for all records/entries in the statuses “Accepted with errors (Canceled)” and “Correct (Canceled)” to prevent the correction of records/entries that have been properly canceled/reversed in SAP and at the Tax Agency/Hacienda Foral. This ensures that the validity of “Creation”/”New” record (Alta) for tax purposes cannot be reactivated through unnecessary corrections of already canceled/reversed documents.
The correction functionality, whether via the Zuzendu Service (Álava and Gipuzkoa) or the submission service of Bizkaia, should only be used when issuing a corrective invoice of type “substitute” or “for differences” (credit note) is not required.
It is important to note that each Provincial Council applies its own validations and consolidation criteria, which may vary. For example, the same accounting document may be “Accepted with errors” in Álava or Gipuzkoa, but rejected as “Incorrect” in Bizkaia.
“Process” button
Allows re-execution of sending the generated record and/or annotation in case it has previously failed.
“TBAI Code” hyperlink
By clicking on the TBAI code, a new window opens in the browser in which the invoice sent to the corresponding Provincial Council will be displayed.
Avvale 2024