Multi-Entity Year-End Close: Automating Intercompany Reconciliation & Consolidation

Multi-Entity Year-End Close: Automating Intercompany Reconciliation & Consolidation

Closing the books for one company is already a coordinated finance process.

Closing a group of companies is different.

A multi-entity organization may have subsidiaries operating across different countries, currencies, accounting systems, charts of accounts, and close calendars.

Each entity can technically complete its own books while group finance is still unable to produce reliable consolidated reporting.

Consider a group with:

• A parent company using QuickBooks
• A UK subsidiary using Xero
• Another subsidiary using Sage
• Different local charts of accounts
• Intercompany management fees
• Intercompany loans
• Multiple currencies
• Different month-end processes

Each entity may report:

“Our books are closed.”

But group finance may still need to resolve:

• Missing trial balances
• Inconsistent account mappings
• Due-to and due-from differences
• Intercompany transactions posted in different periods
• Foreign exchange differences
• Elimination entries
• Consolidation adjustments
• Group reporting variances

That is why completing each subsidiary’s ledger does not automatically mean the multi-entity financial close is complete.

For the broader entity-level process covering AP, AR, balance-sheet reconciliation, close ownership, reporting, approvals, and period lock, see our year-end financial close checklist for CFOs.

A controlled group close follows a sequence:

The opportunity for automation is not simply to create consolidated reports faster.

It is to control the data and workflows that feed those reports.

What Is a Multi-Entity Financial Close?

A multi-entity financial close is the process of completing, collecting, standardizing, reconciling, adjusting, eliminating, consolidating, and reviewing financial information across a parent company and its subsidiaries.

The objective is to move from individually closed entities to a trusted group-level financial view.

Conceptually:

The process becomes more difficult when subsidiaries operate independently.

One company might record an intercompany transaction in QuickBooks on December 29.

Another entity may record the corresponding transaction in Xero on January 2.

One may record the transaction in USD.

The other may maintain its books in GBP.

One may classify the transaction as:

Management Fee Expense

while the other uses:

Intercompany Service Revenue

Before group finance can eliminate those balances, it first needs to understand whether the two records represent the same economic transaction and why the values differ.

That is the core challenge of multi-entity close.

Why Multi-Entity Year-End Close Gets Difficult

The complexity usually does not come from one problem.

It comes from several finance processes interacting at the same time.

1. Different Accounting Systems

A growing group may inherit or intentionally maintain different accounting systems across entities.

Examples include:

• QuickBooks
• Xero
• Sage
• NetSuite
• Microsoft Dynamics 365 Business Central
• Local ERP platforms
• Proprietary finance systems

These systems may expose financial information differently.

Account structures, journal formats, transaction identifiers, currency fields, APIs, and reporting models can vary.

Group finance therefore needs a consistent method for extracting the required financial information from every source.

2. Different Charts of Accounts

Subsidiaries do not always use identical account codes or descriptions.

For example:

For consolidated reporting, all three may need to roll into:

Service Revenue

This does not necessarily mean every entity needs to abandon its local chart of accounts.

It means group finance needs reliable mapping between:

Local Account

and

Group Reporting Account

3. Intercompany Transactions Do Not Always Match

Intercompany relationships can include:

• Sales and purchases
• Shared services
• Management fees
• Loans
• Interest
• Intercompany AR/AP
• Cost allocations
• Inventory transfers
• Cash movements

Even when both entities record the same transaction, the balances may not agree.

Common causes include:

• Different posting dates
• Currency movements
• Missing entries
• Partial settlements
• Incorrect accounts
• Duplicate journals
• Cut-off differences
• Different document references

These differences need to be resolved before elimination.

4. Multiple Currencies

One entity may operate in USD.

Another may use GBP.

Another may use EUR.

The same transaction can therefore appear at different values depending on:

• Transaction currency
• Functional currency
• Exchange rate
• Rate date
• Period-end revaluation
• Group reporting currency

An FX difference can be valid.

But it still needs to be identifiable and explainable.

5. Entities Close at Different Speeds

A parent company may finish its close on January 3.

A subsidiary may not finish until January 6.

Another entity may still be investigating intercompany differences on January 8.

This creates a dependency chain.

The group reporting process cannot be considered complete while material entity-level inputs are still changing.

6. Spreadsheet Dependencies

Many multi-entity close processes still depend heavily on spreadsheets.

Finance teams may repeatedly:

• Export trial balances
• Copy intercompany balances
• Map local accounts
• Calculate FX adjustments
• Prepare elimination journals
• Combine financial statements
• Reconcile consolidated totals

Spreadsheets can be useful tools.

