The Mainfield Mapping dialogue is only available if three conditions are met:

The current period is an annual declaration period.
The current company enters the values manually without tax code into the declaration.
The company must submit preliminary returns and an annual return.

For companies that work with tax codes in VAT@GTC, the tax codes are used to decide how the values are to be transferred from the advance return to the annual return. Without tax codes, this transfer often turns out to be a somewhat more complex undertaking. The problem is that not every field in the advance return can be transferred to just one field in the annual return.

Good to know

For this reason, AMANA recommends always using tax codes, even for companies without an import file, even if these are fictitious or known tax codes from other companies have to be used.

The mainfield Mapping configures the transfer of the pre-announcement values into the annual declaration for purely manual declarants. The preliminary declaration fields and annual declaration fields are mapped to each other. Only one mainfield mapping can be created for each preliminary declaration field. An annual declaration field can theoretically be summed from several preliminary declaration fields if they are only linked to this field in the annual declaration.

Standard Mainfield Mapping

A default mainfield mapping is defined over all preliminary declaration fields that are only linked to one field in the annual declaration. These cannot be deleted. The following mainfield mappings are fixed in the German declaration, for example:

Preliminary VAT return field	Annual VAT return field	Preliminary VAT return field	Annual VAT return field	Preliminary VAT return field	Annual VAT return field
21	721	50	650	89	781
35	155	59	759	89a	781a
36	156	60	209	91	791
37	637	61	761	93	793
41	741	62	762	93a	793a
42	742	67	467	94	794
44	744	73	873	95	798
45	205	74	874	96	796
46	846	77	777	98	799
47	847	84	877
49	749	85	878

Create mainfield mapping

The default mainfield mapping is not binding; it is possible to add further mainfield mappings or to overwrite existing mainfield mappings. This should be done with extreme care.

An example of a relationship between a preliminary and an annual declaration field that is not 1:1 is field 81 in the preliminary declaration in Germany. Values that are mapped to field 81 in the preliminary return must be mapped to field 177, field 178 or field 179 in the annual return, depending on the specific matter. This assignment cannot be made generally, as no distinction can be made in the preliminary declaration for purely manual declarants.

Create new mainfield mapping

Create mainfield mapping across all companies

If you are really sure that only matters for a preliminary declaration field occur across all manual declarants of the group that also affect only one field in the annual declaration, you have the option of adding a mainfield mapping for all companies. To do this for all manual declarants via a single configuration, select "--- - All companies" in the function bar for company.

In the above example, it is not unlikely that no matter in the company affects fields 178 and 179 of the annual return and only field 177 is filled from field 81 of the preliminary return. In this case, field 81 and 177 can be selected in the dropdowns for the declaration fields. This mainfield mapping can be added via the [Create] button. If the transfer of the preliminary values to the annual declaration is then triggered, the values of the year of field 81 are now added up and entered in field 177.

Create mainfield mapping for individual company

If the rule for a mainfield mapping does not apply to all manual declarants of the group, but only to one or more companies, the mainfield mapping can also be created only for this company or companies. To do this, the corresponding company must be selected in the function bar under Company before the mapping is created.

Overwrite mainfield mapping

Mainfield mappings can not only be added, they can also overwrite other mainfield mappings. The following applies in principle:

There are three types of mainfield mappings:
- Standard mainfield mapping
- Period-wide, cross-company mainfield mapping
- Unit specific mainfield mapping
A mainfield mapping can only overwrite another mainfield mapping if it refers to the same field in the preliminary declaration.
A mainfield mapping that is created with the same type as another mainfield mapping on the same preliminary declaration field completely deletes the old mainfield mapping.
Several mainfield mappings can exist for the same preliminary declaration field if they have different types. Here, overwrite means that the overwriting mainfield mapping is marked as active and the overwritten mainfield mapping is not.

Mappings to the same preliminary declaration field with different types overwrite each other according to these rules:

EA mainfield mapping created for a single company overwrites a mainfield mapping with the same preliminary declaration field if it is defined in the standard or if it is defined across all companies.
A mainfield mapping that is created over the entire period overwrites a mainfield mapping with the same preliminary declaration field if it is defined in the standard. A company-specific mainfield mapping is not overwritten.
A mainfield mapping from the standard can only be overwritten and not overwrite anything.

Overview of the mainfield mappings

The existing mainfield mappings are listed in a table. If "--- - All Units" is selected in the function bar under Company, all mainfield mappings are displayed, including all mainfield mappings that have been created for individual companies. If an individual company is selected, the standard mappings and the cross-company mappings are displayed, as well as the individual mappings of this company. The individual mappings of other companies are not displayed.

The meaning and contents of the table are explained below:

Column	Meaning
Copy Button	When this button is pressed, the fields of the mainfield mapping are preselected in the mask for creating a new mainfield mapping. A mapping is not yet created.
Bin	This button only appears for the mappings that were created in the current context. If "--- - All Units" is selected in the function bar under Companies, the cross-company mappings can be deleted. If an individual company is selected, the mainfield mappings that are only created for this company can be deleted. A standard mainfield mapping cannot be deleted.
Active	This column is not displayed if "--- - All units" is selected under Companies, but only if an individual company is selected. If there is a tick in this column, this mainfield mapping is actually applied for the selected company when the preliminary return values are transferred to the annual return. Mainfield mappings without a tick are accordingly not applied because they have been overwritten by another one.
Declaration field (left)	This is the preliminary declaration field to which the mainfield mapping refers.
Declaration field (right)	This is the annual declaration field to which the mainfield mapping refers.
Type	The type of the mainfield mapping is displayed here. There are the following three types: Standard Cross-company (period) Unit specific
Unit ID	The ID of the unit for which the unit-specific mainfield mapping was created is displayed here. This is necessary because all unit-specific mainfield mappings are also displayed in the overview of all units.