Content Comparison

Situation:

If the IncomeTaxes is deployed in the root directory of the application server, the session cookie has been created multiple times. This can lead to inconsistent behaviour of the system, e.g. the user is suddenly logged out.

The behaviour can occur from version 24.4.1.

Solution:

It has been ensured that only one session cookie is ever created, regardless of the deployment path.

GTC-8203

Situation:

Toolbox data, including the toolbox definition (structure of the toolbox dialogue), is regarded in full as transaction data. If a period export is only carried out with master data, no toolbox definitions are exported. As a result, no changes are made to the toolbox definitions during the period import.

Solution:

The structure of the toolbox belongs to the master data and is always included in the export. It is therefore always transferred to the target period.
For all companies included in the export, the toolbox data is taken from the export file (definition and content).
If the ‘Apply toolbox’ checkbox is activated, the toolbox values of all companies that are not included in the export are reset to NIL and the structure of the toolbox is saved for the companies.

GTC-6522

Situation:

When a deferred tax expense (entered as a positive value) is added in the Others dialogue, specifically under "Unrecognised deferred tax asset (without loss carry forward) P&L," it results in a negative amount in the TRR line "Value adjustments / corrections of value adjustments" (pos09a_a). The proposed value for the field in the Others dialogue also has a false sign.

Solution:

When the amount is transferred into the TRR dialogue the sign of the value has not been reversed. The sign of the proposed value for the field in the Others dialogue is reversed.

GTC-8328

-

Situation:

Currently, Income Taxes does not offer the dialogues in French language.

Solution:

Income Taxes supports the French language in the display in the standalone version as well as in the portal environment (from portal version 24.3.1).

Situation:

If the IncomeTaxes is deployed in the root directory of the application server, the session cookie has been created multiple times. This can lead to inconsistent behaviour of the system, e.g. the user is suddenly logged out.

The behaviour can occur from version 24.4.1.

Solution:

It has been ensured that only one session cookie is ever created, regardless of the deployment path.

GTC-8341

Situation:

When a deferred tax expense (entered as a positive value) is added in the Others dialogue, specifically under "Unrecognised deferred tax asset (without loss carry forward) P&L," it results in a negative amount in the TRR line "Value adjustments / corrections of value adjustments" (pos09a_a). The proposed value for the field in the Others dialogue also has a false sign.

Solution:

When the amount is transferred into the TRR dialogue the sign of the value has not been reversed. The sign of the proposed value for the field in the Others dialogue is reversed.

GTC-8205

Transaction data copy

Situation:
Execution of "Copy transaction data" in the status dialogue of single companies does not work for planning periods.
AC
Solution:
"Copy transaction data" in the status dialogue can be executed for planning periods as well.

GTC-8400

Changelog

Situation:

When roles and role assignments are changed in the portal, the change log in the Income Taxes module shows a technical ID as the person who made the change.

Solution:

The change log now displays the name of the user logged into the portal who made the change.

GTC-7864

Situation:
In some units, no gross amount long term usable values are transferred when importing with the import robot, although the corresponding checkbox is selected.

Solution:
If the checkbox for the transfer of gross amount long term usable values is activated, these are transferred to the loss carryforward.

Situation:

In dialogue "Tax liabilities" the rows for "Tax reserves for tax audit risks" are only visible for specific configurations. Customers want to use these rows in a standard configuration as well.

Solution:

The rows "Tax reserves for tax audit risks income taxes" and "Tax reserves for tax audit risks other taxes" are always visible in dialogue "Tax liabilities".

Situation:

The transaction data copy for OBD does not work.

Solution:

The transaction data copy can be executed for OBD.

Situation:

With ticket GTC-4213, a pseudonymisation function was added to the period transfer. The feedback revealed that some properties are not yet sufficiently pseudonymised.

Solution:

Additional master data fields were added to the pseudonymisation.

As part of the long-term goal of standardising Income Taxes as far as possible, the end of support for further customer-specific functions (VOKUS report, editable help in the questionnaire) is hereby announced.

