Control groups grouping
Dimensions > Control groups> Grouping
Attributes groupings tab
Please find below the most important fields.
| Field | Description |
|---|---|
| Control groups default relationships | The node is automatically related to each control group created. |
| Exclude from reporting | This relationship is not included in the reports. |
Attributes tab control groups
Please find below the most important fields.
| Field | Description | Values |
|---|---|---|
| Control type | Type of control group created. | Details Variation Balancing Coherence |
| Control Operator | Operator used for balancing check | Coherence Equality and relational operators |
| Check by element | Only for Balancing control groups. Control groups are validated at the single-account level rather than on the total of accounts. | |
| Dependence by dimensions | Any relationships between accounts and the various custom dimensions. | Account: the control group is only defined for the account. Account/ |
| Accounts definition | ||
| Var. - Det. type filter | Only if the 'Dependence by dimensions' field is set to Account. Node of the var. - det. types grouping associated with the control group. For 'Flow' or 'Detail' type control groups, the system uses this information to automatically update the control group when using the 'update details/flows' utility. For control groups of type “Balancing” and “Coherence”, in addition to being used as a filter in associating Set 2 accounts with a Variation / Detail type, this information is also used by reporting. | - |
| Define Set 1 | In control groups with dependence by dimension, by account or by account/custom dimension, set the accounts or account nodes to be considered as parent accounts. In control groups with dependence by dimension, by dynamic group of accounts, set the dynamic group to be used to define the parent accounts. | - |
| Define Set 2 | In control groups with dependence by dimension, by account or by account/custom dimension, set the accounts or account nodes to be considered as children. In control groups with dependence by dimension, by dynamic group of accounts, set the dynamic group to be used to define the child accounts. | - |
| Definition results | This displays the lists of parent accounts and child accounts. | - |
| Automatic balancing | The control group is made to be balanced automatically. Option that cannot be activated on control groups with Check by Element or with Dependence by Dimension, by dynamic group of accounts. Note: any unbalanced amounts are reported in a dedicated variation account (Balancing variation). | - |
| Advanced | ||
| Validity | This defines a time interval within which the control group may be used. | - |
| Include in the process if | This defines the conditions for the control group to be used, for data collection purposes. | - |
| Documentation link | Opens a page outside Tagetik with additional information. | - |
Diagnostics tab
Please find below the most important fields.
| Field | Description | Values |
|---|---|---|
| Severity | Consequences triggered by a balancing error. | Blocking: the error blocks the submission process. Non-Blocking: the error is flagged up but does not block the submission process. |
| Data types to check | Type of data checked by the diagnostics carried out on the control group. | Gross: runs diagnostics on gross amounts. Net: runs diagnostics on net amounts. Intercompany: runs diagnostics on intercompany data. |
| Advanced | ||
| Check original data on | Currency used to carry out the control group balancing check. | Local currency: this uses the financial statement currency. Transaction currency: this uses the transaction currency. |
| Check original data for | The level at which the control group checks the 'amount’ type categories. | Company: the check is carried out for each individual company. Contributor node: the check is carried out on the total of the amounts for the companies belonging to a contributor node. Company and contributor node: the check is carried out both at company level and at contributor node level. |
| Check consolidation journals by Company | For ‘consolidation journal’ categories, this states whether the control group is to be checked only by the journal number or by the combination of journal number/company. | - |
| Dimensions check | ||
| Check by |
Level of detail of the check carried out within the custom dimension indicated. | Total Lowest level elements Hierarchy nodes |
| This allows you to specify a hierarchy node if the custom dimension check is enabled and the ‘Hierarchy nodes’ mode is selected. | - |
Relationships tab
| Field | Description |
|---|---|
| Nodes | Node within a control group hierarchy. |
Restrictions tab
Please find below the most important fields.
| Field | Description | Value |
|---|---|---|
| Restrictions for the specific custom dimension | None: all custom dimensions are accepted. Restricted: it is possible to define restrictions on enabled custom dimensions. | |
| Counterparty rule for IC checks | This allows you to enable counterparty dynamic groups in IC checks. | - |
Calculation Logics tab
Please find below the most important fields.
| Field | Description |
|---|---|
| Create | This defines whether the control group generates one or more calculation rules. |
| Calculate | This indicates the criteria used to generate the calculation rule. |
| Data to calculate | |
| Run on Gross amounts | The account generated is calculated based on gross amounts. |
| Run on IC amounts | The account generated is calculated based on intercompany amounts. |
| Run on journals | The account generated is calculated based on journals. |
| Other options | |
| Compensate Company on journals | In a costs/revenues elimination journal, this avoids the system generating two rows with an opposite sign. Only enabled if the account generated is calculated based on journals. |
| Keep CTP on journals | The counterparty is kept in the account calculation based on journals. Only enabled if the account generated is calculated based on journals. |
| Keep original currency | The company currency amount and the transaction currency amount are managed separately, |