Release Notes 23.00.XX (R1/2023)

Situation:

Only periods of the type "tax return" can be created for the form sets from 2018. Here, rounding is activated in the tax calculation for Switzerland ("23.45" => "23.00").

Solution:

If a company uses the Swiss tax law, the values are also saved in the more recent assessment periods without rounding.

Situation:

In 2021, a new version of the period transfer was implemented that allows flexible control of the various options in the period transfer directly in the interface.

However, the older variant of the period transfer is still activated by default.

Solution:

The old period transfer is now switched off and the new period import is visible (if purchased).
The new period export is always displayed.

Situation:

In the dialog Participation Deduction, loans to affiliated companies are now to be taken into account. This applies to all cantons that know a participation deduction / capital reduction, except for the cantons BS and FR.

Solution:

For this purpose, new lines have been added to the Participation Deduction dialog, which are automatically used in the corresponding cantons.

Situation:

If roles were assigned to users with contexts (companies, reporting dimensions or countries) from the Income Taxes module via the portal, only the first of these contexts was displayed. Alternatively, it was also possible to display all contexts as single items.

Solution:

The contexts are now delivered to the portal aggregated so that the display shows them together.

At least Portal version 23.02.01 is required.

Situation:

When importing from SmartTaxBalance, mapping to target positions is aborted if one of the target positions does not exist (e.g. if the form is not visible). As a result, subsequent valid target positions are ignored and the import is incomplete.

Solution:

The mapping is completely executed even if one of the target positions does not exist.

Situation:

It is not possible to import in the single company area via a created REST interface in the "Validation" dialogue.

Solution:

It should be possible to import into the "Validation" dialogue via a REST interface with the corresponding mapping in the single company area. In the mapping, TVALIDATION must be specified as the target in the column "Dialogue (target)".

Situation:

If the checkbox "Save Importfile as comment" is activated in an interface structure for file import ("Standard (csv, txt, xls, xlsx)"), only "small" files (under 2 MB) are stored together with a comment. Larger files are not stored: Accessing the file via the comment returns an error message.

Solution:

Larger files are also stored together with a comment.

Situation:

In 2021, a new version of the period transfer was implemented that allows flexible control of the various options in the period transfer directly in the interface.

However, the older variant of the period transfer is still activated by default.

Solution:

The old period transfer is now switched off and the new period import is visible (if purchased).
The new period export is always displayed.

Situation:

In the report REPORT_EXPORT_ALL_GTC_IDS, the values for the keys LCF_LocalTax and LCF_TaxCredits are incorrect.

Here the value from the keys LCF_for.tax.2nd (local tax+ capital losses) or LCF_tax.credit (tax credits and other tax advantages abroad) is found again.

Solution:

The values only contain the local tax and the tax credits and are not supplemented by the capital losses or other tax benefits.

Situation:

If several user accounts are created in the portal by means of an import file, not all user accounts are transferred to IncomeTaxes.

Solution:

Also when user accounts are created via an import file, a complete transfer into IncomeTaxes is done.

Situation:

For the implementation that can be used to jump from the Income Taxes product directly into the VAT product, a password has been defined within the source code. This posed a potential security risk.

Solution:

The password can now be entered via the Tomcat start parameter "-Dgtc.runtime.privatekey.pw=". The password must be specified for this implementation to work.

Situation:

The milestone "Other" was not hidden for consolidation units in the single company, although the corresponding flag was imported.

Solution:

The milestone "Other" is now hidden if the corresponding flag is set.

Situation:

If the Tomcat was stored on a different medium than the Windows installation or its path was changed, then no serial number could be displayed during activation and thus no activation key could be generated.

Solution:

If the path to the Windows folder "System32" is not correct by default and thus no serial number is displayed, the path can be specified with the Tomcat start parameter -Dgtc.runtime.system32="...". This is always favored over the default path.