Original and consolidated rows page
User
Processes tile > select process > Contributor > Detail summary tab or Step tab > (Actions) Edit windows > Edit Entity Journals > 
> Rows > 
> Original and consolidated rows
Processes tile > select process > Consolidator > Overview tab or Step tab > (Actions) Edit windows > Edit Entity Journals > > Rows > > Original and consolidated rows
Processes tile > select process > Consolidator > Overview tab or Step tab > (Actions) Edit windows > Edit Consolidation journals > > Rows > > Original and consolidated rows
Navigation panel > Processes > select process > Contributor > Detail summary tab or Step tab > (Actions) Edit windows > Edit Entity Journals > > Rows > > Original and consolidated rows
Navigation panel > Processes > select process > Consolidator > Overview tab or Step tab > (Actions) Edit windows > Edit Entity Journals > > Rows > > Original and consolidated rows
Navigation panel > Processes > select process > Consolidator > Overview tab or Step tab > (Actions) Edit windows > Edit Consolidation journals > > Rows > > Original and consolidated rows
Purpose of the page¶
This page allows you to view, directly from the journal, the consolidated data that result from the original amount entered (or from the carry forward) and the original amount.
For each amount type, it also shows the Balancing value, i.e. the sum of all the amounts of accounts with “Balance Sheet” nature and “Normal” type.
Consolidated rows are not editable; however, you can delete them or change some of their attributes using the override functions (Actions from journal headers).
Page tabs
| Tab | Description |
|---|---|
| Original and consolidated rows | When the page is opened, the original rows are show. If a consolidation scenario is selected in Consolidation scenario, it will show the consolidated rows for that scenario. |
| Documents | Lists any documents attached to the journal. Allows you to download any attachments. For document management, see Documents page. |
Actions in the Original and consolidated rows tab
| Element | Description |
|---|---|
| Consolidation scenario | Allows you to select a consolidation scenario to view its consolidated rows. |
| Amount Type | Allows you to select the type of data to view. - Original - Consolidable - Converted - Proportional |
Fields in the Original and consolidated rows tab
| Field | Description |
|---|---|
| Amount Type | Allows you to reconstruct the steps that involved the original amount entered: - from original to proportional - from proportional to converted - from converted to consolidable |
| Scenario | Scenario set in the header. Not editable. |
| Period | Period set in the header. Not editable. |
| Journal number | Journal number in the header. Not editable. |
| Entity | Entity set in the header. Not editable. |
| Account | Account on which a value is entered. The chosen account must meet the following requirements: - Editable for the user. - Linked to the data model process associated with the entity to which the journal belongs. - Start date and end date, if set, must be between the start date and end date of the scenario/period to which the journal belongs. If the CTP entity field is defined, it must allow intercompany data management. |
| Category | Category set in the header. Not editable. |
| Custom dimension | For every custom dimension that is managed and enabled in the process’s journal rules, you can select an element of the custom dimension which meets the following requirements: - Editable for the user. - Visible from the entity to which the journal row belongs. - Visible from the selected account. If no value is selected, the custom dimension will be shown as the entity’s default custom dimension or the custom dimension with the lowest code from among those which meet the above requirements. IMPORTANT: the custom dimension 2 is managed even if it is not enabled in the process’s journal rules, but the process’s relationship type is “entity - custom dimension 2” or “entity - synthetic custom dimension 2”. |
| CTP entity | Counterparty entity in the journal. An entity can be chosen, provided it meets the following requirements: - Belong to the selected process. - Must belong to the selected scenario/period. - Start date and end date, if present, must be between the start date and end date of the selected scenario/period. You can define a list of most frequently used counterparty entities, see . To use only a subset of entities as counterparties, it may be useful to create a group of counterparties (Dynamic counterparty groups). You can also declare IC data in the context of the same entity (and therefore use the same code for both the entity and the counterparty). This is only possible if the Allow intercompany declarations towards same Declaring entity option is active (Amount & Intercompany rules page). For example, this is useful for eliminating dividends received from group companies towards profits carried forward, or for eliminating self-invoicing results. |
| CTP custom dimension 2 override type | Only present under the following conditions: - Custom dimension 2 is managed. - The process’ relationship type is “entity - custom dimension 2” or “entity - synthetic custom dimension 2”. - The Spreading - Show CTP custom dimension 2 override type option is active in the process’s gross and IC amount rules. - The user’s role contains function 0002274. It can be set as follows: - To allocate - None - Override |
| Counterparty custom dimension 2 | Only present under the following conditions: - Custom dimension 2 is managed. - The process’ relationship type is “entity - custom dimension 2” or “entity - synthetic custom dimension 2”. It is only mandatory under the following conditions: - A CTP entity has been specified. The field is only editable if the Spreading - Display CTP custom dimension 2 override type option is active in the process’s gross and IC amount rules, or if that option is active and: - The user’s role contains function 0002274. - CTP custom dimension 2 override type is not “To allocate” If the field is editable, it is defined as the CTP entity’s default custom dimension 2 or, if the Spreading - Show CTP custom dimension 2 override type and Show CTP custom dimension 2 with entity’s default element options are not active in the process’s gross and IC amount rules, the field is defined as the default custom dimension 2 element specified in the custom dimension 2 settings. |
| Consolidation currency | Currency of the consolidated rows, generated by the consolidation process. Only defined on the converted and consolidable rows. |
| Consolidation currency amount | Amount of the consolidated rows, generated by the consolidation process. Only defined on the converted and consolidable rows. |
| Conversion | Conversion type applied to generate the consolidated rows. Only defined on the converted and consolidable rows. |
| Company currency | Currency set in the header, not editable. |
| Entity currency amount | Amount expressed in the entity currency. Regardless of the number of decimals inserted, amounts are shown with a number of decimals that is consistent with those assigned to the currency in which they are expressed, with the exception of “Other stocks” and “Other variations” accounts where the Manage maximum number of decimals option is active (see ). For these accounts, it is possible to insert up to 9 decimals. The amount may be shown in two different columns: Entity currency amount - debit and Entity currency amount - credit. This happens if the Amounts option is set to Write amounts in Debit & Credit columns in absolute value in the journal rules definition (Default Settings window). |
| Override FX rate | Only present if the transaction currency is managed on entity journals in the process’s journal rules. If selected, you can edit all the amounts in the current row, thereby indirectly overriding the field applied to change from the entity currency amount to the transaction currency amount. Otherwise, only the transaction currency will be editable, but the transaction currency amount will not be. On saving, it automatically defines the amount in the transaction currency based on the account’s conversion type. |
| Transaction currency | Only present if the transaction currency is managed on entity journals in the process’s journal rules. If not entered, it will be defined as the entity currency. |
| Transaction currency amount | Only present if the transaction currency is managed on entity journals in the process’s journal rules. If the transaction currency has not been entered or is the same as the entity currency, the field is defined as the entity currency amount. Otherwise, if the Override FX rate option is not selected, the entity currency will be defined automatically based on the account’s conversion type. For the rest, the considerations made for the Entity currency amount will be valid. |
| Notes | Any explanatory notes |
| Additional notes | Any additional notes |