Headers (Consolidation journals) page
User
Processes tile > select process > Consolidator > Overview tab or Step tab > (Actions) Edit windows > Edit Consolidation journals
Processes tile > select process > Step tab > from a workflow task > select a Consolidation journals task > Run
Navigation panel > Processes > select process > Consolidator > Overview tab or Step tab > (Actions) Edit windows > Edit Consolidation journals
Navigation panel > Processes > select process > Step tab > from a workflow task > select a Consolidation journals task > Run
Page purpose¶
This page allows you to define the composition of consolidation journal headers. It also shows certain calculated, non-editable information for every header.
Icons on this page
| Element | Description |
|---|---|
| Journal being created and not yet saved | |
| Journal being deleted and not yet saved | |
| Journal not balanced | |
| Draft journal | |
| Journal containing attached documents/journal with amortisation/depreciation plan | |
| The headers cannot be edited. Shows the reason for the lock. |
Actions on this page
| Element | Description |
|---|---|
| Spreadsheet view: shows the data in a spreadsheet. | |
| List view: shows the data in a table. Default view. | |
| Submit all automatic journals: Only if journal submission on at least one entity is active on the process. Opens a window to select the scenario/period and the step for which to submit all automatic journals, or those for which rows with manual origin are not present (INPUT_WEB, INPUT_DEFORM, BREAK_BACK, QDL or MAP_%). See . Post all the draft Journals: Only if categories for which to manage “Draft journal” status are defined on the process. Opens a window to select the scenario/period for which to post all the draft journals, thus making them visible to data processing and reports. See Draft Journals. | |
| Allows you to access specific actions for the headers, see Actions from the journal headers. |
Attributes on the page
The following information is shown in addition to the attributes that can be defined from the configuration tabs:
Not all attributes may be visible by default. Click 
to select other columns to be shown.
| Field | Description |
|---|---|
| In progress | Indicates whether the journal includes “Draft” rows (). These do not influence the result of the data processing or the reports until they are published. Only present if the relative function is activated by creating categories for draft journals (Journal rules and settings page). |
| Balancing | Indicates whether or not the journal is balanced. If it is not, the journal will be reported (). Note: balancing is calculated by adding the amounts of all accounts of “Balance Sheet” nature and “Normal” type that are present in the journal rows. |
| Documents | Indicates whether there are any documents attached to the journal. |
| Amortisation/Depreciation | Indicates whether the journal manages depreciation. |
| Manual rows | Indicates whether the journal contains rows with manual origin. |
| Journal number | Identifier of the journal within the scenario/period. During data entry, it is calculated according to the journal numbering method defined in the default settings (seeDefault Settings window): - if the journal numbering method is manual, it is calculated by concatenating the journal prefix and suffix - if the numbering method is automatic, it is generated by the system by concatenating EJ_ |
| Generator type | For automatically generated journals, this indicates the data processing that generated them. - Ctp elimination logic - Reclassification accounts logic - NER logic - Closing version rule - Mapping - Look Through Vehicle entity - IFRS5 event - Look Through operational entity - IFRS5 IC eliminations write off - Rules Engine Designer |
| Generator | For automatically generated journals, it indicates the code of the generator. For example, if the generator type is equal to “CTP elimination logic”, it will contain the code of the elimination logic. |
| Original generator | For automatically generated journals, it indicates the code of the generator of the original journal from which the journal was generated. |
| Original category | For automatically generated journals, it indicates the category code of the original journal from which the journal was generated. |
| Original entity 1 | For automatically generated journals, it indicates the entity 1 code of the original journal from which the journal was generated. |
| Original entity 2 | In case of automatically generated journal, it indicates the code of Entity 2 of the original journal from which the journal was generated. |
Attributes in the General tab
| Field | Description |
|---|---|
| Scenarios | Scenario to which the journal belongs. You can choose an active original scenario, which you can edit and for which there exists at least one unblocked period belonging to the selected process. IMPORTANT: once saved, this data can no longer be edited. |
| Period | Period to which the journal belongs. The chosen period must not be locked and must be linked to the selected scenario. IMPORTANT: once saved, this data can no longer be edited. |
| Entity 1 | One of the two entities in the relationship to which the journal belongs. The chosen entity must meet the following requirements: - Must be visible for the user. - Belong to the selected process. - Belong to the selected scenario/period and, on that scenario/period, cannot be an “Only CTP” entity. - Start date and end date, if present, must be between the start date and end date of the selected scenario/period. IMPORTANT: once saved, this data can no longer be edited. |
| Custom dimension 2 1 | Only if custom dimension 2 is managed and the process’s relationship type is “entity - custom dimension 2”. You can only select an element of the custom dimension 2 that is visible to entity 1. IMPORTANT: once saved, this data can no longer be edited. |
| Entity 2 | One of the two entities in the relationship to which the journal belongs. The chosen entity must meet the following requirements: - Must be visible for the user. - Belong to the selected process. - Belong to the selected scenario/period and, on that scenario/period, cannot be an “Only CTP” entity. - Start date and end date must be between the start date and end date of the selected scenario/period. IMPORTANT: once saved, this data can no longer be edited. |
| Custom dimension 2 2 | Only if custom dimension 2 is managed and the process’s relationship type is “entity - custom dimension 2”. You can only select an element of the custom dimension 2 that is visible to entity 2. IMPORTANT: once saved, this data can no longer be edited. |
| Journal prefix | Only if the journal numbering method defined in the default settings is manual. Prefix to be used when inserting a new journal to form its number. By default, the prefix defined as the Journal prefix is used (see Default Settings window). IMPORTANT: do not enter any prefixe used by data processes generating automatic journals ("MIN_", "EQ_", "GPN_", "ELICTP_", "RECL_", "EQNFI_", "MRECL_", "IFRS5_", "EPUA_", "EPUT_", "LTO_", "LTV_", "ESM_", "ESR_", "EJ_", "CJ_"). |
| Journal suffix | Only if the journal numbering method defined in the default settings is manual. Suffix to be used when inserting a new journal to form its number. |
| Unit | Journal currency. IMPORTANT: once saved, this data can no longer be edited. |
| Category | Journal category. The chosen categories must meet the following requirements: - Editable by the user. - Belong to the selected process. - The category type must be “consolidation journal”. Based on the category assigned to the journal, certain information is entered automatically according to what is defined in the categories list in the Default for manual journals section. See Categories list. Note: journals attributed to the same category are generally processed and treated in the same way. |
| Note | Any explanatory notes Field not editable if the journal is generated by counterparty eliminations. Note: all journals whose number starts with “ELICTP_” are considered to be journals generated by the counterparty eliminations. |
| Advanced options | |
| Periodic journal | Enables periodic management for the journal. See Journal management. |
| Many to many relationship | Indicates whether the journal rows can be attributed to any entity (and custom dimension, if the process’s relationship type is “entity - custom dimension 2”), regardless of what is declared in the header. Field not editable if the journal is generated by counterparty eliminations Note: all journals whose number starts with “ELICTP_” are considered to be journals generated by the counterparty eliminations. |
| Consolidation Scenarios filter | With the Consolidation scenario function (Consolidation scenario page), it allows you to filter the consolidation scenarios in which a journal is considered. Note: in general, the system decides whether journal is included in a consolidation scenario according to the entity and the category. |
| Journal is complete | Indicates that the journal’s insertion is complete. This can be used, for example, to indicate journals that are ready to be valued to change category. Field not editable if the journal is generated by counterparty eliminations. Note: all journals whose number starts with “ELICTP_” are considered to be journals generated by the counterparty eliminations. |
| Grouping for Journals book | Label that allows you to group the journals within the journal book, if this is run with the Journals grouping option = “Journals grouping” (Headers (Consolidation journals) page). Field not editable if the journal is generated by counterparty eliminations Note: all journals whose number starts with “ELICTP_” are considered to be journals generated by the counterparty eliminations. |
Attributes in the Data Processing tab
| Field | Description |
|---|---|
| Override journal parameters | If enabled, it allows you to override the setup of the Proportional calculation method, Minorities calculation method, Minorities calculation on entity 1, Minorities calculation on entity 2, Equity evaluation method, Tax calculation method, Reverse journal type, Enable carry forward, and Exclude Reclassifications and NER options so they are no longer the default set in the categories list or elimination logic. See Categories list and Intercompany matching and elimination logics . |
| Proportional calculation method | Only if Override journal parameters is selected. This indicates how to determine the proportional calculation percentage: - None - Lesser % - Greater % - Entity 1 % - Entity 1 % * Entity 2 % (only for processes that use the “In memory” consolidation engine). If Override journal parameters is not selected and the generator type is “CTP elimination logic”, then it is defined using what is present on the elimination logic indicated in Generator. For other types of generator, it is defined using the relative value present in the categories list. |
| Minorities calculation method | Only if Override journal parameters is selected. This defines how to calculate the minorities: - Normal - Based on Entity 1 % - Advanced (selectable only if the journal type is not "Many to many relationship") - None If Override journal parameters is not selected and the generator type is “CTP elimination logic”, then it is defined using what is present on the elimination logic indicated in Generator. For other types of generator, it is defined using the relative value present in the categories list. |
| Minorities calculation on entity 1 | Indicates how to calculate the minorities on entity 1. If these requirements are met: - Override journal parameters is selected - The process manages In memory consolidation, i.e. in general configuration the consolidation engine is set to “In memory” or “Defined by process” and on the process, among the consolidation requirements, the in memory consolidation engine is selected. - The minorities calculation method is Advanced. It can take the following values: - Based on entity 1 % - Based on Entity 2 % - None If one of the requirements is not met, then: if Override journal parameters is selected: |
| Minorities calculation on entity 2 | Indicates how to calculate the minorities on entity 2 If these requirements are met: - Override journal parameters is selected - The process manages In memory consolidation, i.e. in general configuration the consolidation engine is set to “In memory” or “Defined by process” and on the process, among the consolidation requirements, the in memory consolidation engine is selected. - The minorities calculation method is Advanced. It can take the following values: - Based on Entity 1 % - Based on Entity 2 % - None If one of the requirements is not met, then: if Override journal parameters is selected: |
| Equity evaluation method | Only if Override journal parameters is selected. This indicates what the system should do during the equity evaluation step where there is an entity at equity: - None - Delete - Evaluate with equity method: single Entity journals - Evaluate with equity method: if entity 2 is at equity (only if entity 1 and entity 2 are different) If Override journal parameters is not selected and the generator type is “CTP elimination logic”, then it is defined using what is present on the elimination logic indicated in Generator. For other types of generator, it is defined using the relative value present in the categories list. |
| Tax calculation method | Only if Override journal parameters is selected. Indicates the calculation method for deferred taxes: - None - Entity 1 - Entity 2 - Entity 1 -Invert credits/debits - Entity 2 -Invert credits/debits - None - Permanent OCI - None - Permanent P&L If Override journal parameters is not selected and the generator type is “CTP elimination logic”, then it is defined using what is present on the elimination logic indicated in Generator. For other types of generator, it is defined using the relative value present in the categories list. |
| Reverse journal type | Only if Override journal parameters is selected. Indicates whether and how the journal must be automatically reversed in the restore step. It can be set as follows: - None - Set BS accounts to 0 (cut off) - Set BS accounts to 0 and Write off P&L impact (IC) - Set BS accounts and Variations to 0 and Write off P&L impact (IC) If Override journal parameters is not selected and the generator type is “CTP elimination logic”, then it is defined using what is present on the elimination logic indicated in Generator. For other types of generator, it is defined using the relative value present in the categories list. For details on reversals, see Journal reversal data processing. |
| Enable carry forward | Only if Override journal parameters is selected. Indicates whether or not the journal must be carried forward into the subsequent scenario. If Override journal parameters is not selected and the generator type is “CTP elimination logic”, then it is defined using what is present on the elimination logic indicated in Generator. For other types of generator, it is defined using the relative value present in the categories list. |
| Exclude Reclassifications and NER | Only if Override journal parameters is selected. This indicates whether equity reclassification and account reclassification must be carried out for the journal. If Override journal parameters is not selected and the generator type is “CTP elimination logic”, then it is defined using what is present on the elimination logic indicated in Generator. For other types of generator, it is defined using the relative value present in the categories list. |
Attributes of the Submission status tab
| Field | Description |
|---|---|
| If journal submission is active, this indicates the submission status of the journal in the step. It can be set as follows: - Not Started - Started - Rejected - In Submission - Submitted - Not relevant. This is the case if the journal submission is not enabled for the step or the entity/node to which the journal belongs. | |
| If journal submission is active, this tells the user who performed the journal’s most recent submission activity in the step. | |
| If journal submission is active, this indicates the date on which the journal’s most recent submission activity in the step was performed. |