Page Comparison

GTC 23.02

Pillar 2 2.0.5

Currency Exchange Rates for the Value “Carrying value of relevant Eligible Tangible Assets located in the jurisdiction at the beginning of the reporting year” of the Substance based Income Exclusion.

Issue is fixed with GTC 23.05

Possible Workaround:

• Insert countries and respective ultimo currency in the default period

• Do not select a previous period snapshot to calculate a snapshot

Explanation:
The Assets at the Beginning of the period are calculated with the prior Ultimo currency exchange rate. The Bug leads to the fact, that the system doesn’t find the previous period. By default, the currency exchange rate of the default period (“---”) is used to calculate the value in the respective currency. It therefore is possible, to enter the currency exchange rates in the default period to calculate the “Carrying value of relevant Eligible Tangible Assets located in the jurisdiction at the beginning of the reporting year”.

Fixed

GTC 23.02

Pillar 2 2.0.5

Recast Amount is zero, if not all percentage values of DT-4.2, DT-4.4 or DT-4.5 unequal 0.

Issue is fixed with GTC 23.05

Workaround:

• Insert any other value but zero in DT-4.2, DT-4.4 and DT-4.6, so the function will calculate the recast amount. If the value of the amount to be recastet (DT-4.1, DT-4.3, DT-4.5) is zero, the function is valid and the result will be zero also if DT-4.2, DT-4.4 and DT-4.6 are not zero.

Explanation:

At the moment the formula of the recast doesn’t work if either DT-4.2, DT-4.4 or DT-4.5 are equal to zero. If zero, the value in DT-4.1 or respectively DT-4.3, DT-4.5 are divided by zero and the whole function is not valid.

Fixed

GTC 23.02

Pillar 2 2.0.5

Authorizations lead to a wrong surface in the dialogue GloBE Income. This concerns just clients, who use authorizations and role concepts for their Pillar 2 Data Collection. For superuser the dialogues work.

Issue is fixed with GTC 23.05

Workaround:

• As superuser, the dialogue has the right surface.

• With a short SQL-Statement the problem can be fixed easily. (via Script)

Explanation:

Technical Issue regarding authorizations.

Fixed