An Oracle Fusion Cloud customer has a complex enterprise structure that includes multiple legal entities in multiple countries. To match the intercompany balancing requirements, all four levels of rules have been defined. In user testing, the business experts are asking which rule will be considered first when balancing an intercompany journal?

Oracle Fusion Intercompany Balancing uses a specific hierarchy to find the most applicable rule for a given transaction. The system always evaluates rules from the most specific to the most general level to ensure the most precise balancing treatment is applied. The most specific rule is at the Primary Balancing Segment Value (BSV) level, which defines balancing for transactions between two specific BSVs. If no rule is found at this level, the system then checks for a rule at the Legal Entity level, followed by the Ledger level, and finally, the most general Chart of Accounts level.

A. Ledger-level rule: This rule is evaluated only after the system fails to find a matching Primary Balancing Segment or Legal Entity level rule.
B. Legal entity-level rule: This rule is less specific than the Primary Balancing Segment rule and is only considered if a BSV-level rule does not exist.
C. Chart of accounts rule: This is the most general rule and is used as a last resort when no other more specific rules apply.

1. Oracle Fusion Cloud Financials, Implementing Intercompany Financials Guide, Release 24B, Chapter 3: Intercompany Balancing, Section: "Intercompany Balancing Rules". The documentation states, "The balancing process searches for a rule in the following order: Primary Balancing Segment, Legal Entity, Ledger, and Chart of Accounts rule."

2. Oracle Fusion Cloud Financials, Using General Ledger Guide, Release 24B, Chapter: Intercompany Processing and Reconciliation, Section: "How Intercompany Balancing Rules Work". This section explicitly details the four-level hierarchy and the order of precedence, starting with the Primary Balancing Segment Value rule.