Martin’s formal request to the project contact went unanswered for two days. When a reply finally arrived, it was brief and defensive. The sender confirmed having written the message instructing Mark to treat the reconciliation certificate as the final position for preparing the transaction summary. However, the sender insisted that the instruction had been based on information supplied by the accounts manager and was not intended to certify that Peter had personally approved every figure.
Martin forwarded the response to Helen for review before sharing it with Eleanor and Claire. He wanted to know whether the explanation was consistent with the records already recovered. Helen found that the message could fit the existing chronology, but it did not resolve the central question. The accounts manager’s approval was missing from the closing checklist, and the outstanding queries had not been marked as resolved. The sender might genuinely have believed that the matter had been settled, but the surviving file did not show what supported that belief.
When Eleanor and Claire arrived at Martin’s office, he placed the reply beside the archived instruction. He explained that the sender had agreed to provide a short statement describing the process and would search for any messages received from the accounts manager. The person had also identified the source of the assurance: an internal note stating that the reconciliation certificate had been accepted as the working basis for closing the project.
“Accepted by whom?” Claire asked.
“That is the question the note does not answer,” Martin said. “It describes a status, but it does not identify the person who had authority to approve the disputed figures.”
Eleanor looked at the wording. It was familiar now: administrative position, final position, completed review. Each phrase sounded conclusive until they asked what evidence supported it. The records had accumulated statements that the accounting was settled, yet the underlying approval remained undocumented.
Helen explained that the distinction mattered financially as well as procedurally. A certificate could be used as a reference point for preparing a report without proving that every payment described in the report had been properly authorized. If the certificate had been attached to a revised schedule after it was signed, or if the outstanding queries remained unresolved, the resulting summary could misrepresent the transaction even if the signature itself was genuine.
Claire asked whether the internal note might have been based on a verbal assurance from Peter or David. Helen said that was possible, but the surviving correspondence made it difficult to assume that either man had accepted the final accounting without further evidence. David had requested the missing breakdown after acknowledging receipt of the packet. Peter’s later letters continued to ask for supporting documents. Any claim that the objections had been resolved would need to account for those records.
Martin then revealed that the project contact had supplied the name of the accounts manager responsible for the closing review: Robert Hales. His name appeared on several routine records, but none of the documents recovered so far carried his signed approval of the disputed payment. The project contact said Robert had told the team that the reconciliation certificate could be treated as the final working document while the remaining queries were being checked.
Eleanor wrote down the name. Robert Hales was not a stranger who had appeared in the story only after the fact. His initials appeared beside ordinary entries in the ledger, and his office had been responsible for confirming that the supporting records matched the approved schedule. That made him an important source of information, but it did not make him guilty of anything.
Martin contacted Robert through the accounting firm’s historical records department. Robert had retired several years earlier, and the firm asked for time to locate his current contact details. Martin did not send an accusation or demand an explanation for the disputed transfer. He asked whether Robert would be willing to clarify the closing procedure and identify any records that might document the approval.
While they waited, Eleanor returned to the original ledger. She compared the disputed transfer with two other payments made during the same period. Both had supporting invoices created before the payment was released. Both had approval references recorded in the ledger. The disputed transfer was different: the approval field remained outstanding, and the invoice that later supported it had been created afterward. The difference did not prove misconduct, but it made the transaction an exception that required a documented explanation.
Helen prepared a comparison table showing the three payments, their dates, supporting invoices, and recorded approval status. She emphasized that the comparison was not a complete audit of the entire project. It was a focused test of whether the disputed transfer had followed the process used for similar transactions. The two ordinary payments had a clearer trail. The disputed payment did not.
Claire studied the table and asked whether someone could have processed the payment under an urgent instruction and planned to complete the paperwork later. Helen said that was possible. Businesses sometimes made payments before all administrative documents were assembled, especially when a manager believed the authorization had already been granted. But the later paperwork should then identify the person who authorized the exception and explain why the supporting documents were completed afterward.
“Do we have that explanation?” Claire asked.
“Not in the records we have,” Helen replied. “That doesn't prove it never existed. It means we have not found it.”
Three days later, Robert Hales agreed to speak with Martin. He asked for copies of the specific ledger entries and the closing checklist before the meeting, explaining that he could not responsibly comment on a transaction from memory alone. Martin sent the requested documents and arranged a meeting at his office.
Robert arrived carrying a thin folder of his own. He was a broad-shouldered man with a careful manner and a tendency to pause before answering. He said he remembered the development because the closing process had been unusually complicated. Several versions of the payment schedule had circulated, and the team had been under pressure to produce a final report before the project review.
He examined the ledger entry for the disputed payment and frowned. He recognized the format but could not remember the individual transaction without checking his notes. When Martin showed him the closing checklist, Robert confirmed that the approval field should ordinarily have been completed before a reconciliation certificate was described as final. He could not explain why the field was blank.
“Did you approve the disputed payment?” Martin asked.
Robert looked at the ledger again. “I would need the original payment instruction to answer that. I don't remember signing off on this particular transfer.”
“Did you tell the project team that the reconciliation certificate could be treated as the final position?”
“I may have told them they could use it as the working document. That would not have meant the outstanding queries were resolved. The distinction should have been clear.”
Claire spoke for the first time. “Would you have expected Mark to understand that distinction?”
Robert turned toward her. He said Mark had not worked in the original accounts office and might not have understood the internal status system. The summary’s wording should have been checked by someone responsible for the accounting before it was circulated. Robert admitted that the closing process had sometimes relied too heavily on informal assurances, especially when a report was needed quickly.
His answer explained how the misleading summary might have emerged without anyone setting out to deceive Claire. A manager could have allowed a working document to be treated as final for convenience. An administrator could have interpreted that as permission to prepare the packet. Mark could have relied on the packet when writing the summary. Each person might have assumed that someone else had verified the approval.
But Eleanor noticed that Robert had carefully described what should have happened without saying what actually happened. She asked whether he had seen Peter’s objections.
Robert opened his folder and took out a handwritten list of project queries. He recognized Peter’s name on it. He said Peter had raised concerns about the changing schedule and had asked for a clear reconciliation of the figures. Robert remembered that the questions had been referred to the accounts team, but he could not recall seeing a written response that resolved them.
“Then why was the certificate treated as final?” Eleanor asked.
Robert looked uncomfortable. He said that, at the time, the team had been trying to separate the remaining accounting questions from the administrative task of producing a summary. He believed the certificate had been accepted as the working basis for the report, but he could not now say who had decided that the unresolved queries would not prevent the summary from being issued.
Martin asked whether Robert had any records showing that the queries were eventually answered. Robert searched the folder but found only the list of questions and a note indicating that the revised schedule was being checked. He had no signed approval, no final response from Peter, and no document showing that the outstanding issues had been closed.
He did not claim that such a record had never existed. He said it might have been held by another department or lost during the project’s closure. But he acknowledged that, based on the papers he had brought, he could not substantiate the claim that Peter had approved the final accounting.
The admission settled one narrow question. The person responsible for the closing review could not produce evidence that the approval had been recorded. It did not establish that the payment was unauthorized, and it did not identify who had changed the summary. Yet it meant that the final wording had rested on a conclusion that the surviving approval records did not support.
After the meeting, Martin prepared a written note of Robert’s statements and sent it to him for confirmation. Robert returned it with minor corrections to the chronology and a clarification that he could not remember personally authorizing the payment. He did not dispute the central point: he had no surviving record showing that the outstanding queries were resolved before the summary was treated as final.
Helen incorporated the statement into her preliminary findings. She wrote that the disputed transfer lacked the same clear approval trail as comparable payments and that the final summary overstated what the surviving documents established. She did not attribute intent to Mark, Robert, Susan, or the unidentified sender of the earlier instruction. Her conclusion was limited to the evidence: the transaction had been presented as approved without a complete, documented basis for that claim.
Claire read the report at Eleanor’s dining table. “So the summary was wrong, but we still don't know whether Mark understood that.”
“That's right,” Eleanor said. “And we still don't know who made the change that removed the qualification.”
Claire looked at the copy of Mark’s final summary. The wording no longer seemed like a single lie with a single author. It looked like the end of a chain in which the original questions had been weakened, passed along, and eventually omitted. But someone had still chosen the words that made the transaction appear settled, and the evidence had not yet established who made that choice.
That evening, Claire asked Mark to meet with her and Martin. She told him that Robert could not substantiate the approval claim and that the closing checklist contained no recorded sign-off. She also told him that the working draft had included a qualification that the final summary omitted. She asked him to bring any records he had found and to explain his role in the revisions.
Mark agreed to meet, but he requested a few days to review the documents and prepare a response. Claire accepted. She did not want a hurried confrontation in which anger replaced evidence. Still, she told him plainly that she could no longer accept his earlier assurance that the accounting had been fully approved without seeing the basis for it.
After she sent the message, Eleanor sat with her in the quiet dining room. The investigation had not uncovered a simple villain or a single decisive act. It had exposed a failure in the project’s approval process, an unsupported claim of final consent, and a summary that concealed unresolved questions. Whether those failures had been exploited deliberately remained unanswered.
Eleanor returned the documents to their folders. Peter had wanted the schedule reconciled and the approval recorded. The records now showed that those requests had not been properly resolved in the surviving file. The next conversation with Mark would have to confront the difference between believing an account was final and having evidence that it truly was.
Click here to continue reading: PART 25: Mark Finally Reviews the Contradictory Records With Claire and Martin, but His Explanation Leaves One Crucial Decision Unaccounted For
The Message Arrived Before Breakfast, and by Noon Her Daughter Had Changed the Locks on Every Door That Mattered
Part 24 of 35
