How a professional services business fixed a recognition problem before it became a restatement

The CFO had been through enough fundraising cycles to know that the room changes the moment investors ask for a quality of earnings review.

Not visibly, not at first. The smiles stay in place. The conversation stays polite. The deck still looks good. But the air shifts. Every number on the screen starts carrying a second meaning. Every line item becomes a question waiting to happen. And in that particular week, with diligence underway and the next round of capital sitting just beyond the horizon, the finance team found itself facing one of the most uncomfortable discoveries a business can make:

The revenue had been recognised too early.

Not fraudulently. Not with intent to mislead. But in a way that would not survive scrutiny.

The warning came quietly, as these things often do. A new investor’s accounting team was working through the books and asking for support behind the revenue pattern. They wanted to understand what had been delivered, when it had been delivered, and how the company had decided that delivery had occurred. The answers were technically plausible, but not convincing enough.

Invoices had been issued on milestone dates. Revenue had been booked on invoice dates. And for years, that had simply been the way the business ran.

No one had formally challenged it.

No one had stopped to ask whether invoicing and performance were actually the same thing.

And once that question was asked, the whole structure began to look a little less stable.

 

A business built on projects, pace, and trust

The business itself was not unusual. It was a professional services company built around project-based delivery. Engagements were scoped, milestones were defined, invoices were sent along the way, and clients paid as those milestones were hit. The commercial model was clean enough on paper: sell a project, deliver the work, recognise the revenue.

But in practice, the accounting process had drifted into something simpler and more convenient. If a milestone invoice went out, revenue followed. If billing happened in a month, so did recognition. The logic had become embedded in operations, and because the system had no stronger guardrails, the practice repeated itself month after month until it started to feel like policy.

That is one of the most dangerous phrases in finance: “That’s just how we’ve always done it.”

Because “always” is not a control.

In this case, the gap between invoice issuance and actual delivery was small enough that nobody noticed the mismatch in the early days. Projects were moving quickly. Client approvals were coming through. Delivery teams were busy enough that finance rarely had to wait long for completion signals. The numbers looked reasonable. The monthly close moved on. The business kept growing.

Growth has a way of hiding small accounting problems.

When a company expands, one period’s overstatement is often followed by another period that partially offsets it. New work starts, old work finishes, invoices catch up, and the timing differences blur together in the aggregate. The error does not disappear. It compounds quietly. It shifts from being a mistake in one period to becoming a pattern across many periods.

And the more successful the business appears, the less likely anyone is to ask whether the recognition logic is actually correct.

Until diligence starts.

 

The problem had been invisible because the company was moving forward

The strangest part of early revenue recognition issues is how normal they can look from the inside.

The finance team had not been ignoring the issue. They had simply been operating with a set of assumptions that had never been stress-tested. Projects were billed in steps. Invoice dates were easy to capture. Delivery evidence lived in emails, project trackers, and team updates rather than in a clean accounting workflow. In a fast-moving environment, timing differences became background noise.

And because each period followed another period, the mismatch was always partially masked by the next cycle.

That is what makes the problem so insidious. It does not arrive as a single dramatic error. It arrives as a series of small decisions that appear harmless on their own. A milestone invoice goes out a little before a deliverable is formally signed off. A project manager confirms progress verbally. Finance books revenue because the bill went out and the client has not objected. No crisis. No red flag. Just gradual drift.

Then one day, someone asks for the evidence.

The quality of earnings review was that moment.

The investors were not just checking whether the numbers added up. They were checking whether the numbers meant what the company said they meant. That is a far more uncomfortable test. Because a revenue line can be mathematically correct and still be economically wrong. It can balance and still mislead. It can be audit-ready in appearance and still fail the question of whether performance actually occurred.

And when the diligence team started pulling on that thread, the finance team saw the risk clearly for the first time.

It was not just an accounting correction.

It could become a misrepresentation in prior financial statements.

The business had also used those financial statements to demonstrate debt covenant compliance, so the implications extended beyond revenue policy. Even a temporary revenue overstatement might have made the business appear more compliant, more profitable, or more stable than it actually was during those periods.

That is the kind of issue that can derail a fundraise, unsettle a lender, or force a painful restatement.

The CFO knew they had to move quickly.

 

EcobSoft was brought in before the issue became a larger story

Several earlier EcobSoft engagements revealed the same pattern: the business had outgrown its finance process, and the system had quietly become part of the problem.

EcobSoft assessed what had happened, determined how deep the mismatch ran, and built a path to fix it before it became a headline inside the transaction.

The first step was not technical. It was interpretive.

EcobSoft started by reviewing the company’s revenue recognition policy against the actual contract terms. The question was simple, but the answer mattered: what did the contracts really promise, and when did the company actually deliver the performance?

That meant looking at milestone definitions, acceptance criteria, project closeout practices, client sign-off language, and the real operational sequence behind each invoice. In many companies, the written policy and the real business process tell two different stories. Here, the policy described revenue recognition based on completed performance. However, the company had configured the system around billing timing.

That gap was the heart of the problem.

The company was not lacking intent. It was lacking alignment, which required NetSuite customization.

And that alignment had to exist not just in a policy document, but inside the accounting system itself.

 

The gap between policy and system configuration

One of the most common reasons revenue issues persist is that the accounting policy is technically correct while the system continues to support an outdated shortcut, making NetSuite customization necessary.

