How a group finance function got visibility into an entity that had been quietly operating outside the consolidation

The group CFO was halfway through preparing the monthly consolidated accounts when a number in the subsidiary trial balance stopped making sense.

It was not a dramatic variance. Not the kind that sets off alarms immediately or causes a meeting to be summoned within the hour. It was smaller than that, which in some ways made it more unsettling. A local operating expense line looked slightly out of pattern. An intercompany balance had moved, but not in the way the group expected. The translation difference was manageable, but only if the underlying data was correct. And the more she looked at it, the clearer it became that the issue was not the number itself.

It was the fact that the number had arrived in a form she could not fully trust.

The subsidiary had been folded into the group years earlier, during a period of international expansion that had felt both strategic and urgent. The new entity gave the business local market presence, a regional team, and a base from which to grow. A local finance manager was appointed, systems were set up, and everyone assumed that the finance process would naturally align with group practice.

That assumption held for longer than anyone realised.

By the time the CFO questioned the trial balance, the subsidiary was no longer operating in the way the group believed it was. It had developed its own routines, its own system habits, and its own version of financial autonomy – most of it informal, some of it accidental, and all of it outside the visibility the group thought it had.

Growth had outpaced oversight

This was a business that had expanded internationally in the way many ambitious groups do: one market at a time, one entity at a time, one local hire at a time.

At group level, the finance function was disciplined. Processes were documented. Close calendars were followed. Reporting packs were reviewed. There were systems, controls, and a clear consolidation rhythm. But in the subsidiary, the practical reality had drifted.

The local team maintained its own accounts in a separate system. It was not malicious or careless. In fact, it had evolved in the opposite direction – as a response to operating needs, local preferences, and the natural tendency of smaller teams to solve problems quickly with whatever tools are available.

The issue was that those local solutions had never been brought back into a formal group framework.

The original expectation had been simple: the subsidiary would operate within the same financial structure as the rest of the group. In practice, that never fully happened. The local finance manager had been working responsibly, but independently. And because no one had ever completed a proper process review, the group did not know how far that independence extended.

The most dangerous words in a growing finance function are often not “we can’t do that.”

They are “we assumed it was already happening.”

The subsidiary had become its own accounting island

Once EcobSoft was brought in, the scale of the issue became clearer.

What the group had thought was a standard operating entity was, in practice, running with a significant degree of independence without NetSuite integration. The subsidiary’s ledger was maintained outside the group NetSuite environment. Month-end results were exported manually and shared as spreadsheets. Intercompany transactions were recorded inconsistently between entities. Expense approvals followed local practice rather than group policy. And there was no reliable system-level bridge between what the subsidiary recorded and what the group consolidated.

That meant the finance team at group level was not receiving clean source data.

It was receiving a version of the subsidiary’s numbers that had already been interpreted, adjusted, and reassembled by hand.

In a smaller business, that might be tolerated for a time. In a multi-entity group, it becomes a structural problem.

The group had grown to a point where the finance function needed consistency, not just effort. It needed transaction-level clarity, not spreadsheet confidence. And it needed a consolidation process that could stand up to scrutiny without depending on a local team member’s memory of which export tab contained the latest figures.

The subsidiary had not gone rogue. But it had gone its own way.

And for group finance, that made the difference very small and very serious indeed.

The consolidation process was carrying too much weight

The real issue was not simply that the subsidiary used a different system.

It was that the consolidation process had to compensate for it.

Every month, the group team was posting manual elimination entries for intercompany balances that should have matched but didn’t. Some differences arose because one entity recorded invoices before the other entity posted them. Timing differences caused others. Local transactions mapped to different account codes than those used by the group created additional discrepancies. Inconsistent application of currency translation at the source also resulted in differences.

The result was predictable, even if nobody had wanted to see it.

The finance team could produce the consolidated P&L, but it required substantial manual adjustments before they could audit it. Every month-end became a reconciliation exercise. Every reporting cycle depended on judgment, follow-up emails, and a series of spreadsheet-based bridging schedules that existed because the systems did not.

This was not just inefficient.

It was risky.

A consolidation process that depends on manual correction is not really a consolidation process. It is a recovery effort.

The group CFO understood that immediately. She also understood something else: if the subsidiary could drift this far from group visibility without anyone noticing, then the problem was bigger than one entity’s reporting mechanics.

It was a control issue.

