Versions Compared

Old Version 46

changes.mady.by.user Lukas Schwalvenberg

Saved on

compared with

New Version 47

changes.mady.by.user Lukas Schwalvenberg

Saved on

Key

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


...

Table of Contents
maxLevel2

...

Deck
idTabelle


Card
label22.00-22.05


ID

Report

Availability of the reports per country, company type or period type

Representative VAT

group member

Consolidated VAT

group member

VAT group

member

Company

Subdivision

Standalone

Preliminary

Declaration

Annual

Declaration

SPPDE

Other

countries

0Annual VAT return




2Variance analysis VAT values



4Reporting values of all VAT group members per tax code








Reporting values of all companies by mapped tax codes




6Vat validation


7Reporting relevant adjustments of the year


25VAT Returns of the past 12 months




26Special prepayment overview







28Variance analysis VAT payment/refund



31Deviation between current month and average of 12 previous months




35Foreign Tax codes



36Reporting values of all companies by tax codes




38Value transfer from preliminary into annual VAT return



39Clearing document




40Total annual value of the preliminary VAT returns within the VAT group








41Comparison annual VAT return/sum of preliminary VAT returns




45Overview prepayment / payable







46Preliminary / Annual VAT return in detail


47Year summary of the VAT returns


48Month overview



49Plausibility of the tax amounts in the VAT report



50Finance plan overview



Teilweise
51All reporting values of the year


52Data base for bookkeeping voucher





Card
label22.06


ID

Report

Verfügbarkeit der Reports pro Land, Gesellschafts- und Periodentyp
OTZOTOGTGSTAVAJESVZDEAusland
0Annual VAT return




2Variance analysis VAT values



4Reporting values of all companies by tax codes







6Vat validation


7Reporting relevant adjustments of the year


25VAT Returns of the past 12 months




26Special prepayment overview







28Variance analysis VAT payment/refund



31Deviation between current month and average of 12 previous months




35Foreign Tax codes



36Reporting values of all companies by tax codes




38Value transfer from preliminary into annual VAT return



39Clearing document




40Total annual value of the preliminary VAT returns within the VAT group








41Comparison annual VAT return/sum of preliminary VAT returns




45Overview prepayment / payable







46Preliminary / Annual VAT return in detail


47Year summary of the VAT returns


48Month overview



49Plausibility of the tax amounts in the VAT report



50Finance plan overview



It depends
51All reporting values of the year


52Data base for bookkeeping voucher





Card
labelsince 22.07


ID

Report

Verfügbarkeit der Reports pro Land, Gesellschafts- und Periodentyp
OTZOTOGTGSTAVAJESVZDEAusland
0Annual VAT return




1Resubmissions of the year


2Variance analysis VAT values



4Reporting values of all companies by tax codes







6Vat validation


7Reporting relevant adjustments of the year


25VAT Returns of the past 12 months




26Special prepayment overview







28Variance analysis VAT payment/refund



31Deviation between current month and average of 12 previous months




35Foreign Tax codes



36Reporting values of all companies by tax codes




38Value transfer from preliminary into annual VAT return



39Clearing document




40Total annual value of the preliminary VAT returns within the VAT group








41Comparison annual VAT return/sum of preliminary VAT returns




45Overview prepayment / payable







46Preliminary / Annual VAT return in detail


47Year summary of the VAT returns


48Month overview



49Plausibility of the tax amounts in the VAT report



50Finance plan overview



Teilweise
51All reporting values of the year


52Data base for bookkeeping voucher





...

If a yearly overview is desired in addition to this comparison, see the report "Deviation between current month and average of 12 previous months".

Tip
titleGood to know!
Deviation analysis is important to ensure the control of sales volumes. Based on the development of the tax base, it is possible to identify wrong entries. In addition, the report can be used to document business development. In addition to the above-mentioned information, the report contains a further worksheet with VAT group data. 

...

Deck
idVat validation


Card
label22.00-22.12

In the VAT validation, data is taken from the return, RFUMSV10 and RFBILA. The fields of the return are listed in the header of the validation, each field is in a separate column. The fields are sorted by tax and input tax. For each field, the tax codes that are mapped to this field are also displayed.

In the first column, all accounts that appear in RFUMSV10 are listed below each other, sorted by account type.

In the table formed from this, the values from RFUMSV10 are entered that were posted to the respective account and posted to one of the tax codes that is mapped in the respective field of the return. 

Between the VAT and input tax columns, a subtotal of the RFUMSV10 values per account is calculated and then reconciled with the value of the account on the RFBILA. The resulting difference, if it is not 0€, must be explained by the input tax side. After the input tax entries, a subtotal of the RFUMSV10 values for the input tax side is calculated again and reconciled with the previous difference. The value in the last column should then be 0€. If this is not the case, the difference must be checked.

