| 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 Mapping of tax codes page contains a list of all mapped tax codes. The [Mapping of tax codes] dialogue requires selection of a period, company and company code. The functions offered in this dialogue are described below.
| Tip |
|---|
| Every Tax Code has to be mapped, otherwise it is not possible to fully import the data into the preliminary or the annual VAT report. |
Create Mapping Positions
| Section |
|---|
|
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 the company code in the corresponding period is available for selection. |
Tax code procedure | The tax code procedure is defined automatically by the VAT@GTC, except for ESA and ESE tax codes. A separate mapping has to be performed for both of these tax codes. |
Reporting country | The reporting country cannot be selected freely, the application automatically preselects [DE]. The reason for this is that exclusively German VAT reports can be generated and sent using the VAT@GTC. |
Field ID | The choice of the field ID depends on the kinds of period selected in the [Master data] main area.
|
| Tip | ||
|---|---|---|
| ||
If the tax code is already mapped to a VAT return field, a warning message appears when trying to map it again. Click “Yes” to overwrite the existing tax code. |
Mapping Validation
When clicking on the [Mapping validation] button the plausibility check of the existing tax code mappings is started (not the completeness check!). It is checked whether the mapping is performed for both the tax base field and tax field in the VAT return. Since partially only the tax fields [e.g. field 66] and partially the assessment fields [e.g. fields 81 and 86] are mapped into the VAT return, the VAT@GTC automatically saves the corresponding tax base and tax fields in the database, and then during the import of the V00-report both tax amounts and tax base are stored. In addition to that, the “Double mapping” [see above] is performed for the fields where it is missing.
During the validation of the tax codes mapping for the annual VAT return the VAT@GTC also checks whether the mapping on the field positions of the monthly VAT return matches the mapping of the annual VAT return. So, e.g. the tax code A5 [“Intra-community supplies”] is mapped in the monthly VAT return to the field 41 and in the annual VAT return to the field 741.
Several status messages can be shown when the validation is finished:
| If no errors have been found during the validation, the corresponding message is shown. In addition, this message states what number of tax codes mapping has been finished successfully. |
| Mapping has to be checked. |
| The tax codes from the preliminary VAT return have not yet been mapped to the yearly VAT return. |
| Specific Tax codes are listed here. |
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
| Section |
|---|
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.
|
| Section |
|---|
To delete a mapping position click on the [Delete   |
| Section |
|---|
|
