IC amounts page
User
Processes tile > select process > Contributor > Detail summary tab > (Actions) Edit windows > Edit IC
Processes tile > select process > Consolidator > Overview tab > (Actions) Edit windows > Edit IC
Processes tile > select process > Step tab > from a workflow task > select an IC amounts task > Run
Navigation panel > Processes > select process > Contributor > Detail summary tab > (Actions) Edit windows > Edit IC
Navigation panel > Processes > select process > Consolidator > Overview tab > (Actions) Edit windows > Edit IC
Navigation panel > Processes > select process > Step tab > from a workflow task > select an IC amounts task > Run
Purpose of the page¶
This page shows a list of the inserted IC amounts and allows you to insert others. Shows a view dedicated to managing the amounts of the selected entities. If nodes are selected, the amounts of entities belonging to the selected nodes will be shown, going down recursively to the last level.
The filters applied to the page can always be edited from the filters panel (
) and saved for future access.
Click 
to view columns with additional information on the page: account nature, account type and origin.
IC amounts inserted manually have “INPUT_WEB” indicated as their Origin.
Note: You can configure CCH Tagetik so that IC amounts with different origins are different colours. See Colours by origin option in the .
Icons on this page
| Element | Description |
|---|---|
| The amounts cannot be edited. Shows the reason for the lock. | |
| The amount data are no longer consistent, e.g. on accounts or entities not belonging to the process. Shows the reason for the inconsistency. The row and the amount can be deleted using the button. |
Actions on this page
| Element | Description |
|---|---|
| Spreadsheet view: shows the data in a spreadsheet. | |
| List view: shows the data in a table. Default view. | |
| Relationship check: shows the result of a diagnostic balancing check which considers, based on the selected relationship, all the IC amounts declared by the declaring entity towards the counterparty entity (and vice versa) for all the accounts present in the IC matching and elimination logic in the process and in which the selected account is found. Check all: shows the result of a diagnostic balancing check which considers, based on the selected relationship, all the IC amounts inserted by the declaring entity towards the counterparty entity (and vice versa) and all the IC amounts in which the entity is present as the declaring or counterparty entity for all the accounts present in the IC matching and elimination logic processed in the process and which includes the selected account. Diagnostic: Only if diagnostic is enabled on the process. Runs the diagnostic on the entities to which the selected amounts belong if the category type is “contributor amount”; runs it on the consolidator nodes if the category type is “consolidator amount”. See . |
Page attributes
The Additional fields tab is only shown if the Enable additional fields on IC option is not set to “No” in the process’s gross and IC amount rules.
Note: these fields contain information that is necessary for the automatic document relationship procedure, which relates an entity’s IC declarations to a counterparty’s declarations based on information related to the invoice.
| Field | Description |
|---|---|
| General | |
| Scenario | Scenario to which the amount 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. |
| Period | Period to which the selected amount belongs. You can choose a different period, provided that it is not locked and is linked to the selected scenario. |
| Entity | Entity to which the selected amount belongs. You can choose another entity, provided it meets the following requirements: - Editable by 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 defined, must be between the start date and end date of the selected scenario/period. |
| Category | Amount category The chosen categories must meet the following requirements: - Editable by the user. - Belong to the selected process. - If the page is opened from the Contributor cockpit, the category type must be “contributor amount”. - If the page is opened from the Consolidator cockpit, the category type must be “consolidator amount”. |
| Account | Account on which the amount was inserted. The chosen account must meet the following requirements: - Enabled for IC management. - Editable for the user. - Linked to the data model process associated with the selected entity. - Start date and end date, if present, must be between the start date and end date of the scenario/period to which the amount belongs. |
| Custom dimension | For every managed custom dimension, if enabled in the process’s gross and IC amount rules, you can select an element of the custom dimension which meets the following requirements: - Editable for the user. - Visible from the selected entity. - Visible from the selected account. If no value is selected, CCH Tagetik will choose the custom dimension to be the entity’s default custom dimension or the custom dimension with the lowest code from among those which meet the above requirements. The custom dimension 2 is managed even if it is not enabled in the process’s gross and IC amount rules, but the process’s relationship type is “entity - custom dimension 2” or “entity - synthetic custom dimension 2”. |
| CTP entity | 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 |
| CTP 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. |
| Entity currency | Currency assigned to the entity in the process. Defined automatically and non-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. |
| Transaction currency | Only present if the transaction currency is managed on IC amounts in the process’s gross amounts and IC rules. If not entered, it will be defined as the entity currency. |
| Transaction currency amount | Only present if the transaction currency is managed on IC amounts in the process’s gross amounts and IC rules. Defined as the entity currency amount even if the Transaction currency field is empty. Defined automatically as the entity currency amount, applying the conversion rate set on the account, if the transaction currency has been entered and is different from the entity currency, and if the entity currency amount is defined and the transaction currency amount is not. The same is true for the entity currency amount, if it is not defined but the transaction currency amount is defined. |
| Notes | Any explanatory notes. For example: - On rows originating from the merger data processing, to store information on the incorporating entity. - On rows originating from the base calculation logics, to store information on which calculation logic generated the row. |
| Additional fields | |
| Relationship | Any information on the relationship between an entity’s IC declarations and the counterparty declarations. |
| Invoice number | Document identifier. Used by the automatic document relationship procedure if it has been requested to relate documents which have the same document number. |
| Invoice date | Document date. Used by the automatic document relationship procedure if it has been requested to relate documents which have the same document date. |
| Document Type | Document type: - Document - Bill - Accrual |
| Accounting date | Date on which the document was booked. |
| Sent/Received | Indicates whether the document has been sent or received. |
| Invoice matching number | Identifier of the relationship created between an entity’s IC declarations and a counterparty’s declarations. It is generated by the automatic invoices relationship procedure. In some cases, it is not possible to automatically create relationships between IC declarations, for example, if an entity has entered the booking date instead of the invoice date. However, you can relate the IC declaration manually by setting the Invoice matching number field with the same number used in the counterparty entity’s IC declaration. You can also edit an automatic relationship number that has been generated by the system. Note: for the manual relationship, do not use a code that starts with $, as this symbol is used by the system to automatic relationships. |