Below the account lines there is also a block in which totals and deviations are calculated. At this point, the totals per declaration field are taken from RFUMSV10 and then compared with the declaration. If there is a difference here, it must also be explained. These differences can result from manual adjustments, reconciliation adjustments in VAT@GTC or posted resubmissions. If there is still a difference after including these adjustments, it should be checked.

A spreadsheet is always created for the current month and a spreadsheet for the quarter.


Card
labelsince 22.13-22.16

In the VAT validation, data is taken from the return, RFUMSV10 and RFBILA. The fields of the return are listed in the header of the validation. The fields are sorted by tax and input tax. If more than one tax code is mapped to a field, there is one column per tax code for this field and one column for the field total, in which all tax codes are added together. 

In the first column, all accounts that appear in RFUMSV10 are listed below each other, sorted by account type. For each account type there is also a totals row in bold type. In addition, all accounts of the same type are grouped in such a way that they can be conveniently shown and hidden in Excel in order to switch between a clearer and a detailed view of the validation.

In the table formed from this, the values from RFUMSV10 are entered that were posted to the respective account and posted to one of the tax codes that is mapped in the respective field of the return. 

Between the VAT and input tax columns, a subtotal of the RFUMSV10 values per account is calculated and then reconciled with the value of the account on the RFBILA. The resulting difference, if it is not 0€, must be explained by the input tax side. After the input tax entries, a subtotal of the RFUMSV10 values for the input tax side is calculated again and reconciled with the previous difference. The value in the last column should then be 0€. If this is not the case, these differences are highlighted in yellow and the difference must be checked.

Below the account rows there is also another block in which totals and deviations are calculated. At this point, the totals per message field are taken from RFUMSV10 and then compared with the message. If there is a difference here, it must also be explained. These differences can be caused by manual adjustments, by reconciliation adjustments in VAT@GTC or by posted resubmissions. If there is still a difference after including these adjustments, they are also marked yellow and should also be checked.

A spreadsheet is always created for the current month and a spreadsheet for the quarter. If the reporting period of the company is neither monthly nor quarterly, another spreadsheet is also offered for the reporting period if the user is in the reporting period.


Card
labelsince 22.17

In the VAT validation, data is taken from the return, RFUMSV10 and RFBILA. The fields of the return are listed in the header of the validation. The fields are sorted by tax and input tax. If more than one tax code is mapped to a field, there is one column per tax code for this field and one column for the field total, in which all tax codes are added together. The columns are grouped in Excel in such a way that the columns can be shown or hidden per tax code.

In the first column, all accounts that appear in RFUMSV10 are listed below each other, sorted by account type. For each account type there is also a totals row in bold type. In addition, all accounts of the same type are grouped in such a way that they can be conveniently shown and hidden in Excel.

When the report is called up for the first time, the above-mentioned grouped columns and rows are collapsed so that a rough overview is initially presented. The function of showing or hiding can be used to switch to the complete detailed view by using the function to expand all columns or all rows. In addition, individual fields or account types can be expanded, especially if a discrepancy that can be seen in the overview is to be examined in more detail subsequently.

In the table formed from this, the values from RFUMSV10 are entered that were posted to the respective account and posted to one of the tax codes that is mapped in the respective field of the return. 

Between the VAT and input tax columns, a subtotal of the RFUMSV10 values per account is calculated and then reconciled with the value of the account on the RFBILA. The resulting difference, if it is not 0€, must be explained by the input tax side. After the input tax entries, a subtotal of the RFUMSV10 values for the input tax side is calculated again and reconciled with the previous difference. The value in the last column should then be 0€. If this is not the case, these differences are highlighted in yellow and the difference must be checked.

Below the account rows there is also another block in which totals and deviations are calculated. At this point, the totals per message field are taken from RFUMSV10 and then compared with the message. If there is a difference here, it must also be explained. These differences can be caused by manual adjustments, by reconciliation adjustments in VAT@GTC or by posted resubmissions. If there is still a difference after including these adjustments, they are also marked yellow and should also be checked.

A spreadsheet is always created for the current month and a spreadsheet for the quarter. If the reporting period of the company is neither monthly nor quarterly, another spreadsheet is also offered for the reporting period if the user is in the reporting period.


Tip
titleGood to know

This report is particularly helpful for a detailed evaluation of reconciliations 3-6.


Tip
titleGood to know

The assessment bases, in particular of the input tax values in the line "turnover declared in preliminary (or annual) declaration (calculated values are marked in bold italics)" are calculated using the tax values and the tax rate. 


...

All companies are listed in this report. Each VAT group has its own spreadsheet, and another spreadsheet summarises all the standalones. This report is similar to the Financial Plan Overview report, but also offers a data comparison. For this purpose, the current month is compared with the previous month and the difference is shown. Likewise, the current month is compared with the same month of the previous year and this difference is also documented.

Deviation between current month and average of 12 previous months

In this report, the reporting values of the last 12 periods are shown with a mean value deviation and configurable threshold value, divided into assessment basis and tax. If the threshold value for a field is exceeded, this is highlighted in red.

...