Release Notes 20.XX.00

Situation:

After you have copied transaction data, data in the surface and the database may differ due to the calculation.

Solution:

After the transaction data copy, the common storage mechanism is executed to keep the data of the surface and the database the same.

Situation:

Neither reports "Details for Report DT II" nor "Mass Export GTC-IDs, all" nor dialogue "Others" can be opened,
- if there is a converted unit to the current unit in the prior period or true-up period and
- if the user has no authorization for the converted unit.
Additionally, values are not taken from the true-up period (if it exists) but always from the prior period.

Solution:

The authorization for the converted unit is not needed as a pre-condition for opening the reports or dialogue "Others". When a true-up period exists, the values for the converted unit are taken from there.

Situation:

At some customers dialogue "B/S comparison" takes quite a long time.
Loading the dialogue "B/S comparison" takes an unusually long time with large balance sheet structures and/or many difference columns.

Solution:

Database requests are accelerated by an additional database index.

Situation:

For toolbox line 18, neither the trade tax apportionment nor the local tax can be calculated if the trade tax apportionment is activated in the master data, because in this case the field is closed.

Solution:

If the trade tax levy is activated, the field is opened. Thus, the behavior with assessment is identical to the behavior without assessment.

Situation:

Dialogue B/S comparison is not shown in the print view of a snapshot.
If an error occurs during creation of a snapshot, an empty snapshot (without underlying data) is created.

Solution:

Dialogue B/S comparison is correctly shown in the print view of a snapshot.
If an error occurs during creation of a snapshot, the snapshot is not created.

Situation:

In dialogue "(Sub-) Group Import" milestones are only closed for tax group members and standalone unites. Milestones of intermediate parents and tax payers of groups remain open.

Solution:

With the option "reset milestones" of an interface structure milestones are reset at the start of the import. This is done in a top-down manner for all group members that occur in the import. The import itself is done bottom-up (independent from the order of rows in a csv file). Current taxes including TB transfer are stored even when the import contains no tax data. In this way milestones will be closed for tax payers as well.

Situation:

In a summary period tax rates of dialoges "Tax losses carry forward" and "Current taxes" (rows 18 and 19.10) are added from the first and adjustment level periods.

Solution:

Tax rates are not added in a summary period, but taken from the first level period.

Situation:

The configuration of a file path in interface structures may use placeholders. There is no placeholder for additional company codes.

Solution:

The placeholder {BUKRS1} may be used for the first additional company code. The placeholder {BUKRS} is replaced by the sequence of all additional company codes (separated by an underscore '_') .

Situation:

Master data changes are documented in the GTC in the so-called changelog. For user roles, the recording of changes does not work correctly.

Solution:

The changelog Excel file now includes several tabs / spreadsheets containing information on master data changes, if applicable.

Changes to or the creation of user roles are shown in a separate tab of the user changelog.
In addition, changes to administration and naming information (Master Data / Administration / Other) are shown in separate tabs.

Situation:

The international configuration of the GTC is currently being used.

If the country assignment is now changed in the master data of the companies, a system error is displayed.

Solution:

Under the abovementioned condition, no system error message is displayed and the data can be saved successfully.

Situation:

Due to a change of period, it can happen that no company is selected in the dropdown for "Company".

If the user now navigates to the master data area and executes one of the following actions, this results in system error messages:
* the creation of a new company,
* calling up the sub-dialogue "Manage columns" in the dialogue "Group balance sheet" and
* calling up the dialogue "Import mapping".

Solution:

As the selection of a company is not necessary in the abovementioned contexts, the error messages are prevented in these cases. The actions can be executed without errors.

Situation:

When milestones are reset, they afterwards have either the status "in process" or „data ok“. For the user, it is not always clear what he or she must then do.

Solution:

The milestones of the single unit are always reset from the status „closed" to the status " in process " when they are reset. All activities that are necessary to close the milestone must be run through again.

Situation:

The user has calculated the current taxes and has transferred the proposed value for the "tax balance corrections" into the calculation. The milestone for current taxes changes to the status "data ok".

Now new findings are gathered in the balance sheet comparison, the proposed value for the "tax balance corrections" changes. However, since the milestone for current taxes is already in status "data ok", the user does not check his entries in current taxes again, but closes the milestone.

