Settings for creating annotations

Transaction: /EDGE/TC_TB_CV003

Through this transaction, the conditions that must be met so that when posting an FI document a TBAI file and / or an entry is created in the LROE, as well as the characteristics that TBAI / entry will have.

It is configured through a cluster of views, one for each LROE book.

This table will have an established order of priorities, so the configuration will be very important so that the mappings are carried out correctly.

The order of priority will be as follows:

Registration with Company / Doc Class / Tax Indicator / Accounting Code
Registration with Company / Class Doc./Indicator of Taxes
Registration with Company / Class Doc./Accounting Key
Registration with Society / Class Doc.
Registration with Company / Tax Indicator / Accounting Code
Registration with Company / Tax Indicator
Registration with Company / Accounting Code
Registration with Society

It should be noted that the company can be completed with '*', in which case the order of priority will be:

Registration with * / Doc Class / Tax Indicator / Accounting Code
Registration with * / Doc Class / Tax Indicator
Register with * / Doc Class / Accounting Key
Register with * / Doc class.
Registration with * / Tax Indicator / Accounting Code
Registration with * / Tax Indicator
Registration with * / Accounting Code
Register with *

ISSUED INVOICES

The configuration carried out in this view will be used for the creation of the TBAI files, for the creation of Invoices Issued With Software Guarantor (FEConSG), which corresponds to subchapter 1.1 of the LROE, and for the creation of Invoices Issued Without Software Guarantor (FESinSG), which corresponds to subchapter 1.2 of the LROE.

For the Invoices issued we have on the one hand the conditions that must be met for creation (in red in the image) and on the other hand the characteristics that the annotation will have (in green in the image).

The detail of the fields to be reported is as follows:

Field	Maenning

Field	Maenning
Company code	Identifier of the FI company where the condition applies. Only one can be chosen among those FI companies that have been entered in the table of Provincial treasury agency by company .
Document type	Class of accounting document that must be taken into account to create the annotation.
Tax indicator	The tax indicator represents a tax category that must be taken into account in the declaration to the Regional Treasury.
Posting key	Posting key that must be taken into account for the creation of the annotation.
Subchapter	You must choose whether the annotation in the LROE should be created as an Invoice Issued with Software Guarantor (FEConSG), in which case subchapter 1.1 is selected, or as an Invoice Issued without Software Guarantor (FESinSG), selecting 1.2 in this case.
Entry type	It is selected if the annotation that will be created will correspond to a registration or an annulment.
Simplified invoice	Allows you to check or uncheck whether the annotation that will be generated will correspond to a simplified invoice or not, in which case it is treated as a complete invoice.
Substitute for simplified	Allows you to check or uncheck whether the annotation that will be generated will correspond to an invoice that is issued in substitution of a simplified invoice. In this case, it will not be necessary to identify either the code and the type of rectification
Summary entry	Allows you to check or uncheck whether the annotation that will be generated will correspond to a summary entry or not.
Corrective code	It allows you to select whether the annotation that will be created will correspond to a corrective invoice, in which case one of the correction codes must be selected from the following values:
Rectification type	If a correction code has been selected, it must be selected whether it is a correction due to differences or substitution.
Regime Code 1	The system code with which the annotation will be created must be selected from the following values:
Regime Code 2	Additionally, a second regime code can be selected.
Regime Code 3	Additionally, a third regime code can be selected.
Breakdown	For those annotations that correspond to invoices issued to foreigners, a type of breakdown can be selected at the operation level. This type of breakdown at the operation level is the one that will be used by default when creating the annotation. However, if you want to configure invoices with different types of breakdown in the same invoice, you can configure it at the tax code level in the BREAKDOWN OF ISSUED view of the Tax Code Settings .
Self-consumption	Allows you to check or uncheck if the annotation that will be generated corresponds to self-consumption, in which case the annotation will be created in subchapter 1.2 (FESinSG).
Issued on behalf of	For those annotations that must be followed by the self-invoice flow, you must configure who will be the issuer of the invoice. The allowed values will be on your own account, on behalf of a third party or on behalf of the recipient. For more details on self-billing, see the section: Self-billing tools
Return made by	For those annotations that must be followed by the self-invoice flow, you must configure who will be the declarant of the invoice. The declaration may be your own or by a third party. For more details on self-billing, see the section: Self-billing tools
Osatu	Flag that enables sending additional information to the Osatu service.

