Consolidation > Setting Up Consolidation > Creating COA Cross-References
  
Creating COA Cross-References
Before you can consolidate, you must use COA Cross Reference Create to map GL accounts, sub-accounts, cost centers, and projects in the source entities to the target COA elements in the consolidation entity. You can create either Combined GL Dimension or Separate GL Dimension COA cross-reference mapping types for use in consolidation.
Combined GL Dimension mappings let you specify cross-references from source COA combinations to target COA combinations. Separate GL Dimension mappings let you specify cross-references from separate source COA elements to separate target COA elements (GL accounts to target GL account, sub-accounts to target sub-accounts, and so on).
You can also use COA Cross Reference Excel Integration (25.3.14.6) to load cross-reference mappings from an Excel spreadsheet, reducing the time required to set up consolidation.
See COA Cross-References for detailed information on creating consolidation cross-references and for information on alternate COA cross-references.
Note: Each subsidiary entity and the COA cross-reference it uses must belong to the same domain.
Finding Separate Cross-Reference Mappings
During consolidation, if the system finds multiple Separate GL Dimension mappings for the same source GL COA element, the first mapping found is used.
Finding Combined Cross-Reference Mappings
During consolidation, when the subsidiary entity’s mapping type is Combined GL Dimension, the system reads the GL combination (account, sub-account, cost center, and project) from the source transaction and looks for a match in the cross-reference table. The system searches for matching cross-references in the following order:
1 Matching account, sub-account, cost center, and project
2 Matching account, sub-account, cost center, and blank project
3 Matching account, sub-account, blank cost center, and project
4 Matching account, sub-account, blank cost center, and blank project
5 Matching account, blank sub-account, blank cost center, and blank project
If no match is found, the transaction is posted to the same GL combination specified on the originating transaction. If multiple matches of the same priority are found, the system uses the first one it finds.