PART 22 – Susan Pike Explains the Office’s Closing Procedure, While a Handwritten Draft Suggests Someone Removed a Crucial Qualification From Mark’s Summary

Susan Pike arrived at Martin Shaw’s office the following Tuesday carrying a small notebook and a pair of reading glasses. She was in her early sixties, with short silver hair and the guarded manner of someone who had spent years working around confidential records. She greeted Eleanor and Claire politely, then asked Martin to confirm that the meeting was intended to clarify the administrative process rather than determine responsibility for the disputed payment.

Martin assured her that it was. He explained that the documents had raised questions about the sequence in which the reconciliation packet was assembled, and that her experience with the filing system might help them interpret the surviving notes. Susan nodded and placed her notebook on the table. She said she would answer what she could, but she would not pretend to remember details that had faded over time.

Martin began with the routing note instructing the office to hold the final packet until outstanding queries were answered. Susan studied the copy, then explained that a hold usually meant the packet could be prepared but should not be marked final or circulated as an approved account. Staff could collect documents, arrange them in order, and identify missing pages while a query remained open. The restriction was intended to prevent a preliminary file from being mistaken for a completed one.

“Would a packet still be sent to someone outside the accounts team while the hold remained active?” Martin asked.

“Not as a final reconciliation,” Susan replied. “Someone might receive selected documents for review, but the cover message should make the status clear. If the recipient was told the file was complete, the hold should have been resolved first.”

Claire leaned forward. “What if the person preparing the packet believed the accounts manager had resolved it?”

“That could happen,” Susan said. “We had managers responsible for different stages. An administrator might receive an instruction to prepare a file and assume that the person authorizing circulation had checked the outstanding items. But the procedure was supposed to make the status visible. There was a field for unresolved queries.”

Eleanor asked whether the status field could be changed without a formal approval. Susan said that it depended on the system used at the time. Some paper records relied on initials, while electronic tracking fields could be updated by staff with the appropriate access. The surviving index might show when the status changed, but it would not necessarily identify who made the decision if several employees used the same account.

Martin showed her the transmittal email and its attachments. Susan recognized the general format of the packet but could not say who had assembled those particular pages. She noted that the message referred to the “current administrative position,” which was not the same as a statement that all parties had approved the figures. The phrase suggested that the sender was describing how the office was treating the matter, not necessarily certifying that every underlying question had been resolved.

“Would you have understood that wording as permission to call the accounting final?” Martin asked.

“Not by itself,” Susan answered. “I would have wanted to see the status field and the instruction from whoever had authority to release the packet. The wording is vague. It might have been intended as a cautious description, or it might have been used to make an unfinished file sound more settled than it was.”

Susan was careful not to go further. She had not prepared the message, and she could not identify the sender from the shared account. She said she remembered Peter because he was unusually persistent about getting the same schedule that other people were using. He would ask for a document, receive a version, and then point out that the figures did not match the version discussed at the previous meeting.

“Did he ever say he thought someone was deliberately changing the figures?” Eleanor asked.

Susan considered the question. “I remember him saying that he could not sign off on figures that kept changing. I don't remember him accusing a particular person of altering them. He wanted the versions reconciled, and he wanted the supporting documents.”

That distinction mattered to Eleanor. Peter’s concern had been real, but Susan’s recollection did not support the more dramatic possibility that he had identified a deliberate scheme. He might have suspected poor administration, a financial disagreement, or something worse. Without his complete correspondence, no one could know how far his suspicions had gone.

Susan then described the closing procedure. Before a transaction could be marked final, the accounts manager was expected to confirm that the outstanding queries had been answered, the supporting invoice had been received, and the payment schedule matched the approved figures. An administrator could assemble the packet, but the manager’s approval was supposed to be recorded separately. The final summary was usually prepared from that packet, although some summaries were drafted before every document had been collected.

Claire looked at the copy of Mark’s summary. “If the summary was drafted early, could the person writing it have used language that later turned out to be wrong?”

“Yes,” Susan replied. “That is why a draft should be checked against the final records. If a query remains open, the wording should reflect that. A draft is not a certification.”

Martin asked whether a later editor could remove a qualification without changing the underlying figures. Susan said that would be easy in any ordinary word-processing document. The difficult question would be who made the edit and why. A draft might pass through several hands, and a final version could contain changes made by the original writer, a manager, or someone preparing it for another audience.

When the meeting ended, Susan agreed to review any additional records that Martin could lawfully share with her. She also suggested that they search for the closing checklist used by the accounts manager. If the checklist survived, it might show whether the outstanding queries had been formally cleared before the packet was released.

