...
| Tip | ||
|---|---|---|
| ||
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 main field 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 main field 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 main field 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 main field mainfield mappings are fixed in the German declaration, for example:
...
Create mainfield mapping
The default main field mainfield mapping is not binding; it is possible to add further main field mainfield mappings or to overwrite existing main field mainfield mappings. This should be done with extreme care.
...
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 main field 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 main field 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.
...
- 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 main field mainfield mapping is not.
Mappings to the same preliminary declaration field with different types overwrite each other according to these rules:
...
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 main field 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.
...
| Column | Meaning |
|---|---|
| Copy Button | When this button is pressed, the fields of the mainfield mapping are preselected in the mask for creating a new main field mainfield mapping. A mapping is not yet created. |
| Bin | This button only appears for the mappings that were created in the current context.
|
| 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 main field 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:
|
| 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. |
...