Configuring Pillar Two

Pillar Two hierarchies

Pillar Two uses specific hierarchies for data collection and reporting.

Dimension	Hierarchy	Use
ACCOUNTS	P2CT – Covered Taxes	Collection of covered taxes for constituent entities.
ACCOUNTS	P2GI – GloBE Income	Collection of GloBE Income for constituent entities
ACCOUNTS	P2REV - Revenue	Collection for GloBE Revenue for constituent entities
ACCOUNTS	P2SBIE5.3 – GloBE Substance Based Income Exclusion	Collection of gross substance-based income exclusion values for constituent entities and calculation of substance-based income exclusion for top-up tax.
ACCOUNTS	P2SBIE5.3RATE – Substance Based Income Exclusion Rates	Holds the rate applied to calculate the substance-based income exclusion amount.
ACCOUNTS	P2TMP – GloBE Temporary Differences	Holds the provision temporary differences and accounts for adjustments for Pillar Two purposes.
ACCOUNTS	P2TT – Adjusted Jurisdictional top-up Tax	Calculation of adjusted top-up tax for a jurisdiction or stateless constituent entity
ACCOUNTS	P2TTP – ETR and Top-up Tax Percentage	Calculation of ETR and top-up tax percentage for a jurisdiction or stateless constituent entity.
ACCOUNTS	QDCT – QDMTT Covered Taxes	Collection of covered taxes adjustments for QDMTT by constituent entity. This hierarchy is synchronized with the P2CT hierarchy.
ACCOUNTS	QDGI – QDMTT Income	Collection of income adjustments for QDMTT by constituent entity. This hierarchy is synchronized with the P2GI hierarchy.
ACCOUNTS	QDSBIE5.3 – QDMTT Substance Based Income Exclusion	Collection of gross substance-based income exclusion values adjustments for QDMTT by constituent entity and calculation of substance-based income exclusion for QDMTT top-up tax.
ACCOUNTS	P2SBIE5.3RATE – Substance Based Income Exclusion Rates	Holds the rate applied to calculate the substance-based income exclusion amount for QDMTT. The rates for QDMTT can vary by jurisdiction.
ACCOUNTS	QDTT – Adjusted Domestic top-up Tax	Calculation of adjusted domestic top-up tax for a jurisdiction or stateless constituent entity
ACCOUNTS	QDTTP – ETR and Top-up Tax Percentage	Calculation of ETR and top-up tax percentage for a jurisdiction or stateless constituent entity under QDMTT rules.
TIMEPER	CYP2PER – Pillar Two Process Current Period	Holds the current period and active scenarios for Pillar Two processes.
TIMEPER	RTNP2PER – Pillar Two Process Return Period	Holds the active return period for Pillar Two processes.
ENTITIES	P2JTotal – Total Jurisdictions	Holds the hierarchy of jurisdictions and constituent entities for Pillar Two purposes. This hierarchy may contain entities also used in Tax Provision or Transfer Pricing.
ENTITIES	Automation_Groups_P2 – Pillar Two Automation Groups	Holds the entity groups used for Pillar Two automation settings
DETAILS	SUMMDET – Detail Summary	Holds the data collected and calculated for Pillar Two. Default target detail for automations.
DETAILS	P2DET – Pillar Two Details	Holds the gross, per provision and per Pillar Two temporary difference balances. Also holds the gross and per Pillar Two adjustments
CURRENCY	<Reporting Currency>	All Pillar Two data is stored in the reporting currency for the Ultimate Parent Entity (UPE).
SEGMENTS	SUMMSEG – Segment Summary	Holds the data collected and calculated for Pillar Two. Default target segment for automations.
ELEMENTS	P2SUMM – Pillar Two Summary	Holds the data collected and calculated for Pillar Two. Default target element for automations.
ELEMENTS	P2EoY – End of Year Balance	Holds the data collected for temporary differences from Provision and adjustments to those temporary differences for Pillar Two
ELEMENTS	QDMTT – QDMTT	Holds the data collected for data collected and calculated for Pillar Two and the QDMTT adjustments.

Pillar Two Attributes

Pillar Two uses specific attributes for configuration. Attributes that are set via an app and should not be set directly are indicated.

Type	Name	Notes
SYSTEM	ASP2Cper	The current period for Pillar Two processes. The time period defined by this attribute is used for all input apps and reports and is updated by the Pillar Two rollover process.
SYSTEM	ASP2CTAutoAccountsSource	The source accounts for pillar two GloBE covered taxes automation. Default (P2): TRIALBAL, P2TMP Default (ASC): TRIALBAL, TaxIncome_ASC, P2TMP, NatTP_ASC, DefTax_ASC Default (ASC MRP): TRIALBAL, TaxIncome_ASC, P2TMP, NatTP_ASC, MSP_DefTax_ASC Default (IAS): TRIALBAL, TaxIncome_IAS, P2TMP, TXCT, DefTax_IAS Default (IAS MRP): TRIALBAL, TaxIncome_IAS, P2TMP, TXCT, MSP_DefTax_IAS
SYSTEM	ASP2CTAutoD0Source ASP2CTAutoD1Source ASP2CTAutoD2Source ASP2CTAutoD4Source ASP2CTAutoD7Source ASP2CTAutotD0Target ASP2CTAutotD1Target ASP2CTAutotD2Target ASP2CTAutotD4Target ASP2CTAutotD7Target	Not used
SYSTEM	ASP2CTAutoD3Source	Source details for pillar two GloBE covered taxes automation. Default: DETAILST, P2DET
SYSTEM	ASP2CTAutoD5Source	Source segments for pillar two GloBE covered taxes automation. Default: SEGMENTST
SYSTEM	ASP2CTAutoD6Source	Source elements for pillar two GloBE covered taxes automation. Default (P2): SUMMELE, Book_Chart_of_Accounts, P2EoY Default (ASC): SUMMELE, Book_Chart_of_Accounts, GrsCY_ASC, GrsNPEqT_ASC, GrsNPOCI_ASC, P2EoY Default (IAS): SUMMELE, Book_Chart_of_Accounts, GrsCY_IAS, GrsEQ_IAS, GrsOCI_IAS, P2EoY
SYSTEM	ASP2CTAutotD3Target	Target detail for pillar two GloBE covered taxes automation. Default: SUMMDET Caution: Changing this value will require overriding all apps and reports.
SYSTEM	ASP2CTAutoD5Target	Target segment for pillar two GloBE covered taxes automation. Default SUMMSEG Caution: Changing this value will require overriding all apps and reports.
SYSTEM	ASP2CTAutoD6Target	Target element for pillar two GloBE covered taxes automations. Default: P2SUMM Caution: Changing this value will require overriding all apps and reports.
SYSTEM	ASP2FX	Enable foreign currency translation for constituent entities. Default: FALSE Caution: Setting this to TRUE will change all constituent entity input and calculations to be in functional currency. Any automations will occur in both functional currency and reporting currency.
SYSTEM	ASP2GIAutoAccountsSource	The source accounts for pillar two GloBE income automation. Default (P2): TRIALBAL Default (ASC): TRIALBAL, TaxIncome_ASC Default (IAS): TRIALBAL, TaxIncome_IAS
SYSTEM	ASP2GIAutoD0Source ASP2GIAutoD1Source ASP2GIAutoD2Source ASP2GIAutoD4Source ASP2GIAutoD7Source ASP2GIAutotD0Target ASP2GIAutotD1Target ASP2GIAutotD2Target ASP2GIAutotD4Target ASP2GIAutotD7Target
SYSTEM	ASP2GIAutoD3Source	Source details for pillar two GloBE income automation. Default: DETAILST
SYSTEM	ASP2GIAutoD5Source	Source segments for pillar two GloBE income automation. Default: SEGMENTST
SYSTEM	ASP2GIAutoD6Source	Source elements for pillar two GloBE income automation. Default (P2): SUMMELE, Book_Chart_of_Accounts Default (ASC Provision): SUMMELE, Book_Chart_of_Accounts, GrsCY_ASC, GrsNPEqT_ASC, GrsNPOCI_ASC Default (IAS Provision): SUMMELE, Book_Chart_of_Accounts, GrsCY_IAS, GrsEQ_IAS, GrsOCI_IAS
SYSTEM	ASP2GIAutotD3Target	Target detail for pillar two GloBE income automation. Default: SUMMDET Caution: Changing this value will require overriding all apps and reports.
SYSTEM	ASP2GIAutoD5Target	Target segment for pillar two GloBE income automation. Default SUMMSEG Caution: Changing this value will require overriding all apps and reports.
SYSTEM	ASP2GIAutoD6Target	Target element for pillar two GloBE income automations. Default: P2SUMM Caution: Changing this value will require overriding all apps and reports.
SYSTEM	ASP2ReportingCurrency	Reporting currency for pillar two. This currency will be used for all input and calculations. Note: This attribute is set by the manage constituent entities app using the currency set on P2JTotal.
SYSTEM	ASP2TMPAutoAccountsSource	The source accounts for pillar two GloBE temporary differences automation. Default (P2): TRIALBAL Default (ASC Provision): TRIALBAL, DefTax_ASC Default (ASC MRP): TRIALBAL, MSP_DefTax_ASC Default (IAS Provision): TRIALBAL, DefTax_IAS Default (IAS MRP): TRIALBAL, MSP_DefTax_IAS
SYSTEM	ASP2TMPAutoD0Source ASP2TMPAutoD1Source ASP2TMPAutoD2Source ASP2TMPAutoD4Source ASP2TMPAutoD7Source ASP2TMPAutotD0Target ASP2TMPAutotD1Target ASP2TMPAutotD2Target ASP2TMPAutotD4Target ASP2TMPAutotD7Target
SYSTEM	ASP2TMPAutoD3Source	Source details for pillar two GloBE temporary differences automation. Default: DETAILST
SYSTEM	ASP2TMPAutoD5Source	Source segments for pillar two GloBE temporary differences automation. Default: SEGMENTST
SYSTEM	ASP2TMPAutoD6Source	Source elements for pillar two GloBE temporary differences automation. Default (P2): SUMMELE, Book_Chart_of_Accounts Default (ASC): SUMMELE, Book_Chart_of_Accounts, GrsCY_ASC, GrsNPEqT_ASC, GrsNPOCI_ASC Default (IAS): SUMMELE, Book_Chart_of_Accounts, GrsCY_IAS, GrsEQ_IAS, GrsOCI_IAS
SYSTEM	ASP2TMPAutotD3Target	Target detail for pillar two GloBE temporary differences automation. Default: P2Det Caution: Changing this value will require overriding all apps and reports.
SYSTEM	ASP2TMPAutoD5Target	Target segment for pillar two GloBE temporary differences automation. Default SUMMSEG Caution: Changing this value will require overriding all apps and reports.
SYSTEM	ASP2TMPAutoD6Target	Target element for pillar two GloBE temporary differences automations. Default: P2EoY Caution: Changing this value will require overriding all apps and reports.
SYSTEM	ASP2TMPTPD3Source	Source details for transfer of temporary differences from Tax Provision to Pillar Two. Default: DETAILST
SYSTEM	ASP2TMPTPD5Source	Source segments for transfer of temporary differences from Tax Provision to Pillar Two. Default: SEGMENTST
SYMBOL	AZP2AutomationGroup	Not used
SYMBOL	AZP2EntityConstituentType	The type of entity. Values: Root, Jurisdiction, Constituent, JurisdictionCalc, Stateless Note: This attribute is set by the manage constituent entities app using the currency set on P2JTotal.
SYMBOL	AZP2EntityMain	The main entity for an entity that is a Permanent Establishment. Note: This attribute is set by the manage constituent entities app using the currency set on P2JTotal.
SYMBOL	AZP2EntityMNEParentType	The type of parent the constituent entity is. Values: Ultimate Parent Entity, Intermediate Parent Entity, Partially Owned Parent Entity, or blank Note: This attribute is set by the manage constituent entities app using the currency set on P2JTotal.
SYMBOL	AZP2EntityStatusType	Not used
SYMBOL	AZP2JointVentureGroup	Not used
SYMBOL	AZPillarTwo	Not used
SYMBOL	AZTaxCalcEnableActivePeriod	Indicates whether active period calculations are enabled on a period. Note: This attribute is set by rollover.
SYMBOL	AZTaxCalcEnableReturnPeriod	Indicates whether return period calculations are enabled on a period. Note: This attribute is set by rollover.
SYMBOL	AZTaxScenarioP2	Indicates if a scenario time period is active for Pillar Two.
SYMBOL	AZTaxScenarioTP	Indicates if a scenario time period is active for Tax Provision. Only applies if the system contains both Tax Provision and Pillar Two.
SYMBOL	ZGPNativeCurrency	The functional currency of the entity. Note: This attribute is set by the manage constituent entities app.

Initial Setup

The account hierarchies deployed contain structures that capture data as described in the Pillar Two Model Rules. Each account hierarchy is deployed with account structures aligned with the articles in the model rules. In cases where it may be desirable to add additional detail to sum up to specific amounts, a default leaf symbol is provided. You may want to add additional accounts and are free to do so using the provided apps.

Entities are managed using the Manage Constituent Entities app. This app is used to:

