Create IC Cockpits page
Data Processing tile > Basic Consolidation > IC matching and elimination logics > IC cockpit
Navbar > Data Processing tile > Basic Consolidation > IC matching and elimination logics > IC cockpit
Purpose of the page¶
This page allows you to configure IC cockpits so you can relate them to steps of the process and thus check the intercompany matching and elimination procedure via an IC matching cockpit.
Actions on this page
| Element | Description |
|---|---|
| Reconciliation accounts for other accounting: opens a page to configure the accounts, both debit and credit, to be used as the reconciliation accounts in the matching logics associated with the selected IC cockpit. These accounts are used when a relationship in the IC matching cockpit is locked/submitted. In fact, the system checks whether the reconciliation accounts are balanced for the various defined debit/credit account pairs. If the same account is specified as the debit and credit account, the balancing check is performed for the individual account. |
IC cockpit attributes
| Field | Description |
|---|---|
| Code | Unique code of the IC cockpit |
| Description | Description of the IC cockpit in all enabled system languages |
| User type | Defines the type of user that can use the cockpit (Contributor or Consolidator). “Consolidator” IC cockpits cannot be accessed from the contributor cockpit. |
| IC matching logics filter | Specifies a group of IC matching and elimination logics managed in the IC cockpit. |
| Category | Specifies the categories on which to insert intercompany entries in the IC cockpit. You can specify a single category or a group of categories. They also depend on the user type. |
| Reconciliation accounts category | Specifies the default category on which to insert the reconciliation accounts in the IC cockpit. They depend on the type of user. |
| Advanced | |
| IC matching details | Specifies the matching method. - by Entity (default) - by Entity / Custom Dimension 2 to match the intercompany entries at a more detailed level than the entity level. For example, use this for entities that operate in various sectors where you want to aggregate the data by line of business. Note: in the IC matching cockpit, matching by Entity / Custom Dimension 2 is only allowed if the Relationship Type is also Entity / Custom Dimension 2 for the data collection process. |
| P&L account matching on periodical data | If selected, the IC matching cockpit shows the amounts considering the periodic (monthly) value instead of the cumulated value. Only valid for P&L accounts and variation accounts. The following actions are possible from the IC cockpit: - View the periodic values with amounts converted to the Cockpit amount. However, the displayed IC entries cannot be edited. - View the cumulated IC entries and insert the transactions for the period. |
| Allows IC matching even without Balancing | If selected, the IC matching cockpit allows you to match a relationship without balancing on one or several matching logics. In particular: - It is not necessary to make the IC insertion complete declaration for the entities of the relationships. - If you block/submit a relationship, the balancing of matching logics is not verified. |
| IC matching for submission check | Indicates the severity to be attributed to matching errors detected by the diagnostics. Note: IC matching diagnostics only check that all the possible relationships calculated/calculable by the cockpit have been matched. - Do not run (default). The diagnostics does not run the IC matching check. - Non blocking. The check is run and the unmatched relationships are marked with Non-blocking severity. - Blocking. The check is run and the unmatched relationships are marked with Blocking severity. - Only Diagnostic. The check is only performed if requested by the running customised diagnostics. When diagnostics are run automatically from the cockpit or from other data processing, the check is not performed. |