What is intercompany reconciliation?

It is the matching of the two entries one movement inside a group produces: the receivable booked by the company that is owed, and the payable booked by the company that owes. Tresora reads both ledgers, pairs the entries on the movement itself, and reports what each side booked along with whatever is left between them.

What happens if only some of our entities are onboarded?

The scope is stated and every leg respects it. Movements between onboarded entities are paired on both sides. A movement facing a company outside the scope keeps its own leg, its counterpart name and the state Unmanaged, so it is never counted as matched and never dropped from a total. Onboard that company later and the second entry arrives with it.

Do both sides have to quote the same reference?

No. The pairing is on the movement — amount, direction, dates, counterpart and the settlement that carried it — and a shared reference counts as one signal among those rather than as the key. Where a reference does survive both postings, it makes the case stronger and nothing more.

Can the balances be netted before we pay?

Yes. Where two of your companies hold positions against each other, Tresora proposes the single transfer that settles both and names every movement inside it. The netting happens before anything moves externally, and the transfer only leaves along the approval path you defined.

What if the two sides book in different currencies?

Each side keeps the amount and the rate its own entry was booked at, and the pair is matched on the movement rather than on a translated figure. The group view shows both amounts, the rate behind each one and the day it applied, so the difference between them is a number your auditor can reproduce instead of one somebody has to explain.

Inside the group

Two companies book the same movement. Intercompany reconciliation is where the two entries meet.

An intragroup invoice, a loan, a rebilling, a transfer: one of your companies holds one side of it and another holds the other. Tresora reads both ledgers, pairs the entries on the movement rather than on a reference somebody re-keyed, and names whatever is left between them.

Request a demo

Intercompany pending review · one movement

Rebilled shared costs

EUR 132,600

4400012884 · Aug 12

Corporation Servicios: EUR 132,600
Corporation España: Nothing posted

StateWaiting for the second entry

Until the second entry is posted, this one document is the whole difference between the two companies.

Two ledgers

Why don’t the two sides of one movement look alike?

Because nothing makes them. Each company posts into its own books, on its own day, under its own document number, and neither entry was written with the other one in mind.

Neither reference means anything to the other.: The issuing company’s document number and the receiving company’s are two independent sequences. A match built on a shared reference holds until somebody re-keys one, which is most weeks.
The two sides post on different days.: One books when it issues, the other when it approves. Across a period cut that is not an error: it is one entry that exists and one that does not yet, and it closes itself the moment the second lands.
Each side books in the currency it actually books in.: So one movement arrives as two amounts, each correct in its own books and translated at the rate on its own posting day. The pair is matched on the movement, and both amounts keep the rate they were booked at.
One side may not have posted at all.: A rebilling issued on Friday and approved on Tuesday is a real position in one company and nothing at all in the other. Read one ledger and that gap looks like a balance. Read both and it has a document, a date and a company name on it.

So the match is on the movement itself: the amount, the direction, the dates around it, the counterpart and the settlement that carried it. A shared reference is one signal among those, never the key the whole thing hangs on.

What it reads

What does it read, and which entities does it cover?

The ledgers of the entities you onboard, and the bank movements that settle between them. You pick the scope, and the scope is printed on the screen rather than assumed.

From each entity’s books

Journal entries, and the intercompany accounts they post to
Open and cleared items on the intercompany customer and supplier accounts
General ledger lines, at the level the entry was actually booked
Intercompany loan schedules, with the interest each side has accrued
The entity catalog and the group structure: who belongs to what, and from when

From the banks in between

The transfer that actually settled the position, and the day the money moved
What the correspondent banks took out of it on the way
Which account it left and which account received it
The value date on each end, which is rarely the same day

The entities with an open intercompany position

Open intercompany positions: EUR 43,611,400; Every movement counted once, never both of its legs.
Entities with an open position: 4; Of 61 in the group structure. The rest have no internal balance to net.
Counterparts outside it: 2; Every leg facing them is labeled, and none of them is dropped.

An entity you have not onboarded is not a gap in the data. It is a boundary, and every figure on this page knows exactly where it runs.

Matched

What does the group position look like once both legs are matched?

Pair by pair, with the amount each side booked beside the other. Add the two legs of an agreed movement and you get nothing back, because they are the same money written down from both ends.

Intercompany · by counterpart

IN SCOPE

Carried by both ledgers

EUR 39,281,000

Aug 14