• Set the reporting currency (at P2JTotal)
• Add Pillar Two specific jurisdictions.
• Add a Constituent entity to a jurisdiction.
• Add a Stateless Constituent entity.
• Assign an existing Tax Provision entity to a Pillar Two Jurisdiction
• Assign an existing Transfer Pricing entity to a Pillar Two Jurisdiction
• Assign an existing Tax Provision entity as a Stateless Constituent entity.
• Assign an existing Transfer Pricing entity as a Stateless Constituent entity.
• Set the status of a jurisdiction or stateless constituent entity to indicate whether it is included or excluded.
  • This value can be different by period.
• Set the elections taken by a Jurisdiction or Constituent entity.
  • The elections taken can vary by period.
• Set a group for automation rules, which allows you to override automation rules for a set of entities.
  • To enable automation groups, you need to add groups in the Automation_Groups_P2 hierarchy using Application Administrator.

Accounts are managed using hierarchy specific apps. To add additional detail to the default account structures, use:

• Manage GloBE Revenue Accounts to add additional detail to the revenue structure.
• Manage GloBE Income Accounts to add additional detail to the income structure and Manage GloBE Income Automations to define calculations for any accounts for which source data exists.
• Manage GloBE Adjusted Covered Taxes Accounts to add additional detail to the covered taxes structure and Manage GloBE Covered Taxes Automations to define calculations for any accounts for which source data exists.
• Manage GloBE Substance-Based Income Exclusion Accounts to add additional detail to the structure.
• Manage GloBE Temporary Differences Accounts to add additional detail to the income structure and Manage GloBE Temporary Differences Automations to define calculations for any accounts for which source data exists.

Configuring user symbol access

Input apps and reports require specific symbol access to allow the user to modify or review data for a jurisdiction or a constituent entity.

To use	Dimension	Minimum access required
Constituent entity input apps (P2200, P2205, P2210, P2300, P2310)	ENTITIES	Write access to a constituent entity. Read access to the constituent entity jurisdiction parent.
	CURRENCIES	If currency translation for constituent entities is disabled, write access to the reporting currency defined by system attribute ASP2ReportingCurrency. If currency translation for constituent entities is enabled, write access to the functional currency defined by the symbol attribute ZGPNativeCurrency.
Constituent entity reports (P2200, P2205, P2210, P2300, P2310)	ENTITIES	Read access to a constituent entity.
	CURRENCIES	If currency translation for constituent entities is disabled, read access to the reporting currency defined by system attribute ASP2ReportingCurrency. If currency translation for constituent entities is enabled, read access to the functional currency defined by the symbol attribute ZGPNativeCurrency.
Jurisdiction input apps (P2510)	ENTITIES	Write access to the jurisdiction parent (0 levels). Write access to the jurisdiction calculation entity.
	CURRENCIES	Write access to the reporting currency defined by system attribute ASP2ReportingCurrency.
Jurisdiction reports (P2500, P2510)	ENTITIES	Read access to the jurisdiction parent (0 levels).
	CURRENCIES	Read access to the reporting currency defined by system attribute ASP2ReportingCurrency.
Jurisdiction detail reports (P2520)	ENTITIES	Read access to the jurisdiction parent and its constituent entities.
	CURRENCIES	Read access to the reporting currency defined by system attribute ASP2ReportingCurrency.
Rate inputs (P2501, P2502)	ENTITIES	Write access to DIM2SET.
	DETAILS	Write access to DIM3SET.
	CURRENCIES	Write access to DIM4SET.
	SEGMENTS	Write access to DIM5SET.

Configuring automation event rules

If you make changes to the source attributes for automation, you may need to modify the standard event rules, or add additional rules.

For example, if you modify the source details for income automation (via system attribute ASP2GIAutoD3Source), to use a hierarchy other than DETAILST, you will need to modify the income automation rules and calculation settings for the change.

To modify the event rules:

1. Open Longview Application Administrator.
2. Select Rules from the Server Explorer.
3. Navigate to the appropriate rule and update the triggering symbols as required.

If you need to add additional rules, be sure not to conflict with the ranges reserved for standard tax, transfer pricing and pillar two model rules. See the implementer’s guide for more detail.

To modify the calculation settings:

1. Open Longview Client.
2. Navigate to Global Transparency > Administration.
3. Expand Calculations and click on Tax Calculations.
4. Enable Show Settings in the administration toolbar.
5. Locate the automation calculation under Pillar Two to be modified and check the box in Active Period. Double-click in the cell for the dimension to update to activate the cell.
6. Click in the cell to edit and press the End key.
7. Enter the additional symbols into the list (separated with a comma and ending with ### to include all leaf symbols under a parent).
8. Repeat steps 5 to 7 for any other dimensions that require modification.
9. Click Save.

Configuring source details and segments for temporary differences

Temporary differences balances are transferred to Pillar Two using the values in total details (DETAILST) and total segments (SEGMENTST). If you want to transfer balances from tax provision using different details and segments you can modify the configuration.

To modify the source details for temporary differences:

1. Open Longview Application Administrator.

2. In server explorer navigate to Attributes > System.

3. Locate the ASP2TMPTPD3Source system attribute.

4. Right-click on the attribute and select Set value…. The attribute values dialog appears.

5. In the Enter New Value field, enter the name of the detail symbol to use as a source for temporary difference transfers. Alternatively, you can click the … button to locate the symbol using the symbol selector.

6. Click the Add to list button to add the symbol to the list of source details.

7. Repeat for each symbol you wish to use as a source.

8. Click OK. The attribute values dialog closes.

9. In the Actions menu, select Maintenance to toggle maintenance mode off and apply the changes.

10. If temporary differences have already been transferred to Pillar Two with the previous settings, you will need to trigger the ‘Temporary Differences Gross Transfer’ and ‘Temporary Differences Net Transfer’ calculations using the Tax Calculations interface in Longview Client.

To modify the source segments for temporary differences:

1. Open Longview Application Administrator.

2. In server explorer navigate to Attributes > System.

3. Locate the ASP2TMPTPD5Source system attribute.

4. Right-click on the attribute and select Set value…. The attribute values dialog appears.

5. In the Enter New Value field, enter the name of the segment symbol to use as a source for temporary difference transfers. Alternatively, you can click the … button to locate the symbol using the symbol selector.

6. Click the Add to list button to add the symbol to the list of source details.

7. Repeat for each symbol you wish to use as a source.

8. Click OK. The attribute values dialog closes.

9. In the Actions menu, select Maintenance to toggle maintenance mode off and apply the changes.

10. If temporary differences have already been transferred to Pillar Two with the previous settings, you will need to trigger the ‘Temporary Differences Gross Transfer’ and ‘Temporary Differences Net Transfer’ calculations using the Tax Calculations interface in Longview Client.

To trigger the transfer of temporary differences to Pillar Two:

1. Launch Longview Client.

2. Select the Administration category from the left navigation bar.

3. Expand Calculations in the navigation pane.

4. Click Tax Calculations. The Tax Calculations interface appears in the workspace.

5. In the Entities field, select the entities you want to calculate. To calculate all entities at once select P2JTotal.

6. Click Update to apply your selection.

7. In the Currencies field, select Currencies and click Update to apply your selection.

8. Check the Active Period box for Temporary Difference Gross Transfer.

9. Check the Active Period box for Temporary Difference Net Transfer.

10. Click Run Calculations. The temporary difference transfer calculations execute.

11. Click Close on the confirmation message.

Foreign Exchange

In pillar two, foreign exchange is disabled by default. It can be enabled by setting the value of system attribute ASP2FX to TRUE.

The impact of this setting is as follows:

ASP2FX Value = FALSE	ASP2FX Value = TRUE
Constituent entity input is done in reporting currency, as defined by the system attribute ASP2ReportingCurrency	Constituent entity input is done in functional currency as defined by the symbol attribute ZGPNativeCurrency value set on the constituent entity
Constituent entity calculations are done in reporting currency, as defined by the system attribute ASP2ReportingCurrency	Constituent entity calculations are done in functional currency as defined by the symbol attribute ZGPNativeCurrency value set on the constituent entity
Automations are processing in reporting currency	Automations are processed in functional currency and reporting currency.
No foreign currency translation	Constituent entity input and calculation results are translated to the reporting currency
Jurisdiction level input and calculations are done in reporting currency, as defined by the system attribute ASP2ReportingCurrency	Jurisdiction level input and calculations are done in reporting currency, as defined by the system attribute ASP2ReportingCurrency

By default, all reports in Pillar Two use reporting currency. If you enable foreign exchange you may want to update the constituent entity reports to use functional currency or create duplicate reports for analysts who will be working in functional currency.

Configuring foreign exchange rates used in Pillar Two

The foreign exchange rates used in Pillar Two are configured using:

• XCC0101/XCC1101 – FX Method Rate Table found in Global Transparency > Administration > Foreign Exchange

If you have tax provision this table will also include the configuration for tax provision elements. Method rate configuration for Pillar Two is found in two groups:

• TRNELE_P2 – which contains the elements used for temporary differences.

• TRNELE_SUMM – which contains the pillar two summary element.

By default, all pillar two elements are translated using the Pillar Two foreign exchange rate.

To modify the rate used for an element:

1. Double-click on the rate you wish to change.
2. Open the selection list that appears in the cell.
3. Select a different rate.
4. Repeat for other elements you wish to modify,
5. Once finished updating rates used click Submit to save the changes.

To apply the changes to existing data, you will need to manually execute Pillar Two foreign exchange calculations from the Tax Calculations interface.

Updating foreign exchange rates in Pillar Two

Foreign exchange rates for Pillar Two are updating using:

• P2100 – FX Rates – Pillar Two found in Global Transparency > Data Collection > Pillar Two > Rates.

When you click on P2100 – FX Rates – Pillar Two you will be prompted to select an entity from your available list of entities, unless you have a default input entity defined in your default symbols configuration. The input will open in the workspace and display the foreign exchange rates for each translation in the system for the current period. Your selected entity will be displayed in the rows dimension, along with any of its descendants, and the translations will be displayed in the columns dimension.

Note: If you are using multiple exchange rates for Pillar Two the input app may be configured with a different orientation.

Enter the appropriate translation rates (for example, USD from CAD) for each entity and when you are finished, click Submit.

Constituent Entities

The Manage Constituency Entities app is used to:

• Manage the jurisdictions in scope for Pillar Two Model Rules
• Manage the constituent entities within jurisdictions for Pillar Two Model Rules
• Manage the stateless constituent entities in scope for Pillar Two Model Rules
• Manage the elections for jurisdictions and stateless constituent entities in scope for Pillar Two model rules, by period.
• Export the jurisdictions, constituent entities, and their elections to a file for import to another system or period.

In addition, for a jurisdiction, you can set its status (for a specific period) to:

• Included – to include the jurisdiction and its constituent entities in Pillar Two Model Rules calculations.
• Excluded (Safe Harbour) – to exclude the jurisdiction and its constituent entities from Pillar Two Model Rules calculations.
• Excluded (de minimis) – to exclude the jurisdiction and its constituent entities from Pillar Two Model Rules calculations.

You can also take specific elections for jurisdictions and stateless entities. These elections will protect specific accounts from input as outlined in GloBE Income, Adjusted Covered Taxes, and Adjusted Jurisdictional Top-up Tax.

Understanding the constituent entity structure

The constituent entity root symbol is P2JTotal and contains jurisdictions, constituent entities, stateless constituent entities, and jurisdictional calculation entities.

The constituent entity structure has the following restrictions:

• Symbols directly under the root (P2JTotal) must be either:
  • A jurisdiction
  • A stateless constituent entity
• Symbols under a jurisdiction must be:
  • A constituent entity
  • A jurisdictional calculation entity

Jurisdictions

A jurisdiction is parent entity directly under the root symbol that has one or more constituent entities and a jurisdictional calculation entity as its direct descendants.

A jurisdiction can have a status of Included, Excluded – de minimis, or Excluded – safe harbour. Excluded jurisdictions and all their constituent entities are excluded from calculations.

Elections are set at the jurisdiction level for convenience, as any election taken by a constituent entity applies to all constituent entities in the same jurisdiction.

The Type, Main Entity and MNE Group Parent fields are not defined for a jurisdiction.

Jurisdictional calculation entity

A jurisdictional calculation entity is a leaf entity under a jurisdiction entity that is managed by the system. This entity holds the results of jurisdiction-level calculations (top-up tax, ETR and top-up tax percentage).

The description and sort order of this entity can be modified.

Constituent entities

A constituent entity is leaf entity under a jurisdiction parent entity.

A constituent entity can have a status of Included, Excluded Entity or Election. Excluded constituent entities are excluded from calculations, but not rollup.

The status of a constituent entity affects other fields as follows:

• A constituent entity with a status of Included can optionally have a type of Hybrid, Investment, Permanent Establishment, Reverse-Hybrid, or Tax Transparent. The default is blank, which indicates a constituent entity that does not meet the criteria for any of the specific types outlined by the Pillar Two model rules.
  • An Included entity that is a permanent establishment must indicate its Main Entity in the provided field.
• A constituent entity with a status of Excluded Entity must have a type of 1.5.1 Election or 1.5.2 Election to indicate which subsection of the Excluded Entity section of model rules pertain to it.
• A constituent entity with a status of Election must have a type of 1.5.3 Election indicating that it would have been excluded under section 1.5.2. but is being included by election.

Any constituent entity other than an entity that is an Investment Entity or Permanent Establishment can be an MNE Group Parent. For each entity that is a group parent indicate whether it is:

• The Ultimate Group Parent (only a single entity can have this designation)
• An Intermediate Parent Entity
• A Partially-Owned Parent Entity

For further details see GloBE Model Rules for Pillar Two.

Stateless constituent entities

A stateless constituent entity is a leaf entity not under any jurisdiction parent entity.

A stateless constituent entity can have a status of Included or Excluded – safe harbour.

The status of a stateless constituent entity affects other fields as follows:

• A stateless constituent entity can optionally have a type of Hybrid,  Permanent Establishment, Reverse-Hybrid, or Tax Transparent. The default is blank, which indicates a stateless constituent entity that does not meet the criteria for any of the specific types outlined by the Pillar Two model rules.

Any stateless constituent entity other than an entity that is an entity that is a Permanent Establishment can be an MNE Group Parent. For each entity that is a group parent indicate whether it is:

• The Ultimate Group Parent (only a single entity can have this designation)
• An Intermediate Parent Entity
• A Partially-Owned Parent Entity

For further details, see GloBE Model Rules for Pillar Two.

Importing constituent entities

The Import option in the Manage GloBE Constituent Entities dialog allows you to import jurisdictions, constituent entities, and their related settings from a .csv file.

To import constituent entities:

1. Click on Manage constituent entities. A prompt appears.
2. Select the Import option.
3. Select the file you wish to import.
4. To skip confirmation of each new parent assignment, check the Automatically confirm parent assignment option.
5. Select the target period for jurisdiction and constituent entity settings contained in the source file.
6. Click OK. A table displays showing the summary of all actions performed by the import.

Note:

• If there are any issues with the file, a table will be displayed indicating the issues. No changes will be made.

• The columns in the file will differ depending on whether any automation groups for pillar two have been created.

.csv file example (without automation groups):

.csv file example (with automation groups):

where:

Parameter	Description
Entity	The name of the jurisdiction or constituent entity symbol.
Description	The description of the entity.
Parent	The name of a parent to assign the entity to. The entity will become a child of the specified parent, and the values in the parent will be calculated from all its children.
Sort Order	Indicates the order of the entity under the parent, with lower numbers ordered before higher numbers. You can specify NULL or 0, which will assign the sort order as 0, which results in the symbol being sorted by when it was created.
Currency	The functional currency of the jurisdiction or constituent entity symbol.
Status	The status of the jurisdiction or constituent entity.
Type	The type for a constituent entity or stateless constituent entity.
Main Entity	The main entity for a constituent entity or stateless constituent entity if its Type is Permanent Establishment. Leave blank otherwise.
MNE Group Parent	The type of parent a constituent entity or stateless constituent entity is. Leave blank for an entity that is not a parent.
Automation Group	The name of the automation group that this entity belongs to for pillar two automations. Automation group can be set on a constituent entity or stateless constituent entity.
[3.2.2] Stock-Based Compensation Election	Indicates whether a jurisdiction or stateless constituent entity is taking this election in the target period. 1 = taking election 0 = not taking election
[3.2.5] Use Realisation Principle Election	Indicates whether a jurisdiction or stateless constituent entity is taking this election in the target period. 1 = taking election 0 = not taking election
[3.2.6] Use Aggregate Asset Gain Election	Indicates whether a jurisdiction or stateless constituent entity is taking this election in the target period. 1 = taking election 0 = not taking election
[4.4.7] Use Unclaimed Accrual Election	Indicates whether a jurisdiction or stateless constituent entity is taking this election in the target period. 1 = taking election 0 = not taking election
4.5] GloBE Loss Election	Indicates whether a jurisdiction or stateless constituent entity is taking this election in the target period. 1 = taking election 0 = not taking election
[5.3.1] Do Not Apply Substance-Based Income Exclusion	Indicates whether a jurisdiction or stateless constituent entity is taking this election in the target period. 1 = taking election 0 = not taking election
[7.3.1] Add Deemed Distribution Tax to Adjusted Covered Taxes	Indicates whether a jurisdiction or stateless constituent entity is taking this election in the target period. 1 = taking election 0 = not taking election

