Email?led intercompany breaks stalled close; SAP, Oracle EBS, and NetSuite APIs auto?mirrored invoices and settlements

Overview

A holding company with multiple subsidiaries ran different Enterprise Resource Planning (ERP) systems and reconciled intercompany activity via email and spreadsheets. Mismatched invoices, timing differences, and currency conversions produced recurring imbalances that delayed close and cluttered suspense accounts. Intelligex implemented an intercompany hub with APIs to SAP, Oracle E?Business Suite, and NetSuite, automated mirror invoice generation and settlement entries, and added a governance layer for eliminations. Close activities shifted from reconciliation firefights to managed workflows with consistent documentation—without replacing any subsidiary ERP or consolidation tooling.

Client Profile

• Industry: Multi?industry holding company with shared corporate services
• Company size (range): Multi?entity structure across regions and currencies

li>Stage: Subsidiaries on mixed ERPs; intercompany handled with spreadsheets, email, and late top?side adjustments

• Department owner: Finance & Accounting (Corporate Controller)
• Other stakeholders: Regional Accounting, Treasury, Tax, FP&A, IT/Integration, Internal Audit, Legal, Compliance

The Challenge

Each subsidiary booked intercompany sales, services, and cost allocations in its own ERP with local processes and calendars. Emails and spreadsheets attempted to reconcile charges and credits, but invoice numbers, dates, and chart of accounts rarely aligned. Some entities posted AR while the counterparty delayed the AP, creating imbalances that surfaced at consolidation. Currency conversions were applied differently, fee deductions were undocumented, and partial settlements lacked clear references. Close meetings revolved around chasing attachments and reconstructing the trail for eliminations.

Structural differences made matters worse. Subsidiaries used varied charts of accounts and product codes, fiscal calendars were not identical, and tax treatment differed by jurisdiction. Netting cycles were informal, so cash movements and accounting entries diverged. When imbalances appeared, corporate teams booked top?side eliminations with limited backup, then reopened items when new information arrived. Internal Audit flagged inconsistent documentation and approvals for eliminations and manual journals.

Why It Was Happening

Root causes were fragmented systems and ad hoc coordination. Without a canonical intercompany data model and identity crosswalks, subsidiaries relied on free?text references and spreadsheets, making deterministic matching difficult. Timing and currency rules were applied locally with uneven visibility to the counterparty. There was no governed workflow to generate mirror entries, route exceptions, and capture approvals before consolidation, so eliminations often became a late corrective step rather than an outcome of aligned ledgers.

Ownership was diffuse. Corporate Accounting owned policy and consolidation, while subsidiaries owned their ledgers and processes. Treasury handled settlements, Tax weighed in on transfer pricing and indirect tax, and IT supported disparate integrations. Without a hub to encode policies and enforce sequencing, consistency depended on individual diligence.

The Solution

Intelligex delivered an intercompany hub that normalized transactions across ERPs, generated mirror invoices and settlements, and governed eliminations. The hub ingested intercompany activity via APIs, applied a canonical schema and mapping rules, and proposed or auto?created the counterparty entry where safe. A netting and settlement module generated accounting entries and references for both sides. Currency, tax, and fee differences were reconciled within policy, and unresolved items flowed into a controlled queue with maker?checker approvals. Elimination rules were applied consistently at consolidation with traceable links back to source documents and postings, aligning with consolidation practices under standards such as IFRS 10.

• Integrations: API connectors to subsidiary ERPs—SAP, Oracle E?Business Suite, and NetSuite—for transaction intake and posting; reference data from the corporate chart of accounts and entity master; notifications to collaboration tools.
• Canonical intercompany schema: Standard fields for counterparties, document numbers, service/product codes, amounts, currency, tax, fees, cost centers/legal entities, and due dates; mapping tables reconciled local codes to corporate standards.
• Matching and mirroring: Deterministic matching on references and amounts; fuzzy matching on descriptions and dates; auto?generation of mirror AR/AP documents with controlled numbering and cross?references.
• Netting and settlement: Netting schedules by currency and counterparty; settlement instruction generation and posting of clearing entries; fee and FX impact captured with policy?aligned reason codes.
• FX and tax handling: Conversion at designated rates with effective dating; out?of?policy deviations flagged; indirect tax and withholding handled via rules where applicable, with exceptions routed to Tax.
• Controls and approvals: Maker?checker workflow for mismatches, manual adjustments, and eliminations; controller approvals required for high?risk journals; segregation of duties enforced.
• Dashboards and alerts: Visibility into open items by counterparty and entity, aging of mismatches, netting posture, and upcoming settlements; alerts for timing breaches and missing counter?postings.
• Audit and lineage: Immutable logs linking source documents, mirror postings, netting entries, approvals, and elimination records; exportable evidence packs for audits and management reviews.

Implementation