The proposed values for the "Tax balance corrections" ultimately differ in the current taxes from the values entered.

Solution:

If the milestone "Current taxes" is in the status "data ok" and the balance sheet comparison is now saved, the mentioned milestone is reset to status "in process". The "Current taxes" dialogue must therefore be saved again afterwards.

If the proposed values in the dialogue current taxes do not match the input values, a warning will also be displayed indicating this circumstance. Since this is only a warning and not an error message, the milestone can be closed despite this message.

Situation:

Specifying a "Subposition/Partner" in the interface structure has no effect.

Solution:

In the standard import (xls, csv, txt) and in the Remote function Call (RfC), the "Subposition/Partner" are now also evaluated and processed in the import mapping.

Situation:

The user who is logged in can see the reports of other users in the report repository, as long as the ID of the other user starts with the same numeric digits.

Solution:

Only the reports of the logged-in user are displayed.

Situation:

Depending on the complexity of the balance sheet structure, it takes a little longer to load the "B/S comparison" dialogue. However, there are imports that do not affect the "B/S comparison". Nevertheless, after saving an import, the user is redirected directly to this dialogue.

Solution:

After saving the application remains in the import dialogue. Additionally the user guidance has been improved. Only relevant buttons are displayed during the import process.

Situation:

There is no separate authorisation for the "Master data / Dialogue configuration" dialogue, the dialogue is controlled with the "System administrator" authorisation. In order to be able to configure the display of the dialogues, the user therefore always needs administration rights.

Solution:

The dialogue "Master Data / Dialogue Configuration" is associated with a new, separate authorisation object "Master Data: Dialogues" with the properties "Read" and "Edit".

With the GTC update, all users who previously had the authorisation "System Administrator" assigned via a role also receive the authorisation "Master Data: Dialogues".

Action is only required if the two authorisations mentioned are no longer to be combined in one role. In this case, the one role must be split into two roles and reassigned to the GTC users.

Situation:

Dialogue Interfaces does not have a dedicated permission object. The user needs the permission "System Administrator", although usually interfaces are not maintained by system administrators.

Solution:

The dialogues "Master data / Interfaces / Configuration" und "Master data / Interfaces / Structure" are associated with a new permission object "Master Data: Interfaces" with "Read" und "Edit" options. Initially all users with "System Administrator" permission are also assigned the permission "Master Data: Interfaces".

Situation:

In a flexible RFC import with default mapping and configured UnitID column in the interface structure, the returned UnitID is ignored and overwritten by the currently selected company.

Solution:

The UnitID, if the parameter is specified in the interface structure, is now used to validate the RFC import.

Situation:
The calculation of the proposed values in lines 2.0 and 2.1 of the foreign current taxes (toolbox) does not take into account the following effects from the dialogue "Others": „Temporary differences ( P&L)" and „Temporary differences (OCI)"

Solution:
The calculation of the proposed values in lines 2.0 and 2.1 of the foreign current taxes (toolbox) now also includes the effects from the lines „Temporary differences (P&L) and "Temporary differences (OCI)" of the dialogue "Others".

As the values are deferred taxes, they are divided by the deferred tax rate in the toolbox to provide the underlying gross difference. The calculated difference then negatively enters the proposed value in lines 2.0 and 2.1.

Situation:

Dialogue Interfaces does not have a dedicated permission object. The user needs the permission "System Administrator", although usually interfaces are not maintained by system administrators.

Solution:

The dialogues "Master data / Interfaces / Configuration" und "Master data / Interfaces / Structure" are associated with a new permission object "Master Data: Interfaces" with "Read" und "Edit" options.

With the GTC update, all users who previously had the authorisation "System Administrator" assigned via a role also receive the authorisation "Master Data: Interfaces".

Action is only required if the two authorisations mentioned are no longer to be combined in one role. In this case, the one role must be split into two roles and reassigned to the GTC users.

A configuration file in the GTC contains "forbidden" passwords. The user is not allowed to use one of these passwords.

Situation:

Login attempts with the superuser account are not subject to any restrictions, for example, the number of login attempts is not restricted.

Solution:

The superuser account is subject to the same policies as other user accounts. Entering the wrong password several times will result in the account being blocked according to the password configuration.

Situation:

In the import dialog, the user must first select the format of the interface before the actual interface can be selected. The handling is inconvenient if different formats are configured in the GTC.

Solution:

In the import dialog, only one selection list with all interfaces available to the company is displayed. The company-specific interfaces are listed first, followed by the standard interfaces.

Situation:

The values from the dialogue "Data transfer" cannot be exported via technical IDs.

Solution:

The values from the dialogue "Data transfer" can be exported via technical IDs. The documentation for this can be found in the GTC manual (https://docs.amana.de/x/c4kpAw). This also allows to use the values in the validation.

Situation:

Before changes have been made:
The tax rate reconciliation effects that are based on the new toolbox features were calculated with the wrong tax rates and the position of the effect within the tax rate reconciliation was wrong.

Solution:

Required changes that have been performed:
An adjustment has been made to use the correct tax rates based on the master data and the position of the tax rate reconciliation effect has ben fixed.

1300941

GewSt 1A

Situation:

The calculation of line 40a column Total in the dialog GewSt 1A is calculated incorrectly. It is calculated at 100% from the Own column for KapGes, but should instead be calculated at 50% as for PersGes.

Solution:

The row 40a column Total in the GewSt 1A dialog is calculated with 50% of the Own column as for PersGes.

Situation:

If no additional tax was stored under the "Countries" dialogue or in the company master data, the TRR effect for the line "Effect of tax loss carry forward (corporate tax)" was calculated as a total of 0.00.

In addition, the group tax rate and not the company tax rate was used in the calculation. This resulted in the TRR not adding up.

Solution:

The calculation of the TRR line "Effect of tax loss carry forward (corporate tax)" was adjusted. If no additional tax is maintained, the TRR effect is calculated based on the corporate income tax rate.

In addition, the calculation of the line is now based on the corporate tax rate.

1300944

Situation:

Since the 2017 assessment period, the "End of period" is relevant for the calculation. Nevertheless, it is possible to change the end of period without resetting the milestones from "finsihed"/"checked" to "in process".

Solution:

If changes are made in the "End of period" field and the period is saved, the milestones are reset. A warning is displayed to the user before this happens.

Situation:

SAP function modules may require special RFC configuration parameters depending from the custom-side infrastructure. These parameters could not be specified in "Master data / Administration / Connection parameters". For example, an infrastructure with load balancing could not be specified.

Solution:

Additional RFC configuration parameters can be specified as key/value pairs in "Parameter 4" of "Master data / Administration / Connection parameters". For load balancing values for jco.client.r3name, jco.client.mshost, jco.client.msserv and jco.client.group can be specified.

Interfaces

Import

Situation:

SAP function modules may require special RFC configuration parameters depending from the custom-side infrastructure. These parameters could not be specified in "Master data / Administration / Connection parameters". For example, an encoded communication via SNC could not be specified.

Solution:

Additional RFC configuration parameters can be specified as key/value pairs in "Parameter 4" of "Master data / Administration / Connection parameters". For Secure Network Communications (SNC) values for jco.client.snc_mode, jco.client.snc_sso, jco.client.snc_qop, jco.client.snc_partnername, jco.client.snc_myname and jco.client.snc_lib can be specified.

Interfaces - Mapping

Import

Situation:

In certain configurations the enhanced import has errors:
- Import with "Import values as comments" and a mapping into dialog "Tax liabilities"
- Comments that are created during the import are aggregated for each target field
- Mapping into dialog "Anlage AESt", when the target column (foreign branch) is calculated from multiple column values
- Milestone robotic is missing in "Import subgroup"
- The enhanced import into dialog "Rollforward LCF" uses some technical IDs which are different from those of the ordinary import.
- csv import with a tab as delimiter does not work.

Solution:

- Import with "Import values as comments" and a mapping into dialog "Tax liabilities" works correctly.
- A comment is created for each imported value.
- Target dialog, line and column may be calculated from multiple column values.
- "Import subgroup" supports the milestone robotic.
- The enhanced and the ordinary import into dialog "Rollforward LCF" use the same technical IDs.
- csv import with a tab as delimiter works correctly.

Situation:

Requests do not always use CSRF tokens.

Solution:

CSRF tokens are used and validated.

Situation:

In a special master data constellation, the OCI values transferred from the summary dialogue are displayed as 0.00 in the dialogue "IAS 34".

Solution:

The OCI values from the summary dialogue are correctly taken over into the dialogue "IAS 34".

The closing balances 'Loss carryforwards', 'Tax credits' and 'Valuation allowance - losses' of the previous period are equal to the opening balances of the subsequent period.

Situation:

If a special flag for the international environment is active, the "Basic Data"-dialogue remains empty and no company-specific tax rates can be defined.

Solution:
The dialogue is shown correctly.

MVB - IFRS

Situation:

In the MVB dialog columns for differences not affecting net income are displayed.

Solution:

From a business point of view, OCI differences are not necessary in the MVB dialog. Therefore, the columns are now hidden and no columns for differences not affecting net income can be added.

Situation:

Authorization for "Tax Reporting - Read" (instead of "Tax Questionnaire Reports - Read") enables access to "Own reports".
The assignment of an "Edit" role to a report is not correctly evaluated.

Solution:

Visibility of "Own reports" is exclusively regulated via authorization for "Tax Questionnaire Reports".
The assignment of an "Edit" role to a report works correctly.

Situation

In the Tax Reports dialog, some additional information such as "Reporting Dimension" are missing in the 'Units' report.

Solution:

In the Tax Reports dialog, the missing additional information are displayed again in the 'Units' report.

Situation:

There are no technical IDs for import and export into columns "FX adjustments" and "Hyperinflation adjustments" of dialog "Rollforward LCF".

Solution:

Import and export of values for "FX adjustments" and "Hyperinflation adjustments" (dialog "Rollforward LCF") are enabled by new technical IDs. The columns are also shown in report "Mass Export GTC-IDs, all".

Basis Data

Situation:

The field "Local tax rate" is not editable, if the user were assigned access rights for "Basisdata" by means of "Country" and "Reporting Dimension".

Solution:

Also if the user are assigned access rights for "Basisdata" by means of "Country" and "Reporting Dimension", the field "Local tax rate" is editable.

Situation:

Robotics in bulk import cannot close the "deferred taxes" milestone if an import is included in the balance sheet comparison. 

Closing the milestone "Deferred Taxes" also does not work if the checkbox for the transfer of tax rates in the loss carry forward dialog is deactivated.

Solution:

If the corresponding checkboxes are set in the interface structure, robotics will close the milestones after a bulk import up to the milestone "TRR".

Situation:

There are two situations, where it is not possible to import values into difference columns of the balance sheet:

1. The unit is newly created and "B/S comparison" has not yet been entered.
2. The period was created without copy of transaction data and "B/S comparison"of the untit has not yet been entered.

Solution:

When creating a new unit as well as when copying a period without transaction data, all difference columns of the balance sheet are created and stored with value 0.

A migration job of the current GTC version creates missing difference columns for all units in active and open periods.

Situation:

Having called a large number of  "Own Reports" or having stored many/large files in the database (e.g. attachments in comments) the database system might run into resource-related problems: GTC then steadily slows down or Oracle shows the error message "ORA-01000: maximum open cursors exceeded").