EcobSoft was asked to map what the group thought it had to what actually existed

EcobSoft’s assessment began where most of these issues do: with a comparison between intent and reality.

The group had a control framework. It had policies for intercompany transactions, reporting deadlines, expense approvals, chart of accounts usage, and month-end submission requirements. But no one was enforcing those policies at the entity level in any meaningful way.

So EcobSoft reviewed the subsidiary’s actual process flow through NetSuite integration from the ground up.

That meant mapping how teams raised invoices, approved expenses, initiated intercompany activity, prepared local reports, and transferred the final numbers into consolidation. It also meant reviewing the subsidiary’s entity-level controls against the group’s expected control framework, and identifying where the two had drifted apart.

The findings were straightforward, but not minor.

The finance team did not reconcile intercompany balances before the month-end close. Local finance staff were exporting data based on timing rather than group reporting rules. The chart of accounts in the subsidiary bore only partial resemblance to the group structure, which made mapping and elimination more difficult than it should have been. The team had built the expense approval process around local convenience rather than group thresholds or delegated authority rules.

None of these things were necessarily wrong in isolation.

Together, they prevented the group from seeing the subsidiary until after someone had already reshaped the numbers.

That is not control. That is hindsight.

The remediation had to bring the entity back inside the system

The solution was not to impose more spreadsheets.

It was to bring the subsidiary into the same operational environment as the rest of the group.

EcobSoft’s remediation work focused on three things: system alignment, intercompany automation, and reporting consistency.

First, the subsidiary was brought into the same NetSuite environment as the parent group through NetSuite integration. That gave the business a shared ledger structure, a shared reporting logic, and a common basis for consolidation. The entity now operated within the same financial framework from the start instead of keeping local accounts in a separate system and translating them later.

Second, the team automated intercompany transactions and designed system rules to eliminate them at consolidation instead of relying on manual journal entries. This approach reduced the number of unexplained differences at month-end and gave both entities a clear view of the transactions recorded on each side.

Third, we enforced the group chart of accounts at the entity level. That meant the subsidiary’s coding had to follow the same structure as the rest of the group, which made reporting cleaner, analysis easier, and eliminations more reliable.

The reporting process changed as well. What had once been a spreadsheet exercise became a system output. Month-end data no longer required manual consolidation. The system produced consolidated figures from a common source of truth, and the finance team reviewed exceptions instead of reconstructing the entire picture each time.

That shift sounds technical, but its effect was operational.

The group stopped spending its time correcting the subsidiary and started seeing the subsidiary.

The first clean consolidation changed the tone of the close

The first fully automated group consolidation did not make the month-end close effortless, but it changed its character completely.

Instead of weeks of back-and-forth, the group completed consolidation in days through NetSuite integration. The team identified and investigated intercompany differences in real time, allowing them to resolve issues before close. They also applied translation adjustments consistently. Entity reporting followed the same chart of accounts. And for the first time, the group CFO could look across every entity and know that the numbers were coming from an integrated finance structure rather than a collection of local habits.

That visibility mattered more than the efficiency gain.

Because the real issue had never been simply that the consolidation took too long.

It was that the group had not had reliable visibility into one of its own entities.

Once the team fixed that, they stopped treating the subsidiary like a remote office with its own reporting personality and started running it as part of a single finance operation.

Which is what it should have been all along.

The lesson was bigger than one entity

In the months that followed, the group leadership began to talk differently about expansion.

The company still wanted growth. It still valued local autonomy where it made commercial sense. Finance structures were no longer treated as something to address after creating an entity. When they established a new subsidiary, they designed its systems, controls, reporting structures, and intercompany logic from day one.

That was the deeper value of the remediation.

It did not just fix a broken close. It changed how the group thought about international scale.

A subsidiary that sits outside your visibility is not a small administrative gap. It is an unmanaged risk with its own P&L, its own assumptions, and its own potential to distort the group picture. The larger the business grows, the more dangerous that gap becomes.

A finance team can only consolidate what it can truly see.

Closing thought

A subsidiary operating outside your visibility is not a remote office – it is an unmanaged risk with its own P&L. For groups that are growing across borders, the real challenge is not just building finance processes that work locally, but making sure they still belong to the same control environment globally. That is the kind of alignment EcobSoft helps finance teams build: not just cleaner reporting, but a structure that gives leadership confidence in every entity they own.