Managing constituent entities

To manage constituent entities:

1. Click on Manage constituent entities, a prompt appears.
   1. Select the Manage option.
   2. Select the entity you wish to manage.
   3. Select the period you wish to manage. This affects how the election settings are retrieved and stored.
   4. Click OK.
2. The Manage constituent entities table appears. Do one of the following actions:
   1. Add a jurisdiction.
   2. Add a new stateless constituent entity.
   3. Add a new constituent entity to a jurisdiction.

Set the reporting currency

All pillar two operations are done in reporting currency. As such, it is necessary to define the reporting currency of the system.

To set the reporting currency:

1. On the first row in the table (P2JTotal).
   1. Select the reporting currency in the Currency field.
   2. Click Apply. The reporting currency system attribute ASP2ReportingCurrency will be updated. The value will be the source currency equivalent if a reporting currency is selected (i.e., if TCAD is selected the attribute value will be CAD).

This currency is used for all input, reports, and calculations.

Add a jurisdiction

To add a jurisdiction:

1. Click the Add Jurisdiction button. A dialog appears.
2. Complete the following fields:
   1. Description: Enter the description for the jurisdiction.
   2. Sort Order: Enter the sort order to determine the order of the jurisdiction under the P2JTotal root symbol.
   3. CURRENCY: Select the functional currency for the jurisdiction. This can be a reporting currency if the jurisdiction contains constituent entities with different functional currencies.
3. Click OK. The jurisdiction and its calculation symbol are added to the table.
   • The calculation symbol is used to store the results of the ETR and Top-up tax calculations.
   • The jurisdiction is added as Included for Pillar Two calculations with no elections taken.
4. Update the status and elections as required. Type, main entity and MNE group parent are not used for jurisdictions.

Note: If a jurisdiction is set to “Excluded – de minimis” or “Excluded – safe harbour,” no ETR, top-up tax percentage, or top-up tax calculations will be executed.

Add a stateless constituent entity

To add a stateless constituent entity:

1. Right-click on the row selector for P2JTotal and select Add Constituent Entity. The Stateless Constituent Entity dialog appears.
2. Do one of the following:
   1. Select New to add a new entity to the system. Complete the following fields:

      • ENTITIES: Enter the name of the new stateless constituent entity.

      • Description: Enter a description of the new stateless constituent entity.

      • Sort Order: Enter the sort order to determine the order the entity appears under the Total Jurisdictions root. Higher Sort Order values appear later. 0 Sort order values appear after all non-zero values, in order of creation.

      • CURRENCY: Select the functional currency of the stateless constituent entity.

        Note: All Pillar Two model rules input, and calculations are done in the reporting currency determined by the Total Jurisdictions functional currency.

   2. Select Assign to select an existing tax provision or transfer pricing entity. Complete the following fields:

      • ENTITIES: Select an existing leaf entity using the symbol selector.

      • Sort Order: Enter the sort order to determine the order the entity appears under the Total Jurisdictions root. Higher Sort Order values appear later. 0 Sort Order values appear after all non-zero values, in order of creation.

      • CURRENCY: Is automatically set using the existing entity’s functional currency.

3. Click OK. The stateless constituent entity is added to the table according to the specified sort order.
4. Update the status, type, and elections as required.
5. If the type is not “Permanent Establishment”, you can also set the MNE Group Parent to one of the following values:
   • Blank, if the entity is not a parent.
   • Ultimate Parent Entity if the entity is the ultimate parent of the group. This can only be specified on a single entity.
   • Intermediate Parent Entity if the entity is a parent, but not the ultimate parent of the group.
   • Partially Owned Parent Entity if the entity is a parent but is not the ultimate parent of the group and more than 20% of its ownership interests are held outside the MNE Group.
6. If the type is “Permanent Establishment”, you must select the Main Entity that includes the Financial Accounting Net Income or Loss of this entity in its financial statements.
7. If pillar two automation groups have been created in your system, you can also set an automation group.

Note: If a stateless constituent entity is set to “Excluded – safe harbour,” no ETR, top-up tax percentage, or top-up tax calculations will be executed.

Add a constituent entity

To add a constituent entity:

1. Right-click on the row selector for a jurisdiction and select Add Constituent Entity. The Constituent Entity dialog appears.
2. Do one of the following:
   1. Select New to add a new entity to the system. Complete the following fields:

      • ENTITIES: Enter the name of the new constituent entity.

      • Description: Enter a description of the new constituent entity.

      • Sort Order: Enter the sort order to determine the order the entity appears under the Jurisdictions parent. Higher Sort Order values appear later. 0 Sort Order values appear after all non-zero values, in order of creation.

      • CURRENCY: Select the functional currency of the constituent entity.

        Note: All Pillar Two model rules input, and calculations are done in the reporting currency determined by the Total Jurisdictions functional currency.

   2. Select Assign to select an existing tax provision or transfer pricing entity. Complete the following fields:

      • ENTITIES: Select an existing leaf entity using the symbol selector.

      • Sort Order: Enter the sort order to determine the order the entity appears under the jurisdiction parent. Higher Sort Order values appear later. 0 Sort Order values appear after all non-zero values, in order of creation.

      • CURRENCY: Is automatically set using the existing entity’s functional currency.

3. Click OK. The constituent entity is added to the table according to its parent and specified sort order.
4. Update the status and type, as required.
5. If the type is not “Permanent Establishment” and is not “Investment Entity”, you can also set the MNE Group Parent to one of the following values:
   • Blank, if the entity is not a parent.
   • Ultimate Parent Entity if the entity is the ultimate parent of the group. This can only be specified on a single entity.
   • Intermediate Parent Entity if the entity is a parent, but not the ultimate parent of the group.
   • Partially Owned Parent Entity if the entity is a parent but is not the ultimate parent of the group and more than 20% of its ownership interests are held outside the MNE Group.
6. If the type is “Permanent Establishment”, you must select the Main Entity that includes the Financial Accounting Net Income or Loss of this entity in its financial statements.
7. If pillar two automation groups have been created in your system, you can also set an automation group.

Exporting constituent entities

The Export option in the Manage GloBE Constituent Entities dialog allows you to export jurisdictions, constituent entities, and their related settings from the database to a .csv file.

To export constituent entities:

1. Click on Manage constituent entities, a prompt appears.
   1. Select the Export option.
   2. Specify the name of the file. Do one the following:
      • Enter the name of the file directly and it will be stored within the Documents\Longview folder.
      • Use the Browse button to select file location and specify its name.
   3. Select the entity you wish to export.
   4. Select the period you wish to export. This election settings for the selected period are exported.
   5. Click OK.
2. The confirmation dialog appears.
   1. Click the View File button to open the file in your default csv file viewer.
   2. Click Close to exit.

Note: The columns in the file will differ depending on whether any automation groups for pillar two have been created.

Invisible: New for v24.4Migrating Election Settings

As of release 24.4 the jurisdiction election settings set in the Manage Constituent Entities editor are no longer used and have been replaced with the settings in the Manage Jurisdiction Elections editor. You can migrate the existing jurisdiction elections using the Migrate Jurisdicton Settings app. This process replaces any settings previously configured using Manage Jurisdiction Elections.

To migrate jurisdiction election settings

1. Open Longview Client.
2. Navigate to the Global Transparency module.
3. Select the Administration category.
4. Expand the System folder and click on Migrate Jurisdiction Settings. A prompt appears.
5. Read the prompt carefully and click OK to proceed.
6. A confirmation message appears. Click OK.

Constituent Entity Elections

Elections for constituent entities are managed using:

• Manage Constituent Entity Elections app found in Global Transparency > Administration > Pillar Two > Entities.

To update constituent entity elections:

1. Click on Manage Constituent Entity Elections in the navigation pane.

2. When prompted select an entity and add a period.

   1. If you select a parent entity all constituent entities under the parent will be displayed.

   The table appears.

3. Update any election settings as required.

4. Click Apply to save the changes.

The following elections are available for a constituent entity:

Election	Description
[1.5.3] Not treating an Entity as an Excluded Entity	Indicates whether an excluded constituent entity is taking this election in the target period. Only applies to excluded entities.
[3.2.1] Debt Release election	Indicates whether a constituent entity is taking this election in the target period. If this election is taken input and automation will be allowed for accounts under P2GI3.2.1.DR (3.2.1 - Debt Releases)
[3.2.1(b)] Inclusion of all dividends with respect to Portfolio Shareholdings	Indicates whether a constituent entity is taking this election in the target period.
[3.2.1(c)] Treating foreign exchange gains or losses attributable to hedging as an Excluded Equity Gain or Loss	Indicates whether a constituent entity is taking this election in the target period.
[4.4.7] Use Unclaimed Accrual Election	Indicates whether a constituent entity is taking this election in the target period.
[6.3.4] Fair value election	Indicates whether a constituent entity is taking this election in the target period.
[7.5] Investment entity tax transparency election	Indicates whether a constituent entity is taking this election in the target period. Only applies to investment and insurance investment entities.
[7.6] Taxable distribution method election	Indicates whether a constituent entity is taking this election in the target period. If this election is taken input and automation will be allowed for accounts under P2GI7.6.1 (7.6.1 - Taxable Distribution Method Election)

Jurisdiction Elections

Elections and settings for jurisdictions and stateless entities are managed using:

• Manage Jurisdiction Elections app found in Global Transparency > Administration > Pillar Two > Entities.