Solution:

Database resources are always closed so that the error does no longer occur.

Situation:

Until now, own reports can only be executed in the reporting area. 

Solution:

Own reports can now be executed directly in company dialogs via the button "Create report ...".

For this purpose, the report is assigned to one or more dialogs and tax forms in the "Own Reports" dialog.

The assigned reports can only be executed if the user has the appropriate rights.

Situation:

With activated BRG 1300882 it may takes several minutes to build the status dialog for a unit with many dependent units.

The visibility of Elster milestones for dependent units might not be completely unit-specific.

Solution:

The implementation is based on an improved algorithm for the retrieval of data for dependent units. It minimizes the number of database queries. This significantly improves the loading tim of the status dialog.

The visibility of Elster milestones (only relevant für german companies) for dependent units is completely unit-specific.

Situation:

When creating a period with accounting standard "Commercial law" based on an IFRS period (incl. transaction data), then not all values from dialog Rollforward LCF (e.g.: "Other adjustments prior period") are copied. Revaluations in Loss Carry Forward are not copied either.

Solution:

All respective values are copied.

Situation:

If the validation milestone is reset after a successful validation, it is possible to complete the validation successfully without having to import again.

Solution:

Resetting the validation milestone resets the process completely, so that a further import is necessary.

Situation:

In application setups with more than 2000 companies and Microsoft SQL Server as database management system no period with a tax form version > 2015 can be created based on the standard period.

