There is a moment in every group close that reveals how stable a finance organization really is. Not the moment when the numbers are done. The moment three weeks earlier, when group accounting reconciles the intercompany balances and finds they don’t match.
That moment determines whether a close is finished on time or not. Whether auditors review routinely or dive deep into the data. Whether management gets reliable numbers or numbers with a caveat.
What becomes visible in that moment is not a posting error. It is the state of governance in a finance organization. How clear responsibilities are. How well processes between entities are coordinated. How seriously intercompany reconciliations are taken as a control instrument, not just an administrative obligation.
This article is for CFOs who have recognized that intercompany reconciliations are not a technical problem that can be delegated to group accounting. They are a structural problem requiring leadership, governance, and consistent process design. And one that, if not addressed, has direct consequences for close quality, audit risk, and the reliability of the entire reporting.
What Intercompany Differences Really Signal
When a CFO hears that the intercompany reconciliation doesn’t match, the most common reaction is operational: Who clarifies it? By when? How big is the difference?
Those are the right questions for the acute moment. But they are the wrong questions for the structural problem behind it.
An intercompany difference signals more than a wrong booking. It signals that two units of the same group have recorded the same economic event differently. That means either the booking logic is not harmonized, communication between units is inadequate, responsibilities are unclear, or systems don’t talk to each other.
In a well-set-up group, intercompany differences should be the exception. They should be detected automatically, classified quickly, and resolved promptly. If differences are instead the rule, if they arise monthly anew, if their resolution takes weeks and they keep tracing back to the same root problems, then that is an unmistakable signal of structural weakness.
This structural weakness has a price. It manifests in extended close times, increased audit effort, loss of trust with auditors, and a group accounting team that spends a substantial part of its capacity solving problems instead of securing closes.
As a CFO, the decisive question is not: How do I clarify the current difference? The decisive question is: Why do these differences arise in the first place, and what must change structurally so they stop?
Why Intercompany Reconciliations Are Systematically Underestimated
There is a structural reason why intercompany reconciliations are chronically under-prioritized in many groups, and it does not lie in lacking expertise or missing resources.
The reason is that the consequences of bad intercompany processes become visible only with delay. The booking made wrong today produces the difference that has to be cleared next month. The clarification postponed today becomes the bottleneck at year-end three months from now. The audit finding arising today becomes visible in the next audit cycle.
This time lag means that the urgency needed to drive structural improvements never becomes strong enough. There is always something more urgent. The day-to-day competes with process improvement, and the day-to-day almost always wins.
There is also a perception problem. Intercompany reconciliations are bookkeeping-wise unspectacular. They produce no strategic discussions in the leadership circle. They appear in no KPI dashboard on the CFO’s desk. They are operational craft that happens in the background and only attracts attention when it doesn’t work.
But that very invisibility is the problem. What is not measured is not steered. What is not steered develops along the path of least resistance. And the path of least resistance in an overloaded finance department is: the immediate first, the structural later.
A CFO who treats intercompany reconciliations as a strategic topic and not as an operational side matter breaks this cycle. They make process quality measurable, set clear expectations, and ensure that the structural conditions for clean reconciliations are in place.
The Three Levels of the Problem
To improve intercompany reconciliations structurally, it must be understood at which level the problems lie. In practice there are three levels, each requiring different solutions.
Level 1: The Technical Problem
The first level is the most technical and at the same time the easiest to solve. It concerns whether systems and processes provide the necessary infrastructure to enable clean intercompany reconciliations.
Concrete symptoms at this level are:
Different ERP systems in different entities with no automated interfaces.
Booking logics that are not harmonized and therefore lead to structural differences.
Missing automation that forces manual work and thereby creates sources of error.
Currency logics that are not uniformly defined and regularly lead to valuation differences.
These problems are solvable through technical investments, system integration, and process harmonization. They require budget and project discipline, but they have clear solution paths.
Level 2: The Governance Problem
The second level is more complex and is often overlooked because it is less visible. It concerns whether the organizational conditions for clean intercompany reconciliations are in place.
Concrete symptoms at this level are:
Unclear responsibilities between group accounting and local entities.
Missing policy that defines binding standards for booking logic, valuation timing, and clarification processes.
Escalation paths that don’t function because no one has the authority to compel local entities to comply with standards.
Lack of consequences when deadlines aren’t met.
These problems cannot be fixed by technical solutions. They require governance decisions made at CFO level, because they touch on questions of authority, accountability, and consequences.
Level 3: The Culture Problem
The third level is the deepest and the hardest to address. It concerns the value placed on process quality and data integrity in the finance organization’s culture.
Concrete symptoms at this level are:
Local entities that view intercompany reconciliations as a burden rather than a shared responsibility.
Teams that don’t escalate differences because they want to avoid conflicts with other entities.
A culture in which speed comes before quality because the close has to be ready on time, regardless of how good the reconciliations are.
These problems require leadership. No technical solution, no policy, no process improvement can change a culture in which data quality is not taken seriously. That is a leadership task, and it begins with the CFO.
What Auditors See and What CFOs Should Know
Auditors have a privileged view of intercompany processes. They see not only the result, the reconciled balances in the year-end close. They see the process behind it:
How long the reconciliation took,
how many differences arose and how they were resolved,
whether documentation is traceable, and
whether the controls that exist on paper also work in practice.
What auditors regularly see in poorly set-up groups is the following:
Reconciliations performed only shortly before the close and under time pressure.
Differences not fully documented and whose resolution is not traceable.
Controls that formally exist but are not consistently applied.
And group accounting teams that are overloaded and have no time to truly check the quality of reconciliations.
What auditors conclude from this is an elevated risk assessment for the entire close.
They know that bad intercompany processes are an indicator of deeper structural weakness. They therefore increase their audit depth, ask more questions, and demand more documentation. That costs time, creates stress in the team, and increases audit costs.
A CFO who understands the auditor’s perspective knows that investments in clean intercompany processes have a direct return in reduced audit risks, lower audit costs, and a smoother close. That is no soft argument. That is an economic argument that should factor into every decision about process improvements.
The Most Common Structural Weaknesses in Practice
From work in various group mandates, the most common structural weaknesses leading to intercompany problems can be identified. They are in the majority of cases the same, regardless of industry, size, or ERP landscape.
Missing central intercompany policy
In many groups there is no binding policy defining how intercompany transactions are to be booked, valued, and reconciled. Each entity works at its own discretion, with its own interpretations and its own priorities. That creates structural differences that don’t stem from booking errors but from different yet individually correct applications of inconsistent standards.
The solution is a central intercompany policy binding for all entities. It defines
which transaction types exist,
how they are to be booked,
which valuation timings apply,
which currency logic is to be used, and
which deadlines for bookings and reconciliations are to be met.
This policy must be mandated by the CFO, not recommended by group accounting.
Unclear ownership between group and local
A classic problem is the unclarity about who is responsible for resolving differences. Is it the initiating entity? The counterparty? Group accounting? In many groups this is not explicitly regulated, and the consequence is that each side waits until the other acts.
The solution is a clear ownership structure that defines, for every step in the intercompany process, who carries responsibility. Transaction Owner, Reconciliation Owner, Reviewer. These roles must be filled by name, not generically assigned to a function.
Abstraction at the level of group accounting
In many groups, group accounting is too far removed from the operational booking processes in the entities. It receives the balances, sees the differences, but cannot judge the causes because it has no insight into local booking logic.
The solution is a stronger interlocking between group and local accounting, not in the sense of centralization but in the sense of transparency. Group accounting must have access to the relevant booking details to judge and prioritize differences.
Intercompany as a year-end topic
In an alarming number of groups, intercompany balances are not systematically reconciled throughout the year. Only at year-end is the attempt made to clarify months of accumulated differences. That creates time pressure, leads to superficial resolutions, and increases the risk that material differences remain in the close.
The solution is monthly intercompany reconciliation as a fixed component of the close process. What is reconciled monthly does not accumulate into year-end problems.
Missing escalation structure
When an entity does not deliver the intercompany reconciliation on time or does not resolve differences, in many groups there is no defined escalation path.
Group accounting reminds, urges, requests. But without a formal escalation path that lands at CFO level, there is no real pressure.
The solution is an escalation structure that explicitly defines from which point a situation is escalated to which level. That requires the CFO’s willingness to also receive escalations and respond to them.
What a Functioning Intercompany Governance Model Delivers
A good model is not complex. It is consistent. That applies to intercompany governance just as to any other form of governance in the finance organization.
The basic structure of a functioning model comprises four elements that must work together.
A binding policy with clear standards
This policy defines not only what is to be done but also what is not acceptable. It establishes which deviations are tolerable and which are not, which cases must be automatically escalated, and which consequences non-compliance has.
A clear ownership structure
For every entity, every transaction type, and every step in the process there is a named accountable person. These people know what is expected of them, by when, and in what format.
A regular governance rhythm
Monthly reconciliations, weekly status calls in the close phase, and a biweekly overview of open differences outside the close phase. This rhythm must be constant, not situational.
An escalation path that works.
That means an escalation path that actually reaches CFO level, and a CFO willing to receive these escalations and make binding decisions.
The Technical Dimension: Systems as Enablers, Not as Solutions
A warning that must be voiced in this context: technology does not solve governance problems. It can make well-functioning processes more efficient. It cannot replace bad processes.
Many groups have invested in specialized reconciliation tools:
BlackLine,
OneStream,
Cadency,
SAP Group Reporting
and the hoped-for improvements have failed to materialize.
Not because the tools are bad, but because the conditions for their effective use were not in place.
Missing policy, unclear ownership, lacking process discipline: these problems are not solved by a new tool. On the contrary, a new tool in an unregulated process often creates more complexity, not less.
The right order is: governance first, technology second.
That means: before investing in automation, processes must be defined, the ownership structure clarified, and the policy established. Only then can technology scale, accelerate, and secure these processes.
When this order is followed, technology unfolds its full impact.
Automatic matching of transactions reduces manual work dramatically. Real-time dashboards make the status of reconciliations transparent for all participants. Automatic escalations ensure that problems do not lie unnoticed. And audit-proof audit trails document every step of the process for auditors.
The decision for a specific tool is less critical than often assumed. Whether SAP ICR, BlackLine, or OneStream is the better choice depends on the ERP landscape, group structure, and budget. What matters is that the tool fits the processes, not the other way around.
What an Interim Manager Can Achieve in This Situation
There are situations in which the structural problems of intercompany reconciliation are so deeply rooted that internal resources alone are not enough to solve them. That happens when the problems have grown over years and no one has a complete overview anymore.
When the internal teams are so deep in operational work that no capacity remains for structural improvements. Or when the changes that are necessary are so far-reaching that they require someone who can act without internal conflicts of interest.
In these situations, an experienced interim manager with group accounting experience can play a decisive role. Not as a bookkeeper resolving differences, but as a structure-setter who builds the governance, harmonizes the processes, and creates the conditions that enable clean intercompany reconciliation in the long term.
What an interim manager concretely delivers in this context: They analyze the current situation without the operational blindness that internal teams develop after years in the same structure. They identify the structural causes of the problems, not just the symptoms. They develop a policy and governance structure that fits the specific requirements of the group. They accompany implementation and ensure that the new processes actually work. And they hand over a documented structure that remains stable even after their departure.
That is interim management as it is effective: not as extended personnel resource, but as catalyst for structural improvements.
What a CFO Should Concretely Do
If a CFO has read this article and recognizes the described structural weaknesses, the question arises what to concretely do. Not someday, but now.
The first step is an honest stocktaking. How many intercompany differences arise monthly? How long does their resolution take on average? How much capacity of group accounting is spent on intercompany clarifications? How many intercompany findings were there in the last audit? These numbers exist in every organization; they are just rarely systematically collected and presented to the CFO.
The second step is identifying the structural causes. Do the problems lie at the technical level, the governance level, or the cultural level? This question must be answered honestly because it determines which solution approaches are sensible.
The third step is the decision which structural changes are necessary and what priority they have. A central policy, a clearer ownership structure, an escalation mechanism, a technical upgrade. These decisions must be made and communicated by the CFO.
The fourth step is consistent implementation. Structural improvements in the finance organization rarely fail at the conception stage. They fail at implementation, because the day-to-day always seems more urgent than the structural improvement. The CFO must ensure that implementation has priority and that there is someone who carries responsibility for it.
What a Well-Functioning Intercompany Reconciliation Is Concretely Worth
In the end, the question a CFO should ask is not operational but strategic: What is a well-functioning intercompany reconciliation worth?
The answer is more concrete than one might think.
Every working day saved in group accounting because differences are detected automatically and resolved quickly is a working day that can be used for value-adding activities. With a team of ten people and a saving of two days per month per person, that’s twenty working days per month, almost a full-time position, freed up for more strategic tasks.
Every hour saved in audit preparation because intercompany balances are cleanly documented and fully reconciled is direct cost savings. Every audit finding avoided reduces the audit risk and thereby the audit effort in future cycles.
And the trust of management in the reliability of financial data built up by clean intercompany processes has a value that cannot be expressed in single numbers, but that is felt in every strategic decision made on the basis of this data.
What I Bring
I am Nicole Vekonj, interim manager for finance & controlling. I accompany groups in structurally improving intercompany processes: from analyzing the current situation through developing a central policy and governance structure to technical implementation and sustainable anchoring in the organization.
My approach does not begin with a tool recommendation. It begins with the question of why the problems arise and what must change structurally so they stop.
You are facing a year-end close and your intercompany reconciliations worry you? Or you know that the processes are not as they should be, but the day-to-day leaves no time for structural improvements?
Let’s talk for 30 minutes.
Nicole Vekonj | Interim Manager Finance & Controlling | zahlenkompetenz.de
