Conso 360.

Intercompany reconciliation software

Find intercompany differences before they turn into consolidation plugs.

Conso 360 matches intercompany balances between entity pairs with rules you configure, shows what does not agree and tracks each difference until it is resolved. Eliminations in the consolidation then start from balances both sides recognise.

Built for: group finance teams, shared service centres and accounting managers.

What the team sees

  • An intercompany matrix of all entity pairs
  • Matched, unassigned and open differences
  • Reason codes and a status for each difference
  • Drill-down from a pair to the underlying balances

Why it takes so long

Two entities, one transaction, two different numbers.

Intercompany differences are rarely complicated. They are slow because nobody can see all of them at once, and because resolving them depends on emails between teams in different entities.

Timing differences

An invoice is booked by the seller in March and by the buyer in April.

Currency differences

Each side records the same balance at a different rate.

Wrong partner or account

A balance is posted without the intercompany partner, or to a non-intercompany account.

No shared status

It is unclear who is investigating which difference, and what has already been agreed.

Example workflow

From identification to resolution.

A typical month-end cycle for a group with several trading entities.

  1. 01

    Prepare

    Entities record intercompany balances with the partner company, in Conso 360 or in the imported trial balance.

  2. 02

    Match

    Run matching. Rules compare the two sides of each pair and mark balances within tolerance as matched.

  3. 03

    Investigate

    Open the pair detail, drill into the balances and assign a reason code to each remaining difference.

  4. 04

    Resolve

    Track the difference through statuses such as assigned, in contact and pending confirmation, until it is corrected or accepted.

  5. 05

    Eliminate

    Run the consolidation. Intercompany balances are eliminated, and any accepted difference is visible rather than hidden.

Product interface

Every entity pair on one screen.

The intercompany view shows each pair's receivable and payable side by side, with the difference and its status.

Intercompany pairs · period-end

Illustrative example
PairReceivablePayableDifferenceStatus
Parent ↔ Subsidiary A 320 320 0 Matched
Subsidiary A ↔ Subsidiary B 145 131 14 Assigned · timing
Parent ↔ Subsidiary B 88 86 2 Within tolerance

Open differences carry a reason code and an owner, so nothing is eliminated without an explanation.

Simplified illustration with fictional companies and figures. It is not a screenshot of customer data.

Capabilities

Reconciliation first, elimination second.

Matching and elimination are separate steps. Reconciliation establishes that both sides agree; the consolidation run then eliminates the agreed balances.

Configurable matching rules

Choose how pairs are matched: exact, grouped or auto-assigned, with tolerances, matching expressions and reason codes.

Intercompany matrix and pair detail

Move from a group-wide matrix to a single pair and down to the balances behind a difference.

Difference lifecycle

Differences move through statuses including new, unassigned, assigned, in contact, pending confirmation and matched.

Rule-based adjustments

Where your policy allows it, small or known differences can be adjusted automatically by rule, and those adjustments are shown separately.

Link to consolidation

Intercompany balances are eliminated in the consolidation run using the same partner and account information.

Run on demand

Rerun matching as entities correct their bookings, and mark a reconciliation as done when the period is clear.

Audit evidence

A record of how each difference was handled.

When the auditor asks about an intercompany difference, the answer is in the system rather than in an email thread.

  • Reason codes

    Each difference can be classified, for example as timing, currency or posting error.

  • Status history

    The current status shows whether a difference is being investigated, waiting for the counterparty or resolved.

  • Drill-down to source

    Every figure in the matrix can be traced to the balances that produce it.

  • Visible residual differences

    Differences that remain at period-end stay visible in reporting instead of disappearing into eliminations.

Frequently asked questions

What is intercompany reconciliation?

It is the process of confirming that balances and transactions between group companies agree on both sides, for example that one entity's receivable equals the other's payable, and of investigating the differences before consolidation.

How is reconciliation different from intercompany elimination?

Reconciliation checks that both sides agree. Elimination removes the agreed balances from the consolidated accounts. Conso 360 supports both, as separate steps, so eliminations are based on balances that have been reconciled.

Does Conso 360 match transactions automatically?

Matching runs automatically against the rules you configure: exact matches, matches within tolerance, grouped matches and auto-assignment. Differences the rules cannot resolve are left for your team to investigate.

Can counterparties confirm balances in the system?

You can record a difference as in contact or pending confirmation and track it to resolution. The conversation with the counterparty itself usually happens through your normal channels; ask us in a demo how your group handles confirmations.

What causes most intercompany differences?

Timing differences, different exchange rates, missing partner codes and postings to the wrong account. Reason codes let you see which causes recur, so you can fix the process rather than the symptom.

Related guides

Show us your intercompany pairs.

We will look at how your entities record intercompany balances and how matching and eliminations would work for your group.