The problem begins when they become the primary integration layer between every finance system.

Each manual export, transformation, formula, and copy-paste step creates another place where errors or version-control issues can appear.

The Multi-Entity Year-End Close Workflow

A controlled multi-entity close should follow a defined sequence.

The following eight-stage framework helps finance teams move from individually closed entities to reviewed group reporting.

Stage 1. Confirm Each Entity Is Ready for Group Close

Consolidation should not begin with incomplete source books.

Before an entity enters the group close process, confirm that its underlying accounting work is sufficiently complete.

Depending on the organization, this may include:

• Accounts payable
• Accounts receivable
• Bank reconciliation
• Accruals
• Adjusting journals
• Payroll-related entries
• Subledger reconciliation
• Fixed asset updates
• Inventory accounting
• Trial balance review
• Local management approval
• Outstanding exceptions

The exact requirements will vary.

The important point is that group finance should know whether an entity is actually ready.

A simple readiness workflow might be:

This status should ideally come from a controlled close workflow rather than informal email confirmations.

Key question

Which entities are ready, and which ones are still blocking the group close?

That visibility is essential for the CFO and controller.

Stage 2. Collect Financial Data From Every Accounting System

Once an entity is ready, group finance needs the required financial data.

Depending on the consolidation model, this may include:

• Trial balance
• General ledger
• Intercompany balances
• Intercompany transactions
• Journal entries
• AR/AP balances
• Entity metadata
• Currency
• Reporting period
• Account mappings

A manual process often looks like:

A more connected architecture can look like:

Automation does not mean every source system has to behave identically.

The integration layer can translate different source formats into a consistent group model.

This is where connected business systems become important. Accounting, ERP, banking, payroll, CRM, and other operational systems can feed controlled financial data into a common integration layer without requiring finance teams to repeatedly move information between platforms manually.

Important control

Every extracted record should retain enough context to identify:

• Entity
• Source system
• Period
• Account
• Currency
• Transaction or journal reference
• Extraction date
• Transformation rule where applicable

Without source traceability, group finance may struggle to investigate differences later.

Stage 3. Normalize the Chart of Accounts

Different entities can keep different local account structures.

Group reporting still requires consistency.

The typical solution is a mapping layer.

For example:

Conceptually:

This mapping should be controlled.

Finance should know:

• Which local accounts are mapped
• Which group accounts they map to
• Who approved the mapping
• Whether a new local account has appeared
• Whether the mapping changed
• Whether historical treatment needs review

Avoid forcing every entity into an identical ledger

Standardization does not necessarily mean every subsidiary must use the same account codes.

A better principle is:

Normalize for group reporting while preserving local accounting detail.

That allows subsidiaries to retain appropriate local structures while group finance still receives consistent reporting.

Stage 4. Reconcile Intercompany Transactions Before Elimination

Intercompany reconciliation is one of the most important controls in a multi-entity close.

Suppose:

Entity A records:

Due from Entity B: $100,000

But:

Entity B records:

Due to Entity A: $98,500

The group has a $1,500 difference.

It would be risky to simply eliminate both balances and move on.

First, finance needs to understand the difference.

Possible causes include:

• FX movement
• Timing
• Missing journal
• Incorrect account
• Partial payment
• Fee
• Duplicate transaction
• Different posting period

The sequence should be:

Reconciliation and elimination are different

Reconciliation asks:

Do both entities agree on the intercompany activity?

Elimination asks:

Which internal activity should be removed from consolidated reporting?

Elimination should not be used to hide an unresolved mismatch.

For organizations with high transaction volumes, reconciliation automation can help by matching transactions using attributes such as:

• Entity pair
• Counterparty
• Invoice number
• Transaction reference
• Date
• Currency
• Amount
• Account
• Tolerance rule

Routine matches can be cleared automatically.

Exceptions can then be routed to finance.

For a deeper look at due-to/due-from balances, transaction matching, many-to-one relationships, FX differences, account mapping, tolerance rules, and exception handling, see our intercompany reconciliation software guide.

Reconcile Before You Eliminate

This principle deserves special emphasis.

Consider:

Entity A Receivable: $250,000

Entity B Payable: $247,500

If both amounts are eliminated without investigating the difference, the group may remove the internal activity while still carrying an unexplained $2,500 problem somewhere else in the close.

The mismatch could represent:

• A missing invoice
• FX
• Timing
• An unrecorded fee
• Incorrect classification
• Partial settlement

The correct sequence is:

Reconciliation → Elimination → Consolidation

not:

Elimination → Hope the Difference Disappears

Automation should reinforce this control.