Counterpart pair	Receivable	Payable	Difference
Corporation Holding · Corporation Servicios Both sides agreeReceivableEUR 4,960,000PayableEUR 4,960,000	EUR 4,960,000	EUR 4,960,000	EUR 0
Corporation Holding · Corporation España Needs a decisionReceivableEUR 18,420,000PayableEUR 18,357,000	EUR 18,420,000	EUR 18,357,000	EUR 63,000
Corporation Servicios · Corporation España Closes itselfReceivableEUR 6,845,000PayableEUR 6,712,400	EUR 6,845,000	EUR 6,712,400	EUR 132,600
Corporation Holding · Corporation México Needs a decisionReceivableEUR 9,260,000PayableEUR 9,251,600	EUR 9,260,000	EUR 9,251,600	EUR 8,400

Both legs, added togetherEUR 0

Named differences · 3EUR 204,000

In every pair the first entity carries the receivable and the second the payable, so the two columns are one movement read from each end.

Nothing here is set to nothing by assumption. Each row holds the amount both companies actually booked, and the zero underneath is what those two columns leave when you put them against each other. What survives is the part one side has and the other does not, with the reason on the row.

Partial scope

What happens when the other company is outside the onboarded set?

It gets a name, a direction and a state of its own. A group onboards the entities it wants managed, so plenty of internal legs face a company whose ledger is not in the picture — and that is a boundary, not a break.

Intercompany reconciliation status · by state

GROUP

Open intercompany positions

EUR 43,611,400

Every movement counted once, never both of its legs.

Carried by both ledgers: EUR 39,281,000
Difference with a named cause: EUR 204,000
Counterpart outside the onboarded set: EUR 4,126,400

Outside the set · 2 counterparts

Corporation PatrimonialEUR 2,940,000UnmanagedOwed by an onboarded entity · Corporation España
Corporation ReEUR 1,186,400UnmanagedOwed to an onboarded entity · Corporation Servicios

UnexplainedEUR 0

A counterpart outside the set is not an exception queue and it is not a zero. It is a labeled leg with a company name on it, and it stays that way until somebody onboards that company — at which point the second entry arrives with it and the pair matches like any other.

What it will not do

It does not invent the other side. No estimate stands in for a ledger nobody gave us, no leg is quietly dropped to make a group figure look complete, and a total that covers part of the book says so on the surface where the reader cannot miss it.

What comes back

What comes back, and who reads it?

A position each entity’s controller can sign, and a group view that says what is agreed, what is named and what sits outside the scope.

A position for every counterpart pair, with both legs beside each other.: Each internal relationship the group carries, the amount each side booked, and the difference between them — open down to the document that produced it.
A netting proposal, before anything moves externally.: Where two companies hold positions against each other, one transfer settles both instead of two. The proposal names the movements inside it and the ones it leaves out, and nothing leaves an account until the approvals you require are in.
The evidence behind every pairing, and the pairings it rejected.: Each match keeps the signals that produced it and the alternatives that scored lower, with their scores, so a controller who disagrees can see exactly what was weighed and argue with it.
A state on every leg, including the ones with nothing to pair against.: Carried by both ledgers, a difference with a named cause, or a counterpart outside the onboarded set. There is no blank cell, no silent zero and no row that quietly leaves the total.

Who reads it

Where it hands off

Questions

What a controller asks before anything else

01What is intercompany reconciliation?: It is the matching of the two entries one movement inside a group produces: the receivable booked by the company that is owed, and the payable booked by the company that owes. Tresora reads both ledgers, pairs the entries on the movement itself, and reports what each side booked along with whatever is left between them.
02What happens if only some of our entities are onboarded?: The scope is stated and every leg respects it. Movements between onboarded entities are paired on both sides. A movement facing a company outside the scope keeps its own leg, its counterpart name and the state Unmanaged, so it is never counted as matched and never dropped from a total. Onboard that company later and the second entry arrives with it.
03Do both sides have to quote the same reference?: No. The pairing is on the movement — amount, direction, dates, counterpart and the settlement that carried it — and a shared reference counts as one signal among those rather than as the key. Where a reference does survive both postings, it makes the case stronger and nothing more.
04Can the balances be netted before we pay?: Yes. Where two of your companies hold positions against each other, Tresora proposes the single transfer that settles both and names every movement inside it. The netting happens before anything moves externally, and the transfer only leaves along the approval path you defined.
05What if the two sides book in different currencies?: Each side keeps the amount and the rate its own entry was booked at, and the pair is matched on the movement rather than on a translated figure. The group view shows both amounts, the rate behind each one and the day it applied, so the difference between them is a number your auditor can reproduce instead of one somebody has to explain.

Two of your entities, and every movement between them.

A working session on your own ledgers: two entities, one period, both legs matched in front of you — including the counterparts that sit outside whatever scope you pick.

Request a demo See the whole product

What it takes from you: a ledger extract from each of the two entities, and the statements for the accounts between them.