Intercompany automation is the end-to-end automation of the intercompany transaction lifecycle — from raising the intercompany charge in the selling entity’s Oracle EBS instance, through the confirmation exchange between entities, the matching of corresponding payable and receivable balances, the resolution of discrepancies, and the elimination of intercompany balances in Oracle FCCS consolidation — without manual email coordination, spreadsheet-based matching, or manual journal creation for eliminations. Intercompany processing is consistently identified by GCC group finance teams as the most time-consuming and error-prone element of the month-end close: the selling entity posts an intercompany charge; the receiving entity must confirm it; the amounts sometimes disagree (currency conversion rates, timing differences, disputed charges); the discrepancies must be resolved before FCCS can eliminate the intercompany balances and complete the consolidation. In a group with 20 entities across Saudi Arabia, UAE, Egypt, and Kuwait, this coordination involves dozens of bilateral email exchanges, manual balance comparisons, and follow-up cycles — all occurring under close deadline pressure.
Intercompany Automation Workflow
| Step | Manual Process | Automated Alternative |
|---|---|---|
| Intercompany charge creation | Selling entity finance team manually enters journal in Oracle EBS; emails receiving entity with details | Selling entity posts journal in EBS; OIC flow automatically creates mirror payable journal in receiving entity’s EBS and sends structured confirmation request |
| Confirmation exchange | Receiving entity reviews email; compares to own records; replies with confirmation or dispute | Automated matching compares EBS intercompany AR and AP balances; matches within defined tolerance automatically; flags discrepancies for review |
| Discrepancy resolution | Finance team members from both entities email back and forth to identify and agree the correct amount | Discrepancy details presented in structured portal with both entities’ figures side-by-side; finance team resolves with audit-logged resolution entry |
| Elimination journal | Group consolidation team manually creates elimination journals in FCCS for each agreed intercompany pair | FCCS intercompany matching module automatically generates elimination journals for matched pairs; unmatched items flagged for review |
| Reconciliation sign-off | Group controller emails all entities to confirm intercompany balances are agreed; tracks responses in spreadsheet | Automated sign-off workflow: FCCS generates intercompany agreement report; OIC routes to each entity controller for digital sign-off; status tracked automatically |
Oracle FCCS Intercompany Matching Automation
Oracle Financial Consolidation and Close Service (FCCS) includes a built-in Intercompany Matching module that automates the comparison of intercompany balances across group entities — identifying matching pairs (selling entity AR balance equals receiving entity AP balance), near-matches (within a defined tolerance percentage), and mismatches (differences above tolerance requiring resolution). FCCS Intercompany Matching can be triggered automatically as part of the close cycle orchestration (after all entity data is loaded, before the consolidation runs) and generates a matching report that shows each intercompany pair’s status. For GCC groups where the intercompany transactions are in multiple currencies (a Saudi entity charges a UAE entity in SAR; the UAE entity records the payable in AED), FCCS’s currency translation handles the conversion comparison — identifying whether a residual difference after translation is within the defined tolerance or represents a genuine dispute requiring resolution.
GCC Intercompany Automation: ZATCA and VAT Considerations
Intercompany transactions between Saudi group entities above the B2B e-invoicing threshold are subject to ZATCA Phase 2 clearance requirements — an intercompany service charge from entity A to entity B within the same group is still a taxable supply if it crosses the threshold, and the intercompany invoice must be cleared by ZATCA. Intercompany automation for Saudi group entities must therefore include ZATCA clearance as an integrated step — the intercompany charge automation posts the Oracle EBS AR invoice, triggers ZATCA clearance via OIC, confirms the clearance UUID, and updates both the selling entity’s AR and the receiving entity’s AP with the cleared invoice reference before the intercompany matching step begins. This ZATCA integration step is a Saudi-specific requirement that adds complexity to intercompany automation not present in UAE or Egypt intercompany workflows.
What Goes Wrong in Practice
The most common intercompany automation failure is an automated matching process that matches balances at the entity level rather than at the transaction level — concluding that two entities’ aggregate intercompany balances match while individual transactions are mismatched (one overstated, one understated, netting to zero at the aggregate level). Transaction-level matching — matching each individual intercompany charge to its corresponding payable — is the correct granularity for FCCS intercompany elimination, because FCCS eliminations operate at the transaction or account level, not at the aggregate balance level. Aggregate matching that obscures transaction-level mismatches allows incorrect individual balances to pass through to the consolidated financial statements even when the aggregate appears clean.
How Loop Wise Solutions Automates Intercompany
We design intercompany automation as a transaction-level matching system — matching individual intercompany charges to their corresponding payables, not aggregate balances — with FCCS Intercompany Matching as the confirmation step and Oracle Integration Cloud as the cross-entity coordination layer. ZATCA clearance integration for Saudi intra-group transactions is included as a standard component for all Saudi entity intercompany flows.
