Pillar 2 Algorithm: Difference between revisions

From Wiki Algonomia
Jump to navigation Jump to search
No edit summary
Tag: Manual revert
Line 22: Line 22:


=== General logic of the algorithm ===
=== General logic of the algorithm ===
The Pillar 2 computations and insuing data structure are excessively complicated. Therefore, next to the unskipable computational steps, most of the steps have been treated by following the "Russian doll" principle, allowing multinational corporations that choses to use our algorithm to move forward with the level of detailed data they are able to provide.
It is also our plan to continue to refine the computational steps that may not be perfectly documented progressively with the publishing of additional guidance as well as the feedback of the community.


=== Data structure ===
=== Data structure ===
Line 34: Line 37:


===== Data =====
===== Data =====
The following tables presents the data points allowed as "Data" :
The Data structure for the Pillar 2 computation being too massive to be referred too in the present article a dedicated page has been created, [[Pillar 2 Data Structure]].
{| class="wikitable sortable mw-collapsible mw-collapsed"
|+Input Data Points
!Role
!Label
!Definition
!Typing
!Multiplicity behavior
!Mandatory
|-
|Matching
|
|
|
|
|
|-
|Matching
|
|
|
|
|
|-
|Matching
|
|
|
|
|
|}
 
===== Rules =====
===== Rules =====
The following tables presents the data points allowed as "Rules" :
In the context of the Pillar 2 computation as all data points need to be collected or retrieved within the Main process, and as changing them amounts to changing part of the compliance data, it has been chosen to not divide the data between Data and Rules, even for Tax rates.
{| class="wikitable sortable mw-collapsible mw-collapsed"
|+Input Rules data points
!Role
!Label
!Definition
!Typing
!Multiplicity behavior
!Mandatory
|-
|Matching
|
|
|
|
|
|-
|Matching
|
|
|
|
|
|}
 
===== Other =====
===== Other =====


Line 97: Line 45:


==== Serie of files ====
==== Serie of files ====
A series of structured files corresponds to the selection of a sequence of structured files whose data and rules can be processed in a coordinated manner in the dashboard or the calculations of the algorithm.
A serie of structured files corresponds to the selection of a sequence of structured files whose data and rules can be processed in a coordinated manner in the dashboard or the calculations of the algorithm.


The selected structured files must form a sequence where their temporal referencing perimeters follow each other in a disjointed and adjacent manner (e.g., a succession of months, quarters, years).
The selected structured files must form a sequence where their temporal referencing perimeters follow each other in a disjointed and adjacent manner (e.g., a succession of months, quarters, years).
Line 108: Line 56:


===== Impact on rules =====
===== Impact on rules =====
None.


=== Computational steps ===
=== Computational steps ===
Line 142: Line 91:
====== Case 2 : Using UPE and a group boolean indicator ======
====== Case 2 : Using UPE and a group boolean indicator ======


===== Step 1.2. - Coherence check of consolidation methods =====
===== Step 1.6. - Coherence check of consolidation methods =====


===== Step 1.6. - Excluded entity identification =====
===== Step 1.6. - Excluded entity identification =====


===== Step 1.7. - Joint-Venture identifications =====
===== Step 1.7. - Joint-Venture identification =====


===== Step 1.8. - MOCE and MOMNE identification =====
===== Step 1.8. - MOCE and MOMNE identification =====


===== Step 1.9. - Specific CE treatments =====
===== Step 1.9. - Specific CE treatments =====
Investment entity identification


==== Macro-step 2 - Safe Harbour ====
==== Macro-step 2 - Safe Harbour ====
Line 170: Line 120:
==== Macro-step 5 - ETR and Top-Up Tax computations ====
==== Macro-step 5 - ETR and Top-Up Tax computations ====


===== Step 5.1. - Construction of Jurisdiction/Sub-group indicators =====
===== Step 5.1. - Construction of Jurisdiction/Sub-group aggregates and indicators =====


===== Step 5.2. - Computation of Jurisdiction/Sub-group Top-Up Tax =====
===== Step 5.2. - Computation of Jurisdiction/Sub-group Top-Up Tax =====

Revision as of 15:33, 10 December 2023

Introduction

Context

Welcome to the OpenSource Pillar 2 Algorithm wiki page! This platform serves as a comprehensive resource for understanding and implementing a pioneering open-source algorithm specifically designed to perform Pillar 2 computations and prepare the GloBE Information Return.

BEPS Pillar 2 represents a significant step in global tax reform, introducing the concept of a Global Minimum Tax to prevent aggressive tax planning and profit shifting by multinational enterprises. Given the intricate nature of international taxation, coupled with the unique structures of individual corporations, computing the tax liabilities under the Global Minimum Tax framework is inherently complex. The scope of the regulation and the various election options available to entities further complicate the computations, requiring in-depth analysis and consideration.

Objectives

Recognizing this complexity, Algonomia has developed a sophisticated algorithm to address these challenges. By opting to release it as open-source, Algonomia aims to foster collaboration among tax specialists, economists, and administrations. This approach not only ensures the refinement and enhancement of the algorithm but also promotes transparency, demonstrating a commitment to a fair and unified international tax landscape.