To update jurisdiction elections:

1. Click on Manage Constituent Entity Elections in the navigation pane.

2. When prompted, select a period.

   The table appears.

3. Update any jurisdiction and election settings, as required.

4. Click Apply to save the changes.

The following settings and elections are available for a jurisdiction:

Election	Description
Sub-group	Indicates if the entities in this jurisdiction compose a sub-group for GloBE purposes. Leave this selection blank if there are no sub-groups in the jurisdiction.
TIN	Enter the tax identification number of the constituent entity at the top of the ownership structure, if this jurisdiction is a sub-group. Leave blank otherwise.
Applicable rules	Select each of the GloBE rules that apply to this jurisdiction.
Safe harbour exclusion applied	If this jurisdiction is excluded due to being a safe harbour, select the safe harbour that applies.
[3.2.1(c)] Equity Investment Inclusion Election	Indicates whether the jurisdiction is taking this election in the target period.
[3.2.2] Stock-based compensation election	Indicates whether the jurisdiction is taking this election in the target period.
[3.2.5] Realisation principle election	Indicates whether the jurisdiction is taking this election in the target period.
[3.2.6] Aggregate asset gain election	Indicates whether the jurisdiction is taking this election in the target period.
[3.2.8] Intra-group transactions election	Indicates whether the jurisdiction is taking this election in the target period.
[4.5] GloBE Loss election	Indicates whether the jurisdiction is taking this election in the target period.
[4.6.1] Immaterial decrease in Covered Taxes election	Indicates whether the jurisdiction is taking this election in the target period.
[5.3.1] Election to not apply the Substance-based Income Exclusion	Indicates whether the jurisdiction is taking this election in the target period.
[7.3.1] Deemed Distribution Tax election	Indicates whether the jurisdiction is taking this election in the target period.

GloBE Revenue Accounts

The Manage GloBE Revenue Accounts app is used to:

• Manage the revenue accounts in scope for Pillar Two Model Rules.
• Export the accounts to a file for import to another system.
• Import accounts from a file to update the GloBE Revenue structure.

The Manage GloBE Revenue Accounts app provides the ability to create and modify custom accounts as well as the ability to edit the properties of existing accounts where permitted.

Understanding the GloBE revenue account structure

The GloBE Revenue Account root symbol is P2REV and the structure of the hierarchy follows the articles outlined in section 3 of the OECD’s Model Globe Rules.

This hierarchy contains some out of box accounts that are used by the system for reporting and calculations. Certain out of box accounts allow for some modifications whereas others can not be changed.

The hierarchy root symbol (P2REV):

• Cannot be deleted.
• Cannot have new symbols assigned to it.

The following accounts are protected:

• P2REV3.2.1
• P2REV3.2

These symbols:

• Cannot be deleted.
• Cannot be modified.
• Cannot have new symbols assigned to them.
• Cannot be assigned to a different parent.

The following symbols are protected from being deleted and modified:

• P2REV3.1.1
• P2REV3.1.2
• P2REV3.2.1.B
• P2REV3.2.1.C
• P2REV3.2.1.D
• P2REV3.2.1.E
• P2REV3.2.1.F
• P2REV3.2.1.H
• P2REV3.2.3
• P2REV3.2.8
• P2REV3.2.9
• P2REV3.3
• P2REV3.4
• P2REV3.5
• P2REV6.2
• P2REV7.1
• P2REV7.6.1

Importing GloBE revenue accounts

The import option in the Manage GloBE Revenue Accounts dialog allows you to create and update GloBE Revenue accounts in the database from a .csv file.

To import accounts:

1. Click on Manage GloBE Revenue Accounts. A prompt appears.
2. For Option, select Import.
3. Select the .csv file to import from.
4. To skip confirmation of each new parent assignment, check the Automatically confirm parent assignment option.
5. Click OK. A table will be displayed showing the summary of all actions performed by the import.

Note: If there are any issues with the file, a table will be displayed indicating the issues. No changes will be made. See Understanding the GloBE revenue account structure for which accounts allow for child accounts to be created below them.

.csv file example:

where:

Parameter	Description
Name	The name of the account symbol.
Description	The description of the account.
Parent	The name of a parent to assign the account to. The account will become a child of the specified parent, and the values in the parent will be calculated from all its children.
Sort Order	Indicates the order of the account under the parent, with lower numbers ordered before higher numbers. You can specify NULL or 0, which will assign the sort order as 0, which results in the symbol being sorted by when it was created.

Managing GloBE revenue accounts

The Manage option in the Manage GloBE Revenue Accounts dialog allows you to create, update and delete accounts from within the Manage GloBE Revenue Accounts table.

To manage accounts:

1. Click on Manage GloBE Revenue Accounts. A prompt appears.
2. For Option, select Manage.
3. Select the GloBE revenue accounts to manage. In the Manage GloBE Revenue Accounts table, the hierarchy of the account selected is displayed.

Working with the hierarchy

The Manage GloBE Revenue Accounts table displays the selected account in a hierarchical view. The view is initially expanded two levels below the selected account.

To change the level of expansion:

• Click a collapsed hierarchy icon to expand the hierarchy one level below the selected symbol.
• Click an expanded hierarchy icon to collapse the hierarchy to the selected symbol.
• Right-click on the top row and select one of these options:
  • Expand All for Selected Row: Expands the entire hierarchy below the selected symbol.
  • Collapse All: Collapses the entire hierarchy.
• Right-click on a parent row and select one of these options:
  • Expand All for Selected Row: Expands the entire hierarchy below the selected symbol.
  • Collapse All: Collapses the entire hierarchy.
  • Collapse Parent: Collapses the hierarchy to the parent of the selected symbol.
• Right-click on a leaf row and select one of these options:
  • Collapse All: Collapses the entire hierarchy.
  • Collapse Parent: Collapses the hierarchy to the parent of the selected symbol.

Adding an account

To add a new account:

1. Select a row in the table. The new account will be assigned as a child of the selected account.

   Note: You can add a new account that has similar settings to an existing account by selecting a row and clicking duplicate. See Understanding the GloBE revenue account structure for which accounts can have new child accounts created below them.

2. Click Add. The Add dialog appears.
3. Fill in the following fields:

   1. Name: Enter the name of the new account. The name of the account is limited to 31 characters.

   2. Description: Enter a description for the new account. The description of the account is limited to 100 characters.

   3. Parent: Select or enter the name of the parent to assign the new account to.

      Note: You can also click the search button to open the symbol selector dialog to access advanced search options.

   4. Sort Order: Enter a number to define the order of the new account under the parent. Accounts are sorted from low to high. Accounts added with a sort order of 0 will appear last, in the order the account was created.

4. Click OK to add the new symbol to the table.

   Note: Accounts are not added to the database until you click Apply.

Modifying an existing account

You can change the properties of an existing account:

1. Modify the description by editing the value in the Description cell.
2. Change the order the account appears under its parent by modifying the sort order value.
3. To change the parent of an account:
   1. Select the row in the table.
   2. Click Edit. The Edit dialog appears.
   3. Enter or select a new parent.
   4. Click OK.

No changes are made to the database until you click Apply.

Note: See Understanding the GloBE revenue account structure for which accounts and properties can be modified.

Applying changes

To apply changes to the accounts click Apply.

For new rows in the table:

1. Each new account will be added under the selected parent symbol.

For modified accounts:

1. Any description changes will be applied.
2. If the parent account is changed, the account will be reassigned to the new parent with the specified sort order.
3. Any changes to the sort order (same parent account) will be applied.

Results:

1. All actions performed are presented at the end of processing with:
   1. Each row identified by its symbol name.
   2. The action performed or the reason any error occurred.
2. Any valid changes, not cancelled, are applied.

Refreshing the accounts

1. Click Refresh to refresh the list of accounts.
2. Click Symbols to change the selected account and refresh the list of accounts.

In either case, if there are any unapplied changes, you will be prompted to apply or discard any changes that have not yet been applied.

• Choose Apply Changes to apply any changes made, then refresh the list of accounts. If there are any errors the refresh will not be performed.
• Choose Discard Changes to discard any changes made, then refresh the list of accounts.
• Click Cancel to return to the table without refreshing the list of accounts.

Exporting from the GloBE revenue accounts table

Click Export to export from the accounts table to a .csv file.

1. Select the .csv file to export to.

   Note: If the file selected does not currently exist, it will be created during the export process.

2. Click OK. A confirmation dialog will appear.
3. Click View File to view the exported file.

Exporting GloBE revenue accounts

The Export option in the Manage GloBE Revenue Accounts dialog allows you to export revenue accounts and their related settings from the database to a .csv file.

To export accounts:

1. Click on Manage GloBE Revenue Accounts. A prompt appears.
2. For Option, select Export.
3. Select the .csv file to export to.

   Note: If the file selected does not currently exist, it will be created during the export process.

4. Select symbols to export.
5. Click OK. A confirmation dialog will appear.
6. Click View File to view the exported file.

GloBE Income Accounts

The Manage GloBE Income Accounts app is used to:

• Manage the income accounts in scope for Pillar Two Model Rules.
• Export the accounts to a file for import to another system.
• Import accounts from a file to update the GloBE Income structure.

The Manage GloBE Income Accounts app provides the ability to create and modify custom accounts as well as the ability to edit the properties of existing accounts where permitted.

Understanding the GloBE income account structure

The GloBE Income Account root symbol is P2GI and the structure of the hierarchy follows the articles outlined in section 3 of the OECD’s Model Globe Rules.

This hierarchy contains some out of box accounts that are used by the system for reporting and calculations. Certain out of box accounts allow for some modifications whereas others can not be changed.

The hierarchy root symbol (P2GI):

• Cannot be deleted.
• Cannot have new symbols assigned to it.

The following accounts are protected:

• P2GI3.2.1
• P2GI3.2

These symbols:

• Cannot be deleted.
• Cannot be modified.
• Cannot have new symbols assigned to them.
• Cannot be assigned to a different parent.

The following symbols are protected from being deleted and modified:

• P2GI3.1.1
• P2GI3.1.2
• P2GI3.2.1.A …P2GI3.2.1.I
• P2GI3.2.2…P2GI3.2.10
• P2GI3.3
• P2GI3.4
• P2GI3.5
• P2GI6.2
• P2GI7.1
• P2GI7.6.1

Note: Invisible: New for v24.4Any updates applied to the GloBE Income account hierarchy using the Import or Manage option will be applied automatically to the QDMTT Income hierarchy.

Importing GloBE income accounts

The import option in the Manage GloBE Income Accounts dialog allows you to create and update GloBE Income accounts in the database from a .csv file.

To import accounts:

1. Click on Manage GloBE Income Accounts. A prompt appears.
2. For Option, select Import.
3. Select the .csv file to import from.
4. To skip confirmation of each new parent assignment, check the Automatically confirm parent assignment option.
5. Click OK. A table will be displayed showing the summary of all actions performed by the import.

Note: If there are any issues with the file, a table will be displayed indicating the issues. No changes will be made. See Understanding the GloBE income account structure for which accounts allow for child accounts to be created below them.

.csv file example:

where:

Parameter	Description
Name	The name of the account symbol.
Description	The description of the account.
Parent	The name of a parent to assign the account to. The account will become a child of the specified parent, and the values in the parent will be calculated from all its children.
Sort Order	Indicates the order of the account under the parent, with lower numbers ordered before higher numbers. You can specify NULL or 0, which will assign the sort order as 0, which results in the symbol being sorted by when it was created.

Managing GloBE income accounts

The Manage option in the Manage GloBE Income Accounts dialog allows you to create, update and delete accounts from within the Manage GloBE Revenue Accounts table.

To manage accounts:

1. Click on Manage GloBE Income Accounts. A prompt appears.
2. For Option, select Manage.
3. Select the GloBE income accounts to manage. In the Manage GloBE Income Accounts table, the hierarchy of the account selected is displayed.

Working with the hierarchy

The Manage GloBE Income Accounts table displays the selected account in a hierarchical view. The view is initially expanded two levels below the selected account.

To change the level of expansion:

1. Click a collapsed hierarchy icon to expand the hierarchy one level below the selected symbol.
2. Click an expanded hierarchy icon to collapse the hierarchy to the selected symbol.
3. Right-click on the top row and select one of these options:
   • Expand All for Selected Row: Expands the entire hierarchy below the selected symbol.
   • Collapse All: Collapses the entire hierarchy.
4. Right-click on a parent row and select one of these options:
   • Expand All for Selected Row: Expands the entire hierarchy below the selected symbol.
   • Collapse All: Collapses the entire hierarchy.
   • Collapse Parent: Collapses the hierarchy to the parent of the selected symbol.
   • Expand All for Selected Row: Expands the entire hierarchy below the selected symbol.
   • Collapse All: Collapses the entire hierarchy.
   • Collapse Parent: Collapses the hierarchy to the parent of the selected symbol.
5. Right-click on a leaf row and select one of these options:
   • Collapse All: Collapses the entire hierarchy.
   • Collapse Parent: Collapses the hierarchy to the parent of the selected symbol.

Adding an account

To add a new account:

1. Select a row in the table. The new account will be assigned as a child of the selected account.

   Note:

   • You can add a new account that has similar settings to an existing account by selecting a row and clicking duplicate.

   • See Understanding the GloBE income account structure for which accounts can have new child accounts created below them.

