The first thing Michael noticed was not the amount of money involved. It was the date on the final page of a customer agreement.
He called me at eight fifteen the following morning, before I had finished reviewing the overnight correspondence. The Whitmore Group had delivered another batch of documents, including several agreements that our team had requested weeks earlier. The submission was incomplete, but it was substantial enough for the auditors to begin comparing the contractual terms against the company's reported revenue.
“Catherine, we need to look at this together,” Michael said. “There is a discrepancy we shouldn't dismiss.”
I joined him in the conference room, where the relevant pages had been enlarged on a screen. Three major customer accounts appeared in the report, each with revenue recorded during the final weeks of a reporting period. The original financial model had treated those amounts as ordinary sales, supported by contracts that appeared to establish firm customer commitments.
The newly delivered documents told a more complicated story.
Two customers had signed purchase agreements, but the agreements contained conditions that had not been reflected in the financial summary provided to us. The third had signed an order that allowed substantial quantities of equipment to be returned if the systems failed to meet specified performance requirements.
“Are those conditions unusual?” I asked.
“Not necessarily,” Michael replied. “Manufacturing contracts can include acceptance testing, installation milestones, warranty provisions, and return rights. The problem is how the company recognized the revenue before we understood those conditions.”
Our auditor joined by video conference and explained the distinction. Revenue could not simply be treated as final because a purchase order existed. The company needed to establish that the relevant accounting requirements had been satisfied. Depending on the precise contractual terms, some revenue might have been recorded appropriately, some might require adjustment, and some might have been recognized too early.
No one was accusing the Whitmore Group of fraud. We did not yet know whether the discrepancies resulted from aggressive accounting, incomplete reporting, poor internal controls, or deliberate misrepresentation. But the differences were material enough that our investment committee could not ignore them.
I studied the third agreement.
The signature page showed that the customer's acceptance was conditional upon a technical review. A separate schedule referred to performance testing at the customer's facility. That schedule had not been included in the original data room.
“Where is the testing report?” I asked.
Michael checked his notes.
“It hasn't been provided.”
“And the return provision?”
“It's in the agreement, but the company's revenue model doesn't appear to account for the possibility of returns.”
I leaned back in my chair.
“Then the model isn't reliable until we understand the exposure.”
“That is our assessment.”
I asked our team to document every discrepancy and identify exactly which additional records were required. We would not accept a general explanation that the contracts were commercially sensitive. The information was directly relevant to the investment decision, and confidentiality arrangements were already in place.
At ten thirty, Richard's chief financial officer, Martin Cole, requested an urgent meeting. He had worked for the Whitmore Group for eleven years and had been described to us as the executive responsible for financial reporting, treasury, and lender relations.
His written request was polite. His assistant's telephone call was less so.
“Mr. Cole needs to know whether the acquisition can still proceed,” she said. “The company has been planning around the transaction for months.”
I replied that the financial questions had to be resolved before anyone could responsibly discuss reinstating the investment.
Martin joined the meeting shortly after noon. He was a lean man in his late fifties, with rimless glasses and the exhausted expression of someone who had spent too many nights reviewing figures that refused to reconcile.
He thanked us for making time, then placed a folder on the table.
“We recognize that some of the documentation was delayed,” he began. “But I want to assure you that the underlying business is sound. Our factories are operating, our customers remain important partners, and our order book is substantial.”
“Those are useful facts,” I said. “They don't answer the questions about revenue recognition.”
He nodded.
“I understand. We've asked the accounting department to reconstruct the reporting for the relevant contracts.”
“Why wasn't that information available when we first requested it?”
Martin removed his glasses and rubbed the bridge of his nose.
“Some of the arrangements were negotiated across different departments. Sales managed the customer relationships, operations handled installation and testing, and finance received the signed agreements after the commercial terms had already been discussed. The records were not consolidated as quickly as they should have been.”
“Who was responsible for consolidating them?”
“I was.”
He did not attempt to shift the responsibility to a junior employee. That earned him a measure of respect, though it did not resolve the underlying problem.
I asked whether Richard had known about the missing documents.
Martin hesitated.
“He knew we were still assembling the supporting schedules. I cannot tell you what he understood about the accounting implications.”
“Did you tell him that the acquisition was not approved?”
“Yes. I explained that the investment remained subject to due diligence and that no definitive agreement had been signed.”
“When?”
“Several times.”
The answer was troubling, but I needed more than his recollection. I asked him to provide the relevant correspondence through the legal teams.
Martin agreed.
Before he left, he made one final request.
“If the committee ultimately decides not to invest, I would appreciate a clear explanation of the reasons. I have employees who will ask me what happened, and I need to be able to answer them honestly.”
“You will receive a documented explanation of our decision,” I said. “But I cannot promise the committee will reconsider the transaction.”
He accepted that without argument.
After the meeting, Michael walked with me toward my office.
“Do you believe him?” he asked.
“I believe he understands the importance of the documentation. Whether his explanation is complete is another question.”
“Richard will not appreciate having Martin's correspondence reviewed.”
“That isn't a reason to avoid reviewing it.”
Michael nodded. We both understood that a difficult executive was not necessarily a dishonest one, just as a polished presentation did not establish that a company was financially sound.
That afternoon, Emma called to tell me she had spoken to Andrew.
She had met him at a quiet café near her apartment rather than at the Whitmore estate. She wanted the conversation to be private, without his parents, my involvement, or the distractions of a formal dinner.
“He apologized again,” she said.
“What did he apologize for this time?”
“For not defending you. For letting his mother speak to me that way. For pretending everything would be fine if I just waited long enough.”
I listened without interrupting.
“He also told me that he has spent years trying to keep his parents happy,” she continued. “He said that when his father gets angry, everyone in the family learns to make themselves smaller.”
“That sounds difficult.”
“It is. And I feel sorry for him. But I told him that I can't marry someone simply because I understand why he behaves the way he does.”
I looked out of my office window at the afternoon traffic.
“What did he say?”
“He asked me not to make a final decision yet. He said he wants to change.”
“And what do you want?”
“I want to believe him. But I don't know whether I can.”
I told her she did not need to make a permanent decision in the middle of an emotional week. Postponing the wedding was enough for now. She could observe what Andrew did next without promising that his efforts would restore the relationship.
She thanked me, then asked whether the business dispute was becoming worse.
I explained that the financial review had identified contractual conditions that were missing from the original reporting model. I did not tell her that the findings proved anything about Andrew's father, because they did not.
“Could the company still be fine?” she asked.
“Yes. It may be able to resolve the questions. But the committee will need reliable evidence before considering another proposal.”
She was silent for a moment.
“I don't want you to think I'm staying away from Andrew because of the money.”
“I don't.”
“I loved him before I knew anything about this deal.”
“And your decision should be based on the relationship you actually have with him, not on a transaction between two companies.”
After we ended the call, I returned to the due diligence report. The distinction seemed especially important now. Emma's engagement and the proposed acquisition had become entangled in the same public embarrassment, but they were separate matters. Neither should be used to pressure the other.
At four o'clock, our legal team received the correspondence Martin had promised. The messages showed that he had repeatedly warned Richard that the investment remained conditional. In one email, sent several weeks earlier, Martin had explicitly stated that the committee had not approved the transaction and that the customer documentation remained outstanding.
Richard's response was brief.
He had instructed Martin to prepare for closing on the assumption that the remaining issues would be resolved.
That instruction did not prove that Richard intended to deceive anyone. Executives often plan around transactions they reasonably expect to complete. But the emails made it difficult to argue that he had misunderstood the difference between an anticipated closing and an approved investment.
Michael read the messages twice.
“This is more concerning than the missing schedules,” he said.
“Because he was warned?”
“Because he was warned in writing, yet continued to describe the deal as effectively guaranteed.”
I asked our counsel to preserve the emails and include them in the transaction file. We would not draw conclusions beyond the evidence, but the committee needed to know that the uncertainty had been communicated directly to the company's leadership.
Shortly before the close of business, Richard called me again.
This time, he did not begin with an apology.
“Catherine, I understand Martin has been discussing internal matters with your team.”
“He has been responding to our due diligence requests.”
“He is making the situation sound worse than it is.”
“Then the complete records should clarify it.”
“He is a cautious man. Always has been. If he had his way, we would never make a significant decision without six months of paperwork.”
I allowed him to finish.
“Richard, your company's financial reporting needs to be supported by the relevant contracts. That is not an unreasonable request.”
“You are turning a documentation issue into a crisis.”
“I am not turning it into anything. We are assessing the information we received.”
He lowered his voice.
“I need you to understand the practical consequences of your decision. We have commitments that were made in expectation of this acquisition.”
“Were those commitments made on the assumption that an unapproved transaction was certain to close?”
He did not answer.
“Richard, if your company has made commitments based on that assumption, your advisers need to assess them. My firm cannot retroactively approve an investment to make those commitments easier to manage.”
His breathing grew audible over the phone.
“You could help us resolve this.”
“We can review complete documentation. We cannot guarantee a favorable outcome.”
He ended the call without saying goodbye.
I remained at my desk for several minutes, considering the difference between an executive who was struggling with a difficult situation and one who believed that everyone else should absorb the consequences of his decisions.
I did not yet know which description best fit Richard.
But I knew that the next set of documents would matter more than his assurances.
At six forty, Michael sent me a message containing the latest audit note. The missing performance report had finally been located, but its results raised a new question: one of the customers had not formally accepted the equipment by the reporting date used in the Whitmore Group's financial statements.
The auditors needed the complete installation records before determining the appropriate accounting treatment.
I read the note twice.
The missing report was no longer merely an administrative inconvenience. It could affect the amount of revenue the company had reported, the timing of that revenue, and the financial assumptions supporting the proposed acquisition.
I closed the document and called Michael.
“Make sure the auditors receive the original records, not a reconstructed summary. We need to know when the equipment was delivered, when testing occurred, and when the customer accepted it.”
“Understood.”
“And keep the committee's position unchanged until that review is complete.”
I ended the call.
For the first time since the dinner, I wondered whether the transaction would ever be viable.
The answer would not come from Richard's confidence, Victoria's indignation, or the embarrassment of having a deal withdrawn in front of influential people. It would come from the records.
And the records were beginning to tell a story that nobody at the Whitmore estate had been prepared to discuss.
Click here to continue reading: PART 6: Andrew Finally Challenged His Father, but the Answer Revealed Why Silence Had Always Been the Whitmore Family’s Safest Habit
The Engagement Dinner Where Thirty Powerful Guests Watched a Mother Be Humiliated by the Family Her Daughter Was About to Join
Part 5 of 12
