Amount & Intercompany rules page
Admin
Database applicativo > tile Data Entry e Regole certificazione > Regole Saldi e IC
Purpose of the page¶
This page allows you to set the default rules for data entry on gross amounts and intercompany entries.
Page sections
| Section | Description |
|---|---|
| Dimensions | Defines the custom dimensions enabled on amounts, intercompany entries and reconciliation accounts. |
| Intercompany | Defines additional fields for the intercompany declaration and specific behaviour for the intercompany declaration methods. |
| Transaction currency | Defines the management mode for the currency in which the transaction was carried out, regardless of the entity that executed it. |
| Editability | Defines the editability options for data originating from specific sources. |
| Break back | Defines, for the managed dimensions, the requirements for entering data from forms at the level of hierarchy nodes. |
| IC Cockpit Advanced rules | Defines advanced requirements for inserting reconciliation accounts from the IC cockpit. |
| Spreading | Defines the way in which the spreading functionality is used. |
| Countervalue calculation | Defines the FX rate used in the countervalue calculation data processing, and the data on which it is run. |
Fields in the Dimensions section
| Element | Description |
|---|---|
| Enables the use of custom dimension |
Fields in the Intercompany section
| Element | Description |
|---|---|
| Enable additional fields on IC | If not set to No, this allows you to manage the following additional fields during data entry: - Only information for document: to manage the following information: |
| Copy intercompany to gross data | Enables the automatic calculation of the gross data based on the saving of intercompany data from forms. By enabling this option, the plausibility diagnostic will diagnose the intercompany data and the minorities share together. |
| Allow intercompany declarations towards same Declaring entity | If selected, allows you to enter intercompany declarations towards the same declaring entity. The declaring entity is therefore the same as the counterparty entity. If NOT selected, in the intercompany data entry step an editability check is enabled which locks records where the declaring entity is the same as the counterparty entity. For example, it is useful to perform intercompany declarations in the context of the same entity to eliminate dividends received from group companies towards profits carried forward. |
| Define CTP |
When entering intercompany data, the CTP custom dimension 2 is automatically defined as the default element of the custom dimension 2 associated with the entity. |
Fields in the Transaction currency section
| Element | Description |
|---|---|
| Managed on gross amount | Allows you to manage the transaction currency and the transaction currency amount on gross amounts. |
| Managed on IC amount | Allows you to manage the transaction currency and the amount in foreign currency of the transaction on intercompany amounts. |
| Keep transaction currency on consolidated gross amount | Keeps details of the transaction currency on consolidated amounts. |
| Use detail window to input gross & IC data on transaction currency | Where the transaction currency is being managed, the entry of data (gross and intercompany amounts) within the form must obligatorily be done from the relative management window and not directly from the cell. |
Fields in the Editability section
| Element | Description |
|---|---|
| Edit data with ETL origin | Enables the data collected by the ETL procedure to be edited manually. |
| Save data in form incrementally | Enables changes to data in forms to be tracked. When saving the form, the system creates a database row for every change made to the individual amount. If disabled, the system sums up all the values entered, and only shows the total. For example, if enabled, if the value 100 is initially present in a cell and the user overwrites that value with 110 first, and then with 150, the system inserts the initial amount record of 100, an amount record of 10 and another amount record of 40, all with INPUT_DEFORM as their origin. Otherwise, there will only be one record with 150 as its amount and INPUT_DEFORM as its origin. IMPORTANT: enabling this option allows you to have full data traceability but generates a high number of rows. IMPORTANT: if the data edited from the form is an intercompany entry and the counterparty entity definition is already present on the form’s columns/rows, or it is not necessary to use the dedicated edit function, the system will always perform incremental saving, regardless of this setting. |
Fields in the Break back section
IMPORTANT: with break back active, data entry forms are also editable if certain dimensions are filtered at the node level.
| Element | Description |
|---|---|
| Dimensions | Allows you to select the dimensions on which to run the break back. - None - Custom dimensions - Custom dimensions - Entity - Accounts |
| Editability check | With break back active, it allows you to select the mode in which the editability check is performed. - Automatic: if the data is saved on a reference element, the system performs the check on the reference lowest element. If no reference element is specified, the editability check is not performed. - On reference lowest element: the system always performs the editability check on the reference element. If no reference element is specified, the data will not be editable. |
| Always write on reference element | With break back active and enabled, for data entry from forms it automatically attributes the changes made on the node to the same node’s reference entity. When disabled, changes made on a node are distributed among the lowest level elements related to the same node in proportion to the values already present. |
Fields in the IC Cockpit Advanced rules section.
| Element | Description |
|---|---|
| Attribute only the reconciliation account category to the cockpit step | If active, the system behaves as follows: For account/category pairs present in an intercompany matching cockpit in which the category is the one used on the IC cockpit for reconciliation accounts, this defines the intercompany step as the step in which the cockpit is currently found. For account/category pairs present in an intercompany matching cockpit in which the category is not the one used on the IC cockpit for reconciliation accounts, it behaves as if the option were not active. If not active, the system behaves as follows: - for account/category pairs belonging to the intercompany matching cockpit, the intercompany step is the same as the cockpit step - for account/category pairs not belonging to any cockpit, where there are overrides, the system considers the intercompany step to be the overridden step. If there are no overrides, it uses the highest step out of the gross data step and the lowest step on which a cockpit is present. |
| Simplified calculation of the ic step | Defines the gross step, or any overridden step, as the intercompany step for accounts/categories not associated with the cockpit. |
| Allow the insertion of reconciliation accounts with IC data entry in progress | Allows you to insert reconciliation accounts even if one of the two entities has not yet finished inserting intercompany entries. Reconciliation accounts can therefore always be added, regardless of the status of the entities of the relationship on the IC matching cockpit. |
| Mandatory notes when inserting reconciliation accounts | Makes it mandatory to insert notes when loading reconciliation accounts. |
Fields in the Spreading section
| Element | Description |
|---|---|
| Intercompany Spreading display method | Tells the system how to display data related to intercompany entries in the data entry step when the intercompany spreading functionality is in use. - All data: the system displays the original declarations and write-off and reallocation entries. - Original data: the system only displays the original declarations. - Only Reallocations: the system only displays data related to reallocations on the counterparty custom dimension 2. |
| Granularity: |
Defines the level of detail for the intercompany spreading functionality. - By element - By node |
| Reference Hierarchy |
Only with |
| Reference level for the |
Only with |
| Display override type CTP |
Enables CTP custom dimension 2 override information in data entry management windows for intercompany entries and entity journals. |
| Preferential allocation to |
Enables the management of intercompany declarations belonging to the entity/counterparty/custom dimension 1 relationships that are balanced as a stand-alone set of declarations. |
| Balancing threshold on |
Defines the threshold below which an entity/counterparty/custom dimension 1 is considered to be balanced. |
| Delete error signs | Enables an intercompany declaration reallocation algorithm on the counterparty custom dimension 2, to eliminate the effects of IC declarations with anomalous signs. For details of the algorithm, see |
Fields in the Countervalue calculation section
| Element | Description |
|---|---|
| Conversion | Defines the type of FX rate to be used in countervalue calculation data processing to convert the following accounts with conversion type set to P&L FX rate. The following FX rates are available: - Average FX rate - Period average FX rate - Final FX rate - Override Period average FX rate on P&L or on Variations accounts: the system converts all P&L accounts, Other Variations accounts and Variations accounts (regardless of their Nature), ignoring the account’s conversion type. Conversion takes place at the period’s average FX rate and the period length is the one indicated on the scenario being processed. For more details on FX rates, see . |
| Run also on Balance Sheet, Other Stock & Guard. and Comm. accounts | Includes balance sheet accounts and normal and detailed other stock accounts in the countervalue calculation data processing. |