Page Comparison

Situation:

In the sections "Withholding Taxes", "Tax Questionnaire", "Risk Management" and "Compliance", the button "My Profile" is displayed.

Solution:

The button is split into "My Data" and "My Settings" in the portal context. This now also applies to the aforementioned areas.

Situation:

The dialogue cannot be opened if one of the tax group members is not existing in the true-up period.

Solution:

The dialogue can still be displayed.

Situation:

Dialogue "Own Reports" allows GTC customers to directly access database tables and use them for a variety of further evaluations and data processing.

Because of security reasons the access to table TUSER and associated tables was forbidden. This restriction was regarded as too far-reaching by several customers.

Solution:

Own reports may again access every database table. There is one exception, namely table TUSER. The view VUSER must be used instead.

Only relevant if the setting SHOW_OCI_AT_SUMMARY=1 is active:

Situation:

When entering a value in the "Others" dialogue in the block "Other, Prior year adjustments - OCI", the calculated value is doubled in the "Summary" dialogue.

Solution:

The value is displayed at the correct amount.

Situation:

If module Income Taxes is integrated into the Portal Suite, roles and role allocations are maintained in the portal. Nevertheless, dialogue "User" of Income Taxes still presents all role assignments. Instead of role names, however, only their internal IDs are shown.

Solution:

Data should generally be shown where they are created and maintained. A second (redundant) presentation only invokes synchronisation problems. Role assignments are therefore no longer shown in dialogue "User" of module Income Taxes.

In dialogue "My profile" of Income Taxes, however, the user's own roles will be shown, as long as this function is not available within the portal.

Situation:

Some features that are now standard features are enabled via customizing flags.

Solution:

If the necessary flags were not yet activated in the GTC, this is now done automatically with the GTC update. The following features belong to this:

• Under Master data / CoA Group, the function "Maintain columns" is always available.
• Under Master data / CoA Group / Maintain columns, the parameters "Permanent differences" and "affecting P&L / affecting OCI" can always be selected.
• For maintenance reasons, very old dialogues such as "Payment Status", "Tax management" and "Tax Tracing" are hidden in the "Reports" area. These dialogues are no longer maintained and have meanwhile been replaced by newer functions / modules.
• Under Master Data / Countries, the simple import for currency conversion rates is always available.
• In the area "Company" the dialogue "Deferred taxes / Report DT Pos" is available.
• In the dialogue B/S comparison (tab Local GAAP - Tax Balance), the button "Calculate Local GAAP" is displayed.
• The period export is always available.
• The table "Change in deferred taxes" is always displayed in the dialogue Summary
• A changelog is always written in the master data area.
• When generating your own reports, the report repository is always used.
• It is always possible to create true-up periods (master data / periods).

Situation:

The status page in the single company area cannot be accessed in a summary period.

The buttons (e.g. Show activities) are not displayed if the milestone " Current taxes" is in the status " finished" or "checked".

Solution:

The status page can also be opened in summary periods and the buttons are always displayed.

Situation:

If no balance sheet items have been created for a period yet, a system error message occurs each time when saving the balance sheet comparison and when copying the transaction data.

Solution:

Issue error messages describing the problem. Intercept the system error message.

MVB - IFRS

Only relevant when using the MVB function:

Situation:

An import interface has been configured in the MVB dialogue. In this interface, the checkbox for resetting the differences columns in the MVB dialogue is activated.

In this case, when the import is performed, all differences in the "Other deferred taxes" tab are reset to 0.00 in all periods and all companies, no matter for which company and which period the import is performed.

Solution:

Only the differences of the currently selected company are reset to 0.00 in the currently selected period.

Situation:

During import of a balancesheet structure an error occurs, if languages besides "german" and "english" are configured in the interface structue, but the Excel file does not contain values. The log file contains no hint with regard to the column responsible for the error.

Solution:

Lanuage-dependent values may be empty in Excel. The log file specifies the column responsible for an error.

Situation:

Output location (CATALINA_HOME/logs) and format of the logging are not freely configurable.

Solution:

The output location as well as the output format of the logging can be configured via startup parameters of the Tomcat. If no settings are made here, logging takes place in the previous format by default.

The default output directory has been changed from CATALINA_HOME/logs to CATALINA_BASE/logs.

Further information on configuration can be found in the user guide.

Situation:

The URLs for calling the GTC interfaces have so far started with "<root>/portalapi/...". This does not correspond to the usual convention.

Solution:

The URL has been changed to "<root>/api/...".

This may result in the portal module no longer being able to connect to the Income Taxes module (GTC). Therefore, please check under "Portal/Administration/Module/Income Taxes/Edit" whether the entry "Api URL" already contains the new URL. If this is not the case, please contact your system administrator for further configuration.

Deferred Taxes

Situation:

The proposed values are displayed as 0.00 in the read view of the Rollforward LCF dialog.

Solution:

During the editing of the dialog Rollforward LCF (period/milestones opened), the proposed values are saved in order to display them later in the read view (period/milestones closed).
No calculation is performed in the read view.

Portal / GTC Suite

Situation:

Some user-related data (e.g.: email and phone number) are not transferred from the portal to GTC. As a consequence they cannot be used in error messages with regard to a concurrent page access.

Solution:

User-related data which are needed in GTC and which are available in the portal are transferred from there to GTC.

Situation:

Users with auditor rights must not be able to create or view comments. This restriction is not completely implemented in all dialogues.

Solution:

Users with auditor rights can neither create nor view any comments.

Furthermore, the report "Comments" is hidden and cannot be called.

Situation:

The proposed value in line 27, corporate tax column is incorrect.

Solution:

The effect from the local tax column is no longer shown in the proposed value of line 27, corporate tax column.

The RestEasy libraries have been updated.

The json-smart libraries have been updated.

Situation:

With every import with transaction data, the language entries are completely emptied (regardless of the period) and then rewritten. In addition, the language entries in the period transfer belong to the transaction data.

If an export is now only carried out with master data, but the selection "Overwrite period" is made on the import page, the language entries are completely deleted during the import, but not rewritten, as they are not available in the export file. Thus, all descriptions that the GTC user can maintain multilingually in the master data are no longer available (e.g. descriptions of balance sheet items and countries).

Solution:

The language entries are never deleted during the import. By using selection fields, the user has the option to update the language entries contained there based on the export file to be imported or to add language entries that do not yet exist.

In addition, the language entries are always exported because they belong to the master data.

Situation:

Authentication and authorization of REST services is not yet homogeneously implemented.

Solution:

REST services can only be called from authenticated and authorized users. Whithin the GTC Suite users are authenticated via access tokens, otherwise Basic Authentication (username/password) is used.

For data access the user authorizations are checked. Outside of the GTC Suite the user needs the "RestInterfaces (RestUseAPI)" permission in order to call a REST service.

If you are already using REST interfaces, you may need to adjust permissions in the GTC.

Situation:

Even if the user uses the GTC in the English language, the German user guide is still opened as a direct link from the GTC.

Solution:

If the user selects a language that is not "German", the English user manual is displayed.
The same behaviour applies to the Release Notes.
Both links can be called up at the top right of the header via the "User" icon.

Situation:
If processing has not yet been started for a company, it can only be started by clicking on one of the workflow milestones (Actual Taxes, Deferred Taxes, ...). This is not intuitive.

Solution:
To open a company, an alternative is to click on the button 'Start processing'. As long as the company has not been started, the single company dialogues are hidden in the menu tree.