Performance Playbooks › Finance › Intercompany Accounting
The discipline that shrinks intercompany close cycles
Learn how to build automation, pre-close alignment, and centralized policy into intercompany accounting so mismatches resolve without escalation and accounts close in 2–5 days. This playbook shows you the three shifts that separate reliable reconciliation from world-class speed.
World-class intercompany accounting rests on three shifts: automation that replaces bilateral email chains with real-time transaction matching; pre-close alignment that surfaces mismatches before consolidation runs; and centralized policy that eliminates local variation in transfer pricing and settlement logic. Strong teams reconcile reliably but still spend days chasing exceptions; world-class teams resolve 90%+ of mismatches without escalation and close intercompany accounts in 2–5 days instead of 5–12.
The benchmarks
| Metric | Minimum | Strong | World-class |
|---|---|---|---|
| Intercompany Transaction Reconciliation TimelinessPercentage of intercompany transactions that are matched, reconciled, and cleared within the standard monthly close window. | 75-85% | 85-95% | 95-99% |
| Intercompany Elimination Accuracy RatePercentage of consolidated financial statements where all intercompany transactions and balances are correctly eliminated without material restatement or adjustment in subsequent periods. | 80-88% | 88-96% | 96-99% |
| Days to Close Intercompany AccountsAverage number of calendar days required to complete all intercompany transaction identification, reconciliation, and elimination entries after month-end. | 8-12 | 5-8 | 2-5 |
| Intercompany Receivables and Payables Outstanding Balance VariancePercentage variance between intercompany receivables reported by the selling entity and intercompany payables reported by the buying entity for the same transaction set. | 5-10% | 2-5% | 0-2% |
| Intercompany Transaction Exception Resolution RatePercentage of identified intercompany mismatches, breaks, or exceptions that are root-caused and resolved without escalation to senior management. | 70-80% | 80-90% | 90-97% |
The distance from strong to world-class on intercompany accounting is not uniform across the five metrics. Reconciliation timeliness (85–95% vs. 95–99%) and elimination accuracy (88–96% vs. 96–99%) show tight ranges because both require discipline that strong performers already have. The real gap widens on speed: strong teams take 5–8 days to close intercompany accounts; world-class teams do it in 2–5 days. That compressed timeline flows from automation and pre-close prep, not from working longer hours. Exception resolution widens too (80–90% vs. 90–97%), reflecting the difference between trained staff who can resolve most breaks and a team culture where problem-solving is distributed and escalations are rare. Receivables-payables variance (2–5% vs. 0–2%) narrows through standardized coding and centralized transaction repositories. The compounding cost of staying in the strong band instead of climbing to world-class is most visible in close cycle time: 3–6 extra days per month, multiplied across 12 months, plus the audit friction and delayed management reporting that lag creates.
What separates the leaders
The step from strong to world-class is hard because it requires moving from periodic reconciliation to continuous visibility. Strong teams have solid month-end processes: they match transactions, catch most breaks, and close intercompany in a predictable 5–8 days. But that timeline rests on concentrated effort compressed into the final week of the close window. Pre-close exceptions emerge late, forcing last-minute investigation and manual entry correction. The structural obstacle is that transactional data lives in operational systems (ERP, billing, cash management) while reconciliation happens in spreadsheets or standalone consolidation tools that receive data at period end. By the time the consolidation team runs matching logic, hundreds of unreconciled items are already days old and their context is lost. World-class organizations solve this by embedding transaction visibility earlier: they tag intercompany transactions in the source system as they are recorded, validate them against policy in near-real-time, and alert the reconciliation team to breaks before the books close. This requires integration between operational systems and a centralized intercompany platform or a well-designed consolidation tool with continuous data feeds. The second structural barrier is decision authority. Strong organizations have clear escalation rules, but exceptions still travel up to the controller or accounting manager for judgment calls on aged items or ambiguous coding. World-class teams distribute that authority: they train accounting staff to resolve common breaks (mismatched invoice amounts, timing differences, coding corrections) without escalation. They document the decision framework in a playbook and measure each accountant's resolution rate to reinforce ownership. Overcoming both barriers requires investment in platform capability and deliberate culture change. Leaders who reach world-class do not start by buying new software; they start by mapping the full transaction lifecycle, identifying where data quality degrades, and routing pre-close exceptions to the right person with the decision authority to act.
Metric by metric
Getting intercompany transactions matched and cleared in the close window
Reconciliation timeliness jumps from 85% to 95%+ when you move from month-end batch matching to continuous validation. The lever: embed intercompany transaction tagging in your source systems so that every sale, service charge, or allocation is marked as IC at the point of entry. Use a centralized reconciliation platform or a consolidation tool with real-time feeds to match buyer and seller records as soon as both are posted, not in a batch review five days later. Track the aging of unmatched items and alert the responsible parties daily. When 95% of transactions are already matched before the formal close window, your close period shrinks and audit risk drops.
Get the full Intercompany Transaction Reconciliation Timeliness playbook →Eliminating intercompany balances without restatement or adjustment
Accuracy moves from 88% to 96%+ through rigorous control design and supervisory review discipline. The core lever is a written elimination checklist keyed to your chart of accounts and subsidiary structure: which intercompany accounts must be eliminated in full, which consolidated at the entity level, which reversed in the subsequent period. Assign one senior accountant to review and certify all elimination entries before posting; require a second person to validate that the eliminations reverse correctly in the following month. This two-step sign-off catches most errors before they appear in draft financials. Track restatements by type (coding error, policy violation, timing difference) and feed findings back to the team monthly. Accuracy compounds over time as patterns become visible.
Get the full Intercompany Elimination Accuracy Rate playbook →Closing intercompany accounts in 2–5 days instead of 8–12
Days to close compresses when pre-close work moves most of the matching and exception resolution upstream. The highest-leverage action is a pre-close alignment meeting, held 2–3 days before period end, where the consolidation team reviews a live dashboard of unmatched and aging intercompany items, and operational finance commits to resolution. Entities submit intercompany subsidiary ledgers one day earlier than before, so breaks surface with time to fix them. Run automated exception reports daily in the final week; route specific breaks to named owners with clear resolution targets. By close day, 80%+ of work is already done and the consolidation team runs eliminations, not investigations.
Get the full Days to Close Intercompany Accounts playbook →Narrowing the gap between receivables and payables recorded by each party
Receivables-payables variance shrinks from 2–5% to 0–2% through standardized transaction coding and a centralized transaction repository. The key lever is a master intercompany agreement register, maintained by a central accounting team, that lists every standing IC relationship, its terms, cost allocation logic, and the GL accounts each party must use. Require all business units to submit IC transactions through a central intake process (email template, web form, or API feed) rather than posting them directly to the ledger. A clearing team matches buyer and seller records and posts them in both entities simultaneously using identical amounts and dates. This eliminates the timing and coding mismatches that inflate variance. Monthly reconciliation of the register against actual postings identifies drift early.
Get the full Intercompany Receivables and Payables Outstanding Balance Variance playbook →Resolving mismatches and breaks without escalation to senior management
Exception resolution rates rise from 80% to 90%+ when you push decision authority down and build a decision framework. Document the most common IC breaks your team encounters—mismatched invoice amounts, in-transit timing differences, coding corrections, allocation disputes—and create a playbook that shows each accountant how to investigate and resolve them. Pair each playbook entry with the GL accounts and approval workflow required. Hold a weekly 30-minute huddle where the team walks through unresolved exceptions from the prior week; rotate who presents each case to build shared problem-solving muscle. Measure each person's resolution rate and cycle time; recognise the fastest resolvers monthly. Over time, escalations become rare and the team's speed and confidence grow.
Get the full Intercompany Transaction Exception Resolution Rate playbook →How leaders approach it
Intercompany Transaction Settlement and Elimination
Build a repeatable process that identifies every intercompany flow—sales, service charges, loans, transfers—validates both sides match, and automatically posts elimination entries in the general ledger. Start by mapping all active intercompany relationships: which entities transact with which, what types of transactions occur, and which GL accounts are used on each side. Create a standing master intercompany agreement register that lists permitted transaction types, standard terms, and the required coding for each party. Require all IC transactions to flow through a central intake point where they are matched and posted in both entities simultaneously. This discipline eliminates the bilateral email chains and mismatched entries that delay consolidation. Your consolidation team's workload shifts from investigation to validation, and your audit team gains confidence that eliminations are systematic and complete.
Leading Practice Report
Full detail: Intercompany Transaction Settlement and Elimination
The full report covers:
- Expected benefits
- Core principles
- Key success factors
- Key metrics
- Risks and mitigations
- Implementation roadmap
Intercompany and Consolidation Pre-Close Alignment
Shift problem detection earlier by validating intercompany balances and consolidation assumptions before the consolidation engine runs. Two to three days before period end, convene the operational finance teams and consolidation lead to review a live exception report: unmatched transactions, aging open items, out-of-policy transactions, and any subsidiary reporting templates that are incomplete. Assign each exception to a named owner with a defined resolution deadline. This upstream review surfaces breaks while there is still time to investigate and correct them in the current period, rather than discovering them after consolidation and forcing rework entries. Document which exceptions are resolved operationally and which require elimination adjustments. By close day, your consolidation team focuses on processing known, pre-agreed entries rather than troubleshooting surprises.
Leading Practice Report
Full detail: Intercompany and Consolidation Pre-Close Alignment
Benefits, core principles, success factors, metrics, risks and the implementation roadmap.
Get the full report →Intercompany Settlement Automation
Automate the full lifecycle of intercompany transactions: capture from operational systems, validate against policy, post matching entries, and settle via centralized cash accounts or internal loans. Implement a centralized intercompany platform or configure your consolidation tool to import transaction feeds from your ERP, billing system, and cost allocation engine at least daily. Program matching rules that compare buyer and seller records on amount, date, and GL account coding; flag exceptions for manual review only when algorithm confidence is below a threshold. Post validated matches automatically in both entities' general ledgers using a standardized intercompany payable-receivable account pair. Set up automated settlement: weekly or monthly, generate an intercompany settlement journal that nets payables against receivables and posts the result to a central cash clearing account. This eliminates manual reconciliation bottlenecks, shrinks cash-in-transit times, and gives the treasurer real-time visibility of consolidated cash position across the enterprise.
Leading Practice Report
Full detail: Intercompany Settlement Automation
Benefits, core principles, success factors, metrics, risks and the implementation roadmap.
Get the full report →Where to start
- Map your intercompany universe in a single document: list every entity pair that transacts, the transaction types permitted (sales, services, transfers, allocations, loans), the GL accounts each side uses, and the standard terms. Identify which relationships lack a written agreement. Spend two hours and you will see the scope of your consolidation challenge and any policy inconsistencies that slow your close. Assign one person to own and update this register monthly.
- Run a pre-close alignment meeting 2–3 days before month-end close. Pull a live report of unmatched intercompany items, aged open items, and any out-of-policy transactions. Invite the operational finance leads from each entity to commit to resolution and triage decisions about which items require correction this period and which can settle next month. This single meeting, held consistently, will shrink your intercompany close time by 1–2 days because most breaks are known and assigned before consolidation begins.
- Measure your exception resolution rate this month: count how many intercompany breaks (mismatched amounts, timing differences, coding errors) your team resolves without escalating to management, and how many days each resolution takes. Document the decision framework for the three most common breaks. Share the framework with your team and track their resolution rates next month. This habit-building step creates accountability and builds a playbook that new hires can use to act independently.
How can we compress our intercompany close from 8 days to 5 without hiring more staff or buying new software?
Start free with Ask Kepler →Advanced and emerging approaches
Advanced & Emerging Practices
Emerging practices are included with Ask Kepler Pro and Max.
Unlock these practices →How are these playbooks made? Read our methodology.