If one of these functions is activated in your system, an appropriate warning message will be displayed and detailed information can also be found in the log files.

New function:

The user cannot work with the application when no number format is stored in the database.

Outlook:

In one of the upcoming versions of Income Taxes, the endpoints will also be available for the GTC Suite. Authorisations will be checked via the user's access token.

Situation:

The application runs into an error, when it is configured and called as a root application.

Solution:

The application can be started with the Tomcat root link.

Situation:

The export with standard reports "Mass Export GTC-IDs, all" (REPORT_EXPORT_ALL_GTC_IDS) and "Mass Export GTC-IDs, mapped" (REPORT_EXPORT_GTC_IDS) displays all values of companies in the local company currency. On the customer's side these reports are often used for group-wide evaluations (e.g., in Power BI). But reporting across multiple companies are not possible, if they use different local currencies.

Solution:

The standard reports "Mass Export GTC-IDs, all" and "Mass Export GTC-IDs, mapped" can be executed with "Scope" and "FX code" selections. All company values are then converted into the corresponding target currency.

New function:

In addition to the standard report, it is now possible to address REST endpoints for the export of technical IDs and associated values. These endpoints are currently available when the module is operated in standalone mode.

1. all values of all companies in a period (/api/periods/{period-id}/positions/)
2. all values of all companies of a period stored in the export mapping (/api/periods/{period-id}/positions/defaultMapping)
3. all values of a company in a period (/api/periods/{period-id}/units/{unit-id}/positions/)
4. all values of a company of a period stored in the export mapping (/api/periods/{period-id}/units/{unit-id}/positions/defaultMapping)

The required authorisations can be found in the documentation in the User Guide.

Outlook:

In one of the upcoming versions of Income Taxes, the endpoints will also be available for the GTC Suite. Authorisations will be checked via the user's access token.

Situation:

In the overview of countries in the master data, the currency conversion rates are displayed with only 4 decimal places, although they can be entered with 10 decimal places.

Solution:

The display has been corrected.

Situation:

In an optional configuration, it is also possible to specify a period when assigning roles to users. This means that this role (and the associated authorisations) is only valid for the specified periods.

The end of support for this function was announced in autumn 2021.

Solution:

This function is no longer supported in the GTC Suite and is therefore no longer available in Income Taxes.

Situation:

Additional company codes that are specified in the company master data or in a company-specific interface are not taken into account in an import of the type ‘SAP RfC (flexible)’.

Solution:

Additional company codes are included in the flexible RfC import.

Situation:

A reclassification column is displayed in the TRR dialogue (optional function). In the event that the reclassifications entered do not add up to 0.00, this is indicated to the user with a warning triangle in the validation line.

Solution:

In order to communicate the difference more clearly during validation, an additional warning message is now displayed to the user. As this is a warning and not an error, it is possible to finalise the processing of the TRR despite existing reclassification differences.

Situation:

When creating and updating roles, access rights are available that do not make sense in relation to the current configuration. As a result, users sometimes generate roles that do not work correctly.

Solution:

Only the authorisation objects that are relevant for the current configuration are available.
Example: As long as the module for the Tax Questionnaire is not activated, the corresponding authorisations are not displayed.

New function:

In addition to the standard report, it is now possible to address REST endpoints for the export of technical IDs and associated values. These endpoints are currently available when the module is operated in standalone mode.

1. all values of all companies in a period (/api/periods/{period-id}/positions/)
2. all values of all companies of a period stored in the export mapping (/api/periods/{period-id}/positions/defaultMapping)
3. all values of a company in a period (/api/periods/{period-id}/units/{unit-id}/positions/)
4. all values of a company of a period stored in the export mapping (/api/periods/{period-id}/units/{unit-id}/positions/defaultMapping)

The required authorisations can be found in the documentation in the User Guide.

Outlook:

In one of the upcoming versions of Income Taxes, the endpoints will also be available for the GTC Suite. Authorisations will be checked via the user's access token.

Situation:

If an export interface is configured using a report template, the name of the spreadsheet is required for the CSV, PDF and XLSX file formats so that the export can be performed for this spreadsheet.

