The board meeting was in forty-eight hours.

Marcus, the CFO of a mid-sized professional services firm, had five entities, four accountants, three different file-naming conventions, and two conflicting consolidated P&Ls sitting open on his screen.

He didn’t know which one was right. Neither did anyone else.

“We spent the first twenty minutes of every board meeting explaining why the numbers were different from last month,” Marcus said. “Not what the numbers meant. Why they were different. That’s not a finance function. That’s damage control.”

Five Entities. Five Sets of Books. No Single Source of Anything

The firm had grown through a combination of organic expansion and two small acquisitions over six years, and leadership had begun exploring a future netsuite implementation to handle increasing complexity. The netsuite implementation was becoming a serious consideration because what started as a single consulting practice had become a group of five operating entities – different service lines, different geographies, two with minority partners, one with a different fiscal year-end.

Each entity had its own QuickBooks file. Each had its own chart of accounts, built independently, at different times, by different people. The naming conventions didn’t match. The account structures didn’t align. What one entity called “Contract Labor” another called “Subcontractor Fees” and a third called “External Resources,” further reinforcing the need for a netsuite implementation to standardize and centralize reporting.

Every month-end, the consolidation process started from scratch. Each entity’s accountant exported their financials into Excel. A senior accountant spent two to three days manually mapping accounts across entities, eliminating intercompany transactions, and building a consolidated view in a master spreadsheet, all work that a netsuite implementation could eventually automate.

The intercompany eliminations were the worst part. The firm had significant intercompany activity – shared services billed between entities, staff allocated across projects, management fees charged by the parent. Every one of those transactions had to be identified, matched, and removed from the consolidated view manually.

When one entity recorded a transaction slightly differently than the other, it created a mismatch. Mismatches had to be investigated. Investigations took time. Time the finance team didn’t have in the last three days of every close cycle.

The team consistently delivered consolidated reports late, carried a margin of uncertainty in every version, and added verbal disclaimers during presentations – key reasons the CFO strongly advocated for a NetSuite implementation.

The High Cost of “Excel-Based” Governance

For Marcus, the issue wasn’t just the manual labor; it was the erosion of trust. When a CFO has to lead with a disclaimer, the board stops looking at growth opportunities and starts looking for errors. In a multi-entity environment, “Excel-based” governance creates a glass ceiling. You can only grow as fast as your spreadsheets can be updated.

Manual consolidation often hides “zombie” data – entries that exist in one ledger but never made it to the other side of an intercompany loan. For this firm, the lack of a unified system meant that intercompany debt was growing silently, untracked by the parent company’s primary oversight. This isn’t just an accounting headache; it’s a massive risk for audits, tax compliance, and valuation.

The Acquisition That Made It Impossible to Ignore

The firm had been managing the complexity for years – not well, but well enough to keep moving. That changed when they acquired a fourth operating entity and inherited a completely different accounting system, a different chart of accounts, and an eighteen-month backlog of intercompany transactions that had never been properly reconciled.

The integration took four months. During that time, the monthly close stretched from ten days to eighteen. The board asked for a reforecast mid-year. It took three weeks to produce.

That was the moment Marcus decided the current approach had no future.

“Expansion was off the table. New markets were paused. Every growth decision had to wait until the financial foundation was finally fixed.”

He brought in EcobSoft.

The Assessment: Complexity That Had Been Normalised

The first thing EcobSoft did was map every financial process across every entity – how transactions were recorded, how the month-end close worked, how intercompany activity was tracked, and how the consolidation was produced.

What they found wasn’t unusual for a firm that had grown without a unified financial infrastructure. But it was extensive.

There were eleven different account names being used across entities to describe the same type of expense. Intercompany loans between two entities had been tracked in a side spreadsheet for two years and had never been formally reconciled. One entity was recognizing project revenue on a completed-contract basis while another was using percentage-of-completion – both valid methods, but inconsistently applied across the group without disclosure.

None of it was fraud. None of it was negligence. It was the natural accumulation of five teams doing their best work inside systems that were never designed to talk to each other.