2. Click Add. The Add dialog appears.
3. Fill in the following fields:

   1. Name: Enter the name of the new account. The name of the account is limited to 31 characters.

   2. Description: Enter a description for the new account. The description of the account is limited to 100 characters.

   3. Parent: Select or enter the name of the parent to assign the new account to.

      Note: You can also click the search button to open the symbol selector dialog to access advanced search options.

   4. Sort Order: Enter a number to define the order of the new account under the parent. Accounts are sorted from low to high. Accounts added with a sort order of 0 will appear last, in the order the account was created.

4. Click OK to add the new symbol to the table.

   Note: Accounts are not added to the database until you click Apply.

Modifying an existing account

You can change the properties of an existing account:

1. Modify the description by editing the value in the Description cell.
2. Change the order the account appears under its parent by modifying the sort order value.
3. To change the parent of an account:
   1. Select the row in the table.
   2. Click Edit. The Edit dialog appears.
   3. Enter or select a new parent.
   4. Click OK.

No changes are made to the database until you click Apply.

Note: See Understanding the GloBE income account structure for which accounts and properties can be modified.

Applying changes

To apply changes to the accounts click Apply.

For new rows in the table:

• Each new account will be added under the selected parent symbol.

For modified accounts:

• Any description changes will be applied.
• If the parent account is changed, the account will be reassigned to the new parent with the specified sort order.
• Any changes to the sort order (same parent account) will be applied.

Results:

• All actions performed are presented at the end of processing with:
  • Each row identified by its symbol name.
  • The action performed or the reason any error occurred.
• Any valid changes, not cancelled, are applied.

Refreshing the accounts

• Click Refresh to refresh the list of accounts.
• Click Symbols to change the selected account and refresh the list of accounts.

In either case, if there are any unapplied changes, you will be prompted to apply or discard any changes that have not yet been applied.

• Choose Apply Changes to apply any changes made, then refresh the list of accounts. If there are any errors the refresh will not be performed.
• Choose Discard Changes to discard any changes made, then refresh the list of accounts.
• Click Cancel to return to the table without refreshing the list of accounts.

Exporting from the GloBE income accounts table

Click Export to export from the accounts table to a .csv file.

1. Select the .csv file to export to.

   Note: If the file selected does not currently exist, it will be created during the export process.

2. Click OK. A confirmation dialog will appear.
3. Click View File to view the exported file.

Exporting GloBE income accounts

The Export option in the Manage GloBE Income Accounts dialog allows you to export income accounts and their related settings from the database to a .csv file.

To export accounts:

1. Click on Manage GloBE Income Accounts. A prompt appears.
2. For Option, select Export.
3. Select the .csv file to export to.

   Note: If the file selected does not currently exist, it will be created during the export process.

4. Select symbols to export.
5. Click OK. A confirmation dialog will appear.
6. Click View File to view the exported file.

Managing GloBE income automations

GloBE income accounts can be calculated rather than manually input or imported. The Manage GloBE income automations app allows you to set accounts to be calculated using source data from your trial balance or tax provision results.

GloBE income automations are period specific and can be overridden:

• For an entity.
• For an automation group if automation groups exist.
  • Entity overrides supersede automation group overrides.

To manage automations:

1. Click on Manage GloBE Income Automations. A prompt appears.
2. Select the GloBE income accounts to manage.
3. Select the period to update automations for. In the Manage GloBE Income Automations table, the current automations for the selected accounts are displayed.

Managing default settings

1. From the Default Settings tab, click Add to add automation default settings for an account. Automation settings are not added to the database until you click Apply.

Note: You can add settings on an account that has similar settings to another account by selecting an existing row and clicking duplicate.

2. For each account, fill in the following fields:

   1. Account: Select the account for which you would like to set default automation settings.

   2. Automate: Check this option if this account will be automated. For the default settings, the automation check box is selected by default. Automated accounts will have data automatically transferred from the defined source to the target account.

   3. %: Enter the percentage you want to apply to the source amount prior to transferring it to the target account. The % value entered must be a number between -100 and 100.

   4. Source Accounts: Specify the source account(s). You can select one or more parent or leaf symbols.

   5. Source DETAILS: Specify the source detail symbol(s). The source details column will display if attribute ASP2GIAutoD3Source is set to a parent symbol or contains multiple symbols.

   6. Target DETAILS: Specify the target detail. The target details column will display if ASP2TMPAutoD3Target is set to a parent symbol or contains multiple symbols.

   7. Source SEGMENTS: Specify the source segment symbol(s). The source segments column will display if attribute ASP2GIAutoD5Source is set to a parent symbol or contains multiple symbols.

   8. Source ELEMENTS: Specify the source element symbol(s). The source elements column will display if attribute ASP2GIAutoD6Source is set to a parent symbol or contains multiple symbols.

Managing override settings

1. From either the Group Override or Entity Override tab, click Add to add new override settings. Override settings are not added to the database until you click Apply.

Note:

• The Group Override tab is used to override account settings at an automation group level. This tab will only appear if you have Pillar Two automation groups set up in your system (under entity root symbol Automation_Groups_P2).

• The Entities Override tab is used to override account settings at an entity level. This tab will only appear if you have leaf entities under the P2JTotal structure.

2. For each account, fill in the following fields:

   1. Account: Select the account for which you would like to set override automation settings.

   2. Automation Group/Entity: If on the Group Override tab, select the automation group you would like to set override settings for. If on the Entity Override tab, select the entity you would like to set override settings for.

   3. Automate: Check this option if this account will be automated at the override level. Automated accounts will have data automatically transferred from the defined source to the target account.

   4. %: Enter the percentage you want to apply to the source amount prior to transferring it to the target account. The % value entered must be a number between -100 and 100.

   5. Source Accounts: Specify the source account(s). You can select one or more parent or leaf symbols.

   6. Source DETAILS: Specify the source detail symbol(s). The source details column will display if attribute ASP2GIAutoD3Source is set to a parent symbol or contains multiple symbols.

   7. Source SEGMENTS: Specify the source segment symbol(s). The source segments column will display if attribute ASP2GIAutoD5Source is set to a parent symbol or contains multiple symbols.

   8. Target DETAILS: Specify the target detail. The target details column will display if ASP2TMPAutoD3Target is set to a parent symbol or contains multiple symbols.

   9. Source ELEMENTS: Specify the source element symbol(s). The source elements column will display if attribute ASP2GIAutoD6Source is set to a parent symbol or contains multiple symbols.

Modifying an account

You can change the properties of an existing account:

• Change the automation setting on the account by checking or un-checking the automate option.
• Change the % to be used in the automation calculation by modifying the % value.
• Change the source account(s) by selecting different source account symbols.
• Change source details, segments, or elements symbol(s) by selecting different source symbols.

No changes are applied until you click Apply.

Applying changes

To apply changes to the automation settings, click Apply.

• Any changes to the ‘Automate’ setting will be applied.
• Any changes to the ‘%’ setting will be applied.
• Any changes to the ‘Source Accounts’ setting will be applied.
• Any changes to the source details, segments, or elements settings will be applied.

Refreshing the automations

Click Refresh to refresh the list of automation settings.

If there are any unapplied changes, you will be prompted to apply or discard any changes that have not yet been applied.

• Choose Apply Changes to apply any changes made, then refresh the list of automation settings. If there are any errors the refresh will not be performed.
• Choose Discard Changes to discard any changes made, then refresh the list of accounts.
• Click Cancel to return to the table without refreshing the list of accounts.

Deleting automation settings

You can delete an automation setting at the default automation group override or entity override level:

1. Highlight the row you want to delete.
2. Click the delete button.
3. Automation settings are not deleted until you click Apply.

GloBE Adjusted Covered Taxes Accounts

The Manage GloBE Adjusted Covered Taxes Accounts app is used to:

• Manage the covered taxes accounts in scope for Pillar Two Model Rules.
• Export the accounts to a file for import to another system.
• Import accounts from a file to update the GloBE Adjusted Covered Taxes structure.

The Manage GloBE Adjusted Covered Taxes Accounts app provides the ability to create and modify custom accounts as well as the ability to edit the properties of existing accounts where permitted.

Understanding the GloBE adjusted covered taxes account structure

The GloBE Adjusted Covered Taxes Account root symbol is P2CT and the structure of the hierarchy follows the articles outlined in section 4 of the OECD’s Model Globe Rules.

This hierarchy contains some out of box accounts that are used by the system for reporting and calculations. Certain out of box accounts allow for some modifications whereas others can not be changed.

The hierarchy root symbol (P2CT):

• Cannot be deleted.
• Cannot have new symbols assigned to it.

The following accounts are protected:

• P2CT4.1
• P2CT4.4
• P2CT4.4.6

These symbols:

• Cannot be deleted.
• Cannot be modified.
• Cannot have new symbols assigned to them.
• Cannot be assigned to a different parent.

The following symbols are protected from being deleted and modified:

• P2CT4.1.1
• P2CT4.1.2
• P2CT4.1.2.A
• P2CT4.1.2.D
• P2CT4.1.3
• P2CT4.1.3.A
• P2CT4.1.3.E
• P2CT4.2
• P2CT4.3
• P2CT7.3.1
• P2CT4.4.1
• P2CT4.4.1.A
• P2CT4.4.1.E
• P2CT4.4.2
• P2CT4.4.2.A
• P2CT4.4.2.C
• P2CT4.4.3
• P2CT4.4.4
• P2CT4.4.6
• P2CT4.4.7
• P2CT4.6.1
• P2CT4.6.2
• P2CT4.6.3
• P2CT4.6.4

Note: Invisible: New for v24.4Any updates applied to the Covered Taxes account hierarchy using the Import or Manage option will be applied automatically to the QDMTT Covered Taxes hierarchy.

Importing GloBE adjusted covered taxes accounts

The import option in the Manage GloBE Adjusted Covered Taxes Accounts dialog allows you to create and update GloBE Adjusted Covered Taxes accounts in the database from a .csv file.

To import accounts:

1. Click on Manage GloBE Adjusted Covered Taxes Accounts. A prompt appears.
2. For Option, select Import.
3. Select the .csv file to import from.
4. To skip confirmation of each new parent assignment, check the Automatically confirm parent assignment option.
5. Click OK. A table will be displayed showing the summary of all actions performed by the import.

   Note: If there are any issues with the file, a table will be displayed indicating the issues. No changes will be made. See Understanding the GloBE adjusted covered taxes account structure for which accounts allow for child accounts to be created below them.

.csv file example

where:

Parameter	Description
Name	The name of the account symbol.
Description	The description of the account.
Parent	The name of a parent to assign the account to. The account will become a child of the specified parent, and the values in the parent will be calculated from all its children.
Sort Order	Indicates the order of the account under the parent, with lower numbers ordered before higher numbers. You can specify NULL or 0, which will assign the sort order as 0, which results in the symbol being sorted by when it was created.

Managing GloBE adjusted covered taxes accounts

The Manage option in the Manage GloBE Adjusted Covered Taxes Accounts dialog allows you to create, update and delete accounts from within the Manage GloBE Adjusted Covered Taxes Accounts table.

To manage accounts:

1. Click on Manage GloBE Adjusted Covered Taxes Accounts. A prompt appears.
2. For Option, select Manage.
3. Select the GloBE adjusted covered taxes accounts to manage. In the Manage GloBE Adjusted Covered Taxes Accounts table, the hierarchy of the account selected is displayed.

Working with the hierarchy

The Manage GloBE Adjusted Covered Taxes Accounts table displays the selected account in a hierarchical view. The view is initially expanded two levels below the selected account.

To change the level of expansion:

1. Click a collapsed hierarchy icon to expand the hierarchy one level below the selected symbol.
2. Click an expanded hierarchy icon to collapse the hierarchy to the selected symbol.
3. Right-click on the top row and select one of these options:
   • Expand All for Selected Row: Expands the entire hierarchy below the selected symbol.
   • Collapse All: Collapses the entire hierarchy.
4. Right-click on a parent row and select one of these options:
   • Expand All for Selected Row: Expands the entire hierarchy below the selected symbol.
   • Collapse All: Collapses the entire hierarchy.
   • Collapse Parent: Collapses the hierarchy to the parent of the selected symbol.
5. Right-click on a leaf row and select one of these options:
   • Collapse All: Collapses the entire hierarchy.
   • Collapse Parent: Collapses the hierarchy to the parent of the selected symbol.

Adding an account

To add a new account:

1. Select a row in the table. The new account will be assigned as a child of the selected account.

   Note:

   • You can add a new account that has similar settings to an existing account by selecting a row and clicking duplicate.

   • See Understanding the GloBE adjusted covered taxes account structure for which accounts can have new child accounts created below them.

2. Click Add. The Add dialog appears.
3. Fill in the following fields:

   1. Name: Enter the name of the new account. The name of the account is limited to 31 characters.

   2. Description: Enter a description for the new account. The description of the account is limited to 100 characters.

   3. Parent: Select or enter the name of the parent to assign the new account to.

      Note: You can also click the search button to open the symbol selector dialog to access advanced search options.

   4. Sort Order: Enter a number to define the order of the new account under the parent. Accounts are sorted from low to high. Accounts added with a sort order of 0 will appear last, in the order the account was created.

4. Click OK to add the new symbol to the table.

   Note: Accounts are not added to the database until you click Apply.

Modifying an existing account

