Page Comparison

Situation:

The import via the extended mapping (flags: INTERFACE_CONFIG = 2, MAPPING_VERSION = 3) in dialogues of the current taxes area from VZ 2018 onward runs into a general error.

Solution:

The error occurred as part of an optimization during the provision of the import for the dialogue "Anlage FE-K-Bet" and was corrected accordingly at this point.

Situation:

The company transfers deferred taxes.

If you copy a period with transaction data but without milestones, the milestones for deferred taxes are not copied.

As a result, the milestone is only initialised with the status "not started" when the dialogue " Single company / status" is called up.

This leads to errors, especially for true-up periods, as these companies cannot be accessed in the following period.

Solution:

The milestones are also copied and set directly to the status "not started".

Situation:

In the interface structure for importing a csv or excel file there is a checkbox "Save Importfile as comment".

When the checkbox is activated, it is not taken into account in the dialog "(Sub-) Group / Import".

It is furthermore ignored during the enhanced import (mapping engine) in the dialog "Company / Import".

Solution:

The checkbox "Save Importfile as comment" of the interface structure is taken into account in all variants when importing a csv or Excel file.

Situation:

In the dialog "(Sub) Group Import" via RFC and REST, data is first retrieved for each group company before the filter for materiality and reporting dimensions is subsequently applied. Thus, unnecessary data may be retrieved.

Solution:

To improve performance, RFC and REST calls are now only made for those group companies that are not screened out by the filter on materiality and reporting dimensions.

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:

After importing a period with activated option "Overwrite period", there are no balance sheet positions (the dialog "CoA Group" is empty), if the export had previously been performed with the option "Master data only".

Solution:

Balance sheets are considered as master data. In the current case, the balance sheet positions of the exported period are imported into the target period. However, all balance sheet values are set to zero.

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:

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.