Feature Overview

The algorithm will present the following features:

  • Scope and Groupe perimeter analysis, to determine the different sub-groups in each jurisdictions for the safe-harbour rules, elections and ETR computations,
  • Safe Harbour computation and analysis, to identify the sub-perimeters requiring less detailed data collection and resulting in simpler computations,
  • GloBE Income and Adjusted covered tax computation
  • Election treatments
  • Post-filing and additional Top-Up Tax computation
  • Effective Tax Rate and Top-Up Tax computation for LTCE's
  • Charging provisions and Paying entity identifications (UPE, POPEs, IPEs)
  • UTPR computation

General logic of the algorithm

The Pillar 2 computations and insuing data structure are excessively complicated. Therefore, next to the unskipable computational steps, most of the steps have been treated by following the "Russian doll" principle, allowing multinational corporations that choses to use our algorithm to move forward with the level of detailed data they are able to provide.

It is also our plan to continue to refine the computational steps that may not be perfectly documented progressively with the publishing of additional guidance as well as the feedback of the community.

Data structure

Structure overview

Algonomia API Framework

The Transfer Pricing Algorithm uses Algonomia API Framework to receive input data and send output data for the computations. In the following sections, it is assumed that data has been transferred to the Transfer Pricing Algorithm using this framework.

Input

The input data follows the usual division required by the Algonomia API Framework : Data, Rules, Other.

Data

The Data structure for the Pillar 2 computation being too massive to be referred too in the present article a dedicated page has been created, Pillar 2 Data Structure.

Rules

In the context of the Pillar 2 computation as all data points need to be collected or retrieved within the Main process, and as changing them amounts to changing part of the compliance data, it has been chosen to not divide the data between Data and Rules, even for Tax rates.

Other

Output

Serie of files

A serie of structured files corresponds to the selection of a sequence of structured files whose data and rules can be processed in a coordinated manner in the dashboard or the calculations of the algorithm.

The selected structured files must form a sequence where their temporal referencing perimeters follow each other in a disjointed and adjacent manner (e.g., a succession of months, quarters, years).

Impact of series on Post-filing computations

The Pillar 2 computations allows and sometimes requires to perform the recalculation of the Top-Up Tax liability of the previous fiscal years to generate the Additional Top-Up Tax. This will only be possible under the following conditions.

  1. Structured files exists for the fiscal years prior to the one under computation. They must be present in an interrupted sequence of 5 fiscal years starting with N-5.
  2. Input data leading to the application of the recalculation are present,
Impact on rules

None.

Computational steps

Macro-step 1 - Scope and Perimeter

Step 1.1. - Generation of the Ownership Interests and Control matrices
Step 1.2. - Sanity checks on Ownership interests
Step 1.3. - Indirect ownership computation
Step 1.4. - Controlling interest matrix computation
Step 1.5. - Definition of the MNE Group
Case 1 : Using Controlling interests and consolidation method

UPE identification : entity with

  • consolidation "full"
  • no parent entity with
    • controlling interest in it
    • and consolidation method
      • full/proportional/equity
      • or not consolidated for reasons in article 1.2.2.b) "size or materiality grounds"/, or "is held for sale"

Entity is part of the MNE Group if :

  • UPE has Controlling interest in the entity
  • and consolidation method
    • full/proportional/equity
    • or not consolidated for reasons in article 1.2.2.b) "size or materiality grounds"/, or "is held for sale"
Case 2 : Using UPE and a group boolean indicator
Step 1.6. - Coherence check of consolidation methods
Step 1.6. - Excluded entity identification
Step 1.7. - Joint-Venture identification
Step 1.8. - MOCE and MOMNE identification
Step 1.9. - Specific CE treatments

Investment entity identification

Macro-step 2 - Safe Harbour

Step 2.1. - Definition of Safe harbour perimeters
Step 2.2. - Application of Safe harbour elections
Step 2.3. -

Macro-step 3 - General Financial data treatments

Step 3.1. - Data reallocation for specific CEs
Step 3.2. - Post-filing recalculations

Macro-step 4 - Specific elections treatments

Macro-step 5 - ETR and Top-Up Tax computations

Step 5.1. - Construction of Jurisdiction/Sub-group aggregates and indicators
Step 5.2. - Computation of Jurisdiction/Sub-group Top-Up Tax
Step 5.3. - Allocation of Top-Up Tax among LTCEs

Macro-step 6 - Charging Mechanisms

Step 6.1. - Construction of the "Is in IIR" Matrix
Step 6.2. - Identification of potential IPE/POPEs
Step 6.3. - Identification of IPEs and POPEs
Step 6.4. - Construction of Allocable share matrix
Step 6.5. - Exclusion of IIR and Offset mechanism
Step 6.6. - Final charging mechanism of LTCE's TUT to paying entities

Macro-step 7 - UTPR computation

Step 7.1. - Computation of Total UTPR amount
Step 7.2. - Computation of coefficients per Jurisdictions
Step 7.3. - Final UTPR computation per jurisdiction