Import financial investment data into ownership structure register

Introduction¶

The import of financial investment data to ownership structure register allows the import of F.I data uploaded by the contributor users.

The following data can be imported:

Financial investments
Assignment price for the intra-group assignment events with sales model
FX Rates

The data processing reads the F.I. variation accounts and the assignment price account from IC Amounts and from Entity journals, and writes data on the events involving the same Entities.

Setup¶

To run the data processing, it is necessary to:

enable it in the data processing tree of the process
in the requirements, define the scenarios / periods from which to read the contributor data by specifying the period length for the data import
In the Ownership structure accounts Configuration, define the categories node for F.I. data and the F.I. variation accounts to be used.

Activation of data processing¶

The data processing can be enabled in the data processing tree of the process under the Basic Consolidation node Import Financial Investment data into Ownership Structure Register

Important Data processing is only available in processes using the 'In Memory' consolidation engine

Important The "Import financial investment data into ownership structure register" data processing is an alternative to the "Load financial investments on amounts" data processing. If both are enabled, a blocking preliminary check is reported when launching the Entity, group and "Import Financial investment data" data processing from the ownership structure register window.

Definition of imported data period length¶

In the requirements its is necessary to define the Import data period length on the scenarios / periods from which F.I data are to be read. The data processing can only be performed for periods with the "Import data period length" field different from "Do not run". The Import data period length is used to determine the previous period in the calculation of the periodic amount.

In the data processing tree, the requirements icon appears in red if all period scenarios of the process are set to "Do not run".

Locked or archived scenarios / periods are not editable.

Definition of import mode, category node and financial investment accounts¶

The Group Structure Accounts Configuration window can be accessed via Data processing > Basic Consolidation > IC matching and elimination logics.

In the Financial investment data import tab, you must specify the import mode:

Do not use (functionality is deactivated)
Financial Investments and Other Information (F.I. data and assignment price on existing ownership structure register events created by the consolidator beforehand are imported)
Events, Financial investments and Other Information (as for the previous option, but with automatic creation of non-existing events).

In addition, the Category Node for F.I. data must be specified. This is the node that contains the Amount and Entity journals type categories from which to import the financial investment contributor data.

The import reads the variation accounts defined in the Financial Investments tab with the "Use on Ownership structure register" option enabled. If the Import Data option is 'Events, Financial investments values and Other info', it is necessary to configure the event type for import.

The Import Exchange rates option also allows the import of FX rates.

Data Processing¶

Running the data processing¶

Data processing is available from the following menus

Admin, Ownership structure Register window accessible from the process, Consolidation requirements.
User, Consolidator Cockpit. The Import of Financial Investments data into Ownership Structure Register is part of the group data processes.

Run from Ownership Structure Register window

To access the data processing, access the Ownership Structure Register via the Admin menu > Processes >Process definition > Data processing pane > Consolidation > Requirements > Group Events pane > Ownership structure register. The Wizards > Import Financial Investments Data menu key is only visible if the data processing has been enabled and the Category node for Financial Investments data has been specified.

It is necessary to select the original scenario / period to be processed. The scenarios / periods of the process having the 'Import data period length' field different from 'Do not run' (excluding inactive scenarios and locked or archived periods) are displayed.

The data processing:

is run on all Entity nodes, node selection is not possible
is run also on submitted nodes
the Impacted functionality is not applied: it is not possible to run edited data only
user rights on consolidation odes are not applied
it is possible to select one scenario / period at a time

Important: Data processing is only available in processes that use the 'in memory' consolidation engine. Data processing is not available in the Ownership structure register window accessible via the menu User > Events because the F.I. data import affects all Entity relationships, whereas this window applies user restrictions on Entities.

Run from consolidator cockpit

The data processing is run in the group data processing before Incoming mergers.

The data processing:

is run on the selected entity nodes
is not run on submitted nodes
the Impacted functionality can be applied: run edited data only
user rights on consolidation odes are applied
it is possible to select one scenario / period at a time

Important: Data processing is only available in processes that use the 'In Memory' consolidation engine. Selected scenarios/periods that have the 'Import data period length' field set to 'Do not run' are not processed and are reported in the audit window as 'Not processable'.

If the category node for Financial Investments data is undefined, the data processing is not run.

Import Financial investments data¶

Important If the import mode is Financial investments values and Other info, events must be entered into the ownership structure register by the consolidator user before data processing is performed.

The data processing handles the events of the event scenario linked to the selected process. The events with a date between the end date of the previous period and the end date of the selected period are taken into account:

Event date > previous period end date. If, based on the Import data period length, the previous period does not exist, the 'event date >= start date of the selected period' filter is applied.
Event date <= end date of the selected scenario/period

The system reads the financial investments data present on IC Amounts and on Entity journal by:

Amounts and Entity journals categories belonging to the specified category node
variation accounts present in the ownership structure register accounts Configuration with "Use on Ownership structure register" option enabled
Origin other than 'Carry forward on Original scenarios': 'PREL_RESTORE'

The value to be imported into the ownership structure register is calculated as the difference between the amount of the selected scenario / period and the amounts of the previous period. The previous period is determined based on the Import data period length.

IC Amounts and Entity Journals data are linked to an event in the ownership structure register with the following characteristics:

Owner Entity of the event = Entity of data
Owned Entity of the event = Ctp Entity of data
if the Relationship Type of the process is by Entity / Custom dimension 2 : Custom dimension 2 Owner Entity of the event = Custom dimension 2 of data
Event Owner Entity currency = Currency of data (entity currency in the process)
If the import mode is "Events, Financial investments values and Other info": Event Type=Event Type for data import associated with the data account in the ownership structure register account configuration

if data are linked to more than one event, the event with latest date is chosen. When the event dates are the same, the event with the greatest event number is chosen.

If the import mode is 'Events, Financial investments values and Other info' and the data row does not match any existing event, the data processing creates a new event by filling the fields as follows:

The event date is the first day of the data processing period.
The event number is the maximum existing event number, for the same Owner entity/Owned entity relationship , + 10.
The Ownership percentage is the same as the previous event or 100% for non-existing Owner entity/Owned entity relationships.
The event type is defined based on the link between financial investment accounts and event types.

Events are created based on the financial investment variation movement, so some corporate events may not be intercepted. For example, in the case of a share capital increase that is not subscribed by the holding company belonging to the group, the event to record the reduction of the direct percentage is not created.

Events entered or updated by the consolidator will not be overwritten by subsequent data processing

IC Amounts and Entity Journals data are loaded into the Financial Investments of the chosen event, keeping the account, the custom dimensions and the category present on contributor data.

The origin generated by the data processing is ‘PROC_OSR_FI_LOADING’.

FX rates import¶

FX rates are imported if under Configuration > Import Financial Investment Data, the option 'Import FX rates' is activated.

The FX rates in the FX Rates table for the selected Scenario/Period are read.

FX rates relationship to output events

For each event for which there is F.I. data to be entered, FX rates are entered.

The average, period average or final FX rate is read out according to conversion type present in the account accounts list for the Financial investments account.

If the event has F.I. data to be entered for more than one account, the conversion type of the account with the largest code is considered.

FX rates are not imported for currencies that were manually entered in the event.

Import financial investment data into the Intra-group assignment events with management of the Custom dimension for third Entity¶

Three Entities are specified for the intra-group assignment events with sales model:

owner Entity : seller
owned Entity: sold Entity
Buyer Entity

Two Entities exist on contributor data:

declaring Entity : seller
Counterparty : sold Entity

If you want the system to import the value of the financial investment to the ownership structure register by also matching the buyer Entity of the event with the contributor data, you can parametrize a custom dimension to contain the third Entity.

The custom dimension for the third Entity can be defined in the Settings > General tab, Financial Consolidation option:

Intra-group financial investment assignment with sales model - Custom Dimension for the third Entity. It is possible to choose one of the active custom dimensions, excluding the custom dimension 2.

The 'Import financial investment data' data processing uses the custom dimension for the third Entity only in processes with 'by Entity' relationship type (because for processes with 'by Entity / Custom dimension 2' relationship type, the information on the custom dimension 2 of the third Entity is missing).

If the Custom dimension of the third Entity is defined and the Relationship Type of the process is By Entity , the system imports:

the Financial investment data by also matching the buyer Entity with the contributor
the assignment price value

Import Financial investments data with third Entity¶

Contributor data that have the custom dimension for the third Entity different from the default value are linked to the intra-group assignment event with sales model having:

Owner Entity of the event = Entity of data
Owned Entity of the event = Ctp Entity of data
if the Relationship Type of the process is by Entity / Custom dimension 2 : Custom dimension 2 Owner Entity of the event = Custom dimension 2 of data
Event Owner Entity currency = Currency of data (entity currency in the process)
Event buyer Entity = custom dimension for the third Entity of data

Contributor data that have the custom dimension for the third Entity equal to the default value are linked to a non-intra-group assignment event having:

Owner Entity of the event = Entity of data
Owned Entity of the event = Ctp Entity of data
if the Relationship Type of the process is by Entity / Custom dimension 2 : Custom dimension 2 Owner Entity of the event = Custom dimension 2 of data
Event Owner Entity currency = Currency of data (entity currency in the process)

Assignment price import

The system reads the Assignment Price from contributor data on:

"F.I. : Sale value in the P&L account" accounts defined in the Accounts Configuration for Intra-group financial investment assignments (Sale models)

The contributor data of the assignment price is matched to the intra-group assignment event with sales model that has:

Owner Entity of the event = Entity of data
Owned Entity of the event = Ctp Entity of data
if the Relationship Type of the process is by Entity / Custom dimension 2 : Custom dimension 2 Owner Entity of the event = Custom dimension 2 of data
Event Owner Entity currency = Currency of data (entity currency in the process)
Event buyer Entity = custom dimension for the third Entity of data
"F.I. : Sale value in the P&L account" account of the Account model for Intra-group assignments specified on the event = Data account

IC Amounts and Entity Journals data are loaded into the Other Information tab of the chosen event, keeping the account, the custom dimensions and the source category.

Final checks¶

Upon completion of the data processing, the following checks are reported in the audit window:

Contributor data to be loaded for which there is no event. The relationships Owner Entity / Owned Entity / Custom dimension 2 Owner Entity (in case of 'by Entity /Custom Dimension 2' relationship), Custom dimension for the third Entity (if defined) of the rows of F.I. data and Assignment price that have not been matched to any event are reported.
Events without financial investments data. The events for which there is no automatic or manual F.I data row are reported.