Catching a revenue spread problem before the buyer did

The situation

Ngozi was three weeks into preparing the data room when she pulled the same report twice and got two different growth numbers. The first came from the finance system her bookkeeper had set up years earlier, which booked each annual subscription contract as revenue the day it was signed. The second came from a spreadsheet a summer intern had built the year before, spreading that same revenue evenly across the twelve months it actually covered. The two numbers were not close. On the bookkeeper's method, the company's year-over-year growth looked like roughly forty percent. On the spread method, it was closer to twenty-two.

Ngozi, Ama and Rahel had built the company together over nine years, moving from a small patient-monitoring tool used by a handful of respiratory clinics into a subscription platform with several hundred healthcare-provider customers across Ontario. Ngozi had trained as a respiratory therapist before the software work took over; Rahel had run IT support for a hospital network before joining full time; Ama had handled sales and had been the one repeating the forty percent figure to every prospective buyer who asked how the company was performing. Neither of them had ever had reason to look closely at how the bookkeeper counted revenue, because the number that mattered day to day was cash in the bank, and the cash was fine. Growth on paper was a separate question none of the three had thought to ask.

The buyer, a larger healthcare technology company assembling a portfolio of clinical software tools, had signed a letter of intent based on the forty percent growth figure, in a deal valued in the low twenty millions. That figure appeared in the pitch materials, in the management presentation, and in the working model the buyer's corporate development team had built to justify the price to its own board. It was also the number Ama had used, in good faith, in every conversation with the buyer's executives over the preceding four months.

Ngozi brought the discrepancy to us the same week she found it, still assuming it was a bookkeeping quirk rather than something that could change the shape of the deal. She was clear about what she wanted: fix it quietly, keep the reported number close enough that the deal did not need to move, and get to closing before anyone on the buyer's side had a reason to ask the question she had just asked herself. Rahel, more cautious by nature, wanted to understand exactly how large the gap was before deciding anything. Ama, worried the buyer would lose confidence, wanted the conversation kept as small as possible.

What the other side was relying on

The buyer's diligence team was doing what most acquirers do at this stage of a deal: testing the numbers the seller had already provided, rather than rebuilding them from scratch. Their accountants would eventually pull sample contracts and trace the revenue recognized against them, but that work was scheduled for later in the process, after the purchase agreement was substantially negotiated and both sides had spent real money on legal and advisory fees. By the time that testing happened, the buyer's own corporate development team would be committed, emotionally and organizationally, to a deal that had already been presented internally as done.

That timing mattered because of what it would let the buyer do if the error surfaced late instead of early. Discovering a revenue recognition problem after signing, but before closing, hands a buyer enormous leverage. It can walk away entirely, citing a material change in the business it thought it was buying. More commonly, it uses the discovery to renegotiate price downward under time pressure the seller cannot afford, because by then the seller has told employees, landlords and sometimes customers that a sale is happening, and backing out is no longer a real option. Discovering it after closing is worse still: most purchase agreements include seller representations that the financial statements were prepared properly and fairly present the business, and a buyer that finds a revenue overstatement after the money has changed hands has grounds to pursue a claim for the difference, sometimes years later, once the sellers have long since spent the proceeds.

The buyer's team, in other words, was relying on the ordinary sequence of a deal to do their scrutiny for them, and on sellers not volunteering problems that scrutiny would eventually find anyway. That is not dishonest on the buyer's part; it is simply how diligence timelines usually work, and most sellers never test their own numbers early enough to find out whether they will hold up under that kind of scrutiny. The buyer's accountants had no reason to expect the seller to hand them the answer to a question they had not asked yet, and every reason to assume that a management team pitching forty percent growth had checked the number before repeating it.

The company that gets ahead of its own error, before the other side's process reaches it, is the one that controls how the conversation about that error happens, rather than having the conversation forced on it during the final weeks of a deal, at the worst possible moment for its own leverage.

What we did

