20.18.6 Map Level Reconciliation

In map level reconciliation, the difference between GL Data and PP Data at each reconciliation dimension node level across all PPs is identified. Unlike GL level reconciliation, map level reconciliation is computed at an aggregate level of the reconciliation definition; by ignoring the GL code and by considering reconciliation dimensions. Map level reconciliation is applied at the legal entity level - either solo or consolidated. If it is at the solo level, then exposures originating in a particular legal entity are selected. If it is at the consolidated level, then exposures originating in the selected legal entity and its child entities (excluding intra-group exposure depending on GL structure) are selected.

Note:

In a map level reconciliation, adequate filters for the PP data must be selected to ensure that the actual data selected on both sides are the same.

You need to create GL hierarchy data with one additional node value as 'MSG'. You can provide this Child code as 'MSG' and the name of the node can be set to 'Missing'. Add this node under the root node of the General Ledger Hierarchy which is sourced in the application.

The adjustment entry allocation depends on the reconciliation type selected. In map level reconciliation, after a definition has been executed the differences that emerge as a part of the reconciliation (General Ledger–Product Processor Level Reconciliation) are reported in the Adjustment Entry Table. This table shows all the entries of an executed map that requires adjustment. The difference in amount can either be posted to Product Processors or an external table. The adjustment allocation can be either automatic or manual.