.svg)
Intercompany reconciliation for SME CFOs: complete guide (2026)
Why IC balances almost always differ, what the monthly cycle looks like, and how to move from a multi-day manual chore to a 30-minute routine.
.png)
Intercompany reconciliation is the monthly matching of IC accounts between entities in a group — the diagnostic on elimination, which runs automatically as part of consolidation. IC balances almost always differ due to timing, FX, posting errors, mapping inconsistencies, and missing accruals. Finstack matches at transaction level, with configurable thresholds per IC relationship and native connections to Exact, AFAS, Twinfield, Yuki, Pennylane, eAccounting, Tripletex, Nmbrs, Xero, QuickBooks Online, and Microsoft Dynamics 365 BC.
Intercompany reconciliation for SME CFOs: complete guide (2026)
What it is, why IC balances almost always differ, how to run the cycle, and what your tool needs to do.
TL;DR
Intercompany reconciliation is the monthly matching of IC accounts between entities — the diagnostic on elimination, which runs automatically as part of consolidation. IC balances almost always differ for five recognisable reasons: timing, FX, posting errors, mapping inconsistencies, and missing accruals. For a five-entity SME group, manual reconciliation takes 1-3 working days a month; transaction-level matching through Finstack brings that down to 30 minutes. The discipline that matters: match at transaction level (not just at trial balance), set tiered thresholds per IC relationship (auto-eliminate, investigate, escalate), and run the cycle inside the five working days after month-end. Reconciliation follows elimination as the diagnostic — without reconciled IC balances, elimination differences keep piling up as residual on the group balance sheet and quietly erode the credibility of your consolidated numbers.
What is intercompany reconciliation, and why does it matter?
Intercompany reconciliation is the process of matching IC accounts between entities in a group, with one purpose: get the IC balances on both sides to agree so that elimination, which runs automatically as part of consolidation, lands cleanly. If production sells €800,000 of goods to distribution, that posting shows up as an IC receivable at production and as an IC payable at distribution. By month-end, those two numbers should be identical — and that's exactly where it almost always goes wrong.
Reconciliation matters because of its diagnostic role on elimination: elimination runs automatically as part of consolidation, but without reconciliation you can't tell whether the IC balances actually tie out. Balances that don't tie out lead to elimination differences that sit on the group balance sheet as residual amounts. Concrete example: if production books €800k of IC revenue and distribution only books €785k of IC cost, you'll have €15k left unexplained in your consolidated P&L after elimination. That's not a real loss in the group — it's a matching problem that reconciliation surfaces and that you then have to resolve.
In a typical SME group, IC postings fall into five categories: current accounts (intercompany loan-style balances between entities), loans and interest, intercompany revenue and cost, intercompany receivables and payables, and participations (only relevant at the holding level, with the mirror category of equity items at the subsidiary level — share capital, share premium, reserves). Reconciliation covers all five, and each category has its own pitfalls.
Reconciliation and elimination are two steps that reinforce each other, not synonyms. Elimination = stripping out IC postings during consolidation — this runs automatically. Reconciliation = matching IC balances between entities to find and resolve elimination differences. For the four elimination methods (full GLA, per IC relationship, per transaction and manual IC entry), see the complete guide to elimination methods. For the broader consolidation context: consolidation pillar for SME CFOs.
Why IC balances almost always differ: five causes
In practice, IC balances between entities are rarely identical out of the box. Five causes show up in nearly every SME group, in order of frequency.
Posting-period differences
Production sends an invoice on 28 June and books it as IC revenue in June. Distribution receives the invoice on 2 July and books it as IC cost in July. At month-end, the IC balance differs by the amount of that one invoice — correctly booked on both sides, just in different periods. The most common cause across SME groups, especially around month-ends and quarter-ends.
Currency translation effects
Both entities post in their functional currency, but if one reports in a different currency than the group (a Swiss entity reporting in CHF, for example) and the booking rate differs from the group's presentation rate, you get FX translation differences. In multicurrency SME groups, this typically accounts for 1-3% of IC volume per month. For the multicurrency context: see multicurrency consolidation for SME CFOs.
Incorrect entries
Plain mistakes: wrong account, wrong amount, invoice booked twice or not at all. Each individual error tends to be small, but at higher IC volumes (production to distribution) they add up. Transaction-level auto-matching surfaces these errors immediately; trial-balance reconciliation only shows the net effect.
Different IC account structures between entities
Production uses GL account 1605 "IC receivable Dis BV"; distribution uses 2105 "IC payable Pro BV". Reasonable individually — but if the mapping to the group-level IC line isn't consistent, you end up with structural differences that aren't really "errors" but mapping issues. Usually discovered at first reconciliation and resolved once and for all by adjusting the mapping table in your consolidation tool.
Missing intercompany accruals
Production delivers in June but doesn't invoice until July. For group reporting, June should carry an IC revenue accrual at production and an IC cost accrual at distribution. In practice: one entity books the accrual, the other doesn't — and the IC balance disagrees. Mostly seen in groups without a tight discipline on month-end accruals.
In aggregate: SME group IC balances typically differ by 2-15% of monthly IC volume due to these five causes combined. Good reconciliation distinguishes which cause is responsible for which variance — not as an academic exercise, but because the response per cause is different (accept the timing, post the FX, correct the posting, fix the mapping once, tighten the accrual discipline).
The monthly IC reconciliation cycle in four steps
A well-run IC reconciliation cycle moves through four steps, embedded in the month-end close. The cycle should complete within five working days after month-end — anything later and it ends up in variance reporting instead of supporting decisions.
Pull trial balances and IC account balances per entity
Once each entity's month-end close is complete, trial balances and IC account balances flow in from every bookkeeping system. Manual approach: export from ERP, import into a spreadsheet. Automated sync through Finstack (refreshing every 3 hours): trial balances and the underlying transactions are immediately available on the Reconciliation page in the Entries menu, with no manual export.
Match per IC relationship
Per IC relationship (the combination of two entities plus the IC GL account), match the receivable at entity A against the payable at entity B. At trial-balance level you only see the net difference; at transaction level, the tool pairs every individual invoice or posting between seller and buyer and flags any unmatched transactions.
Analyse differences by cause
For every difference above the threshold: which of the five causes is it? Timing differences are typically accepted (they correct themselves next month). FX differences get booked to a translation P&L line. Posting errors need correction in the source entity. Mapping issues call for a one-off table adjustment. Missing accruals signal a need for tighter month-end discipline.
Corrections and sign-off
Corrections get booked (in the source entity, with audit trail). Any remaining differences that haven't been resolved get explicitly documented: which difference, which cause, how it will be handled in elimination. Sign-off by the group controller or CFO. After sign-off you re-run the consolidation so elimination lands cleanly on the reconciled IC balances — see the guide to elimination methods.
Total monthly time for a well-run cycle in a five-entity SME group: 30 minutes to an hour with automated matching, 1-3 working days by hand. That gap almost always decides whether the cycle gets sustained as a discipline or quietly slips.
IC reconciliation at transaction level vs. trial balance
The most important choice in IC reconciliation is the level at which you match. Trial-balance reconciliation compares only the closing balances of IC accounts between entities. Transaction-level matching pairs every individual IC posting between seller and buyer. For SME CFOs, the difference is fundamental.
For SME groups with up to 2 entities, trial-balance reconciliation can still work. From 3 entities upward, the investigation work climbs to hours per IC relationship per month — and with a monthly cadence, that becomes unsustainable. Transaction-level matching is, for SME CFOs, the difference between "I know there's a problem" and "I know which posting is missing and can correct it". For the broader positioning of transaction-level vs. trial-balance in consolidation: see transaction-level vs. trial-balance consolidation.
Threshold management: when is a mismatch acceptable?
Not every difference needs to be investigated in detail. Good IC reconciliation works with thresholds per IC relationship, tiered by materiality. Three thresholds work well in SME practice.
1. Auto-elimination threshold — typically €1-5k per IC relationship per month. Below this line, differences get booked automatically to a rounding/translation P&L line without further investigation. This stops you from spending hours each month on small FX or timing differences that resolve themselves the next month anyway.
2. Investigation threshold — typically €5-25k per IC relationship. Between the auto-elimination line and this threshold, the responsible controller has to explain monthly which of the five causes accounts for the difference. Not blocking for sign-off, but a documentation requirement for the audit trail.
3. Escalation threshold — typically above €25k. Differences above this line block consolidation sign-off until resolved. Usually triggered by large posting errors or structural mapping issues that shouldn't slip under the radar. For PE portcos with covenant tracking: lower this threshold, because elimination differences flow straight through to EBITDA reporting.
More important than the absolute amounts is consistency: same thresholds per IC relationship every month, so trend analysis is possible. For groups with large IC volumes (production to distribution above €5m per month), percentage thresholds (1-2% of IC revenue) tend to work better than euro amounts. Finstack supports configurable thresholds per IC relationship with auto-flag above each tier.
A related point: any residual balance after elimination also needs a home on your balance sheet. Finstack automatically generates elimination GL accounts as you apply eliminations — you map those to either a generic "Other equity" line (hides the residual) or to a dedicated "Elimination reserve" line under Equity (makes the residual explicit). For SME CFOs who want to report transparently to the board and investors: pick the Elimination reserve approach. Hiding feels easier but builds a weaker information position with stakeholders.
Multi-entity and multicurrency IC reconciliation
For SME groups with more than two entities, IC reconciliation becomes an N×N problem. A five-entity group has up to 10 IC relationship pairs (each pair has two sides); a ten-entity group has up to 45 pairs. Manual matching scales badly; transaction-level tooling scales linearly.
The practical setup for multi-entity: a matrix view with all IC relationships visible at once. Entities on one axis, counter-entities on the other, IC positions in each cell. Finstack supports this through the "View entities" mode on the Reconciliation page — entities as rows, counter-entities as columns, with the source of any difference immediately visible. For multi-entity context in detail: see multi-entity consolidation.
For multicurrency groups, FX translation adds another layer. An IC relationship between a Dutch production entity (EUR) and a Swiss sales entity (CHF) has three views: in EUR (the production-side perspective), in CHF (the sales-side perspective), and in the group's presentation currency. Matching has to account for booking rates that can vary between entities and posting moments. FX translation differences between booking and presentation rates get booked to a translation reserve, not treated as IC mismatches.
Practical tip: surface every IC relationship in both transaction currency and group currency. Differences in transaction currency point to real matching problems (timing, posting); differences only in group currency point to FX effects. That distinction structurally saves SME controllers hours every month. For the multicurrency context: multicurrency consolidation.
What your tool needs to do for IC reconciliation
A good IC reconciliation cycle stands or falls on tooling. Manual matching is workable at 1-2 entities; from 3 entities upward the update cost climbs to the point where the discipline dies within a quarter. Six tool requirements make the difference for SME CFOs.
1. Transaction-level matching, not just trial balance. Per individual IC posting, pair seller and buyer and auto-flag unmatched transactions. Essential for traceable difference analysis and audit trail. Finstack delivers this through the Eliminations page in the Entries menu, with a "% IC Relations" column that shows how much of each GL account is IC-related — useful for confirming you've covered all your IC accounts.
2. Configurable thresholds per IC relationship. Auto-elimination, investigation, and escalation tiers set per IC relationship. For PE portcos, often tighter than for independent SME groups; for groups with large IC volumes, usually percentage-based.
3. FX-aware matching for multicurrency groups. Match postings across different currencies while distinguishing real mismatches (in transaction currency) from FX translation effects (in group currency). Essential for groups with international entities.
4. Native ERP connections for automatic IC data feeds. Trial balances and transaction data should refresh automatically from the bookkeeping systems, not through manual exports. Finstack connects at transaction level with Exact, AFAS, Twinfield, Yuki, Pennylane, eAccounting, Tripletex, Nmbrs, Xero, QuickBooks Online, and Microsoft Dynamics 365 BC — the standard Dutch and international ERPs for SMEs.
5. Audit trail per correction. Which correction was booked when, by whom, for which transaction. Essential for auditors and bank reviews; for PE portcos, often a mandatory component of investor reporting.
6. Multi-entity in parallel. Reconcile all IC relationships simultaneously, not sequentially pair by pair. For groups with five or more entities, the difference between feasible and infeasible within the five-working-day cycle.
Start with your largest IC relationship (usually production ↔ distribution) and set up transaction-level matching plus thresholds there first. Run the cycle for one month before scaling out to the rest of your IC relationships. Start with the 14-day free Finstack trial to feel the matching workflow yourself.
Explore Finstack.
Free trial for 14 days.
Access to all features. No credit card required.
.png)
Three common mistakes in IC reconciliation
Matching only at trial-balance level
The monthly report shows "€15k difference" with no cause attached. Controllers spend hours investigating each IC relationship, and small errors disappear into the net effect without ever being corrected. Workable version: transaction-level matching with auto-flag on unmatched transactions, so causes surface immediately and corrections are traceable.
Not setting thresholds — investigating everything
Every month you spend time on €500 FX translation differences or small timing effects that resolve themselves the next month. The discipline dies within a quarter because the cost per cycle is too high. Workable version: three thresholds (auto-elimination / investigation / escalation) tiered by materiality per IC relationship, applied consistently.
Starting IC reconciliation only after month-end close
Reconciliation gets squeezed in at the end of the close cycle, after every other closing activity. Differences only surface on workday 8-10 — too late for variance reporting. Workable version: reconciliation runs in parallel with the month-end close, with IC balances already available by workday 1-2 through automated ERP sync. Sign-off by workday 5 at the latest.
Frequently asked questions
Can't find your question? Let us know
What is intercompany reconciliation, exactly?
Intercompany reconciliation is the monthly matching of IC accounts between entities in a group. The goal: get the IC balances on both sides (receivables at the seller, payables at the buyer) to agree, so that elimination — which runs automatically as part of consolidation — lands cleanly. With matched IC balances, elimination flows through correctly; when balances don't tie out, reconciliation surfaces the elimination differences you have to resolve. In practice, IC balances almost always differ due to timing, FX, posting errors, mapping inconsistencies, or missing accruals — and reconciliation is the process of explaining those differences and correcting what should be corrected, before they sit as residual amounts in your consolidated numbers.
Why do IC balances almost always differ between entities?
Five causes show up in nearly every SME group: (1) timing differences — invoice booked in month 1 by the seller, in month 2 by the buyer; (2) FX differences — postings in different currencies translated at different rates; (3) posting errors — one entity books to the wrong account or amount; (4) mapping inconsistencies — different IC chart-of-accounts structures across entities; (5) missing accruals — one entity books an accrual, the counterparty doesn't. In SME groups, IC balances typically differ by 2-15% of monthly IC volume due to these five causes combined.
How often should I reconcile IC?
Monthly at minimum, right after the month-end close — otherwise differences pile up and the eventual investigation becomes painful. For SME groups with heavy IC traffic (production plus distribution, multiple countries), weekly is more practical because differences surface sooner. The cycle should be complete within five working days after month-end; anything later and it ends up in variance reporting instead of decision-making. Manual matching takes 1-3 working days a month for a five-entity group; automated transaction-level matching through Finstack takes 30 minutes to an hour.
What is the difference between IC reconciliation and IC elimination?
Elimination runs as part of consolidation, and reconciliation follows as the diagnostic. Elimination = stripping out IC transactions and balances during consolidation. Reconciliation = matching IC balances between entities (receivables = payables, IC revenue = IC cost) to find where elimination differences sit. Elimination differences — IC balances that don't tie out — surface through reconciliation and have to be resolved; then you re-run the consolidation so elimination lands cleanly. Without reconciliation, those differences sit on the group balance sheet as residual amounts and undermine the reliability of your consolidated numbers. For the four elimination methods (full GLA, per IC relationship, per transaction and manual IC entry), see the guide on elimination methods.
What is an acceptable threshold for IC mismatches?
Scale-dependent, but practical ranges for SME groups: auto-elimination threshold €1-5k per IC relationship per month (rounding, FX translation); investigation threshold €5-25k (timing, posting errors require an explanation); escalation threshold above €25k (blocks sign-off until resolved). More important than the absolute amounts is consistency — same thresholds per IC relationship every month, so trend analysis is possible. For groups with large IC volumes (production to distribution above €5m per month), percentage thresholds (1-2% of IC revenue) are usually more practical than euro amounts.
What is IC reconciliation at transaction level, and how does it differ from trial balance?
Trial-balance reconciliation compares only the closing balances of IC accounts — you see there's a €15k difference, but not what caused it. Transaction-level matching pairs every individual IC posting between seller and buyer, so a difference is traceable to the exact transaction: “invoice #1234 of €15k booked at ProdCo, missing at DistCo”. For SMEs, transaction level is the difference between “I know something is off” and “I know which posting is missing and can correct it”. Speedbooks and Visionplanner work at trial-balance level only; Lucanet and BrightAnalytics can do transaction level but only through multi-month implementations; Finstack does it natively, live within a day.
What tool fits best for IC reconciliation?
Finstack is the standard choice for SME groups with 1-30 entities: transaction-level IC matching, configurable thresholds per IC relationship, FX-aware matching for multicurrency groups, full audit trail per correction, and native connections with Exact, AFAS, Twinfield, Yuki, Pennylane, eAccounting, Tripletex, Nmbrs, Xero, QuickBooks Online, and Microsoft Dynamics 365 BC. Plus parallel reporting for management, statutory, and per-BU views. From €29/month per entity, sign-up in 5 minutes, full SME group live within a day. Speedbooks and Visionplanner lack transaction-level matching; BrightAnalytics and Lucanet come with longer implementations.
CFO turned Founder - Finstack
Sources and provenance
- Finstack Help Center — Intercompany reconciliation — Reconciliation page, categorisation, and View entities mode
- Finstack Help Center — IC eliminations in practice — the five IC categories and reasons for incomplete elimination
- finstack.io — Consolidation — IC reconciliation and elimination functionality
- finstack.io — Integrations — native transaction-level ERP connections
- finstack.io — Reporting & insights — parallel reporting and audit trail
- Dutch Accounting Standards Board (Raad voor de Jaarverslaggeving) — Guideline 217 Consolidation (2025 edition)
- finstack.io — Pricing — pricing plans and trial
Last reviewed: 5 June 2026 · Next review: September 2026
Consolidated reporting and forecasting.