RECEIVED INVOICES

The configuration made in this view will be used exclusively for the creation of annotations in chapter 2 (Received Invoices) of the LROE.

For the Invoices received, we have, on the one hand, the conditions that must be met for creation (in red in the image) and, on the other hand, the characteristics that the annotation will have (in green in the image).

The detail of the fields to be reported is as follows:

Field	Meaning

Field	Meaning
Company code	Identifier of the FI company where the condition applies. Only one can be chosen among those FI companies that have been entered in the table of Provincial treasury agency by company .
Document type	Class of accounting document that must be taken into account to create the annotation.
Tax indicator	The tax indicator represents a tax category that must be taken into account in the declaration to the Regional Treasury.
Accounting key	Posting key that must be taken into account for the creation of the annotation.
Send type	It is selected if the annotation that will be created will correspond to a registration or an annulment.
Invoice type	You must indicate what type of invoice will correspond to the annotation that will be created, being able to choose one of these values:
Corrective code	It allows you to select whether the annotation that will be created will correspond to a corrective invoice, in which case one of the correction codes must be selected from the following values:
Type of rectification	If a correction code has been selected, it must be selected whether it is a correction due to differences or substitution.
Regime Code 1	The system code with which the annotation will be created must be selected from the following values:
Regime Code 2	Additionally, a second regime code can be selected.
Regime Code 3	Additionally, a third regime code can be selected.
Breakdown	The type of breakdown must be indicated, choosing one of these values. This type of breakdown at the operation level is the one that will be used by default when creating the annotation. However, if you want to configure invoices with different types of breakdown in the same invoice, you can configure it at the tax code level in the BREAKDOWN OF RECEIVES view of the Tax Code Settings .
Self-consumption	Allows you to check or uncheck if the annotation that will be generated corresponds to self-consumption.
Self-billing	It allows to define if the flow will go by self-billing or by the normal flow.
Return made by	For those annotations that must be followed by the self-invoice flow, you must configure who will be the declarant of the invoice. The declaration in this case will be paid by the provider. For more details on self-billing, see the section: Self-billing tools

INVESTMENT GOODS

The LROE Chapter 3 (Investment goods) is currently only available for the provincial tax agency of Bizkaia, starting from version 1.5

The configuration made in this view will be used exclusively for the creation of annotations in chapter 3 (Investment goods) of the LROE.

For investment goods we have, on the one hand, the conditions that must be met for creation (in red in the image) and, on the other hand, the characteristics that the annotation will have (in green in the image).

The detail of the fields to be reported is as follows:

Field	Meaning

Field	Meaning
Company code	Identifier of the FI company where the condition applies. Only one can be chosen among those FI companies that have been entered in the table of Provincial treasury agency by company .
Document type	Class of accounting document that must be taken into account to create the entry.
Tax indicator	The tax indicator represents a tax category that must be taken into account in the declaration to the Provincial Treasury.
Posting key	Posting key that must be taken into account for the creation of the annotation.
Entry type	It is selected if the annotation that will be created will correspond to a registration or an annulment.

CASH ACCOUNTING SCHEME

The LROE Chapter 5 (Cash accounting scheme) is currently only available for the provincial tax agency of Bizkaia, starting from version 1.6

The configuration set in this view will be used exclusively for creating annotations in Chapter 5 (Cash accounting scheme) of the LROE.

For 'Receipts' and 'Payments,' we have, on one hand, the conditions they must meet for creation (red in the image), and on the other hand, the entry type the annotation will be (green in the image)."