Versions Compared

Old Version 61

changes.mady.by.user Lukas Schwalvenberg

Saved on

compared with

New Version 62

changes.mady.by.user Lukas Schwalvenberg

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Deck
idView

The following fields are displayed for each mapping position:

Card
label22.00-22.18


Company codeThe company code in whose context the tax code exists.
Reporting countryThe configured reporting country of the tax code.
Tax codeThe tax code that is mapped in the mapping position.
Tax code formThe 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 IDThe 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 conditionThis is the default setting. An imported value is always transferred to the return via this mapping.
Only if import-value positiveThe value from the import is only inserted into the declaration via this mapping if the imported value is positive.
Only if import-value negativeThe 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 positiveThe 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 negativeThe 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 signThe sign of the import value is always rotated. 


Tip
titlePraxishinweis

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



Card
label22.19


Company codeThe company code in whose context the tax code exists.
Reporting countryThe configured reporting country of the tax code.
Tax codeThe tax code that is mapped in the mapping position.
Tax code formThe 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 IDThe 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 conditionThis is the default setting. An imported value is always transferred to the return via this mapping.
Only if import-value positiveThe value from the import is only inserted into the declaration via this mapping if the imported value is positive.
Only if import-value negativeThe 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 positiveThe 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 negativeThe 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 signThe sign of the import value is always rotated. 


Tip
titlePraxishinweis

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 valuetype

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

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

JA
ImportwertImport typeBemessungsgrundlageBaseVolle SteuerAbzugsfähige SteuerNicht abzugsfähige Steuer
Feldtyp
BruttoJAJAJAJA
BMGJASteuerJAJAJAVorsteuerJAJAFull taxDeductible taxNon dedutcible tax
Field type
GrossYESYESYESYES
BaseYES


Tax
YESYESYES
Input tax
YESYESYES


Tip
titleGood 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. 


Warning
titleAttention!

In the selected version 22.19, this column is purely informative and has no further effect.





...

IndicationMeaning
Tax code mapping is not existing for monthly VAT ReturnsA 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.

...