For example, the workflow can block elimination preparation when the corresponding entity pair remains outside an approved tolerance.

Stage 5. Resolve Currency and FX Differences

Multi-currency groups add another layer to intercompany matching and consolidation.

Consider:

Parent Company: USD

UK Subsidiary: GBP

The parent records an intercompany management fee of:

$50,000

The UK company records the corresponding value as:

£39,600

By year-end, the translated value used for group reporting may be:

$49,750

The apparent difference is:

$250

That difference may be legitimate.

The important control is that finance can explain it.

A connected workflow should preserve:

• Transaction currency
• Local currency
• Reporting currency
• Exchange rate
• Rate date
• Translation result
• Revaluation or translation adjustment
• Manual override where allowed
• Approval history

Avoid hiding FX inside tolerance rules

Tolerances can be useful.

But a tolerance should not become a generic bucket for unexplained differences.

FX differences should be identifiable and explainable rather than silently absorbed into reconciliation.

Worked Example: Intercompany Matching Across Currencies

Consider a simple three-entity group:

Parent Co.

USD

QuickBooks

UK Subsidiary

GBP

Xero

EU Subsidiary

EUR

Sage

The parent company charges the UK entity:

$50,000 management fee

The UK company records:

£39,600

During the year-end close, the group reporting translation produces:

$49,750

The reconciliation workflow could be:

1. Extract both records

Pull the source transactions from QuickBooks and Xero.

2. Confirm the relationship

Identify:

Parent ↔ UK Subsidiary

3. Map corresponding accounts

Parent:

Intercompany Service Revenue

UK:

Intercompany Management Expense

4. Match transaction references

Use invoice number, entity pair, date, or another controlled identifier.

5. Compare translated values

Parent: $50,000

UK translated value: $49,750

Difference: $250

6. Identify the reason

If the difference is caused by exchange-rate treatment, classify it appropriately according to the group’s accounting policy.

7. Mark the pair reconciled

Only after the difference is understood or appropriately approved.

8. Prepare the elimination

Remove the internal revenue/expense effect from group reporting.

9. Consolidate

Include the remaining external economic activity in group-level statements.

This example is illustrative. Actual FX, accounting, and consolidation treatment depends on the organization’s policies, systems, entity structure, and applicable accounting framework.

Stage 6. Prepare Intercompany Eliminations

Once intercompany balances have been reconciled, finance can prepare eliminations.

Common intercompany activity may include:

• Intercompany revenue
• Intercompany expenses
• Intercompany receivables
• Intercompany payables
• Intercompany loans
• Internal service charges
• Certain inventory transfers
• Interest between group entities

The purpose of elimination is to prevent transactions within the group from overstating consolidated results.

Conceptually:

Important distinction

Reconciliation verifies the relationship.

Elimination removes the group-internal effect.

They are connected processes, but they should remain separate controls.

Automation opportunity

Where relationships and mappings are consistent, automation may help:

• Identify eligible intercompany balances
• Associate corresponding entity pairs
• Prepare elimination data
• Flag unbalanced eliminations
• Detect duplicate elimination journals
• Preserve source references
• Route exceptions for approval

Final accounting judgment and approval should remain with finance.

Stage 7. Consolidate Entity Financials

Once financial data is:

• Complete
• Standardized
• Reconciled
• Translated where required
• Adjusted
• Ready for elimination

group finance can move into consolidation.

A simplified flow is:

Depending on the organization, consolidation may also need to reflect:

• Ownership structures
• Acquisitions
• Non-controlling interests
• Group-level adjustments
• Management reporting classifications

Those topics can become technically complex and should follow the organization’s applicable accounting framework and policies.

The key point for this workflow is:

Consolidation should consume controlled data, not compensate for unresolved upstream problems.

For a deeper explanation of ownership structures, acquisitions, non-controlling interests, currency translation, consolidation adjustments, and group-level statements, see our guide to consolidated financial reporting.

If group finance is constantly correcting entity data inside the consolidation workbook, the underlying close process may need attention.

Stage 8. Validate and Lock Group Reporting

A consolidation run is not the end of the close.

Group finance should review the resulting reporting.

Typical review areas include:

• Consolidated profit and loss
• Consolidated balance sheet
• Cash flow reporting
• Intercompany elimination balances
• FX and translation adjustments
• Material variances
• Consolidation journals
• Entity-to-group reconciliations
• Outstanding exceptions

The final sequence should be:

The close should retain an audit trail showing:

• Who reviewed the reporting
• What adjustments were made
• When they were approved
• What source evidence supported them
• Which exceptions remained open
• Who approved final close

This becomes particularly important when multiple teams contribute to the group close.

