Your organization has implemented a global Chart of Accounts, which is used by all ledgers. It has the following segments: Company, Department…

The hierarchy for evaluating intercompany balancing rules is Ledger, Legal Entity, and then Chart of Accounts. When an organization uses a single, global Chart of Accounts (COA) and has standardized intercompany accounts, defining the rule at the COA level is the most efficient and minimal configuration. This approach creates a single rule that applies to all ledgers and legal entities sharing that COA. This avoids the need for redundant, more specific rules at the Ledger or Legal Entity level, simplifying maintenance and ensuring consistency across the enterprise.

A. Ledger Rules: This is a more specific level of configuration. It is not the minimum level if the rule applies globally to all ledgers sharing the COA.

B. Primary Segment Rules: These rules are evaluated after COA rules and are used for balancing at the primary balancing segment level, which is a more granular setup.

D. Legal Entity Rules: This is also more specific than the COA level. It would require creating separate rules for each legal entity, which is inefficient.

1. Oracle Fusion Cloud Financials, Implementing Intercompany (Release 24B), Chapter 3: Intercompany Balancing, Section: "How Intercompany Balancing Rules Work". The documentation states, "The balancing process first searches for a rule for the combination of provider and receiver ledger... If no rule is found, it continues to search for a rule at the legal entity level... If no rule is found, it searches for a chart of accounts rule..."

2. Oracle Fusion Cloud Financials, Using Intercompany (Release 24B), Chapter 2: Intercompany Balancing, Section: "Intercompany Balancing Rules: Explained". This section details the hierarchy and purpose of each rule type, confirming that the Chart of Accounts rule is the broadest level for entities sharing a COA.