Intercompany
Every IC pair, matched on the day it posts
The IC Recon Flows match every intercompany AR/AP entry, elimination pair, netting input, and transfer-pricing transaction at the line item — across entities, on the day of posting. Group consolidation lands in 1–2 days; BEPS / §90 AO evidence is a byproduct.
1–2 days
IC consolidation vs 8–10 today
T+0
IC match day of posting
4–6 wks
Demo to live
The structural failure
IC breaks where the n × (n−1)/2 explosion meets the period-end deadline
Quadratic scale. Period-end discovery. Cross-entity feed heterogeneity. Annual TP scrambles. Four named failures appear in every group-finance IC stack.
Failure 01
n × (n−1)/2 explosion
Reconciliation pairs grow quadratically with entities. Manual matching at scale collapses; sampling becomes the unofficial standard, line-item differences disappear into the totals.
Failure 02
Period-end discovery
IC mismatches surface in the consolidation week, when the originating entities have already closed. By the time the gap is found, the only fix is a top-side adjustment.
Failure 03
Cross-entity feed heterogeneity
Different entities run different ERPs, different chart-of-accounts mappings, different IC posting conventions. Normalisation happens in spreadsheets at quarter-end, one entity at a time.
Failure 04
Transfer-pricing scramble
BEPS Action 13 / §90 AO documentation gets assembled annually, under deadline pressure, from a chain of evidence that was never captured continuously. Audit findings become routine.
The 4 IC Recons
The Intercompany RECON library
Each RECON covers one of your IC reconciliation use cases end-to-end. Ingestion, matching, exception workbench, audit trail, write-back. Start with one. Build your IC Layer over time.
01
From Reconciled to Reconciled with Confidence
IC moves from "as good as scale allows" to "reconciled with confidence."
Every IC match — entity-to-entity pair, elimination evidence, netting input, transfer-pricing transaction — carries a confidence score. Long-tail patterns AI-authored, group controllers approve once, exceptions raised on the day they appear. The n × (n−1)/2 explosion stops being a manual problem and becomes a continuous operating condition.
95%+
Automation rate
100%
Line-item coverage
Hours, not weeks
Exception backlog
02
Revenue Recovery
Release working capital tied up in unmatched IC pairs
Settled-gross IC AR/AP pairs lock up working capital and multiply FX exposure. Reconciled, attested netting cycles release cash that was sitting against itself between entities. Margin in Group transactions stays visible.
Working capital
Released, not locked
FX
Compressed, not multiplied
Margin
Visible across entities
03
Audit-Ready Close
BEPS Action 13 and §90 AO as a byproduct
Every IC match, every elimination, every transfer-pricing transaction logged immutably with rule, timestamp, user, confidence, rationale. The TP evidence chain is built continuously — not assembled annually under deadline. GoBD, IFRS 10, HGB §297, and §90 AO covered in one integrated trail.
BEPS · §90 AO
Continuous, not annual
−30–50%
Year-end audit time
IFRS 10 · HGB §297
One integrated trail
04
Real-Time Control of Working Capital
Group consolidation in 1–2 days, not 8–10
IC matches across all entities on the day of posting. Elimination evidence pre-assembled before consolidation begins. Transfer-pricing evidence is continuous, not annual. The Group close lands as a confirmation, not a scramble.
1–2 days
IC consolidation
T+0
Day-of-posting match
−87%
Manual IC work
IC Data Sources
Read from every entity ledger your Group runs on
Native ingestion across heterogeneous entity ERPs, IC sub-ledgers, treasury systems, and TP documentation. Configured to your group structure — not bent into a generic schema.
Sources we read
Entity sub-ledgers
Per-entity ERP · multi-platform
IC AR sub-ledger
Group · entity-level
IC AP sub-ledger
Group · entity-level
IC agreements & TP method
Contract · pricing basis
Treasury / cash pool
Netting · settlement feeds
Read-from · write-to
Modular Layer · Built for your data
Start with one RECON. Build your Layer over time.
Reconciliation is inherently group-specific. No two groups have the same legal-entity tree, the same chart-of-accounts mapping, or the same TP method by transaction type. Every RECON ships with standardised behaviour and is customized for the cases the standard logic doesn't solve.
Live in 4–6 weeks
Read from · write to
The engine writes rules against your IC data
Where IC posting conventions differ across entities — different ERPs, different chart-of-accounts mappings, different reference styles — the engine drafts the match rule against your group structure. Your group controllers review and approve it.
Entity-specific COA mappings & TP methods
Per legal entity, per jurisdiction, per transaction type. The TP method that matches your contractual basis — not a generic schema we force on you.
Human-on-the-Loop on every override
AI accelerates the matching; group controllers and tax own the decision. Every override is logged with rule, user, timestamp, rationale — exportable for the tax auditor.
95%+
Automation rate confidence score on every match
1–2 days
IC consolidation vs 8–10 today
T+0
Day-of-posting match across all entity ERPs
BEPS · §90 AO
TP evidence chain continuous, not annual
Validate the business case on your data