Solution:

Database statements are internally transformed so that periods can be created in SQL Server as well.

Situation:

The milestone Deferred taxes can be closed in commercial law periods previous to the milestone Current taxes. This may result in incorrect calculation of the loss carryforwards.

Solution:

Also in commercial law periods, the milestone Current Taxes must first be set to closed before the milestone Deferred Taxes can change to the status plausible and then closed.

Situation:

The mapping engine cannot import into all GTC dialogs.

Solution:

The mapping engine supports the import of values via comments, the import into dialogs "Tax liabilities", "Others", "LCF", "Rollforward LCF", "Anlage AESt" as well as into difference columns of balancesheet issues. Furthermore, the mapping engine is integrated into group imports.

Situation:

The function 'Copy transaction data' in the single company area has been revised.

Solution:

The sequence of control elements was adjusted, the English translations were completed and explanations were added.

Situation:

In the dialog 'Rollforward LCF' the value 'Amount prior period' is not taken from the previous period when the BP module is activated.This behavior occurs if the target period is a reporting period and no BP period is assigned to the previous period.

Solution:

If no BP period has been assigned to the previous period of a reporting period, previous year values are taken from this period. If a BP period is assigned to the previous period, the previous period values are taken from this period.

Report DT

Situation:

In the dialog "Report DT" (View = Normal) values from companies that are not within the group structure and have activated "Deliver deferred taxes" in the master data are missing. This causes the validation to fail.

Solution:

In the dialog "Report DT" (View = Normal) values from all companies within the group structure are shown, which have activated "Deliver deferred taxes" in the master data. This causes the validation to succeed.

Situation:

Previously, the toolbox did not include the options for withholding taxes and tax credits. It was also not possible to apply different tax rates to certain portions of taxable income.

Solution:

By creating explicit areas for these three issues, it would be possible to apply different tax rates, tax credits and withholding taxes. The relevant effects are linked into the TRR.

Situation:

When resetting the milestones, the status and name of the executing user in the milestone is changed, but not the timestamp.

Lösung:

When resetting the milestones, the timestamp is also automatically updated.

FAQ

Situation:

After downloading a file attachment in the FAQ section, the page does not react anymore, e.g. when selecting another main category.

Solution:

After downloading a file attachment, the user can continue to work in the same dialog without having to reload the page.

Situation:

When importing payments in the Compliance module, an empty import log is displayed and nothing is saved. Nevertheless, a successful import message was displayed.

Solution:

The import is working properly again. If there are not enough columns to create a payment, the user will receive an error message.

Situation:

In the Toolbox, depending on the configuration, there is the possibility to add your own lines within a category and also to delete them again.

However, the deleting is independent of period, company, country or milestone status. Therefore, it is possible that the Toolbox displays different information in periods that have already been closed.

Solution:

Toolbox lines can now only be deleted if no values other than 0.00 are stored for this line in any period.

Situation:

When using an import structure with file path configuration the import file cannot be moved after the import.

Solution:

After the import the import file is released so that it can be moved.

Situation:

When adding roles to a user, the user receives every time a warning message "You just modified your details ...", even if no changes have been made there at all.

Solution:

The warning message "You just modified your details ..." is now only displayed if user information has actually been edited and not yet saved.

Situation:

It is not possible to download the template of an own report without superuser permissions.

Solution:

Any user who can open the edit view of the own report can also download the attached template.

Situation:

If a tax rate changes between two periods, the corresponding effect on deferred taxes is shown once in the TRR and in the dialog Others. However, with different signs.

Solution:

In case of a tax rate change between two periods, the corresponding effect on deferred taxes is shown once in TRR and in the Others dialog with the same sign.

Situation:

The milestone for current taxes can be closed by clicking on the milestone without the calculation having been marked as valid before.

Solution:

Only when the milestone for current taxes has reached the status "data ok" can it be set to "closed" by clicking on it.

Situation:

Roles that contain an "AllObjects" permission can be assigned by the user administrator.

Solution:

The user administrator itself must have the "AllObjects" permission to assign this role to a user.

Situation:

After a login via Single Sign On (SSO) the menu bar is closed.
The login link on the logout page refers to the standard login screen (user name/password); no SSO is automatically done.

Solution:

The menu bar is also displayed expanded after a login with SSO.
The login link on the logout page refers directly to the SSO login, so an automatic login is automatically done.

Import

Situation:

With an enhanced import from STB, profit and loss values are temporarily stored in the GTC. With a subsequent import of the STB values into the GTC they are displayed in the import log. However, they remain after a change of company.

Solution:

With each new access to the import dialog, previous import logs are deleted.

Situation:

In the dialog B/S comparison, a flag displays two blocks for other issues, in which rows of the dialog Others can be selected. However, some rows are missing here.

Solution:

All editable lines of the dialog Others are available for selection.

Situation:

The calculation of the proposed values in lines 2.0 and 2.1 of the foreign current taxes (toolbox) does not take into account the following effects from the dialogue "Others": „Temporary differences ( P&L)" and „Temporary differences (OCI)"

Solution:

The calculation of the proposed values in lines 2.0 and 2.1 of the foreign current taxes (toolbox) now also includes the effects from the lines „Temporary differences (P&L) and "Temporary differences (OCI)" of the dialogue "Others". The values are added to the proposed value.

Situation:

Transaction data from dialog MVB are copied in a period copy even when the checkbox "Tax calculation with transaction data" is not activated.

Solution:

Transaction data are only copied when the checkbox "Tax calculation with transaction data" is activated.

HB/StB

Situation:

An automatic closing of the milestone current taxes is not always possible.

Solution:

It is now also possible for those companies that use a local GAAP balance sheet (the dialogue HB/StB) in the GTC in addition to the IFRS balance sheet, to automatically close the milestone current taxes via the GTC robot.

TRR

Situation:

With the extension of the company-specific tax rates (patch 13008672), the line "Taxes foreign countries" in the TRR dialog was adjusted, among others. The value displayed there is too large by a factor of 100 because the tax rate was calculated incorrectly.

Solution:

The tax rate for additional taxes is now loaded correctly for calculation and the presentation in the TRR dialog is shown correctly.

Situation:
In the tax planning of a foreign company the following behavior occurs. If a higher value is entered in line 16 "Utilisation of tax losses" than in line 14 "Taxable income for corporate tax", this leads to an incorrect utilisation of losses in line 29 "Corporate tax loss / use of TLCF of the current year".

Solution:
There is now a proposed value for line 16. This value is calculated from the minimum of line 31 and (line 14 + line 15), whereby the proposed value cannot become negative.

If a negative income is calculated in line 17 because, for example, the default value from line 16 has not been applied, the user will receive a warning message pointing out this fact.

Situation:

When copying transaction data, currency conversion is executed even if the currency is the same, due to different exchange rates. This is wrong.

Solution:

Currency conversion is only executed if both the currencies and the exchange rates are different.

Situation:

1. Issues from the (special) investment income dialog cannot be exported
2. The added fields in the § 8b KStG dialog in VZ 2019 cannot be exported

Solution:

1. Issues from the (special) investment income dialog can be exported
2. The added fields in the § 8b KStG dialog in VZ 2019 can be exported

Situation:

Own reports of type "Export" can only be edited with system administrator privileges if the report was created by another user.

Solution:

Reports of type "Export" are now treated like reports of type "Standard". Access to these reports can be restricted by using the general rights for the "Own Reports" area or by using the role assignment in the report itself.

Situation:

The calculation for line 83, Net Profit (CH) subtracts the value from line 82.3 and line 11 of the Investment Deduction (CH) takes the value from Net Profit (CH) line 82.3.

Solution:

Line 83, Net Income (CH) is calculated from line 79, minus line 80, plus line 82.2 and minus line 82.

Line 11, Participation Deduction (CH) now feeds from line 3, Federal Tax (CH).

Situation:

The effects from the lines „Change in consolidation (cur. year)" in the dialog Others are not processed correctly in TRR for a foreign company.

The value of the line "Additions/Disposals loss carried forward corporate tax" is displayed twice in the TRR. The value of the line "Additions/Disposals loss carried forward local tax" is not shown at all in TRR.

Solution:

The TRR line "Deviations due to local tax" only contains the other line "Additions/Disposals loss carried forward local tax".

Interfaces

Situation:

If problems occur when establishing an RFC connection to an SAP system, three attempts are always made in sequence. If the connection could not be established due to an incorrect password in the connection configuration of GTC, this can lead to the SAP account being locked.

Solution:

Only one attempt is made to establish a connection to the SAP system per each import.

Situation:

When the permissions of one user are copied to another, all roles containing the "Family Office" object are filtered out.

Solution:

If the user who assigns permissions has a Family Office permission himself, all roles are considered when copying roles.

If the user who assigns permissions does not have a Family Office permission himself/herself, only those roles that do not contain the "Family Office" object are considered when copying roles.

Situation:

A compilation error occurs with local balance sheets, which prevents the display of the CoA Company dialog. Furthermore, there were some layout errors in the headings of this dialog.

Solution:

The compilation error was fixed and the layout was revised.

Usability

Correction of English translations

Situation:

For some configurations the amount at the end of the previous period in dialog "Tax liabilities" is not completely transferred into the current period.

Solution:

The amount at the end of the previous period is completely transferred into the current period for all client configurations.

Situation:

Currently, it is not possible to set the milestone to the status "plausible" or close it in planning periods when the tax audit module is activated.

Solution:

The milestone can be set to the status "plausible" or closed again in planning periods.

Situation:

The Excel and print views in the dialog MVB - IFRS or MVB - STB were not displayed correctly. The heading columns have been moved.

Solution:

The Excel and print views in the dialog MVB - IFRS or MVB - STB are displayed correctly. The headings are displayed completely.

Situation:

With the Import Interface "Direct import" you can import data from a transfer table, which have been saved there before via web service.

Solution:

Now it is not only possible to import web service data, but also data provided by a database command. This so-called StoredProcedure can be named in the interface structure and is then called up first when importing the balance sheet.

Situation:

When saving an import into the TIMPORT table, all values for the importing period/unit are first deleted from the table. If you only import into other GTC dialogs, the entries in the TIMPORT table are retained.

If a manual adjustment has been made to an entry in the TIMPORT table, these values are not transferred during a new import.

Solution:

In the interface structure under "Data transfer: Reset columns", you can explicitly specify whether all import values or all manual adjustments of the TIMPORT table should be reset (checkbox "Import value" or "Manual adjustment").

The resetting of the values will also be done if the import is done exclusively into other GTC dialogs. If both checkboxes are activated and both values are empty after the import (i.e.: no reimport for the key), the entire entry is deleted from the TIMPORT table.

The interface for the import of tax audit data has been revised.
The import supports the addition, change and deletion of issues. Individual attributes (e.g. "status") of imported issues can still be edited in the GTC. The GTC user can see which issues have been imported.
To simplify the integration of this interface, log outputs have been added.

GewSt 1 A

(german tax law)

Situation:

If a period is copied from tax form 2017 to tax form 2019, the value from line 34 GewSt1A (tax form 2017) is copied to line 34 GewSt1A (tax form 2019). This is not correct, as line 34 of tax form 2017 is now line 33 in tax form 2019.

Solution:

Line 34 GewSt1A (tax form 2017) is no longer copied to line 34 GewSt1A (tax form 2019). Line 33 GewSt1A (tax form 2019) is calculated.

§8b KStG

Situation:
The structure of the §8b issues in the tax form 2019 is different from previous years. The import template and the standard report for the issues have not yet been adjusted accordingly.

Solution:
A new import template is now defined for tax form 2019, the import routine has been adapted accordingly.
The standard report for §8b-issues is also adapted to the new structure. The report can be accessed directly in the overview for §8b issues and replaces the special reports "8b-Report for indirect investments" and "8b-Report for all investments".

Situation:

In the Swiss tax calculation, the canton "Basel Stadt" was previously given special treatment, as the tax calculation was based on a yield-dependent tax rate.

