Cross-Entity Journal Posts Without Intercompany Due To/Due From Lines
Arboria Group runs three legal entities in one primary ledger, each mapped to a balancing segment value: LE-01 (United States), LE-02 (Canada), and LE-03 (Mexico). A shared-services accountant posted a manual journal debiting LE-02 consulting expense for 85,000 USD and crediting LE-01 cash for 85,000 USD. The journal posted without error, but no due-to or due-from lines were created, and the LE-01 and LE-02 trial balances are now out of balance by 85,000 each even though the ledger-level journal balanced. Investigation shows the Intercompany option on the primary ledger is set to No, and no intercompany balancing rules exist. A secondary ledger, Arboria IFRS, is configured at the adjustment level with journal-level conversion, and the controller wants to know whether enabling intercompany in the primary ledger will also fix the IFRS ledger and what will happen to the 85,000 already posted.
1. Why were no due-to/due-from lines generated, and what must be configured to make intercompany balancing work going forward?
Read the worked answer
Intercompany balancing is a ledger-level behavior, not an automatic property of a journal with two balancing segment values. With the Intercompany option set to No, General Ledger accepts the cross-entity journal as balanced at the ledger level and does nothing to balance each legal entity. To turn it on, enable Intercompany on the primary ledger, then define intercompany balancing rules that specify the due-to and due-from accounts for each from/to balancing segment combination, the journal source and category to which they apply, and whether the rule covers all balancing values or specific pairs. Confirm the accounts are enabled and postable and that the rules are dated to cover the current period. Also check the intercompany accounts used by payables and receivables if those flows are in scope. After the change, test with a small cross-entity journal in a test period and verify that the due-to/due-from pair appears, balances by legal entity, and posts to the intended accounts before going live.
2. How should the existing 85,000 cross-entity journal be corrected, and how do you prevent a recurrence?
Read the worked answer
Enabling the option does not retroactively balance journals already posted. The clean correction is to reverse the original journal in the current open period and re-enter it after intercompany balancing is configured, so the system generates the due-to and due-from lines and the audit trail shows one reversal and one corrected entry. If reversing is impractical because the period is closed, post a correcting journal that creates the missing intercompany pair with a clear description referencing the original journal number. Either way, reconcile each legal entity's trial balance afterward and confirm it nets to zero. To prevent recurrence, add a validation step to the shared-service checklist for cross-entity journals, restrict who can post them, and monitor the intercompany reconciliation report each period. Do not simply net the 85,000 against an unrelated account, because that hides the imbalance rather than resolving it.
3. Will enabling intercompany on the primary ledger flow to the adjustment-level IFRS secondary ledger, and what should the controller verify?
Read the worked answer
Do not assume it will. The secondary ledger has its own ledger options, including its own intercompany setting, and an adjustment-level secondary ledger holds only the adjustments defined for it, not a full copy of primary ledger journals. Journal-level conversion converts the primary journal amounts, but the intercompany entries generated in the primary ledger flow only if the secondary ledger is configured to accept them and its own intercompany option and rules are in place. The controller should verify three things: whether the secondary ledger's intercompany option is enabled, whether the intercompany balancing rules exist in the secondary ledger's context or are inherited, and whether the adjustment level actually includes the intercompany journals. Test by posting a cross-entity journal in the primary ledger after configuration and inspecting the secondary ledger for the due-to/due-from pair. If the adjustment-level design means only manual adjustments belong there, document that intercompany is deliberately handled in the primary ledger and reconcile the secondary separately.