IC matching diagnostic
Description of the check¶
Intercompany matching is carried out via a special cockpit which shows IC data by entity/counterparty entity (or entity-custom dimension2/entity-counterparty custom dimension2), which the manager users from the entity and the counterparty entity use to confirm that the loaded IC data is correct. See .
This check does not go into the details of the declared IC data, but simply verifies that all the possible relationships that are/can be calculated by the cockpit have been matched. It is only run on original scenarios and reports any unbalanced amounts on the step to which the cockpit is related.
Note: one or several intercompany cockpits can be associated with every step of the process.
Entity elements table and IC and diagnostic cockpits¶
The following attributes are significant for running diagnostic data processing:
| Attribute | Description |
|---|---|
| IC Cockpits elements table | |
| IC matching for submission check | The IC matching diagnostic is only run for IC cockpits whose setting is not equal to None (). |
| Entity elements table | |
| IC matching | Mandatory: failure to run IC matching will block submission. Optional: IC matching is not mandatory for the entity because it cannot carry out that activity in time for the closing date of the relative step. If A and B are entities for which IC matching is not mandatory while it is mandatory for entity C, then: - C does not have to match its own intercompany entries to A and B - A and B must match their own intercompany entries to C - in cases of IC relationships between A and B, the first to submit data does not have to match, while the other is obliged to do so Automatic: relationships in which at least one of the two entities has this option active are matched automatically, consequently: - they do not appear in the IC cockpit - failure to run matching does not block submission See . |
The check is run according to the following logic:
| If... | Then... |
|---|---|
| IC matching for submission check = Non blocking | the check is run and unmatched relationships are reported with Non-blocking severity. |
| IC matching for submission check = Blocking | the check is run and unmatched relationships are reported with Blocking severity. |
| IC matching for submission check = Only Diagnostic | the check is only run if explicitly requested by manually running the diagnostic from the Detail summary (for the contributor) or Overview (for the consolidator) cockpit tabs; in this case it is possible to customise the filters before running the data processing. However, whenever diagnostics are run automatically (from the cockpit/from other data processing), the check is not performed. |