...
If manual message creation without tax code mapping is selected, the message values can be entered directly into the form manually. If there is a direct relationship to a related BMG or tax field, and a unique percentage applies, then the opposite side is calculated automatically.
It is not possible to enter values from different transactions separately in the same field and to view a breakdown afterwards. However, a file with a comment can be attached via the paper clip with the plus sign, in which such a breakdown can be made alternatively. Any other files can also be uploaded there. If adjustments are necessary, the existing values in the declaration lines can be overwritten.
...
The values are not entered directly into the field when creating with mapping. In order for a field to be filled, a mapping to the field must exist.
Information on whether a tax code is stored is provided by a small triangle in front of the corresponding field. If the mouse is held over the triangle, the tax codes that are mapped to this field are listed.
...
Each entry in the declaration is represented with the following columns:
...
| id | Fielddetails |
|---|
...
| label | 22.00-22.13 |
|---|
...
This symbol can be used to create an offsetting entry. The fields Change, Value and Comment are filled in on the basis of the original line. The change must then be added via the plus sign.
...
| label | 22.14-22.19 |
|---|
...
This symbol can be used to create an offsetting entry. A pop-up opens that lists all offsetting entries that result from this and asks for confirmation of this process. Offsetting entries not only affect the field itself, but also, for example, the corresponding mapping of the tax base or tax, or a multiple mapping. In the pop-up, as in the normal input mask, a comment must be written which, when saved, is supplemented by the information as to which entry of the declaration has been offset.
...
| Identifier | The identifier consists of the tax code, the tax code type and a consecutive number. If the sequential number is [0], this means that the value originates from the import file RFUMSV00, as can also be seen in the comment field. |
| Type | This field is only shown for gross fields. These are currently only available in Belgium. For gross fields, not only the tax base but also the tax can be mapped to a field. In this case, both values are entered separately. In order to distinguish whether it is the tax base or the tax, the type is also indicated. The following types are available: |
| CC | Indication of the company code number to which the declaration value is assigned. |
| Value | Amount of the tax base or tax amount depending on whether a tax base field or a tax field is considered. Negative amounts are marked with a preceding minus. |
| Comment | The comment field explains the origin of the line item that is part of the message value. The comment is assigned by the system for automatic entries, e.g. the first entry (consecutive number = "0") is stored by default with the text "Import Report V00". |
| Red X | This symbol can be used to create an offsetting entry. A pop-up opens that lists all offsetting entries that result from this and asks for confirmation of this process. Offsetting entries not only affect the field itself, but also, for example, the corresponding mapping of the tax base or tax, or a multiple mapping. In the pop-up, as in the normal input mask, a comment must be written which, when saved, is supplemented by the information as to which entry of the declaration has been offset. |
| Paper clip | Individual positions and files can be attached to the value via this symbol. |
| Compliance stamp | The last symbol in this overview is the compliance stamp. With mouse over, it is possible to see who made this entry, when and in which correction. |
Tax codes are often mapped not only to a single field, but also to the corresponding tax or base field. An adjustment to this other field is automatically calculated based on the tax rate of the tax code used and is also added. There are also cases where a tax code should run on several fields in the declaration that are not directly related. In Germany this is rather an exception, but internationally it is needed more often. By default, an adjustment to a tax code is transferred to all fields to which this tax code is linked, taking into account the field types and the tax rate. This functionality can be switched off for most countries in the [Settings → Countries → Edit country] dialogue under [Declaration field update]. For some countries, however, this is fixed.
...