You can change the properties of an existing account:

1. Modify the description by editing the value in the ‘Description’ cell.
2. Change the order the account appears under its parent by modifying the sort order value.
3. To change the parent of an account:
   1. Select the row in the table.
   2. Click Edit. The Edit dialog appears.
   3. Enter or select a new parent.
   4. Click OK.

No changes are made to the database until you click Apply.

Note: See Understanding the GloBE adjusted covered taxes account structure for which accounts and properties can be modified.

Applying changes

To apply changes to the accounts click Apply.

For new rows in the table:

• Each new account will be added under the selected parent symbol.

For modified accounts:

• Any description changes will be applied.
• If the parent account is changed, the account will be reassigned to the new parent with the specified sort order.
• Any changes to the sort order (same parent account) will be applied.

Results:

• All actions performed are presented at the end of processing with:
  • Each row identified by its symbol name.
  • The action performed or the reason any error occurred.
• Any valid changes, not cancelled, are applied.

Refreshing the accounts

1. Click Refresh to refresh the list of accounts.
2. Click Symbols to change the selected account and refresh the list of accounts.

In either case, if there are any unapplied changes, you will be prompted to apply or discard any changes that have not yet been applied.

1. Choose Apply Changes to apply any changes made, then refresh the list of accounts. If there are any errors the refresh will not be performed.
2. Choose Discard Changes to discard any changes made, then refresh the list of accounts.
3. Click Cancel to return to the table without refreshing the list of accounts.

Exporting from the GloBE adjusted covered taxes accounts table

1. Click Export to export from the accounts table to a .csv file.

2. Select the .csv file to export to.

   Note: If the file selected does not currently exist, it will be created during the export process.

3. Click OK. A confirmation dialog will appear.
4. Click View File to view the exported file.

Exporting GloBE adjusted covered taxes accounts

The Export option in the Manage GloBE Adjusted Covered Taxes Accounts dialog allows you to export accounts and their related settings from the database to a .csv file.

To export accounts:

1. Click on Manage GloBE Adjusted Covered Taxes Accounts. A prompt appears.
2. For Option, select Export.
3. Select the .csv file to export to.

   Note: If the file selected does not currently exist, it will be created during the export process.

4. Select symbols to export.
5. Click OK. A confirmation dialog will appear.
6. Click View File to view the exported file.

Managing GloBE adjusted covered tax automations

GloBE covered tax accounts can be calculated rather than manually input or imported. The Manage GloBE covered taxes automations app allows you to set accounts to be calculated using source data from your trial balance or tax provision results.

GloBE covered tax automations are period specific and can be overridden:

• For an entity.
• For an automation group if automation groups exist.
  • Entity overrides supersede automation group overrides.

To manage automations:

1. Click on Manage GloBE Covered Taxes Automations. A prompt appears.
2. Select the GloBE covered tax accounts to manage.
3. Select the period to update automations for. In the Manage GloBE Covered Taxes Automations table, the current automations for the selected accounts are displayed.

Managing default settings

1. From the Default Settings tab, click Add to add automation default settings for an account. Automation settings are not added to the database until you click Apply.

Note: You can add settings on an account that has similar settings to another account by selecting an existing row and clicking duplicate.

2. For each account fill in the following fields:

   1. Account: Select the account for which you would like to set default automation settings.

   2. Automate: Check this option if this account will be automated. For the default settings, the automation check box is selected by default. Automated accounts will have data automatically transferred from the defined source to the target account.

   3. %: Enter the percentage you want to apply to the source amount prior to transferring it to the target account. The % value entered must be a number between -100 and 100.

   4. Source Accounts: Specify the source account(s). You can select one or more parent or leaf symbols.

   5. Source DETAILS: Specify the source detail symbol(s). The source details column will display if attribute ASP2CTAutoD3Source is set to a parent symbol or contains multiple symbols.

   6. Source SEGMENTS: Specify the source segment symbol(s). The source segments column will display if attribute ASP2CTAutoD5Source is set to a parent symbol or contains multiple symbols.

   7. Source ELEMENTS: Specify the source element symbol(s). The source elements column will display if attribute ASP2CTAutoD6Source is set to a parent symbol or contains multiple symbols.

Managing override settings

1. From either the Group Override or Entity Override tab, click Add to add new override settings. Override settings are not added to the database until you click Apply.

Note:

• The Group Override tab is used to override account settings at an automation group level. This tab will only appear if you have Pillar Two automation groups set up in your system (under entity root symbol Automation_Groups_P2).

• The Entities Override tab is used to override account settings at an entity level. This tab will only appear if you have leaf entities under the P2JTotal structure.

2. For each account, fill in the following fields:

   1. Account: Select the account for which you would like to set override automation settings.

   2. Automation Group/Entity: If on the Group Override tab, select the automation group you would like to set override settings for. If on the Entity Override tab, select the entity you would like to set override settings for.

   3. Automate: Check this option if this account will be automated at the override level. Automated accounts will have data automatically transferred from the defined source to the target account.

   4. %: Enter the percentage you want to apply to the source amount prior to transferring it to the target account. The % value entered must be a number between -100 and 100.

   5. Source Accounts: Specify the source account(s). You can select one or more parent or leaf symbols.

   6. Source DETAILS: Specify the source detail symbol(s). The source details column will display if attribute ASP2CTAutoD3Source is set to a parent symbol or contains multiple symbols.

   7. Source SEGMENTS: Specify the source segment symbol(s). The source segments column will display if attribute ASP2CTAutoD5Source is set to a parent symbol or contains multiple symbols.

   8. Source ELEMENTS: Specify the source element symbol(s). The source elements column will display if attribute ASP2CTAutoD6Source is set to a parent symbol or contains multiple symbols.

Modifying an account

You can change the properties of an existing account:

• Change the automation setting on the account by checking or un-checking the automate option.
• Change the % to be used in the automation calculation by modifying the % value.
• Change the source account(s) by selecting different source account symbols.
• Change source details, segments, or elements symbol(s) by selecting different source symbols.

No changes are applied until you click Apply.

Applying changes

To apply changes to the automation settings, click Apply.

• Any changes to the ‘Automate’ setting will be applied.
• Any changes to the ‘%’ setting will be applied.
• Any changes to the ‘Source Accounts’ setting will be applied.
• Any changes to the source details, segments, or elements settings will be applied.

Refreshing the automations

Click Refresh to refresh the list of automation settings.

If there are any unapplied changes, you will be prompted to apply or discard any changes that have not yet been applied.

• Choose Apply Changes to apply any changes made, then refresh the list of automation settings. If there are any errors the refresh will not be performed.
• Choose Discard Changes to discard any changes made, then refresh the list of accounts.
• Click Cancel to return to the table without refreshing the list of accounts.

Deleting automation settings

You can delete an automation setting at the default automation group override or entity override level:

1. Highlight the row you want to delete.
2. Click the delete button.
3. Automation settings are not deleted until you click Apply.

Substance-based Income Exclusion Accounts

The Manage GloBE Substance-based Income Exclusion Accounts app is used to:

• Manage the accounts used to calculate the substance-based income exclusion amount.
• Export the accounts to a file for import to another system.
• Import accounts from a file to update the GloBE Substance-based Income Exclusion structure.

The Manage GloBE Substance-based Income Exclusion Accounts app provides the ability to create and modify custom accounts as well as the ability to edit the properties of existing accounts where permitted.

Understanding the GloBE substance-based income exclusion structure

The GloBE Substance-based Income Exclusion Account root symbol is P2SBIE5.3 and the structure of the hierarchy is designed to capture the amounts required for calculating the exclusion amount as defined in section 5.3 of the OECD’s Model Globe Rules.

The hierarchy contains accounts to capture gross amounts for payroll and tangible asset carve-out and adjustments required for permanent establishments and flow-through entities. Certain out of box accounts allow for some modifications whereas others can not be changed.

The hierarchy root symbol (P2SBIE5.3):

• Cannot be deleted.
• Cannot have new symbols assigned to it.

The following accounts are protected:

• P2SBIE5.3.6.PC and all its descendants
• P2SBIE5.3.7.PC and all its descendants
• P2SBIE5.3.6.TA and all its descendants
• P2SBIE5.3.7.TA and all its descendants
• P2SBIE5.3.1

These symbols:

• Cannot be deleted.
• Cannot be modified.
• Cannot have new symbols assigned to them.
• Cannot be assigned to a different parent.

The following symbols are protected from being deleted and modified:

• P2SBIE5.3.3
• P2SBIE5.3.4

Note: Invisible: New for v24.4Any updates applied to the GloBE Substance Based Income Exclusion account hierarchy using the Import or Manage option will be applied automatically to the QDMTT Substance Based Income Exclusion hierarchy.

Importing GloBE substance-based income Exclusion accounts

The import option in the Manage GloBE Substance-based Income Exclusion Accounts dialog allows you to create and update GloBE Substance-based Income Exclusion accounts in the database from a .csv file. For efficiency, your source file should only contain accounts under P2SBIE5.3.3 and P2SBIE5.3.4.

To import accounts:

1. Click on Manage GloBE Substance-based Income Exclusion Accounts. A prompt appears.
2. For Option, select Import.
3. Select the .csv file to import from.
4. To skip confirmation of each new parent assignment, check the Automatically confirm parent assignment option.
5. Click OK. A table will be displayed showing the summary of all actions performed by the import.

Note: If there are any issues with the file, a table will be displayed indicating the issues. No changes will be made. See Understanding the GloBE substance-based income exclusion account structure for which accounts allow for child accounts to be created below them.

.csv file example:

where:

Parameter	Description
Name	The name of the account symbol.
Description	The description of the account.
Parent	The name of a parent to assign the account to. The account will become a child of the specified parent, and the values in the parent will be calculated from all its children.
Sort Order	Indicates the order of the account under the parent, with lower numbers ordered before higher numbers. You can specify NULL or 0, which will assign the sort order as 0, which results in the symbol being sorted by when it was created.

Managing GloBE substance-based income exclusion accounts

The Manage option in the Manage GloBE Substance-Based Income Exclusion Accounts dialog allows you to create, update and delete accounts from within the Manage GloBE Temporary Differences Accounts table.

To manage accounts:

1. Click on Manage GloBE Substance-Based Income Exclusion Accounts. A prompt appears.
2. For Option, select Manage.
3. Select the GloBE substance-based income exclusion accounts to manage.In the Manage GloBE Substance-Based Income Exclusion Accounts table, the hierarchy of the account selected is displayed.

Working with the hierarchy

The Manage GloBE Substance-Based Income Exclusion Accounts table displays the selected account in a hierarchical view. The view is initially expanded two levels below the selected account.

To change the level of expansion:

• Click a collapsed hierarchy icon to expand the hierarchy one level below the selected symbol.
• Click an expanded hierarchy icon to collapse the hierarchy to the selected symbol.
• Right-click on the top row and select one of these options:
  • Expand All for Selected Row: Expands the entire hierarchy below the selected symbol.
  • Collapse All: Collapses the entire hierarchy.
• Right-click on a parent row and select one of these options:
  • Expand All for Selected Row: Expands the entire hierarchy below the selected symbol.
  • Collapse All: Collapses the entire hierarchy.
  • Collapse Parent: Collapses the hierarchy to the parent of the selected symbol.
• Right-click on a leaf row and select one of these options:
  • Collapse All: Collapses the entire hierarchy.
  • Collapse Parent: Collapses the hierarchy to the parent of the selected symbol.

Adding an account

To add a new account:

1. Select a row in the table. The new account will be assigned as a child of the selected account.

   Note:

   • You can add a new account that has similar settings to an existing account by selecting a row and clicking duplicate.

   • See Understanding the GloBE adjusted covered taxes account structure for which accounts can have new child accounts created below them.

2. Click Add. The Add dialog appears.
3. Fill in the following fields:

   1. Name: Enter the name of the new account. The name of the account is limited to 31 characters.

   2. Description: Enter a description for the new account. The description of the account is limited to 100 characters.

   3. Parent: Select or enter the name of the parent to assign the new account to.

      Note: You can also click the search button to open the symbol selector dialog to access advanced search options.

   4. Sort Order: Enter a number to define the order of the new account under the parent. Accounts are sorted from low to high. Accounts added with a sort order of 0 will appear last, in the order the account was created.

4. Click OK to add the new symbol to the table.

   Note: Accounts are not added to the database until you click Apply.

Modifying an existing account

You can change the properties of an existing account:

1. Modify the description by editing the value in the ‘Description’ cell.
2. Change the order the account appears under its parent by modifying the sort order value.
3. To change the parent of an account:
   1. Select the row in the table.
   2. Click Edit. The Edit dialog appears.
   3. Enter or select a new parent.
   4. Click OK.

No changes are made to the database until you click Apply.

Note: See Understanding the GloBE substance-based income exclusion account structure for which accounts and properties can be modified.

Applying changes

To apply changes to the accounts click Apply.

For new rows in the table, each new account will be added under the selected parent symbol.

For modified accounts:

• Any description changes will be applied.
• If the parent account is changed, the account will be reassigned to the new parent with the specified sort order.
• Any changes to the sort order (same parent account) will be applied.

Results:

All actions performed are presented at the end of processing with:

• Each row identified by its symbol name.
• The action performed or the reason any error occurred.
• Any valid changes, not cancelled, are applied.