Solution:

With BRG 1300881 the standard calculation is also used for the canton "Basel Stadt". For this purpose, the currently valid tax rate of 6.5% must be entered in the tax rate import file in the column "Total - Level 1" of the municipalities in the canton of "Basel Stadt".

Situation:

If the language in the GTC is set to "english", the dialog "ERiC transfer" cannot be called.

Solution:

The missing translations were added, so that the dialog "ERiC transfer" can be used even if the language is set to "english".

Situation:

Some labels in the international context are only available in German language or are not translated comprehensibly.

Solution:

The translations were added or revised.

Company / Deferred Taxes

Situation:

The tax loss carryforwards can be split between different lines - depending on their expiration. However, it is not directly apparent in which specific year the loss will then expire.

Solution:

In addition to the number of year until expiry, the actual year is now also displayed in the respective rows.

Tax liabilities

Situation:

In the dialog Tax liabilities there is a fixed link between current taxes and this dialog: In the case of standalone companies, for example, line 49.1 goes into the second column of the dialog as tax expense/income. Tax group members do not have their own tax expense, which is why there is no link there.
If a company now changes from a tax group member to a standalone company, the 0.00 in the last column of the previous period is not transferred as the opening balance. Instead, it is calculated again using the settings for the current period (that is, standalone) and then transferred. As a result, the company suddenly has an opening balance.

Solution:

The opening balance in the current period corresponds to the closing balance of the previous period.

Situation:

If several users simultaneously retrieve data from different SAP systems, error messages may occur sporadically (invalid user/password).

Solution:
The SAP interface has been enhanced so that simultaneous data retrievals are processed correctly.

Situation:

The list of available Web Services and the list of all users can be retrieved by all logged-in users if the URL is entered directly.

Solution:
When retrieving the list, the system checks whether the user has the necessary authorizations.

Situation:

The master data of companies, that are only relevant when using German tax law, are also displayed for non-German companies.

Some translations are also missing.

Solution:

The master data of companies that are only relevant when using German tax law can be hidden by activating a customizing flag.

TB Transfer

Situation: 

In the TB transfer, a balance sheet item number can be entered under lines 59.3.5 and 59.4.5. Then the value from rows 59.3.5 and 59.4.5 is transferred accordingly to the balance sheet comparison (tab Local GAAP - Tax Balance). The TB transfer had to be saved twice for the value to be transferred correctly.

Solution:

After the first saving the value is correctly transferred to the Balance Sheet Comparison.

Anlage OG

(german tax law)

Situation:

If row 16 in dialog Anlage OG is not calculated, it should be cleared. This does not yet happen in periods with tax form 2019.

Solution:

If row 16 in dialog Anlage OG is not calculated, it will be cleared correctly in periods with tax form 2019.

Company

Situation:

Using the company master data, it was previously possible to adjust the following tax rates for specific companies: "Combined current income tax rate", "Combined deferred tax rate", "thereof, deferred tax rate local tax".

Solution:

With patch 1300872 it is now possible to adjust the following tax rates individually for a specific company:

• Corporate income tax (CIT) rate
• Local/State tax rate
• Combined current income tax rate
• Combined deferred tax rate
• thereof, deferred tax rate local tax
• Additional tax rate

In addition, the company-specific tax rates can now also be adjusted in the individual company area in the dialog Basis Data.

Tax Reports

(german tax lax)

Situation:

The report "Kurzübersicht Organgesellschaften" does not work.
In periods with tax form 2017, the report is executed but does not contain any data. In periods with tax forms 2018 and 2019, the report cannot be executed.
The report is erroneously also displayed for foreign companies.

Solution:

The report "Kurzübersicht Organgesellschaften" is created correctly in periods with tax forms 2016 and 2017.
In periods with tax form 2018 and later, the report cannot be executed. Short overview reports are available in Confluence as "Own Reports" for download.

Situation:

Up to now there is no possibility to show FX and hyperinflation effects on tax losses.

Solution:

The newly added column Hyperinflation is used to show hyperinflation adjustments according to IAS 29. This column is linked to the TRR. 

The newly added column Exchange rate adjustments serves to show the effects of exchange rate changes. Here too, the link to TRR is automatic.