Build a Multi-Entity Close Control Matrix

CFOs and controllers need visibility into where the close is blocked.

A simple control matrix can show status across all entities.

This immediately tells group finance:

Which entity is preventing the consolidated close from progressing?

Without this visibility, finance teams often spend time requesting status updates rather than resolving exceptions.

The matrix can also be expanded to show:

• Owner
• Reviewer
• Due date
• Exception count
• Material variance
• Last refresh time

Common Multi-Entity Close Exceptions

A strong close process should make problems visible rather than bury them inside spreadsheets.

The objective should be to identify:

Where did the exception occur?

Who owns it?

What needs to happen next?

What Should Be Automated in a Multi-Entity Close?

Not every finance activity should be automated.

A practical model is:

The objective is not a completely hands-off close.

The better principle is:

Automate data movement, standardization, routine matching and monitoring. Escalate exceptions. Keep accounting judgment and final approval with finance.

More broadly, accounting automation can connect record-to-report activities such as intercompany transactions, reconciliations, close checklists, consolidation, exception management, and financial reporting while preserving approval and audit controls.

Where Multi-Entity Close Automation Creates the Most Value

Automation is most useful where finance teams repeatedly perform predictable work.

1. Financial Data Collection

Instead of manually exporting data from every accounting platform, integrations can retrieve required entity-level information using controlled schedules or close triggers.

Finance can then focus on whether the data is correct rather than repeatedly collecting it.

2. Chart-of-Accounts Mapping

Reusable mapping rules can translate local accounts into group accounts.

New or unmapped accounts can be flagged for review rather than silently excluded.

3. Intercompany Matching

Routine transactions can be matched using identifiers such as:

• Entity pair
• Invoice number
• Date
• Amount
• Currency
• Account
• Reference

Unmatched transactions can move into an exception queue.

4. FX Processing

Configured FX logic can consistently apply appropriate data inputs while maintaining the relevant rate, date, currency, and adjustment information.

Material or unusual differences can be escalated.

5. Elimination Preparation

Once relationships are reconciled, automation can prepare or support elimination workflows using controlled mappings.

This reduces repeated spreadsheet manipulation.

6. Consolidated Reporting

When standardized entity data feeds the reporting process directly, group reports can be refreshed without rebuilding the entire consolidation workbook.

7. Close Monitoring

A central status view can show:

• Late entities
• Unmapped accounts
• Unmatched intercompany transactions
• FX exceptions
• Pending eliminations
• Outstanding approvals

This helps CFOs identify where the close is actually losing time.

Cross-ERP Multi-Entity Close Architecture

A multi-entity business does not necessarily need every subsidiary to operate the same ERP.

A connected architecture can accommodate multiple systems.

For example:

The integration layer becomes responsible for preserving:

• Entity identity
• Account mapping
• Currency
• Reporting period
• Transaction relationships
• Intercompany counterparties
• Source references
• Processing status

Core principle

The group close does not require every entity to use the same accounting system. It requires controlled collection, mapping, reconciliation, and reporting across the systems already in use.

This becomes especially valuable when an organization grows through acquisitions and inherits different accounting platforms.

A practical example is Satva’s multi-entity financial consolidation case study, where multiple Xero organizations were connected to a centralized reporting workflow so finance users could generate P&L, balance sheet, and trial balance reports directly in Excel while maintaining organization-level access and multi-currency reporting.

When Standard Consolidation Tools May Not Be Enough

A standard consolidation platform may work well when:

• Entity structures are consistent
• Accounting systems are supported
• Charts of accounts map cleanly
• Intercompany relationships are straightforward
• Reporting requirements are standard

Complexity increases when the group has:

• Multiple ERPs
• Proprietary accounting systems
• Complex entity relationships
• Custom intercompany transaction types
• Many-to-many transaction matching
• Custom group chart of accounts
• Non-standard FX requirements
• Bespoke management reporting
• Acquisition-driven system diversity
• Custom approval workflows
• Heavy spreadsheet dependencies
• Source systems that do not expose required data cleanly

At that point, the key question is not necessarily:

Do we need different consolidation software?

A better question may be:

Is consolidation failing because the financial data reaching it is inconsistent, disconnected, incomplete, or unreconciled?

If the problem exists upstream, changing the reporting layer alone may not solve it.

The workflow may require:

• Custom integrations
• Controlled transformation logic
• Intercompany matching rules
• Exception monitoring
• Data validation
• Group-account mapping
• Reconciliation automation
• Custom consolidation feeds
• Management reporting workflows

The objective should be to solve the actual finance-process bottleneck.