Eleanor thanked her for coming. Susan looked uncomfortable when Eleanor asked whether she remembered Peter personally, beyond the paperwork. She said he had seemed tired during the final meetings, but she could not say whether that was because of the accounting dispute or something unrelated. She remembered that he had insisted on receiving copies of his own correspondence and had asked for confirmation whenever a document was replaced.

“He wanted a record of what had been sent to him,” Susan said. “I remember that much.”

After Susan left, Martin reviewed his notes and emphasized that her account explained procedure but did not identify who had violated it. The office’s rules made the disputed sequence more concerning, yet a rule could be ignored accidentally as well as deliberately. The missing approval record remained essential.

The draft summary arrived that afternoon. Martin had requested the original file if it remained available, but the archive provider could initially release only a printed copy and a metadata sheet. The document was titled “Transaction Summary—Working Draft.” Its text was broadly similar to the final version Mark had used, but one paragraph contained a qualification that did not appear in the final copy.

The draft stated that the reconciliation certificate had been received, while noting that the supporting schedule and outstanding client queries still required confirmation. The next paragraph summarized the payment as part of the proposed final account, but it described the status as provisional pending completion of the review. Those qualifications were absent from the final summary, which stated that Peter and David had approved the accounting.

Claire read the two versions side by side. “The draft admits that the questions were still open.”

“Yes,” Martin said. “And the final version presents the matter as settled. The difference is significant. But we still need the editing history and the identity of whoever made the changes.”

The printed draft carried handwritten marks in the margin. One line had been drawn beside the sentence about outstanding client queries. A short note said, “Remove qualification after confirmation.” The handwriting was not identified, and the note did not specify what confirmation was expected or who had supplied it. The marks could have been instructions to revise the draft once approval arrived. They could also have been used to justify removing a warning without obtaining the required approval.

Eleanor felt the room grow quiet around the papers. The difference between the two summaries was no longer a matter of interpretation. The final document had omitted language acknowledging that the schedule and queries remained unresolved. What they did not yet know was whether the omitted qualification had been removed after a legitimate confirmation or before anyone had actually resolved the outstanding questions.

Helen examined the two copies later that day. She confirmed that the financial figures in the draft and final summary were substantially the same, but the statements about approval were different. The draft described an incomplete process. The final version represented the outcome as complete. Helen said that a change in wording could be more consequential than a change in a number when it altered the status of a disputed transaction.

She also cautioned that the printed copy did not allow her to authenticate the handwriting or determine whether the note had been added before or after the draft was printed. The original electronic file and its revision history would be more informative. If those records had been preserved, they might show when the qualification was deleted and whether the change was made on Mark’s computer, on a shared office system, or by another person.

Martin submitted a new request for the original draft file, its version history, and the closing checklist Susan had described. He asked the archive provider to identify any records showing who approved the final summary and whether the outstanding queries had been cleared. He also requested any email containing the confirmation referred to in the handwritten note.

Claire watched him type. “If the qualification was removed before the confirmation arrived, that would matter.”

“It would,” Martin said. “But we must establish the timing before drawing a conclusion. The note may refer to a confirmation that existed elsewhere. We need to locate it.”

That evening, Mark called Claire. He said he had heard that old records were being reviewed and wanted to know whether his name had been mentioned. Claire told him that the archive contained a working draft of the summary, and that the draft acknowledged unresolved questions that the final version omitted.

Mark went quiet. When he spoke again, he said he remembered working from a summary that had already been compiled by the project team. He had made edits to improve the language and organize the information for the business arrangement, but he did not remember removing a warning about outstanding queries. He asked Claire to send him the draft so he could see exactly what she meant.

Claire declined to send the document directly. She explained that Martin was managing the records and would provide copies through the proper process if Mark needed to respond to them. She asked him to preserve his own files and identify any versions he still possessed.

Mark said he understood, but his voice sounded strained. He insisted that he had never intended to mislead her or anyone else. He had trusted the project’s administrative position and believed the reconciliation certificate represented the final agreement. If the records showed that the process had been incomplete, he said, that was something the original project team needed to explain.

After the call, Claire sat beside Eleanor without speaking. Her husband’s explanation was possible, but it was no longer enough to settle the matter. The working draft demonstrated that someone had once acknowledged the unresolved questions. The final summary removed that acknowledgment. Whether Mark had made the change, approved it, or merely received a version already changed remained unknown.

Eleanor placed the two copies in separate folders. She wanted them kept apart so that no one could accidentally treat the draft as the final record or confuse the notes on one with the wording of the other. The evidence had become clearer, but the identity of the decision-maker had become more important than ever.

The next document they needed was not another summary. It was the confirmation that supposedly justified removing the qualification. If such a confirmation existed, it should have a date, a sender, and a clear connection to the outstanding queries. If it did not exist, the note in the margin would raise a more troubling possibility: that someone had removed the warning because the final account needed to look complete, not because the underlying questions had been answered.