How a scaling business stopped arriving at board meetings with numbers that were already history

On day nineteen of the following month, the finance team sent out the management accounts.

A department head read the pack, paused for a moment, and replied with a question that said more than it seemed to: were the figures final? She had already made a resourcing decision based on her own estimate of how the month had gone, because by the time the numbers arrived, the business had already moved on.

That was the problem in miniature.

The finance team was working hard, the reports were technically accurate, and the monthly cycle was being completed. But what the business was receiving was not timely enough to shape decisions while they still mattered. By the time the numbers reached the board, they were already describing a month that had effectively passed into history.

For a scaling business, that is a dangerous place to be.

 

The close had grown into a manual chain

The month-end close had originally been designed for a much smaller, simpler entity.

At that stage, the process was manageable because the volume was low, the transactions were familiar, and a few manual steps could be absorbed without much disruption. But as the business grew, the same process became a sequential chain of dependencies. One task waited on another. Every step depended on someone else finishing their part. And none of it had been automated in a way that allowed the close to move at the speed the business now required.

Just as importantly, no one owned the close in a way that created accountability for timing.

The result was predictable.

What had once been a practical operating rhythm became a bottleneck. Finance was not just closing the books. It was chasing inputs, correcting late data, and assembling a month-end picture from fragments that arrived at different times and in different formats.

The process had not broken suddenly.

It had simply never been rebuilt for the business it had become.

 

 The mechanics of delay were hiding in plain sight

When EcobSoft reviewed the close process, it found that a collection of small, familiar manual tasks consumed time and compounded delays at every subsequent step.

The finance team posted payroll journals manually after the payroll provider confirmed the final numbers. Accruals were built from email requests instead of system data. Intercompany recharges were calculated in spreadsheets and posted manually. Depreciation was also run by hand each month, despite the fixed asset data already existing in the system.

Individually, each task looked like something a finance team could live with.

Together, they explained why the close was taking so long.

The finance team was spending a large part of the month doing work that was administrative rather than analytical. They were gathering, checking, posting, reconciling, and reworking. The effort was visible, but the value was not always moving in the same direction.

And because so much of the process was manual, there was very little room for the team to recover time once the close had slipped.

 

 Nineteen days meant decisions were being made without current numbers

The most serious cost of the delayed close was not the delay itself. It was what the delay forced the rest of the business to do in the meantime.

While finance was still trying to close the previous month, budget holders were making decisions in the current one based on estimates. Managers were guessing their own positions. Commercial teams were moving ahead without a formal financial reference point. The CFO understood the business’s position, but she could not defend its financial figures until the third week had passed.

That kind of lag changes behaviour.

When reliable numbers arrive too late, leaders begin to create their own versions of the truth. They do not necessarily do it because they distrust finance. They do it because they need to act, and the finance function has not yet given them the information they need to act well.

That is how a slow close becomes a leadership problem.

Not because the finance team is failing, but because the business begins making decisions in the absence of a proper financial anchor.

 

 The hidden cost was time finance could never get back

There was another problem too, one that is often less obvious because it hides inside the routine.

The finance team was spending the first three weeks of every month closing the one before it. That left less than a week for actual forward-looking work: analysis, commercial support, forecasting, and the kind of financial judgment that justifies having a finance team in the first place.

This is where slow close processes become strategically expensive.

A finance function that spends most of its time assembling the past has very little time left to influence the future. The people in the team may be highly capable, but low-value repetition consumes their capacity. And over time, that changes the perception of finance inside the business.

Instead of being a partner to decision-making, finance starts to look like the department that confirms what everyone already guessed.

This business did not want that kind of function.

 

 EcobSoft mapped the close step by step

EcobSoft’s assessment began with process mapping.

Each close task was documented, timed, and traced to the dependency that caused it to start, stop, or stall. That made it possible to separate tasks that were genuinely slow because of system gaps from tasks that were slow because of the way the process itself had been designed. In particular, the review looked at where NetSuite was being used effectively, where data was still being handled outside the system, and where better NetSuite integration could remove unnecessary manual effort from the close.

That distinction mattered.