The finance team may know the right treatment. The auditors may have noted it in a prior cycle. But if the ERP still recognises revenue from invoice events, the operational behavior will keep winning.

That was the case here.

EcobSoft mapped the revenue recognition logic into NetSuite through NetSuite customization and compared it against how project records, milestones, and billing events were actually flowing.

The system could not distinguish between billing progress and performance completion. It assumed they were the same, which they were not.

That distinction mattered across the full life of each project.

Some milestones represented true completion points. Others represented deposit or billing events that had no direct relationship to delivery. In some cases, the team had delivered only part of the work but had already invoiced the full milestone amount. In others, the company recognised revenue before the client accepted the work or before the formal completion date, even though delivery was essentially complete.

The accounting treatment needed to follow the substance of the work, not the timing of the invoice.

So EcobSoft’s role became twofold: first, to translate the contract reality into a clear recognition framework; and second, to rebuild the system logic so the business could apply that framework consistently, month after month.

 

Remediation had to be both accounting-led and system-led

This was not the kind of issue solved by a memo.

A memo can explain the right answer. It cannot enforce it.

EcobSoft reconfigured the project accounting structure in NetSuite through NetSuite customization so revenue recognition would be tied to performance rather than billing. Milestone completion became the trigger only when the milestone truly represented delivery. The finance team could no longer rely on invoice timing as a proxy for earned revenue.

Deferred revenue schedules were automated to hold amounts that had been billed but not yet earned. That created a clean bridge between cash collection and actual performance. Instead of revenue being pulled forward by invoicing, it was released into the income statement only when the delivery evidence supported it.

For longer engagements, the company also needed percentage completion tracking at the engagement level. That was essential because not every project fit neatly into a binary complete/incomplete model. Work advanced in stages. Deliverables often overlapped. Certain milestones reflected partial completion and partial billing. Percentage completion allowed the finance team to measure progress more accurately and avoid the extremes of either over-recognition or unnecessary deferral.

Equally important was the operational workflow around approvals. Project managers needed a defined process to confirm completion. Finance needed evidence, not assumptions. The system had to capture status consistently enough through NetSuite customization that recognition became repeatable, reviewable, and defensible.

This was the real shift: from a revenue process built on convenience to one built on control.

The hard part was not the adjustment. It was the honesty

The most difficult conversations in revenue remediation are rarely technical.

They are reputational.

Once the finance team understood the issue, they decided how much to adjust, how to explain the historical impact, and how to communicate the fix without weakening the fundraise. That decision required discipline and a certain level of courage because acknowledging that they had recognised revenue too early could feel like admitting that the business had gotten the basics wrong.

But the truth is more valuable than the appearance of certainty.

The company chose to address the issue before it became a forced correction. That decision mattered. It meant the team could control the narrative, investigate the periods affected, and present the solution as a sign of governance maturity rather than as a late-stage cleanup.

Investors do not expect perfection. They do expect transparency.

By confronting the issue early, the business showed that it understood the difference between a finance function that merely closes the books and a finance function that can actually stand behind them.

The fundraise stayed on track

Once the team implemented the system changes and aligned the revenue policy with real contract performance, the fundraise moved forward.

That was not because the problem had been trivial. It was because the business had shown it could respond appropriately to a serious issue.

The quality of earnings review no longer pointed to an uncontrolled revenue process. The finance team had a documented policy, a system that matched that policy, and a process for proving recognition with evidence. Deferred revenue was visible. Project completion logic was auditable. Management explained, line by line, why it recognised revenue when it did.

That changed the conversation.

The CFO defended a number grounded in substance instead of a number that merely looked convenient. That is a very different kind of confidence. And in fundraising, confidence is not just emotional. It is structural.

The business reassured investors not because it had never had a problem, but because it found the problem before they did.

That distinction protected the transaction. It also protected the company’s credibility.

A finance function that could stand up to scrutiny

What the business gained was larger than a corrected revenue schedule.

It gained a finance process that could survive scrutiny from multiple directions: investors, lenders, auditors, and internal leadership. Along with that came consistency between contract reality and accounting logic, a cleaner month-end close, and better visibility into project economics. And perhaps most importantly, it gained the ability to say, with confidence, that reported revenue represented delivered value rather than premature optimism.

That is the real outcome of good remediation work.

Compliance built trust.

Not just accuracy, but durability.

Not just a cleaner set of numbers, but a stronger operating rhythm behind them.

The company’s finance team no longer had to hope that the revenue line would withstand questions. They knew how they built it, what supported it, and how delayed milestones, partially completed projects, or pending client acceptance would affect the outcome. And because the system now reflected those realities, the business could scale without rebuilding the same correction every quarter.

Closing thought

Revenue recognised too early isn’t revenue.

It borrows confidence.

Borrowed confidence always demands repayment.

The business learned that lesson before the repayment became public, before the issue turned into a restatement, and before a temporary accounting habit became a permanent credibility problem. By acting early, it transformed a hidden timing mismatch into a stronger control environment, a better ERP configuration, and a finance function that could defend its numbers at any level of scrutiny.

That, in the end, is what good NetSuite customization looks like. Just precise enough to keep trust intact.EcobSoft often works with teams at this exact intersection of process, controls, and system behaviour – where the goal is not simply to patch an issue, but to make the next one less likely.