...
| Table of Contents |
|---|
...
During the mapping of tax codes the tax codes are assigned to certain fields in the monthly VAT return and/or the annual VAT return. The mapping of tax codes can also be done manually. Alternatively, this can be done during the import of tax codes or by means of master data copy during the period creation.
...
The following fields are displayed for each mapping position:
| Company code | The company code in whose context the tax code exists. | |||||||||||||
| Reporting country | The configured reporting country of the tax code. | |||||||||||||
| Tax code | The tax code that is mapped in the mapping position. | |||||||||||||
| Tax code form | The tax code form of the tax code. Since a tax code can be stored with different tax code forms, it is important to distinguish between them here. | |||||||||||||
| Field ID | The mapping ID of the field in the declaration to which values of the imported tax code are to apply. This is not the line in the return, as it may change periodically while the IDs remain the same. | |||||||||||||
| Mapping condition | This column is only displayed if the corresponding setting for the current country is configured in the Settings → Countries area or is explicitly shown via the [Show / Hide Columns] function. With this function, the import of a value into the return can be tied to a condition. The following conditions can be configured:
Using this function, it is also possible to provide a tax code with several mappings that are tied to different conditions. | |||||||||||||
| Sign handling | This column is only displayed if the corresponding setting for the current country is configured in the Settings → Countries area or is explicitly shown via the [Show / Hide Columns] function. This function can be used to adjust the sign when importing a value. The following functions are available:
Manual changes in the declaration are always applied to the field without sign change as they are typed. However, if there is another mapping of the tax code, the sign change setting is applied to the other fields. The sign is only changed at the end if the settings for the original field and the other field differ. However, only the options [Invert sign] and [Without sign handling] can be considered for manual adjustments. The options [Always positive] and [Always negative] are treated as [Without adjustment]. |
| Tip |
|---|
It must be ensured that all tax codes are mapped, as this is the only way to ensure a complete transfer of the imported data to the advance return or annual return. Tax codes that are not to be included in the declaration must also be mapped, as the system assumes an error if the mapping is missing in order to avoid missing tax codes in the declaration. Tax codes that are not included in the declaration must be mapped to the fictitious field 0. |
...
Tax code | Please select the tax code that has to be mapped to the corresponding field of the VAT return form. Every tax code that has been created for company in the current period is available for selection. |
Tax code form | The tax code form can be selected here. In most cases, only one tax code form should be available; this is then preselected. However, in the case of ESA and ESE tax codes, for example, a tax code can exist for several tax code forms. A separate mapping must be carried out for each of these tax code forms. |
Reporting country | The reporting country cannot be selected and is already filled in by the application with the country currently being processed in VAT@GTC. |
Field ID | The selection of field positions depends on the form version selected in the period. A distinction must also be made between the period types.
|
| Mapping condition | This field is only displayed if the corresponding setting for the current country is configured in the Settings → Countries area. The default is [Map without condition] and is selected even if this setting is turned off. If this setting is configured, you can select from several mapping conditions. |
| Sign handling | This field is only displayed if the corresponding setting for the current country is configured in the Settings → Countries area. The default is [Without sign handling] and is selected even if this setting is turned off. If this setting is configured, it is possible to select from several sign handling variants. |
In the preliminary return or annual return form there are lines in which both the assessment basis and the tax have their own field designation (e.g. fields 35 and 36 in the German preliminary return form). Also, in cases where a assessment basis field and a tax field are directly connected in a line but have only one ID, the tax field in the VAT@GTC always has its own Mapping ID (e.g. field 81 and field "81a" in the German preliminary return form). In such cases, the VAT@GTC automatically carries out a so-called corresponding mapping. If such a field is entered when mapping a tax code, the corresponding mapping is automatically added.
If a field position is already assigned to a tax code, a query appears when a new assignment is attempted asking how this mapping should be handled. There are either two or three options:
| Overwrite/Yes | The existing mapping position is archived and replaced by the new position. | |||||
| Add | In the event that multiple mapping is allowed in this combination, the mapping can be added to the existing positions so that both mapping positions are active and used. It is important to note that multiple mapping is not always practical if it is technically possible.
| |||||
| No | The new tax code mapping is not created. |
Mapping Validation
Via [Validate Mapping], several plausibility checks of the existing tax code mapping are triggered (no completeness check!). The number of available checks varies depending on the country and period type.
...
Several status messages can be shown when the validation is finished:
| Indication | Meaning |
|---|---|
| Tax code mapping is not existing for monthly VAT Returns | A mapping of the tax codes in the preliminary VAT return has not yet taken place. |
| Mapping this Tax code to this field seems not to be valid. | The Mapping should be checked. |
VAT Return fields for monthly VAT Return not mapped in yearly VAT Return: | This error message appears directly below the function bar at the top of the page. A list of the missing tax codes follows. |
Mapping this tax code to this field seems not to be valid. Tax rate of tax code does not match the tax rate of the field. | Either the tax rate of the tax code should be changed here, or the tax code should be mapped to another field for the tax rate concerned. |
The tax code mapping is part of an incomplete multiple mapping. | For mappings to this field, the VAT@GTC expects a multiple mapping, but the tax code is only mapped to this field. |
| The tax code mapped to this field may only be mapped to certain other fields. | This mapping represents an invalid multiple mapping. It should be checked whether the multiple mapping is correct. |
If the validation should be carried out for all companies simultaneously, click on the [Mapping Validation (All Units)] button.
...