Oracle Fusion Cloud ERP · GL Architecture

The Case for Additional Balancing Segments
by Industry

Why one balancing segment was never enough — and what Oracle Fusion's secondary and tertiary balancing segments solve across every major vertical. Includes typical CoA structures per industry.

CoA Segment Colour Coding — Frequency of Use
Mandatory (always present)
Essential (near-universal)
Common (most industries)
Frequent (specific verticals)
Optional / Industry-specific
▼
Segment:
Industry ↕ Who to Talk To ↕ Question to Ask ↕ Segment ↕ Typical CoA Structure Key KPIs Saved ↕
No results found. Try a different search or filter.
0
Industries Covered
70–80%
Avg. Reduction in Manual Journals
50–65%
Faster Month-End Close
~95%
Reduction in OU Sprawl
40–60%
Less IT Customization Effort
Configuration Reference
Intracompany vs Intercompany Balancing Rules
▼

A common implementation question is whether configuring secondary or tertiary balancing segments requires setting up intercompany balancing rules. The answer is no — what is required is intracompany balancing rules. These are fundamentally different concepts in Oracle Fusion, and confusing them is one of the most frequent configuration mistakes during GL setup.

Intercompany Balancing

Intercompany Balancing Rules

Applies when a transaction crosses two different legal entities — for example a sale between Company A and Company B under the same group. Fusion generates intercompany receivable and payable entries to keep each legal entity's books balanced.

This is driven by the Primary Balancing Segment and its association to legal entities. It involves two separate sets of books and is governed by the intercompany relationship setup between legal entities.

Example: Company 100 (UK) sells goods to Company 200 (France). Fusion auto-posts an intercompany receivable in Company 100 and an intercompany payable in Company 200 to keep both entities balanced.
Intracompany Balancing

Intracompany Balancing Rules

Applies when a transaction crosses multiple values of a balancing segment within the same legal entity. This is exactly what secondary and tertiary balancing segments require. Fusion generates Due-To and Due-From lines to ensure every segment value carries a balanced set of financial statements.

This is configured per ledger and applies independently to the primary, secondary, and tertiary balancing segments. It does not involve multiple legal entities.

Example: A journal touches Fund 100 and Fund 200 within Legal Entity 10. Fusion auto-posts a Due-From entry in Fund 100 and a Due-To entry in Fund 200 so both funds independently balance.
Side-by-Side Comparison
Dimension Intercompany Intracompany
Triggered byTransaction crosses legal entitiesTransaction crosses balancing segment values within the same legal entity
Driven by segmentPrimary Balancing Segment (Legal Entity)Secondary or Tertiary Balancing Segment
Entries generatedIntercompany receivable / payableDue-To / Due-From entries
Involves multiple legal entities?YesNo — same legal entity
Required for secondary / tertiary bal seg?NoYes — mandatory
Where configured in FusionSetup and Maintenance → Manage Intercompany Balancing RulesSetup and Maintenance → Manage Intracompany Balancing Rules (under Intercompany menu)
Configured at levelLegal Entity or Intercompany OrganisationLedger — applies across all legal entities in that ledger
Accounts definedIntercompany receivable & payable accounts per entity pairDue-From & Due-To accounts per balancing segment value combination
Can be defaulted / catch-all?Yes — default rules by source/categoryYes — default rules by source/category
What happens if not configured?Intercompany journals error or post to suspenseCross-segment journals error or post to suspense — blocking dependency
⚠️ Implementation Note In Oracle Fusion's Setup and Maintenance navigation, the Intracompany Balancing Rules setup sits within the Intercompany menu path. This causes frequent confusion — implementers see "Intercompany" in the navigation and assume they are in the wrong place. They are not. The intracompany rules are correctly located there and must be configured for any ledger using secondary or tertiary balancing segments. Without them, any journal that crosses balancing segment values will fail to post or will route to suspense — making this a hard blocking dependency before any transaction processing can begin.