Refreshing the accounts

Click Refresh to refresh the list of accounts.

Click Symbols to change the selected account and refresh the list of accounts.

In either case, if there are any unapplied changes, you will be prompted to apply or discard any changes that have not yet been applied.

• Choose Apply Changes to apply any changes made, then refresh the list of accounts. If there are any errors the refresh will not be performed.
• Choose Discard Changes to discard any changes made, then refresh the list of accounts.
• Click Cancel to return to the table without refreshing the list of accounts.

Exporting from the GloBE substance-based income exclusion accounts table

Click Export to export from the accounts table to a .csv file.

1. Select the .csv file to export to.

   Note: Note If the file selected does not currently exist, it will be created during the export process.

2. Click OK. A confirmation dialog will appear.
3. Click View File to view the exported file.

Exporting GloBE substance-based income exclusion accounts

The Export option in the Manage GloBE Substance-Based Income Exclusion Accounts dialog allows you to export accounts and their related settings from the database to a .csv file.

To export accounts:

1. Click on Manage GloBE Substance-Based Income Exclusion Accounts. A prompt appears.
2. For Option, select Export.
3. Select the .csv file to export to.

   Note: If the file selected does not currently exist, it will be created during the export process.

4. Select symbols to export.
5. Click OK. A confirmation dialog will appear.
6. Click View File to view the exported file.

GloBE Temporary Differences Accounts

The Manage GloBE Temporary Differences Accounts app is used to:

• Manage the temporary difference adjustment accounts in scope for Pillar Two Model Rules
• Export the accounts to a file for import to another system.
• Import accounts from a file to update the GloBE Temporary Differences structure.

The Manage GloBE Temporary Differences Accounts app provides the ability to create and modify custom accounts as well as the ability to edit the properties of existing accounts where permitted.

Understanding the GloBE temporary differences account structure

The GloBE Temporary Differences Account root symbol is P2TMP and the structure of the hierarchy is designed to help bridge the differences between temporary differences for tax provision and the mechanism for addressing temporary differences in section 4.4 of the OECD’s Model Globe Rules.

This hierarchy contains any temporary differences you created for tax provision, and some out of box accounts that are used by the system for reporting and calculations. Certain out of box accounts allow for some modifications whereas others can not be changed.

The hierarchy root symbol (P2TMP):

• Cannot be deleted.
• Cannot have new symbols assigned to it.

The following accounts are protected:

• P2TMP4.4.1 and all its descendants as these are managed by tax provision.

These symbols:

• Cannot be deleted.
• Cannot be modified.
• Cannot have new symbols assigned to them.
• Cannot be assigned to a different parent.

The following symbols are protected from being deleted and modified:

• P2TMP4.1.1.A
• P2TMP4.1.1.B
• P2TMP4.1.1.C
• P2TMP4.1.1.D
• P2TMP4.1.1.E

Importing GloBE temporary difference accounts

The import option in the Manage GloBE Temporary Differences Accounts dialog allows you to create and update GloBE Temporary Differences accounts in the database from a .csv file. For efficiency, your source file should only contain accounts under P2TMP4.1.1.A P2TMP4.1.1.E.

To import accounts:

1. Click on Manage GloBE Temporary Differences Accounts. A prompt appears.
2. For Option, select Import.
3. Select the .csv file to import from.
4. To skip confirmation of each new parent assignment, check the Automatically confirm parent assignment option.
5. Click OK. A table will be displayed showing the summary of all actions performed by the import.

Note:

• If there are any issues with the file, a table will be displayed indicating the issues. No changes will be made.

• See Understanding the GloBE adjusted covered taxes account structure for which accounts can have new child accounts created below them.

.csv file example

where:

Parameter	Description
Name	The name of the account symbol.
Description	The description of the account.
Parent	The name of a parent to assign the account to. The account will become a child of the specified parent, and the values in the parent will be calculated from all its children.
Sort Order	Indicates the order of the account under the parent, with lower numbers ordered before higher numbers. You can specify NULL or 0, which will assign the sort order as 0, which results in the symbol being sorted by when it was created.

Managing GloBE temporary differences taxes accounts

The Manage option in the Manage GloBE Temporary Differences Accounts dialog allows you to create, update and delete accounts from within the Manage GloBE Temporary Differences Accounts table.

To manage accounts:

1. Click on Manage GloBE Temporary Differences Accounts. A prompt appears.
2. For Option, select Manage.
3. Select the GloBE temporary differences accounts to manage. In the Manage GloBE Temporary Differences Accounts table, the hierarchy of the account selected is displayed.

Working with the hierarchy

The Manage GloBE Temporary Differences Accounts table displays the selected account in a hierarchical view. The view is initially expanded two levels below the selected account.

To change the level of expansion:

1. Click a collapsed hierarchy icon to expand the hierarchy one level below the selected symbol.
2. Click an expanded hierarchy icon to collapse the hierarchy to the selected symbol.
3. Right-click on the top row and select one of these options:
   • Expand All for Selected Row: Expands the entire hierarchy below the selected symbol.
   • Collapse All: Collapses the entire hierarchy.
4. Right-click on a parent row and select one of these options:
   • Expand All for Selected Row: Expands the entire hierarchy below the selected symbol.
   • Collapse All: Collapses the entire hierarchy.
   • Collapse Parent: Collapses the hierarchy to the parent of the selected symbol.
   • Expand All for Selected Row: Expands the entire hierarchy below the selected symbol.
   • Collapse All: Collapses the entire hierarchy.
   • Collapse Parent: Collapses the hierarchy to the parent of the selected symbol.
5. Right-click on a leaf row and select one of these options:
   • Collapse All: Collapses the entire hierarchy.
   • Collapse Parent: Collapses the hierarchy to the parent of the selected symbol.

Adding an account

To add a new account:

1. Select a row in the table. The new account will be assigned as a child of the selected account.

   Note: You can add a new account that has similar settings to an existing account by selecting a row and clicking duplicate. See Understanding the GloBE temporary differences account structure for which accounts can have new child accounts created below them.

2. Click Add. The Add dialog appears.
3. Fill in the following fields:

   1. Name: Enter the name of the new account. The name of the account is limited to 31 characters.

   2. Description: Enter a description for the new account. The description of the account is limited to 100 characters.

   3. Parent: Select or enter the name of the parent to assign the new account to.

      Note: You can also click the search button to open the symbol selector dialog to access advanced search options.

   4. Sort Order: Enter a number to define the order of the new account under the parent. Accounts are sorted from low to high. Accounts added with a sort order of 0 will appear last, in the order the account was created.

4. Click OK to add the new symbol to the table.

   Note: Accounts are not added to the database until you click Apply.

Modifying an existing account

You can change the properties of an existing account:

1. Modify the description by editing the value in the ‘Description’ cell.
2. Change the order the account appears under its parent by modifying the sort order value.
3. To change the parent of an account:
   1. Select the row in the table.
   2. Click Edit. The Edit dialog appears.
   3. Enter or select a new parent.
   4. Click OK.

No changes are made to the database until you click Apply.

Note: See Understanding the GloBE temporary differences account structure for which accounts and properties can be modified.

Applying changes

To apply changes to the accounts click Apply.

For new rows in the table:

• Each new account will be added under the selected parent symbol.

For modified accounts:

• Any description changes will be applied.
• If the parent account is changed, the account will be reassigned to the new parent with the specified sort order.
• Any changes to the sort order (same parent account) will be applied.

Results:

• All actions performed are presented at the end of processing with:
  • Each row identified by its symbol name.
  • The action performed or the reason any error occurred.
  • Any valid changes, not cancelled, are applied.

Refreshing the accounts

• Click Refresh to refresh the list of accounts.
• Click Symbols to change the selected account and refresh the list of accounts.

In either case, if there are any unapplied changes, you will be prompted to apply or discard any changes that have not yet been applied.

• Choose Apply Changes to apply any changes made, then refresh the list of accounts. If there are any errors the refresh will not be performed.
• Choose Discard Changes to discard any changes made, then refresh the list of accounts.
• Click Cancel to return to the table without refreshing the list of accounts.

Exporting from the GloBE temporary differences accounts table

Click Export to export from the accounts table to a .csv file.

1. Select the .csv file to export to.

   Note: If the file selected does not currently exist, it will be created during the export process.

2. Click OK. A confirmation dialog will appear.
3. Click View File to view the exported file.

Exporting GloBE temporary differences accounts

The Export option in the Manage GloBE Temporary Differences Accounts dialog allows you to export income accounts and their related settings from the database to a .csv file.

To export accounts:

1. Click on Manage GloBE Temporary Differences Accounts, a prompt appears.
2. For Option, select Export.
3. Select the .csv file to export to.

   Note: If the file selected does not currently exist, it will be created during the export process.

4. Select symbols to export.
5. Click OK. A confirmation dialog will appear.
6. Click View File to view the exported file.

Managing GloBE temporary difference automations

GloBE temporary difference accounts can be calculated rather than manually input or imported. The Manage GloBE temporary differences automations app allows you to set accounts to be calculated using source data from your trial balance or tax provision results.

GloBE temporary difference automations are period specific and can be overridden:

• For an entity.
• For an automation group if automation groups exist.
  • Entity overrides supersede automation group overrides.

To manage automations:

1. Click on Manage GloBE Temporary Differences Automations. A prompt appears.
2. Select the GloBE temporary difference accounts to manage.
3. Select the period to update automations for. In the Manage GloBE Temporary Differences Automations table, the current automations for the selected accounts are displayed.

Managing default settings

1. From the Default Settings tab, click Add to add automation default settings for an account.

Note:

• You cannot automate accounts within the Temporary Differences per Provision sub-hierarchy as these amounts are calculated from tax provision.

• You can add settings on an account that has similar settings to another account by selecting an existing row and clicking duplicate.

2. For each account fill in the following fields:

   1. Account: Select the account for which you would like to set default automation settings.

   2. Automate: Check this option if this account will be automated. For the default settings, the automation check box is selected by default. Automated accounts will have data automatically transferred from the defined source to the target account.

   3. %: Enter the percentage you want to apply to the source amount prior to transferring it to the target account. The % value entered must be a number between -100 and 100.

   4. Source Accounts: Specify the source account(s). You can select one or more parent or leaf symbols.

   5. Source DETAILS: Specify the source detail symbol(s). The source details column will display if attribute ASP2TMPAutoD3Source is set to a parent symbol or contains multiple symbols.

   6. Source SEGMENTS: Specify the source segment symbol(s). The source segments column will display if attribute ASP2TMPAutoD5Source is set to a parent symbol or contains multiple symbols.

   7. Source ELEMENTS: Specify the source element symbol(s). The source elements column will display if attribute ASP2TMPAutoD6Source is set to a parent symbol or contains multiple symbols.

   8. Target ELEMENTS: Specify the target element. The target elements column will display if ASP2TMPAutoD6Target is set to a parent symbol or contains multiple symbols.

Automation settings are not added to the database until you click Apply.

Managing override settings

1. From either the Group Override or Entity Override tab, click Add to add new override settings.

Note:

• The Group Override tab is used to override account settings at an automation group level. This tab will only appear if you have Pillar Two automation groups set up in your system (under entity root symbol Automation_Groups_P2).

• The Entities Override tab is used to override account settings at an entity level. This tab will only appear if you have leaf entities under the P2JTotal structure.

2. For each account, fill in the following fields:

   1. Account: Select the account for which you would like to set override automation settings.

   2. Automation Group/Entity: If on the Group Override tab, select the automation group you would like to set override settings for. If on the Entity Override tab, select the entity you would like to set override settings for.

   3. Automate: Check this option if this account will be automated at the override level. Automated accounts will have data automatically transferred from the defined source to the target account.

   4. %: Enter the percentage you want to apply to the source amount prior to transferring it to the target account. The % value entered must be a number between -100 and 100.

   5. Source Accounts: Specify the source account(s). You can select one or more parent or leaf symbols.

   6. Source DETAILS: Specify the source detail symbol(s). The source details column will display if attribute ASP2TMPAutoD3Source is set to a parent symbol or contains multiple symbols.

   7. Source SEGMENTS: Specify the source segment symbol(s). The source segments column will display if attribute ASP2TMPAutoD5Source is set to a parent symbol or contains multiple symbols.

   8. Source ELEMENTS: Specify the source element symbol(s). The source elements column will display if attribute ASP2TMPAutoD6Source is set to a parent symbol or contains multiple symbols.

   9. Target ELEMENTS: Specify the target element. The target elements column will display if ASP2TMPAutoD6Target is set to a parent symbol or contains multiple symbols.

Override settings are not added to the database until you click Apply.

Modifying an account

You can change the properties of an existing account:

1. Change the automation setting on the account by checking or un-checking the automate option.
2. Change the % to be used in the automation calculation by modifying the % value.
3. Change source details, segments, or elements symbol(s) by selecting different source symbols.
4. Change the target element by selecting a different target symbol.
5. Change the source account(s) by selecting different source account symbols.

No changes are applied until you click Apply.

Applying changes

To apply changes to the automation settings, click Apply.

1. Any changes to the ‘Automate’ setting will be applied.
2. Any changes to the ‘%’ setting will be applied.
3. Any changes to the ‘Source Accounts’ setting will be applied.
4. Any changes to the source details, segments, or elements settings will be applied.

Refreshing the automations