The fix wasn’t going to come from better spreadsheets. It required a single platform.

One Chart of Accounts. One System. Every Entity

The NetSuite implementation was built around the multi-entity architecture at the core of the platform – NetSuite’s ability to run multiple legal entities inside a single instance, with a shared chart of accounts, consolidated reporting, and automated intercompany eliminations.

The first task was the chart of accounts. EcobSoft worked with Marcus and the entity controllers to build a unified account structure that worked for every entity – specific enough to capture the nuances of each business, standardised enough to roll up cleanly into a group view. Every legacy account was mapped to the new structure. Every naming inconsistency was resolved before a single transaction was migrated.

Each entity was set up as a subsidiary within a single NetSuite instance. Entity-level reporting remained fully intact – each controller could work within their entity exactly as before. But every transaction posted at the entity level was immediately visible at the group level, without any manual export or consolidation step.

Leveraging NetSuite for Global Visibility

By utilizing NetSuite, EcobSoft enabled the firm to handle different tax jurisdictions and reporting requirements seamlessly. For the entities operating in different geographies, NetSuite automatically handled the local compliance while simultaneously rolling up the data into the headquarters’ functional currency. This removed the “manual translation” risk that previously plagued their international service lines.

Intercompany transactions were configured as a managed process inside NetSuite. When one entity billed another for shared services, NetSuite recorded the receivable on one side and the payable on the other simultaneously. At month-end, those transactions were eliminated automatically in the consolidated view. The manual matching process – the one that had been consuming two to three days of a senior accountant’s time every month – was gone.

The team configured currency consolidation for the two entities operating in different currencies, while NetSuite automatically handled exchange rate adjustments and posted translation differences to the correct equity account in the consolidated balance sheet.

The team standardized revenue recognition across the group. They configured project accounting using NetSuite’s native project module, applied a consistent recognition methodology across all service entities, and documented it for audit purposes.

The team set up live consolidated P&L, balance sheet, and cash flow reports that pulled real-time data from all entities simultaneously while automatically applying intercompany eliminations.

The First Clean Close

The first month-end close after go-live took six days.

Not eighteen. Not ten. Six.

The consolidated financials were ready before the deadline, without a single manual mapping exercise. The intercompany eliminations balanced automatically. The board package was prepared in an afternoon.

Marcus sent the report to the board twenty-four hours early – something that had never happened before.

“The board didn’t say anything about it at first,” he recalled. “Then one of them said – wait, these are the final numbers? And I said yes. And he said, since when?”

The answer was: since they stopped managing five separate ledgers and started running one system.

What the Manual Consolidation Was Really Costing

The cost of the old process was easy to underestimate because most of it was invisible.

The problem showed up in close cycles that ran nearly three weeks and left the finance team exhausted before the reporting cycle even started. It also appeared in board conversations that spent more time on methodology than on performance. The same issue surfaced in the acquisition integration that took four months instead of four weeks and in the reforecast that took three weeks to produce and arrived too late to be fully useful.

A subtler problem emerged too: teams avoided decisions because they didn’t trust the data, ignored opportunities because nobody wanted to open another spreadsheet, and deferred strategic conversations because the foundation wasn’t solid enough to build on.

A manual consolidation process doesn’t just slow down reporting. It slows down the entire business.

The Foundation That Scales

The firm has since completed another acquisition. The integration took three weeks. The team set up the new entity inside the existing NetSuite instance, mapped it to the unified chart of accounts, and produced consolidated financials within the first month of operation.

“The first acquisition almost broke us,” Marcus said. “The second one was unremarkable. That’s exactly how it should be.”

Multi-entity complexity doesn’t have to mean multi-version confusion. With the right infrastructure, every entity runs independently and reports collectively – in real time, without the manual layer in between.

If your monthly close still involves a consolidation spreadsheet and a two-day reconciliation process, the problem isn’t your people. It’s the architecture.EcobSoft helps multi-entity firms build financial infrastructure that consolidates automatically and scales without friction. Let’s talk.