Release Notes Version 24

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.

• When editing periods, the tax calculation of all companies is also calculated and saved.
• When mass editing companies, the same data cleaning is triggered as when editing single companies and the tax calculation of the companies is also calculated and saved.
• Only for german tax calculation: In addition, when changing the legal form type, the data in the ‘Anteilseigner’ and ‘Empfangsbevollmächtigter’ tabs is now cleansed if this data is no longer relevant for the current legal form.

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:

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:

Up to now, it has only been possible to maintain foreign branches in the basis data. This means that it is not possible to transfer branches in a period copy (without a transaction data copy).

Solution:

Foreign branches can now be maintained in the master data and also in the standard period. For this purpose, the table in the Basis data dialogue has been removed and implemented as a separate dialogue in the master data.






A separate authorisation object is available for the new dialogue. A migration of authorisations was applied to existing systems. This means that all users who previously had rights for the ‘Basis data’ dialogue now also have access to the ‘Foreign branches’ dialogue.

The data in the ‘Foreign branches’ dialogue is also transferred during the master data and transaction data copy.

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.

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:

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:

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:

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:

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:

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:

Regardless of the chosen tax return year, the dialogue Anlage FB can no longer be saved for partners that are not maintained in master data area.

Solution:

The dialogue Anlage FB can be saved correctly.

Situation:

In the toolbox, the row block with the 19.x rows and the rows 20.1.1 to 22.2 could not be displayed or hidden.

Solution:

The row block with the 19.x rows can now be activated as usual via a checkbox above row 19.1.










In addition, the individual activation of rows 20.1.1 to 22.2 has been made possible.

Situation:

The user overview lists the assigned roles without information on reporting dimensions and countries.

Solution:

The assigned roles are displayed in complete form in the overview again.

Situation:

If the function "Automatically transfer proposed tax rates" is activated, the proposed values for the tax rates are displayed with only two decimal places, although the tax rates in the country master data can be maintained with four decimal places.

Solution:

Four decimal places are taken into account when the tax rates are transferred.

Situation:
With patch 1301086, lines that are not visible due to company settings were excluded in the calculation of sum lines.
This led to incorrect calculations, for example in line 33, where line 20.1, among others, is no longer included.

Solution:
With patch 1301090, patch 1301086 is deactivated.

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:

The automatic migration of users, roles and role assignments from Income Taxes to the portal does not work. The error message refers to an error in the target module during ID mapping.
















The behaviour occurs since version 23.05.00.
















Solution:

The automatic migration works and supports an error-free transfer of users, roles and role assignments from Income Taxes to the portal.

Situation:

All lines from 20.1 to 22.2 are fixed (displayed always). This extends the dialogue unnecessarily. In most cases, only a few lines from this block are required.

Solution:
Only lines 20.1 and 20.2 are fixed lines.
















All other lines in this area can be deactivated in the toolbox master data.

Situation:
Saving the TB transfer for groups with many subordinate companies is time-consuming. This is caused by the high number of insertions and updates on the database table TUNITADDINFO.

Solution:
The number of insertions and updates on database table TUNITADDINFO is minimized. Saving the TB transfer is therefore significantly faster.

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

Situation:

If a user is restored in the portal, this event is not correctly sent to the Income Taxes module. The user is still archived and cannot log in to Income Taxes.

Solution:

The user is restored in both Income Taxes and the portal. To correct the behaviour, please archive the user a second time and restore them again.

Situation:
Previously, certain lines in the toolbox, such as lines 20.1.2 and 20.1.4, were included in the calculation even if they were not relevant for the respective company type. In such cases, these lines were activated in the master data but hidden from the user in the toolbox.

Solution:
Now rows that are not displayed due to the company type are no longer included in the calculations.

GTC-3803

Situation:
Currently individuals (natural persons) only can be created when the flag SHOW_FAMILY_OFFICE is activated.

Solution:
The new flag SHOW_NATURAL_PERSONS for individuals controls whether individuals (natural persons) can be created. When SHOW_FAMILY_OFFICE was activated in the database, SHOW_NATURAL_PERSONS will be activated as well.

Situation:
Since version 9.0.80, Tomcat delivers an adjustment in the server.xml file that may not be compatible with Income Taxes.


















If, for example, a dialogue with many input fields is to be saved (e.g. balance sheet comparison with a large balance sheet, income with many co-entrepreneurs, BMG transfer with many subordinate companies), it can happen that the values are not saved, but the user does not receive a message.

Solution:
The entry "maxParameterCount = 1000" must be removed from the server.xml file. We strongly recommend that you carry out this step as a precautionary measure, even if no problems are currently known. The entry must be checked with every version update of the Tomcat server and removed if necessary.

Situation:

inconsistent behaviour when increasing milestones for certain units

Solution:

all milestones should be able to be incremented regardless of the character string.

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

Situation:

The customer still uses SmartTaxBalance but Income Taxes is connected to the Portal already.

In this case the Import tab for SmartTaxBalance is hided.

Solution:

