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.

Overview of the Mapping of Tax codes

The Mapping of tax codes page contains a list of all mapped tax codes. 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:

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.

Praxishinweis

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 type

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 type.

Depending on the field, however, not all of these options are offered.

Import type	Base	Full tax	Deductible tax	Non dedutcible tax
Field type	Base	Full tax	Deductible tax	Non dedutcible tax
Gross	YES	YES	YES	YES
Base	YES
Tax		YES	YES	YES
Input tax		YES	YES	YES

Depending on which import type is configured, the corresponding column is read in when importing the reporting values and transferred to the declaration.

Good to know

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.

Manual adjustments, reconciliation adjustments and adjustments from resubmissions must be carried out separately for deductible and non-deductible tax.

Tax codes that have a mapping with the import type (non) deductible tax are not considered for reconciliation 1.

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.

Create Mapping Positions

To create a new mapping position, fill out the following fields and click on the [Create] button.

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 type	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.

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. Praxishinweis A multiple mapping is to be distinguished from a corresponding mapping: A multiple mapping is required if a tax code is to be taken into account in a declaration on different fields that do not have a direct assessment basis-tax relationship in the ratio 1:1. For example, if the tax code AX is mapped to field 35 in the German preliminary return, a corresponding mapping to tax field 36 is automatically created. If the tax code AX is also to be mapped to field 50, a multiple mapping is required.
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.

For mappings to fields that have a corresponding field (assessment basis and tax field with a direct 1:1 relationship), the system checks whether the mapping has been created for both field positions. If this is missing, the VAT@GTC carries out the [corresponding mapping] for these fields.
Another validation checks the fixed tax rate. If a field of the declaration has a fixed tax rate, the tax code mapped to this field cannot have another tax rate.
Some fields may be omitted with a new form. This means that existing mappings to these fields cannot continue to be used. Mappings to non-existing fields are removed.
Mappings to fields that still exist but may no longer be mapped for various reasons are also removed.
When validating the tax code mapping for the annual return, the VAT@GTC also checks whether the mapping to the field items of the preliminary VAT return matches the mapping of the annual return for VAT. If, for example, the tax code A5 ("Intra-Community supplies") was mapped to the field with the number 41 in the advance return for VAT, the VAT@GTC checks whether the field with the number 741 was mapped accordingly in the annual return. If this is not the case, an error message is displayed.
In addition, it is checked in the annual return whether an existing tax code is mapped both in the preliminary VAT return and in the annual return and whether there is a mapping to field 0.
Mainly abroad, it is also checked whether a multiple mapping is required for a tax code, but is missing.
A validation takes place whether the content of the Import Value column also matches the field type of the mapped field. For example, a tax amount should not be mapped to a field where the tax base is expected.

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.

Copy, edit and delete tax code maping

To create a new mapping position, it is possible to use the [Copy] function. The selected line is copied to the [Create new mapping position] input. Tax code, tax code procedure and field ID can be changed after that. The entry is saved by clicking on the [Create] button. The new entry appears in the overview table.

To delete a mapping position click on the [Delete ] button. The deleted mapping position does not disappear, it is moved to the archived and can be viewed using the Display function. By archivating a field that is part of the so-called double mapping, the other part is archived aswell.

Previously deleted mapping positions can be restored using the [Restore] button. The restored mapping positions are shown under the Active again. Fields with double mappings are restored too.