Automation and tighter NetSuite integration solved some issues. Process owners addressed others. In some cases, teams completed work later than necessary because no one set hard deadlines or made timelines visible across the wider team.

Once we mapped the close properly, the pattern became clear. The delay was not one issue. It was a system of delay.

We can redesign systems of delay.

 

The remediation focused on automation, timing, and ownership

The remediation work was practical and focused.

The finance team automated and scheduled recurring journal entries so they no longer prepared them manually each month. They used open purchase orders and contract data to generate accruals instead of relying on email requests, allowing finance to work from source information rather than chase updates. They ran fixed asset depreciation as a system process instead of a manual task. Improved NetSuite integration automatically calculated and posted intercompany recharges at period end.

Just as importantly, we rebuilt the close calendar around task ownership.

Every step had a clear owner. Every deadline was visible to the team. The close sequencing allowed tasks to run in parallel wherever possible instead of waiting on one another unnecessarily.

That may sound like an operational detail, but it changed the rhythm of the entire finance function.

The goal was not simply to make people work faster.

It was to stop asking them to do the same things by hand every month when the system could do them once and do them consistently.

 

The close moved from a three-week event to a first-week discipline

The effect was immediate.

The close reduced from nineteen days to six. The finance team distributed management accounts in the first week of the following month. The finance team no longer spent the opening phase of each month assembling reports. Instead, it had time to review results, explain movements, and support decisions while they were still live, supported by stronger NetSuite integration across the close process.

That changed the quality of conversation across the business.

Budget holders were no longer estimating their own positions in the dark. The CFO had a number she could defend much earlier. And the finance team was finally able to redirect its energy toward analysis, business partnering, and the work that required judgment rather than repetition.

In other words, the team stopped spending its month explaining the past and started helping shape what came next.

A finance function does that.

 

The lesson was not just about speed

A three-week close is not just a timing issue. It is often a sign that the finance function has become trapped in a cycle where it is optimising effort rather than output. Everyone works hard, completes the close, and delivers the reports, but the business pays a hidden price for every day that slips.

The real problem is that slowness in the close rarely stays confined to finance. It spills into management behaviour. When the numbers are not ready, managers begin creating their own versions of performance. Leaders begin deferring decisions, relying on estimates, and acting on incomplete information, while the business operates with a level of commercial blindness that becomes more dangerous as it grows.

That was exactly the pattern here. The delay in reporting had not only stretched the close process; it had also weakened the rhythm of decision-making across the organisation. Leaders were relying on estimates. Budget holders were building their own assumptions. The board was receiving information that described a period after the business had already moved on from it. And because the gap repeated every month, people began to treat it as normal.

That is how an inefficient close becomes part of the culture.

It also changes the role of finance in subtle ways. When the month-end process takes too long, the team spends most of its energy gathering and correcting data instead of interpreting it. The finance function becomes known for producing reports rather than informing decisions. Teams compress analysis, push back forecasting, and spend valuable time on reconciliation, review, and rework instead of partnering with the business.

In this case, the issue was especially clear because the underlying data already existed in the systems. Payroll information, fixed asset records, purchase orders, and intercompany activity were all there in some form. But the team had not designed the process around them to use that data efficiently. Instead, the team was still relying on manual extraction, email-based requests, spreadsheet calculations, and late-stage journal entries that turned a routine close into a long assembly exercise.

So the lesson was not simply that the close needed to be faster.

It was that the business needed a finance process that matched the speed and complexity of the organisation it had become. That meant reducing manual dependence, tightening ownership, and using the systems already in place – including NetSuite – in a way that supported timely, repeatable reporting instead of delaying it through effective NetSuite integration.

Once that shift happened, the close was no longer just a monthly administrative burden. It became a source of current financial truth.

And that is a much more valuable role for finance to play.

 

Closing thought

A close process that takes three weeks is not just slow – it means your business is always making decisions about the future using information about the past that hasn’t arrived yet. For scaling businesses, the real opportunity is not only to close faster, but to build a finance rhythm that gives leadership a timely view they can actually use. That is the kind of improvement EcobSoft helps teams make through practical, system-led changes – including stronger NetSuite integration – that reduce the drag of manual close work and give finance back its time for analysis, support, and control.