The tab for the import of SmartTaxBalance is displayed again, until support of SmartTaxBalance is discontinued.

Situation:

The automatic migration of users, roles and role assignments from Income Taxes to the portal does not work. The error message refers to an error in the target module during ID mapping.

The behaviour occurs since version 23.05.00.

Solution:

The automatic migration works and supports an error-free transfer of users, roles and role assignments from Income Taxes to the portal.

The Excel export has been adapted. Additional information such as company and period are now also displayed.

The PDF export has been adapted so that no representations are cut off and the dialogue is always represented completely

Situation:

For technical reasons, the drop-down list of periods for the "Calculation bases" field is no longer displayed. The calculation basis must now be entered directly.

Solution:

The latest available calculation base is displayed as proposed value. When creating new periods, the latest calculation base is always used. If a period is copied, this also applies to the "Calculation base" field.

Situation:

The pop-up for copying transaction data could not be accessed.

Solution:

The authorisation check has been corrected so that it can be opened again.

Situation:

In some dialogues, the authorisation checks do not work correctly. The following dialogues were affected by this in certain constellations and have now been corrected:

1) 8b Subjects - Import
2) Development of losses carried forward
3) Trade tax decomposition - export
4) Master data / CoA companies
5) Basis data / notification of tax structures
6) Period transfer - import
7) Master data / Toolbox

Situation:

The prior-year values for tax rates are no longer displayed in the basis data.

Solution:

The issue has been corrected.

Situation:
The Reports REPORT_EXPORT_ALL_GTC_IDS and REPORT_EXPORT_GTC_IDS include the category "Interest Capping Rule" of dialogue LCF only for german entities, even if the "Interest capping rule" ist activated for foreign companies.

Solution:
The report also displays values for non-German entities if the interest capping rule is used for non-german companies.

Situation:
For technical reasons, the drop-down list of periods for the "Calculation bases" field is no longer displayed. The calculation basis must now be entered directly.

Solution:
The latest available calculation base is displayed as proposed value. When creating new periods, the latest calculation base is always used. If a period is copied, this also applies to the "Calculation base" field.

Situation:

In newly installed environments, the behaviour occurs that it is not possible to switch from the Income Taxes module to the Portal module. The same behaviour occurs when a newly created user works with the system.

Solution:

The connection between the Portal and Income Taxes modules works properly in both directions.

Situation:

To close all milestones (" finished"), the user must save the dialogues in the correct order and close the milestones one after the other. If the "Deferred taxes" milestone is set to "Completed", the "Reconciliation" milestone always remains in the "In progress" status, even if the status is plausible in theory. The milestone status only changes to "plausible" after the TRR dialogue has been saved. Only then is it possible to close the dialogue.

Solution:

If the "Deferred taxes" milestone is closed, the TRR dialogue is recalculated directly in the background. The "Reconciliation" milestone is automatically set to the "plausible" status according to the validation calculated from it or remains in the "in progress" status.

Situation:

The "Import Suite" dialogue enables the import of values from module Tax Balance.

The import process can currently be started on this page. However, the user must then call up the dialogue manually to update the page. If the import takes longer, this process may have to be repeated several times until the Tax Balance processing is complete. Only then the import result is displayed and can be saved by the user.

Solution:

After starting the import, the page refreshes automatically. As long as the import is running, a corresponding message appears. As soon as the import is finished, the import log is displayed.

The page can also be exited during the import.

Situation:

Direct imports (import from database table TIMPORTBS) were only available in combination with the standard mapping (direction: "Import").

Solution:

Direct imports (import from database table TIMPORTBS) can also be used in combination with the mapping engine (direction: "Import (enhanced)"). A corresponding is maintained in dialogue "Import mapping".

Situation:

Dialogue "Import Suite" (reading data from Tax Balance) cannot be used in combination with the mapping engine.

Solution:

In dialog "Import Suite" (reading data from Tax Balance) an interface structure of the mapping engine with source "Direct import" can be used.

Situation:

Role changes and assignments done in the portal might be out of sync with the data stored in the Income Taxes database (eg because of a network error). Note that the only possible error concerns deletions of roles and role assignments.

Solution:

Roles and role assignments are synchronised with the portal during startup of the Income Taxes Tomcat and during user login.

Situation:

In some dialogues the confirmation popup for deleting an entry (eg: § 8b KStG) does not display any details about the selected item.

Solution:

The confirmation popup for deleting an entry shows significant details about the selected item.

Situation:

If an internal row (Typ '---' in mapping, "alias") is processed, the column number is not correctly displayed when an error occurs during evaluation or validation of a mapping field (eg: because of a syntax error).

Solution:

The column number is correctly specified in an error message.

Situation:

What is wrong:
The activation of Income Taxes works with the MAC address of the server. Under Linux, the implementation detects the MAC address with "/sbin/ifconfig -a". This command has long been deprecated and is no longer available in newer Linux versions.

Solution:

The implementation now additionally determines the MAC address with "/sbin/ip -a address".