Satva’s solutions for CFOs and finance leaders focus on connecting entity-level accounting platforms, automating reconciliation and intercompany workflows, normalizing financial data, and improving consolidated reporting visibility across multi-entity environments.

Multi-Entity Year-End Close Checklist

Before final group approval, confirm:

• Each entity has completed its local close
• Trial balances have been validated
• Financial data has been collected from all required systems
• Reporting periods are aligned
• Entity mappings are correct
• Local accounts are mapped to the group chart of accounts
• New or unmapped accounts have been reviewed
• Intercompany accounts have been identified
• Due-to and due-from balances have been reconciled
• Transaction-level intercompany exceptions have been resolved or approved
• FX differences have been reviewed
• Elimination balances have been prepared
• Elimination entries have been reviewed
• Consolidation adjustments have been reviewed
• Ownership and reporting structures have been validated where relevant
• Consolidated statements have been reviewed
• Material variances have been explained
• Outstanding exceptions have owners
• Group-level approval has been completed
• Period has been locked
• Supporting evidence and audit trail have been retained

The checklist should not end with:

“All entities submitted their numbers.”

The stronger question is:

Can group finance trace how those entity numbers were standardized, reconciled, adjusted, eliminated, and consolidated into the final reporting?

A Better Group Close Starts Before Consolidation

Consolidation is often treated as the final step in a multi-entity close.

But many consolidation problems begin much earlier.

They begin when:

• Entity data is late
• Accounts are mapped inconsistently
• Intercompany balances do not agree
• FX differences are unexplained
• Eliminations are prepared from unreconciled balances
• Spreadsheets become the connection between every finance system

A more controlled process follows the full sequence:

The automation opportunity is therefore larger than faster reporting.

It is about connecting the systems and workflows that feed group reporting so routine data collection, transformation, matching, and monitoring happen consistently, while finance retains control over exceptions, accounting decisions, consolidation adjustments, and final approval.

That is what turns multi-entity year-end close from a spreadsheet exercise into a controlled finance process.

Frequently Asked Questions

What is a multi-entity financial close?

A multi-entity financial close is the process of completing entity-level books and then standardizing, reconciling, adjusting, eliminating, consolidating, and reviewing financial information across multiple companies within a group.

The process typically includes entity readiness, financial data collection, chart-of-accounts mapping, intercompany reconciliation, FX review, eliminations, consolidation, and group reporting.

How is a multi-entity close different from a normal year-end close?

A normal entity-level close focuses on the financial records of one company.

A multi-entity close adds group-level requirements such as:

• Collecting data from several companies
• Standardizing charts of accounts
• Reconciling intercompany balances
• Handling multiple currencies
• Preparing eliminations
• Consolidating entity financial statements
• Reviewing group-level results

Each entity can be individually closed while the group close remains incomplete.

Should intercompany reconciliation happen before consolidation?

Intercompany reconciliation should generally occur before elimination and consolidation because finance first needs to determine whether corresponding entities agree on the underlying transactions and balances.

Eliminating mismatched balances can hide timing, currency, mapping, or posting differences rather than resolving them.

A stronger sequence is:

Reconcile → Eliminate → Consolidate

How do you consolidate financial data from different accounting systems?

Financial data can be extracted from each accounting or ERP platform and transformed into a standardized group data model.

The workflow may include:

1. Source data extraction
2. Entity identification
3. Period alignment
4. Chart-of-accounts mapping
5. Currency handling
6. Intercompany reconciliation
7. Eliminations
8. Consolidated reporting

The subsidiaries do not necessarily need to use the same accounting platform if the required financial data can be collected and mapped reliably.

How are different charts of accounts handled during consolidation?

Local accounts can be mapped to a standardized group chart of accounts.

For example:

Entity A: Consulting Revenue

Entity B: Professional Services

Entity C: Management Income

may all map to:

Group Account: Service Revenue

This enables consistent consolidated reporting while allowing entities to maintain appropriate local account structures.

Can intercompany reconciliation and consolidation be automated?

Many repeatable parts can be automated, including:

• Source data collection
• Chart-of-accounts mapping
• Routine intercompany matching
• FX calculations based on configured rules
• Elimination preparation
• Duplicate detection
• Consolidated report refreshes
• Exception monitoring

Accounting judgment, material adjustments, unresolved variances, final approval, and period lock should remain under appropriate finance control.

How do multi-currency entities affect the year-end close?

Multi-currency groups need to preserve transaction currency, entity-level currency, group reporting currency, relevant exchange rates, and translation adjustments.

Intercompany transactions may appear at different values across entities because of currency movements or timing.

Those differences should be identified and explained before the related balances are eliminated and consolidated.