Click Refresh to refresh the list of automation settings. If there are any unapplied changes, you will be prompted to apply or discard any changes that have not yet been applied.

• Choose Apply Changes to apply any changes made, then refresh the list of automation settings. If there are any errors the refresh will not be performed.
• Choose Discard Changes to discard any changes made, then refresh the list of accounts.
• Click Cancel to return to the table without refreshing the list of accounts.

Deleting automation settings

You can delete an automation setting at the default automation group override or entity override level:

1. Highlight the row you want to delete.
2. Click the delete button.
3. Automation settings are not deleted until you click Apply.

Pillar Two Rollover

At the close of each period, the system needs to be moved from the current time period into the next. This process is called a rollover. The rollover is run at period end and at year end. The Pillar Two rollover process will advance the period and/or year independently of Tax Provision. Prior to executing the rollover, it is advised that you take a backup of the database, either using the export function in server manager or taking a RDBMS backup.

The Pillar Two Period End rollover process performs the following steps:

1. Updates time period alternate hierarchies.
2. Updates these system attributes to reflect the current period:
   1. ASP2Cper (Time Period - Current Period Symbol)
3. Copies the minimum tax rate to the next period.
4. Copies the Substance-Based Income Exclusion rates to the next period.
5. Copies the QDMTT minimum tax rate to the next period.
6. Copies the QDMTT Substance-Based Income Exclusion rates to the next period.
7. Copies automations settings for GloBE Income to the next period.
8. Copies automations settings for GloBE Covered Taxes to the next period.
9. Copies automations settings for GloBE Temporary Differences to the next period.
10. Copies jurisdiction and constituent entity settings to the next period.

If the rollover is a year end rollover, and the rollover for tax provision has not been executed yet, the Pillar Two rollover process will also:

1. Create time period symbols for next year for the actuals timeframe (Months, Quarters, Year, YTD Months, YTD Year, and Return time periods).
2. Delete the seventh prior year time period symbols for actuals timeframe (Months, Quarters, Year, YTD Months, YTD Year, and Return time periods).

Note: In a system with Tax Provision and Pillar Two, whichever rollover is executed first will perform the create and delete steps.

The following time period hierarchies are updated during the period end rollover:

Hierarchy	Old symbol removed	New symbol added
CYP2PER - Pillar Two Process Current Period	Current period symbol, e.g., A2303YTD	New current period symbol, e.g., A2306YTD

The following time period hierarchies are updated during the year end rollover:

Hierarchy	Old symbol removed	New symbol added
ActualYTD - Actual YTD Time Periods	Seventh prior year time period symbols, e.g., CP17	New YTD symbols, e.g., CP24

Preparing for a rollover

Before you perform a rollover in Longview Tax, make sure the following conditions are met:

• Ensure that all data intersections and the associated criteria have been defined for the period end or year end and return rollovers.
• Inform all users that a rollover is imminent and make sure they have time to exit the system, then ensure no users are in the system.
• Ensure all events are completed prior to beginning the rollover.
• Ensure all data submissions are completed prior to beginning the rollover.
• Ensure there are no outstanding locks.
• Create a backup of the Longview production database and copy to a safe place by running an Export through Longview Server Manager.

Running the tax rollover process (period end and year end)

You can use the Rollover tool to run the pillar two rollover process for the end of the current period. The rollover procedure in the Rollover tool is the same for period end and year end rollovers.

The rollover type in the Rollover tool is determined by the following:

• If the current period is the last period for the year in the ASP2CPer attribute, the rollover is a year end rollover.
• If the current period is any other period in the ASP2CPer attribute, the rollover is a period end rollover.

Caution: Be sure to have a complete and recent backup of your database prior to running the rollover process.

To perform a rollover

1. In the Global Transparency navigation pane, click Administration.
2. Expand Pillar Two, then expand Rollover.
3. Click Rollover. The Rollover tool opens in the workspace. If there are any locks in the target period, a message displays. Locks can prevent the rollover from running successfully. Click Data Locks to open the Data Locks tool and review the conflicting locks. Clicking Data Locks will end the rollover process.
4. If there are any user submissions in progress, a message displays. You must wait until all user submissions are complete before you start the rollover process. Click User Submissions to open the User Submissions tool and monitor any user submissions in progress. Clicking User Submissions will end the rollover process.
5. If there are any events in progress a message displays. You must wait until all events are complete before you start the rollover process. Click Events to open the Events tool and monitor any events in progress. Clicking Events will end the rollover process.
6. Click Start Rollover. The progress message appears. When the rollover is complete, the summary page appears.

   Note: If the rollover fails, you must restore the database by running an Import of your backup through Longview Server Manager. For more information, see the Longview Server Manager Guide.

7. If you want to view the rollover log file, click View Log File. The log file is saved to the following location:

   C:\Users\<userID>\Documents\Longview\Rollover\

8. When you are finished, click Close.

Exporting and importing automation settings

There may be occasions when you need to manually copy automation settings between periods or Longview instances. You can use export and import to accomplish this.

To export automation settings:

1. 1. In Longview Client navigate to Global Transparency > Administration and expand the Import and Export folder.
2. Click Export Pillar Two Automations. The Export Pillar Two Automations form appears.
3. Select the account hierarchy to export automation settings for using the Accounts radio buttons.
4. Select the period from which to export automation settings. Default is the current period.
5. Click OK. The automation settings are exported to a file and a confirmation dialog appears.
6. You can:
   1. Click View File to open the automation settings file in your default comma-separated values (.csv) editor.
   2. Click Close to exit the process.

To import automation settings:

1. In Longview Client navigate to Global Transparency > Administration and expand the Import and Export folder.
2. Click Import Pillar Two Automations. The Import Pillar Two Automations form appears.
3. Select the account hierarchy to import automation settings for using the Accounts radio buttons.
4. Select the period to import automation settings. Default is the current period.
5. Select the file.
6. Click OK. The automation settings are imported from the selected file and a confirmation dialog appears.
7. Click Close to exit the process.

.csv file example (GloBE Income): 

where:

Column	Description
Account	The pillar two account for which you would like to set automation settings. Note: This must be an account under the structure selected using the Accounts radio button.
Entity	The entity the automation settings will be applied to. If this is a default automation setting, the entity should be set to ENTITIES_Default. If this is a Group Override setting, the automation group should be specified. Note: This must be an entity under Automation_Groups_P2 If this is an Entity Override setting, the entity you would like to set override settings for should be specified. Note: This must be a constituent entity under P2JTotal.
Automate	1 if the account will be automated. 0 if the account will not be automated.
Percent	The percentage you want to apply to the source amount prior to transferring it to the target account. The % value entered must be a number between -100 and 100.
Source Account	The source account(s) for the target account. You can set one or more parent or leaf symbols; they must be separated by a semi-colon(;)
Source <Non-Key Dimension>	The source non-key dimension symbol(s) for the account. Source non-key dimension values are only required for any non key dimensions or controls where attribute ASP2<XX>AutoD<#>Source is set to a parent symbol. Typically, source must be specified for DETAILS, SEGMENTS, and ELEMENTS though the configuration in your system may vary. Note: If the target non-key dimension symbol specified is a parent, the source non-key dimension symbol must also be the same parent. If the target non-key dimension symbol specified is a leaf, you can set one or more parent or leaf symbols for the source
Target <Non-Key Dimension>	The target non-key dimension symbol for the Profitability Analysis account. Target non-key dimension values are only required for any non key dimensions or controls where attribute ASP2<XX>AutoD<#>Target is set to a parent symbol. Typically target must be specified for ELEMENTS for temporary differences only, though the configuration in your system may vary. Note: If the target non-key dimension symbol specified is a parent, the source non-key dimension symbol must also be the same parent. If the target non-key dimension symbol specified is a leaf, you can set one or more parent or leaf symbols for the source

Exporting and importing Pillar Two elections

There may be occasions when you need to manually copy election settings between periods or Longview instances. You can use export and import to accomplish this.

To export election settings:

1. In Longview Client, navigate to Global Transparency > Administration and expand the Import and Export folder.

2. Click Export Pillar Two Elections. The Export Pillar Two Elections form appears.

3. Select the period from which to export election settings. Default is the current period.

4. Click OK. The election settings are exported to a file and a confirmation dialog appears.

5. You can:

   1. Click View File to open the election settings file in your default comma-separated values (.csv) editor.

   2. Click Close to exit the process.

Note: Only entities that have taken an election in the selected period will be included in the export. This included entities where an election was selected and then subsequently removed.

To import election settings:

1. In Longview Client, navigate to Global Transparency > Administration and expand the Import and Export folder.

2. Click Import Pillar Two Elections. The Import Pillar Two Elections form appears.

3. Select the period to import automation settings. Default is the current period.

4. Select the file.

5. Click OK. The election settings are imported from the selected file and a confirmation dialog appears.

6. Click Close to exit the process.

To create an import file for pillar two elections:

1. Create a new command separated values file (.csv).

2. Add a header row with the values ENTITY, ARTICLE153, ARTICLE321, ARTICLE321b, ARTICLE321c, ARTICLE447, ARTICLE634, ARTICLE75, ARTICLE76.

3. For each entity that you wish to modify the elections:

   1. Specify the name of the entity symbol. You must enclose the entity name in square brackets if it is numeric.

   2. For each election, enter ‘1’ to take the election, or ‘0’ to not take the election:

      1. ARTICLE153: Not treating an Entity as an Excluded Entity election.

      2. ARTICLE321: Debt release election

      3. ARTICLE321b: Inclusion of all dividends with respect to Portfolio Shareholdings.

      4. ARTICLE321c: Inclusion of all dividends with respect to Portfolio Shareholdings.

      5. ARTICLE447: Unclaimed Accrual Election.

      6. ARTICLE634: Fair Value election.

      7. ARTICLE75: Investment entity tax transparency election.

      8. ARTICLE76: Taxable distribution method election

4. Save the file.

.csv file example	.csv file example
ENTITY, ARTICLE153, ARTICLE321, ARTICLE321b, ARTICLE321c, ARTICLE447, ARTICLE634, ARTICLE75, ARTICLE76 [ABG1],0,1,0,0,0,0,0,0 [0110],1,0,0,0,0,0,0,1	ENTITY, ARTICLE153, ARTICLE321, ARTICLE321b, ARTICLE321c, ARTICLE447, ARTICLE634, ARTICLE75, ARTICLE76 [ABG1],0,1,0,0,0,0,0,0

Deploying the transitional safe harbour starter kit

Before deploying the transitional safe harbours starter kit, review the following items and adjust as necessary for your system:

• Open the Deploy Transitional Safe Harbours app in Longview Designer to review the event rules deployed.
  • By default, event rules will be deployed to transfer:
    • CbCR total revenue, if available.
    • CBCR profit before tax, if available.
    • UTP, if available.
    • Substance-based income exclusion.
  • Invisible: New for v24.4By default, event rules will be deployed to IDs: 5950170-5950176.
  • To deploy additional rules, you will need to:
    • Modify the EventFiles procedure to include additional rule files.
    • Add the additional rules files as Supporting Files.
    • The most obvious addition is to add a rule that triggers on change to income tax expense as this is one of the feeds to calculate the simplified ETR.

No other changes should be required. You can run the deployment app from Designer via the Run button or publish the app and run it from the navigation pane of the Longview Client.

The transitional safe harbours deployment app will perform the following actions:

• Deploy the transitional safe harbours account hierarchy (P2TSH).
• Publish the Transitional Safe Harbours adjustments app to the Analysts and CorporateAnalysts groups within the Jurisdictions folder of data collection.
• Publish the Transitional Safe Harbours across jurisdictions app to the Analysts and CorporateAnalysts groups within the Jurisdictions folder of reports.
• Deploy the event rules for executing the transitional safe harbour transfers.

For efficient event execution the rule merging should be updated for the rules added to support transitional safe harbours. The RuleMerges document in the Supporting Files folder contains the configuration assuming all the default rules were deployed. You can copy the text from RuleMerges and paste it into the Event Rue Merging Setup window in Application Administrator. Adjust as necessary if not all rules were deployed, or you deployed any additional rules for the transitional safe harbours transfer.

Additional modifications will be required if you want to add additional transfers into the P2TSHTransfer event.

To modify the transitional safe harbours event, open the event P2TSHTransfer in Longview Designer:

By default, the event assumes all the default sources and included configuration to only run the transfers for the source symbols that exist.

The following source symbols are configured into the event (you can review these in the Main procedure):

• CbCR Revenue: CbC_TotalRevenue (variable: sourceP2TSHDMTRCbCR).
• CBCR Profit or Loss before Tax: CbC_PnLB4Tax (variable: sourceP2TSHDMTRCbCPBT).
• Substance-based Income Exclusion: P2SBIE5.3.1 1 (variable: sourceP2TSHRPTSBIE53).
• Uncertain tax positions (IAS): NatAddCurrentM004T_IAS, NatAddCurrentM005_IAS, NatAddCurrentM006_IAS (variable: sourceP2TSHSETRTUTP).
• Uncertain tax positions (ASC): NatAddCurrentM005T_ASC, NatAddCurrentM006_ASC, NatAddCurrentM007_ASC (variable: sourceP2TSHSETRTUTP).

In addition, there is a place to configure the source for income tax expense (variables: sourceP2TSHSETRTITE_Account and sourceP2TSHSETRTITE_Element).