Example: Passing an Audit-Readiness Review Without a Restatement
A B2B healthcare software vendor preparing for a pre-IPO audit had two years of close processes that would not have survived outside scrutiny. Rebuilding the revenue recognition process ahead of the audit avoided a restatement that would have delayed the company's IPO timeline.
The company sells implementation and subscription software to hospital systems and outpatient clinics under multi-year contracts that bundle services and subscription components, and its finance team had been recognizing that revenue on a simplified straight-line basis for two years. An early scoping conversation with the company's incoming audit firm made clear that revenue recognition under the actual applicable accounting standard would look materially different once services and subscription revenue were properly separated and recognized on their own distinct schedules, a difference large enough to require a multi-quarter restatement if left uncorrected before the audit began.
The revenue recognition policy was rebuilt from the ground up, going contract by contract to separate implementation services from subscription revenue and recalculating two full years of historical revenue under the corrected methodology before the audit firm's first day of fieldwork. The monthly close checklist and account reconciliation process were also redesigned to hold up under a genuine audit trail rather than the internal review standard that had missed the issue in the first place.
Audit-readiness review completed with zero material findings and no restatement required, keeping the company's IPO-track timeline intact
An accounting policy that has quietly been wrong for two years rarely announces itself. It usually takes one specific question from an outside party who has no reason to assume the existing approach is correct.
Background
The company sells implementation and subscription software to hospital systems and outpatient clinics, a customer base that tends to sign multi-year contracts bundling an upfront implementation services engagement with an ongoing subscription fee. For two years, the finance team, which had grown from one person to a small team over that period without ever fully revisiting its founding-era accounting choices, had recognized that combined revenue on a simplified straight-line basis across the life of each contract. It was a reasonable shortcut for a small team focused on cash and growth. It was not a shortcut built to survive a real audit.
The conversation that changed the timeline
An early scoping conversation with the company’s incoming audit firm, standard practice ahead of any IPO-track engagement, made the gap explicit almost immediately: recognizing the services and subscription components separately, as the applicable accounting standard actually requires, would produce materially different revenue figures for prior periods, potentially shifting several quarters of recognized revenue by a meaningful percentage. Left uncorrected, that gap would have surfaced during fieldwork as a formal restatement, exactly the kind of finding that adds months to an audit timeline and invites broader scrutiny into every other accounting judgment the company had made.
Rebuilding recognition before the audit firm arrived
The revenue recognition policy was rebuilt from the ground up, working through the company’s contract portfolio one agreement at a time to separate the implementation services and subscription components based on their actual standalone selling prices, then recalculating two full years of historical revenue under the corrected methodology, all completed before the audit firm’s first day of fieldwork. Alongside that historical correction, the monthly close checklist and account reconciliation process were redesigned specifically to hold up under a genuine audit trail rather than the lighter internal review standard that had let the original issue persist undetected for two years.
Why this particular mistake is common in B2B software selling to healthcare systems
Contracts with hospital systems and large clinical groups are often negotiated as a single bundled price covering both a substantial implementation effort and an ongoing subscription, because that is how the buyer’s procurement process prefers to see it. Translating that single negotiated price back into two separately recognized revenue streams, each on its own accounting schedule, is a step that is easy to skip under time pressure and easy for an audit firm to flag as soon as they look closely, which makes this exact gap unusually common among healthcare-focused B2B software companies heading toward their first real audit.
What audit-readiness work actually involves, beyond fixing the one issue found
Correcting the historical revenue recognition was necessary but not sufficient on its own. The broader audit-readiness engagement also involved walking through every other significant accounting policy, deferred revenue, capitalized software costs, accrued liabilities, with the same question in mind: would this hold up to an auditor who assumes nothing and verifies everything. Two smaller issues were found and corrected the same way, before they had a chance to become their own late discoveries during fieldwork.
Results
The audit-readiness review closed with zero material findings and no restatement required, keeping the company’s IPO-track timeline intact and leaving it with a close process built to survive the deeper scrutiny still ahead as the actual IPO audit approaches.
Questions
FAQ
Why hadn't this revenue recognition issue been caught earlier, given two years of history?
The company's earlier-stage financial reviews had been internal and focused primarily on cash position and runway, which is a defensible allocation of a small finance team's limited time before a company is actively preparing for outside audit scrutiny. Straight-line recognition of a bundled contract is also a common simplification at earlier stages, one that regulators and auditors tend not to focus on until a company is approaching a transaction, like an IPO, that requires audited financials under the full applicable standard. The gap only became consequential once IPO-track accounting requirements applied, which is exactly when it surfaced.
What would an actual restatement have cost the company, beyond the accounting work itself?
Beyond the direct cost of recalculating and re-filing prior-period financials, a restatement discovered mid-audit typically adds two to four months to the overall audit timeline, since the audit firm has to re-scope its testing plan around the correction and often widens scrutiny into adjacent areas of the financials that hadn't originally raised concerns. For a company on an active IPO timeline, that kind of delay can mean missing a specific market window, which carries a cost far larger than the accounting fix itself.
How is the monthly close process structured differently now, to prevent the same issue from recurring?
Every new contract now has its services and subscription components explicitly identified and priced separately at signing, rather than left as a single bundled number to be allocated later, and revenue for each component is recognized on its own correct schedule from day one. A monthly reconciliation step was also added specifically to catch any drift between contract terms and recognized revenue before it can compound across multiple quarters, which is the exact failure mode that produced the original two-year gap.
Working on something similar?
Tell us about your stage and what's next.