...
| Deck |
|---|
|
The following fields are displayed for each mapping position: | Card |
|---|
|
| 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: | Map without condition | This is the default setting. An imported value is always transferred to the return via this mapping. | | Only if import-value positive | The value from the import is only inserted into the declaration via this mapping if the imported value is positive. | | Only if import-value negative | The value from the import is only inserted into the declaration via this mapping if the imported value is negative. |
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: Without sign handling | This is the default setting. An imported value is transferred to the return unchanged. | | Always positive | The value is always entered as a positive value in the declaration, regardless of the sign. This function should only be used in exceptional cases. In this case, please contact Amana directly. | | Always negative | The value is always entered as a negative value in the declaration, regardless of the sign. This function should only be used in exceptional cases. In this case, please contact Amana directly. | | Invert sign | The sign of the import value is always rotated. |
| Tip |
|---|
| A sign change of all output positions from the RFUMSV00 takes place beforehand, independent of this configuration, because these positions are in the RFUMSV00 with a reversed sign. The sign handling function via the mapping of tax codes considers the values after this reversal. |
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]. |
|
| Card |
|---|
|
| 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: | Map without condition | This is the default setting. An imported value is always transferred to the return via this mapping. | | Only if import-value positive | The value from the import is only inserted into the declaration via this mapping if the imported value is positive. | | Only if import-value negative | The value from the import is only inserted into the declaration via this mapping if the imported value is negative. |
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: Without sign handling | This is the default setting. An imported value is transferred to the return unchanged. | | Always positive | The value is always entered as a positive value in the declaration, regardless of the sign. This function should only be used in exceptional cases. In this case, please contact Amana directly. | | Always negative | The value is always entered as a negative value in the declaration, regardless of the sign. This function should only be used in exceptional cases. In this case, please contact Amana directly. | | Invert sign | The sign of the import value is always rotated. |
| Tip |
|---|
| A sign change of all output positions from the RFUMSV00 takes place beforehand, independent of this configuration, because these positions are in the RFUMSV00 with a reversed sign. The sign handling function via the mapping of tax codes considers the values after this reversal. |
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]. | | Import value |
Import files from the ERP system can contain not only the tax base and the tax, but also the portion of the tax that is deductible and the portion that is not deductible. Depending on the field, circumstance or similar, different information may be required. | Depending on the declaration field to which a tax code is mapped, different values may have to be entered. In most cases, a distinction is only made between base and tax. In some cases, however, the deductible tax, or even the non-deductible tax, must be entered explicitly. Therefore, these 4 different options can be selected for the import value.
Depending on the field, however, not all of these options are offered. | Importwert | Bemessungsgrundlage | Volle Steuer | Abzugsfähige Steuer | Nicht abzugsfähige Steuer |
|---|
| Feldtyp |
|---|
| Brutto | JA | JA | JA | JA |
|---|
| BMG | JA |
|
|
|
|---|
| Steuer |
| JA | JA | JA |
|---|
| Vorsteuer |
| JA | JA | JA |
|---|
| Tip |
|---|
| If the complete gross amount is to be entered in the field, then one mapping with the tax base and one with the tax must be created. |
| Warning |
|---|
| In the selected version 22.19, this column is purely informative and has no further effect. |
|
|
|
| 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. |
...
| Deck |
|---|
|
| Card |
|---|
|
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. - In the case of [Monthly VAT return], the fields of the monthly VAT return can be selected.
- In the case of [Annual VAT return], only the fields of the annual VAT return are available. It is important to note that not all fields of the annual VAT return as well as appendix UN and appendix UR have certain field positions. Special designations are used in order to fill out the fields using the VAT@GTC. These designations depend on the type of the VAT return form ([je] for yearly VAT return; [un] for appendix UN and [ur] for appendix UR) and the row of the form in which a certain field can be found.
- In the case of [Special prepayment], there will be no field IDs to choose from.
| | 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. |
| Card |
|---|
|
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. - In the case of [Monthly VAT return], the fields of the monthly VAT return can be selected.
- In the case of [Annual VAT return], only the fields of the annual VAT return are available. It is important to note that not all fields of the annual VAT return as well as appendix UN and appendix UR have certain field positions. Special designations are used in order to fill out the fields using the VAT@GTC. These designations depend on the type of the VAT return form ([je] for yearly VAT return; [un] for appendix UN and [ur] for appendix UR) and the row of the form in which a certain field can be found.
- In the case of [Special prepayment], there will be no field IDs to choose from.
| | 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. | | Import value | This field is only displayed if the corresponding setting for the current country is configured in Settings → Countries. The default is [Tax base] for Tax base fields and [Full tax] for Tax as well as Input tax fields and is also selected when this option is turned off. |
|
|
|
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.
...
| 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. |
...