As organisations expand across markets, entities, currencies, and finance systems, intercompany accounting can quietly slow the financial close. Intuit’s 2026 Enterprise Technology Benchmark Report found that 80% of multi-entity businesses face bottlenecks in managing intercompany transactions and billing. The challenge goes beyond transaction volume. Mismatched records, timing differences, and manual investigation can surface when finance teams have the least time to resolve them.
Why is intercompany accounting a bottleneck in financial close?
Intercompany accounting becomes a close bottleneck when two entities record the same economic event differently, leaving finance teams to identify and resolve the gap before consolidation.
More entities mean more points of reconciliation
Every intercompany transaction creates a relationship between two sets of books. As an organisation adds entities, the number of intercompany relationships, reconciliation dependencies, and balances that must align increases across:
- Transaction values and dates
- Currencies and exchange rates
- Account classifications and mappings
- Counterparties and supporting records
That makes the close more than a matter of completing each entity’s books. Finance teams must also confirm that the books agree with one another.
Timing and systems create avoidable exceptions
Different close calendars, accounting practices, ERP or GL environments, and posting schedules can create discrepancies even when neither entity has made an accounting error. Currency movements and inconsistent mappings can add further complexity.
Planful’s 2025 Global Finance Survey found that 43% of respondents cited complex intercompany transactions and eliminations as a major financial-close or consolidation friction point. Data reconciliation issues and multiple ERP or GL integrations are also among the leading sources of friction.
These issues compound each other. Fragmented systems make data harder to align, while reconciliation problems force finance teams to spend more time investigating discrepancies during an already time-sensitive close.
The problem surfaces at the worst possible time
When teams discover mismatches during close, they often turn to spreadsheets, emails, manual investigation, and adjustment journals. Even a small-value discrepancy can consume disproportionate time when teams must trace its cause across entities.
The real bottleneck, therefore, is not the discrepancy alone. It is late discovery combined with manual resolution.
How do enterprises simplify intercompany reconciliation?
Effective intercompany reconciliation starts before the close. Finance leaders can reduce downstream effort by creating consistent processes, matching transactions earlier, and making unresolved exceptions visible.
Standardise the rules before automating
Organisations should establish common rules for entity and counterparty identification, account mapping, transaction coding, cut-off, currency treatment, approvals, and documentation.
This matters because automation cannot compensate for inconsistent processes. If two entities capture the same transaction differently, technology may simply move the inconsistency through the process faster.
Match transactions closer to the point of entry
Waiting until month-end to compare balances gives discrepancies time to accumulate. Matching transactions soon after they enter the books gives teams a better chance to investigate while the relevant activity, documentation, and ownership are still clear.
This shift turns intercompany reconciliation from a close-stage clean-up exercise into an ongoing control.
Manage exceptions rather than chase every balance
A mature process should make exceptions easy to prioritise and assign. Useful controls include:
- Ageing unmatched items to prevent them from rolling forward
- Prioritising material discrepancies
- Assigning clear ownership for resolution
- Escalating overdue exceptions
- Tracking recurring root causes
Each unresolved discrepancy carried into another period adds reconciliation debt, more history to trace, more effort to resolve, and greater risk of another delayed close.
How does automation speed up multi-entity close?
Automation can accelerate a multi-entity close when it removes repetitive reconciliation work and gives finance teams earlier visibility into exceptions. The objective is not to automate professional judgement; it is to reserve human attention for the issues that genuinely require it.
Automate high-volume matching and monitoring
Rules-based automation can handle activities such as:
- Matching corresponding intercompany transactions
- Comparing balances across entities
- Identifying exceptions
- Tracking reconciliation status
- Supporting recurring elimination processes
That reduces the manual comparison work that often absorbs finance capacity during close.
Redirect expertise towards complex exceptions
Automation handles volume; finance teams handle complexity. Instead of spending hours confirming routine matches, professionals can investigate material discrepancies, unusual transactions, root causes, and accounting judgements.
Planful found that 37% of finance teams take more than six days for account reconciliations, while another 37% take six or more days for consolidation adjustments. These figures highlight how much close capacity can remain tied up in activities that lend themselves to greater standardisation and automation.
Reduce the work that reaches close
The strongest automation strategy does not simply make the final reconciliation faster. It reduces the number of unresolved items entering the close cycle.
That distinction matters. A faster close comes from resolving exceptions earlier, not from asking teams to work through the same volume of exceptions more quickly at month-end.
Infosys BPM helps organisations standardise, automate, and optimise finance processes across complex operating environments. Its AI-enabled finance and accounting solutions, including record-to-report, automation, analytics, and scalable finance operations, can help embed stronger intercompany controls within the wider finance transformation agenda.
Conclusion
Finance leaders should measure more than how quickly teams clear intercompany discrepancies during close. The stronger measure is how effectively the operating model prevents those discrepancies from reaching close in the first place. Standardised processes, earlier matching, continuous visibility, exception-based management, and automation can turn intercompany accounting from a recurring source of friction into a controlled part of a more predictable, scalable multi-entity close.
Frequently asked questions
Any transaction between two entities under common ownership: intercompany sales, shared service recharges, management fees, royalties, interest on internal loans, and transfers of inventory or fixed assets. Each one has to be recorded by both entities and then eliminated on consolidation, which is where mismatches surface.
Reconciliation confirms that both entities recorded the same transaction the same way. Elimination removes the resulting balances so the group accounts show only external activity. Elimination is only reliable once reconciliation is clean; eliminating unreconciled balances hides the discrepancy in the consolidated numbers instead of resolving it.
Timing and treatment, mostly. Different close calendars mean one entity books a transaction in a period the other has already closed; different exchange-rate policies produce different local-currency values for the same amount; and inconsistent account mappings put the same transaction in different places. None of these is an accounting mistake, but all three create exceptions someone has to investigate.
Tolerances should be set by materiality and by transaction type rather than as one group-wide number, and reviewed as volumes change. The practical test is whether the tolerance stops teams investigating rounding and currency noise without letting genuine differences accumulate. A tolerance that never produces an exception is usually set too wide.
Centralising the transactional work (matching, exception tracking, reporting) makes standardisation possible, which is the precondition for automation. Local finance teams still need to own the accounting judgement and the relationships behind the transactions. The split that works is central execution against globally defined rules, with local ownership of the exceptions that need business context.
Any transaction between two entities under common ownership: intercompany sales, shared service recharges, management fees, royalties, interest on internal loans, and transfers of inventory or fixed assets. Each one has to be recorded by both entities and then eliminated on consolidation, which is where mismatches surface.
Reconciliation confirms that both entities recorded the same transaction the same way. Elimination removes the resulting balances so the group accounts show only external activity. Elimination is only reliable once reconciliation is clean; eliminating unreconciled balances hides the discrepancy in the consolidated numbers instead of resolving it.
Timing and treatment, mostly. Different close calendars mean one entity books a transaction in a period the other has already closed; different exchange-rate policies produce different local-currency values for the same amount; and inconsistent account mappings put the same transaction in different places. None of these is an accounting mistake, but all three create exceptions someone has to investigate.
Tolerances should be set by materiality and by transaction type rather than as one group-wide number, and reviewed as volumes change. The practical test is whether the tolerance stops teams investigating rounding and currency noise without letting genuine differences accumulate. A tolerance that never produces an exception is usually set too wide.
Centralising the transactional work (matching, exception tracking, reporting) makes standardisation possible, which is the precondition for automation. Local finance teams still need to own the accounting judgement and the relationships behind the transactions. The split that works is central execution against globally defined rules, with local ownership of the exceptions that need business context.