If ‘File path’ is selected as the target, the ‘Excel sheet name’ field is not displayed and therefore cannot be maintained. This means that the export cannot be triggered.

The behaviour occurs since version 24.2.1.

Solution:

The ‘Excel sheet name’ field is displayed for the ‘Download’ and ‘File path’ destinations in the interface configuration.

Situation:

The provided features are being standardised. Special functions that are only used by very few customers were communicated as no longer available some time ago. Affected customers received a corresponding warning message within the application indicating this fact.

Until now, an old version of the mapping was still available.

Solution:

The old version of the mapping is no longer supported.

Situation:

No information about the BRG and used TQ version is displayed in the snapshots.

Solution:

When creating a snapshot, the highest active and relevant BRG in the period and the used TQ version should be saved and listed as 2 new columns on the overview page.

Situation:

The "Save" action can take several minutes in the snapshots. A display is not available.

Solution:

Introduction of a progress bar for the save action to indicate to the user that the application is performing an action.

Situation:

CbCR-specific information needs to be added to the UNIT Master Data (isAMAExx information).

Solution:

The tab of the Pillar 2 Unit Master Data has been relabeled to 'International Tax'. There are three new fields: TIN01, TIN02, and AMAC00. TIN01 is an input field, TIN02 is a select box, and AMAC00 is also a checkbox.

Situation:

The Excel export of B/S comparison does not show difference values. Furthermore the Excel file can only be opened after confirmation of a warning concerning repairs of the file.

Solution:

All exports of B/S comparison show the correct values. The Excel export file can be opened without warning.

Situation:

The data of the dialogue “Ausländische Zwischengesellschaften” and of "§8b KStG" entries in snapshots may not be exported correctly.

Solution:

The export contains the specified data correctly and completely.

Situation:

An Import (Cockpit > Import > Income Tax) is not possible if there is no milestone status (P2 main milestone) set.
The milestone status is set just when the entity is selected at least one time in the Company drop-down.

Solution:

Milestone status is now always set.

Situation:

There was an error when opening the Pillar 2 tab in the company edit view. The tab had to be clicked multiple times for the content to be displayed.

Solution:

An error with opening the Pillar 2 tab in the company edit view has been fixed.

Situation:

The dialogue “Valuation allowance gross” under “(Sub-) Group” is no longer required.

Solution:

The dialogue “Valuation allowance gross” under “(Sub-) Group” and all calculations linked to it are removed.

Situation:

The tax rates are displayed incompletely in the ‘Basis data’ dialogue. For example, the value for the Local tax/State tax rate is not listed.

Solution:

The display of the tax rates in the Basis data dialogue has been corrected.

Situation:

In certain cases, customer problems cannot be reproduced by AMANA. For data protection reasons, it is sometimes not an option to fully export period data, which makes problem solving more difficult.

Solution:

An anonymisation function is now available when exporting periods. This option is only used in exceptional cases and must be activated through a configuration in the system.
Please note that the anonymisation function has only been set up for the calculation of current and deferred taxes starting with the 2022 form set. Modules such as Tax Questionnaire and Pillar 2 do not currently support data anonymisation.
If the function is activated, the period export allows the anonymisation of company and personal data by ticking the "Anonymisation" box. This data includes, for example, names of (reporting) entities and address details. In addition, a further "Reset values" checkbox can be used to ensure that all amount values in the export are changed to 0.

Situation:

The module Income Taxes offers REST interfaces which can be accessed from external Systems. To call these interfaces, a API Key is needed which currently is not displayed in the tool itself.

Solution:

In the 'My settings' dialogue, users can click the 'Show API Key' button to access their key. A popup will appear with a button to automatically copy the API key to the clipboard. This key remains available for 15 minutes after it refreshes. To ensure the key can be used for the full duration, it refreshes each time the dialog is opened.













More details can be found in the user guide.

Situation:

In the Master data dialogue 'Position mapping' the checkbox "Extend default mapping?" is not displayed in the list of the existing mappings.

Solution:

The checkbox entries for the field "Extend default mapping?" are displayed correctly.

Situation:

Under some circumstances, the "Basis data" dialogue shows too many fields/properties for companies that do not work with German tax law.

Solution:

The display has been corrected.

Situation:

It is possible to import into non-editable fields. In addition, it is not possible to import into both the "IFRS adjustment" and "Reclassification" fields of the same line.

Solution:

It is now possible to import into two fields of the same row. In addition, the system displays an error message when importing into a non-editable or non-visible field.

Situation:

Incorrect Tomcat start parameters are the cause of some problems. However, when a customer contacts support, these have to be requested and entered manually, which means that the actual parameters may differ from the transmitted ones.

Solution:

The start parameters are now automatically transferred to the ‘system.log’ files so that we can provide faster support in the event of a problem and obtain more accurate information.

Reporting Engine

Situation:

In a period with deactivated tax calculation (eg: pure TaxQuestionnaire, CbCR, Pillar 2 periods) the dialogue "Reporting Engine" is not displayed in the menu tree.

Solution:

The ‘Reporting Engine’ dialogue is visible in periods with deactivated tax calculation, as long as the user has the necessary permissions.

Situation:

The provided features are being standardised. Special functions that are only used by very few customers were communicated as no longer available some time ago. Affected customers received a corresponding warning message within the application indicating this fact.

Previously, an additional function was offered in the ‘Report VV’ dialogue using the customising flags NOTES_ROW_CALCULATION and similar.

Solution:

The additional functions that could be activated with the NOTES_ROW_CALCULATION and similar flags have been completely removed. It is no longer possible to display or use these functions.

GTC-5400

Situation:

Under some circumstances, the "Basis data" dialogue shows too many fields/properties for companies that do not work with German tax law.

Solution:

The display has been corrected.

Situation:

The provided features are being standardised. Special functions that are only used by very few customers were communicated as no longer available some time ago. Affected customers received a corresponding warning message within the application indicating this fact.

Previously, the customising flag SHOW_PERIODOPTION_FORECAST enabled the configuration of periods as forecast or half-year periods.

Solution:

Forecast and half-year periods are no longer supported. Existing forecast and half-year periods are closed and archived.

GTC-4306

Situation:

The provided features are being standardised. Special functions that are only used by very few customers were communicated as no longer available some time ago. Affected customers received a corresponding warning message within the application indicating this fact.

Until now, an old version of the import configuration was still available.

Solution:

The old version of the import configuration is no longer supported.

Situation:

The provided features are being standardised. Special functions that are only used by very few customers were communicated as no longer available some time ago. Affected customers received a corresponding warning message within the application indicating this fact.

The ENABLE_DEPRECATED_XML_UPLOADS flag was previously used to activate the uploading of XML files in special system configurations.

Solution:

The uploading of XML files is no longer supported.

GTC-4305

Situation:

The provided features are being standardised. Special functions that are only used by very few customers were communicated as no longer available some time ago. Affected customers received a corresponding warning message within the application indicating this fact.

Until now, an old version of the validation (version 2) was still available.

Solution:

Validation variant 2 is no longer supported. Variant 4 can be set up as an alternative.

Only relevant when using the Income Taxes module in the GTC Suite environment:

Situation:

When importing values from SmartTaxBalance, values are also saved as comments. The new interface to the ‘Tax Balance’ module does not support this function.

Solution:

The import is carried out via the ‘Import Suite’ dialogue.


















If values are imported into the dialogues of the actual tax calculation, they can also be stored as comments if the ‘Standard’ option has been selected in the ‘Interface structure’ dropdown.


















In the case of an interface with extended mapping, these comments are only created if the ‘Create additional import values as comments’ option is selected in the selected interface structure.

Situation:

The enhanced import for (sub-) groups does not work correctly for foreign companies. When saving, an error message appears.

Solution:

All imports work correctly for foreign companies.

This behaviour has occurred since version 24.3.1.

Situation:

The overview dialogue "Companies" takes a long time to load if there are a large number of companies.

Solution:
















The loading performance has been optimised.