• Discovery: Cataloged intercompany flows by entity (sales, shared services, allocations), current reconciliation methods, and common mismatch patterns; reviewed ERPs, charts, calendars, and currency sources; collected examples of eliminations and audit comments.
• Design: Defined the canonical schema, identity crosswalks, and mapping rules; authored mirroring logic by transaction type; specified netting schedules and settlement posting patterns; established FX and tax policy rules; designed approval tiers for adjustments and eliminations; planned dashboards and evidence artifacts.
• Build: Implemented ERP connectors and data intake; built normalizers, matchers, and mirroring services; developed netting and settlement generation; configured FX/tax rule engines; added maker?checker workflows and approval routing; assembled dashboards and audit logging.
• Testing/QA: Ran in shadow mode: ingested live transactions and produced draft mirrors and settlements while subsidiaries continued existing processes; reconciled results to prior periods; tuned mapping, FX rules, and matching thresholds; exercised exception routing with Accounting, Treasury, and Tax.
• Rollout: Enabled mirroring and netting for selected entity pairs and currencies first; kept manual reconciliations as a controlled fallback; expanded to additional entities and flows as stability grew; turned on approval gates for eliminations and high?risk journals once teams were trained.
• Training/hand?off: Delivered sessions for subsidiary accountants, Corporate Accounting, Treasury, and Tax on queues, mirroring, netting, and approvals; updated SOPs for intercompany creation, cutoffs, settlements, and eliminations; transferred ownership of mappings, schedules, and policy rules to Controllership under change control.
• Human?in?the?loop review: Established a monthly review for mapping changes, FX sources, tax exceptions, and elimination policies; decisions recorded with rationale and effective dates.

Results

Intercompany transactions moved through a governed workflow. Mirror entries were created consistently with cross?references, netting schedules produced settlement and clearing entries, and timing differences surfaced early. Exceptions landed in a single queue with ownership, evidence, and approval paths. Corporate Accounting focused on policy and review instead of reconstructing transactions at consolidation.

Eliminations became predictable and auditable. Documentation tied eliminations to source and mirror postings, FX rules, and approvals. Treasury saw upcoming netting and settlement needs in one view, and Tax reviewed exceptions with context. The group retained SAP, Oracle E?Business Suite, NetSuite, and its consolidation tools; the shift was a hub and governance layer that made intercompany processes consistent across subsidiaries.

What Changed for the Team

• Before: Subsidiaries reconciled via email and spreadsheets. After: A hub matched and mirrored entries with clear cross?references.
• Before: Settlements and clearing were ad hoc. After: Netting schedules generated settlement instructions and accounting entries.
• Before: Currency and tax differences were resolved late. After: FX and tax rules applied at intake with exceptions routed to owners.
• Before: Top?side eliminations had uneven backup. After: Maker?checker approvals and lineage tied eliminations to source postings.
• Before: Audit trails were reconstructed post?close. After: Evidence packs linked documents, postings, approvals, and eliminations.
• Before: Close calls chased status across entities. After: Dashboards showed open items, blockers, and upcoming netting.

Key Takeaways

• Normalize intercompany activity; a canonical schema and mappings unlock reliable matching and mirroring.
• Automate netting and settlement; scheduled clearing entries reduce timing differences and suspense.
• Apply FX and tax policies up front; rules with effective dating prevent late surprises.
• Govern eliminations; maker?checker approvals and lineage strengthen controls and audit readiness.
• Make posture visible; shared dashboards and alerts shorten cycles and focus effort on true exceptions.
• Integrate, don’t replace; connect SAP, Oracle E?Business Suite, and NetSuite with a hub and workflow.

FAQ

What tools did this integrate with? The hub connected to subsidiary ERPs via APIs—SAP, Oracle E?Business Suite, and NetSuite—to ingest intercompany activity and post mirror entries and settlements. It synchronized reference data from corporate masters and aligned eliminations with consolidation practices consistent with IFRS 10. Notifications and dashboards used the client’s collaboration and BI tools.

How did you handle quality control and governance? Mapping tables, FX and tax rules, netting schedules, and approval tiers lived under change control. Maker?checker workflows enforced segregation of duties for adjustments and eliminations. Every match, mirror, settlement, and approval was logged immutably with documents and cross?references. Policy changes carried effective dates and were visible in lineage.

How did you roll this out without disruption? The hub ran in shadow mode first, generating draft mirrors and settlements while subsidiaries continued their processes. Results were reconciled to prior periods, and rules were tuned. Rollout began with a subset of entity pairs and currencies; manual reconciliations remained as a fallback. Approval gates were tightened gradually as teams gained confidence.

How were currency and tax differences handled? The hub applied designated FX rates with effective dating and posted remeasurement or realized differences per policy. Indirect tax, withholding, and fee impacts were recognized with reason codes and routed to Tax when outside rules. Exceptions required approval before posting.

How did you deal with different charts and calendars across ERPs? Identity crosswalks mapped local GL accounts, products, and cost centers to the corporate chart. Calendars were normalized to the group close calendar with cutoffs encoded in the hub. When local dates conflicted, items were queued with context and routed to the right owner for resolution.

How were settlements executed? Netting schedules consolidated open items by currency and counterparty, produced settlement instructions for Treasury, and posted clearing entries in both ERPs with shared references. If cash movements differed from netting (for example, bank fees), the hub reconciled differences and routed approvals where policy required.