Parent vs subsidiary ledger matching + exception taxonomy — intercompany elimination automation in under 15 seconds per close cycle.
| Txn Ref | Counterparty | Txn Type | Ccy | Amount (INR) |
|---|---|---|---|---|
| IC-2026-0012 | Acme Logistics Pvt Ltd | Interco Receivable | INR | 18,50,000 |
| IC-2026-0018 | Acme Logistics Pvt Ltd | Interco Receivable | INR | 9,25,000 |
| IC-2026-0024 | Acme Logistics Pvt Ltd | Interco Receivable | INR | 6,45,000 |
For a mid-market group running three to five entities, intercompany elimination automation replaces the most failure-prone step of the period close — the manual VLOOKUP of two ERP exports that every group controller dreads.
The group controller downloads the parent interco ledger, requests a matching export from each subsidiary, then manually reconciles 50–200 transaction pairs by VLOOKUP on Txn Reference — a process that routinely runs two to three full days inside a five-day close window, leaving zero buffer for corrections.
Manual reconciliation misses the four exception types that matter most: amount differences caused by timing or rounding beyond the Rs 100 threshold; FX translation gaps where one leg is USD-translated at a different rate; single-sided postings where only one entity booked the transaction; and account classification divergences where one entity calls it a loan and the other a trade payable.
An uneliminated intercompany receivable inflates current assets on the consolidated balance sheet. An uneliminated intercompany revenue inflates consolidated turnover and EBITDA — distortions that ripple directly into working-capital loan covenant calculations and can trigger a technical default or a restatement under Ind AS 8.
Auditors sample intercompany eliminations as a standard substantive procedure under ICAI SA 500. Unresolved mismatches — particularly classification divergences between loans and trade balances — can delay the statutory audit sign-off or trigger a qualified opinion on the consolidated financial statements, requiring correcting entries after the close window.
The time a group controller at a 3–5 entity mid-market group spends on manual interco reconciliation each quarter — time that could be recovered entirely with deterministic intercompany reconciliation automation. A missed mismatch discovered post-filing requires a restatement under Ind AS 8 (Accounting Policies, Changes in Accounting Estimates and Errors) with mandatory public disclosure of the prior-period error.
Four overlapping standards demand complete intercompany elimination before consolidated statements can be signed off. Any residual balance is a material misstatement under all four.
An entity preparing consolidated financial statements must eliminate in full all intragroup assets and liabilities, equity, income, expenses, and cash flows relating to transactions between entities of the group. Any residual intercompany balance after consolidation is treated as a material misstatement under this standard. The parallel US GAAP requirement is ASC 810-10-45-1 (consolidation of variable interest entities and voting-interest entities).
For groups with intercompany transactions denominated in a foreign currency, the FX translation difference between the parent's functional currency books and the subsidiary's functional currency books must be quantified and disclosed — not silently offset. Ind AS 21 and its US equivalent ASC 830 both require disclosure of exchange differences recognised in other comprehensive income, which originate from intercompany positions translated at different rates per side.
Section 186 of the Companies Act, 2013 governs loans and advances made by a company to its subsidiaries and associates, setting limits on the aggregate amount and requiring board approval beyond prescribed thresholds. When one entity classifies an intercompany balance as a Loan Receivable and the counterparty classifies the same transaction as a Trade Payable, the loan limit calculation is incorrect — a compliance breach independent of the consolidation error.
SA 230 requires the auditor to document procedures performed and evidence obtained in sufficient detail to enable an experienced auditor to understand the nature, timing, and extent of procedures. For intercompany eliminations, this means the working paper must carry field-level provenance — source file name, extraction timestamp, match key used, and the specific check result for each exception — satisfying the documentation standard without requiring supplementary manual annotation.
For groups reporting under both Ind AS and IFRS (for international investors or cross-listed entities), IFRS 10 · Paragraphs B86–B87 imposes an identical full-elimination requirement, with IFRS 9 governing inter-entity financial instruments. The Cadel workflow produces a working paper that satisfies all four regulatory frames simultaneously.
Seven deterministic passes from dual-ledger ingestion to a cleared consolidation working paper — in under 15 seconds for 200 intercompany transaction pairs.
Accepts two Excel or CSV files dropped together — the parent entity interco ledger and the subsidiary interco ledger. Cadel auto-classifies each file as Parent Ledger or Sub Ledger using document-type detection, then parses every row into a typed entry object with fields txn_ref, counterparty_entity, txn_type, account, currency, amount_inr, and txn_date.
A lookup table is built keyed on the three-field composite (txn_ref, counterparty, period). Every parent row is paired with its subsidiary counterpart deterministically — no fuzzy matching, no heuristic — ensuring re-running the same input files produces byte-identical match results and a fully auditable trail under ICAI SA 230.
For every matched pair, the amount_inr on the parent side is compared to the amount_inr on the subsidiary side. Differences within Rs 100 pass as rounding; differences beyond that threshold — such as the Rs 12,500 gap on IC-2026-0018 (Rs 9,25,000 vs Rs 9,37,500) — are flagged AMOUNT MISMATCH and held from auto-elimination pending manual resolution.
The currency code on the parent leg is compared to the subsidiary leg for each matched pair. A USD/INR divergence — same transaction reference but different currency codes per side, as in IC-2026-0042 — is flagged CURRENCY INCONSISTENCY and routed for FX translation review under Ind AS 21 / ASC 830, isolating the translation difference for disclosure.
Entries present in the parent ledger but absent in the subsidiary ledger — such as IC-2026-0024 recorded only by the parent — are classified SOURCE-ONLY (missing leg) and flagged for the subsidiary to post the offsetting payable before elimination can proceed. Subsidiary-only entries are symmetrically surfaced as TARGET-ONLY.
For matched pairs, txn_type is compared across both legs. A Loan Receivable on the parent side matched to a Trade Payable on the subsidiary side (as in IC-2026-0031, Rs 50,00,000 vs Rs 50,000 under different accounts) is flagged CLASSIFICATION MISMATCH and blocked from auto-elimination — a critical catch given the Section 186 Companies Act loan-limit compliance implications.
Fully reconciled pairs — matched on reference, counterparty, period, amount within tolerance, consistent currency, and consistent classification — receive a MATCHED status badge and a system-generated elimination journal entry (Dr Interco Payable / Cr Interco Receivable) written to the consolidation working paper, formatted for direct insertion into the audit file as evidence under Ind AS 110 / ASC 810.
Five seeded exception scenarios — each one exercises a real-world failure mode the manual VLOOKUP process routinely misses. Every scenario produces a deterministic outcome an auditor can verify in seconds.
Two synthetic ledger files cover one full consolidation period (Mar-2026) — the parent entity's 60-row interco ledger and the subsidiary's 58-row mirror. Upload them together to drive a complete demo run.
60 intercompany transactions keyed by Txn Reference (IC-2026-1001 onward), each booking a receivable, interco revenue, or loan against Acme Logistics Pvt Ltd. Nine rows plant the full exception taxonomy for the demo run.
58 rows mirror the parent's payables and expenses. The 2 missing rows are the seeded missing-leg exceptions; other rows plant amount, FX, classification, period and currency breaks covering all five exception types.
Running the workflow against parent_ledger.xlsx (60 rows) and sub_ledger.xlsx (58 rows) for Mar-2026 produces the following deterministic output in under 15 seconds.
Of the 60 transaction pairs, 51 reconcile cleanly — matched on Txn Reference, counterparty, amount within the Rs 100 tolerance, currency, classification, and period — and receive a MATCHED badge with a system-generated elimination journal entry (Dr Interco Payable / Cr Interco Receivable). The remaining nine transactions are flagged across the workflow's full exception taxonomy:
The most operationally significant exception class is the classification mismatch: a manual VLOOKUP of the same 60-row ledger pair typically takes a senior accountant 30–45 minutes and routinely misses both the single-sided and classification breaks. The workflow surfaces all nine breaks in under 15 seconds with full field-level provenance, giving the group controller a cleared working paper ready for audit file insertion — rather than a blank Excel that needs two days to populate.
For a group running three to five entities with 100–300 intercompany transaction pairs per quarter, Cadel reduces a two-to-three day manual reconciliation to a 15-second deterministic run — with four exception classes that VLOOKUP misses entirely.
Amount mismatches beyond Rs 100, FX translation gaps, single-sided postings, and account classification divergences are all invisible to a manual VLOOKUP process. Each undetected exception class carries a distinct compliance risk — from a consolidated balance sheet overstatement under Ind AS 110 / ASC 810 to a loan-limit breach under Section 186 Companies Act — that the workflow catches deterministically every close cycle.
Every reconciliation run produces a structured elimination schedule with per-transaction status badges, system-generated journal entries for MATCHED pairs, and field-level provenance (source file, extraction timestamp, match key, check result). The working paper is directly insertable into the audit file as evidence under ICAI SA 230, replacing the manual spreadsheet the controller would otherwise annotate by hand over two days.
A missed intercompany mismatch discovered after the consolidated statements are filed triggers a restatement under Ind AS 8 (Accounting Policies, Changes in Accounting Estimates and Errors) with mandatory public disclosure — a reputational and regulatory cost that dwarfs the time saved by skipping a rigorous reconciliation. Deterministic pre-filing detection removes this risk entirely by catching every exception before elimination.
The questions group controllers and consolidation accountants ask most often before deploying intercompany reconciliation automation.
Two intercompany ledgers for the same consolidation period — the parent entity's interco ledger and the subsidiary's interco ledger, each as an Excel/CSV with the columns Counterparty Entity, Txn Reference, Txn Type, Account, Ccy, Amount (INR) and Txn Date. Drop both together; Cadel classifies each as Parent Ledger or Sub Ledger automatically.
Each parent row is matched to its subsidiary counterpart on Txn Reference, then cross-checked on counterparty, amount and date. A clean interco transaction is a mirrored pair — a receivable on the parent and the equal payable on the subsidiary — so the pair nets to zero on consolidation. The match is deterministic: re-running the same input files produces byte-identical results.
Five exception types are flagged. Amount mismatch — the two legs differ by more than the Rs 100 tolerance. FX translation gap — a foreign-currency txn translated at different rates per side. Missing leg — booked on one side only. Classification mismatch — one side calls it a loan, the other a trade balance. Period/currency drift — the legs fall in different periods or carry different currency codes.
Amounts must agree within Rs 100; anything beyond that is an amount mismatch. Transaction dates may differ by up to 5 days for posting delays — a larger gap is flagged as a period-alignment warning, since the legs likely fall in different reporting periods and the interco balance would straddle two financial periods in the consolidated statements.
Open the Exceptions view. Every unmatched or mismatched transaction is listed with the reason and the Txn Reference used for the lookup. Click any row to drill into the underlying ledger and see exactly which field tripped the rule, then correct the source ledger before re-running.
The workflow generates elimination journal entries (Dr Interco Payable / Cr Interco Receivable) automatically for every MATCHED pair — pairs that reconcile on all five checks. The flagged exception pairs must be cleared in the source ledgers first; once corrected and re-processed, they also receive MATCHED status and a corresponding elimination entry. The exported working paper carries all generated entries ready for audit file insertion.
Bank and GST reconciliations match your books against an external statement. Intercompany elimination reconciles two internal ledgers within the same group that should mirror each other exactly — the goal is a clean net-to-zero so consolidated revenue, balances and profit are not overstated by transactions the group made with itself. The failure modes are also different: bank recon catches timing and bank-error breaks; interco recon catches classification and missing-leg breaks that only appear when two internal ledgers are compared side by side.
No. Your ledgers are processed only to produce this workflow's reconciliation results and are never used to train any model.