1. Told the management team plainly why the fast, quiet fix was the wrong move. Ngozi's instinct was to smooth the numbers internally and keep going without telling anyone. We explained that if the buyer's accountants found the discrepancy independently later in diligence, even one with an entirely innocent explanation, it would read as concealment rather than an honest accounting method question, and would poison trust for the rest of the deal regardless of how small the dollar amount turned out to be.
2. Brought in an accountant to properly re-spread every active contract. Rather than estimate the impact from a sample and hope it held up, we had every subscription contract in the portfolio recalculated on a deferred revenue basis, contract by contract, so the restated growth figure was defensible line by line under scrutiny rather than a rounded guess a skeptical buyer's accountant could later pick apart during their own testing.
3. Quantified exactly what changed and what did not. We had the accountant separate the restatement into what it did to reported revenue, which fell noticeably, and what it did to actual cash collected and customer retention, which did not change at all, because the underlying contracts and payments were exactly the same as before. That distinction became the foundation of everything that followed.
4. Rebuilt the growth narrative around the corrected number. Twenty-two percent growth on properly recognized revenue tells a buyer a materially different story than forty percent growth on revenue booked early, so we worked with the team to reframe the pitch around customer retention and contract renewal rates, both of which held up well under either accounting method and gave the buyer a real reason to stay interested in the deal.
5. Disclosed the restatement to the buyer's counsel before their diligence reached it. We drafted a short, factual disclosure explaining the original method, the correction, and the revised figures, and delivered it proactively rather than waiting to be asked, which framed the issue in the buyer's mind as a correction the seller had caught and fixed, not a problem the buyer's own team had uncovered.
6. Renegotiated the price on our terms rather than the buyer's. With the corrected numbers on the table weeks before the buyer's own accountants would otherwise have reached them, we negotiated a modest downward adjustment reflecting the true growth rate, in a calm conversation rather than a hurried one during the final week before closing, which kept the adjustment proportionate to the actual change in the numbers rather than inflated by the leverage a late discovery would have handed the buyer.
7. Tightened the financial representations in the purchase agreement. We made sure the agreement's warranties about the financial statements referenced the corrected, deferred-revenue figures specifically rather than the original method that had produced the inflated growth number, so there was no ambiguity later about which numbers the seller had actually stood behind, and no room for a future claim built on the discarded method or its abandoned assumptions.
8. Walked the management team through what a late discovery would have cost. To make the value of the early fix concrete for Ngozi, Ama and Rahel, we set out, in plain terms, what a post-closing claim on the original overstated figures could realistically have looked like, so the team understood the correction as protection they had paid for up front, not an unwanted delay imposed on them.

The outcome

The deal closed roughly six weeks later than the management team's original target, at a price adjusted down by an amount in the low single-digit percentages to reflect the corrected growth rate. That adjustment was real money, and Ngozi, Ama and Rahel were not pleased about giving it up, particularly Ama, who had spent months building the buyer relationship around the higher figure. But it was negotiated calmly, against a number both sides had already agreed was accurate, rather than extracted under pressure during a final week of due diligence with the deal's survival on the line.

No claim was ever made against the seller representations, because there was nothing left in the financial statements for a claim to attach to. The purchase agreement's warranties matched the corrected numbers exactly, and the buyer's own diligence, when it eventually reached the revenue testing stage some weeks later, confirmed figures it had already seen and accepted. What could have been a mid-deal crisis, or a lawsuit surfacing a year after closing once the sale proceeds were long spent, became a routine adjustment that both sides could explain to their own stakeholders without embarrassment or blame.

The buyer's corporate development lead later told Ngozi, informally, that the early disclosure was part of what kept the board comfortable with the deal despite the price adjustment, since it suggested a management team that would flag problems rather than bury them once inside a larger organization.

The harder outcome to measure is the one that did not happen. Nothing prevents a determined mistake from teaching itself twice, and it is entirely possible that had the team taken the fast, quiet route they originally wanted, the deal still would have closed at the higher price, and no one would have noticed the discrepancy for a year or more. Prevention rarely announces itself the way a crisis does. What the file shows is a company that found its own error, fixed it before anyone had to ask, and closed a deal on numbers that would still be true a year after the ink dried.

What you can learn from this