Martin Shaw\u2019s next update arrived three days after the accounting firm acknowledged their expanded request. The archive provider had located additional correspondence, including an earlier draft of the transaction summary and several messages exchanged during the week it was prepared. The firm was still reviewing the materials for confidentiality, but Martin had been given a preliminary inventory. One entry caught his attention: a folder labeled \u201cOutstanding Queries,\u201d dated from the period when Peter was still challenging the revised payment schedule.<\/p>\n
Eleanor read the inventory at the dining table while Claire stood behind her, following each line. The folder might contain Peter\u2019s objections, but it could also contain routine questions unrelated to the disputed transfer. They had learned not to mistake a promising label for a reliable conclusion. Still, the fact that the folder had survived suggested that the objections might have been preserved somewhere in the original project archive, even though they had not been included in the packet Mark received.<\/p>\n
\u201cCould the folder tell us who removed the objections from the summary?\u201d Claire asked.<\/p>\n
\u201cPerhaps,\u201d Eleanor said. \u201cOr it may only show who received them. We need to know what the documents actually say.\u201d<\/p>\n
Martin\u2019s inventory included a name Eleanor had not seen before: Susan Pike, a former project administrator who had handled document circulation during the development\u2019s final review. Her name appeared beside several entries relating to the reconciliation certificate and the revised schedule. The inventory did not say she had prepared the disputed packet. It simply showed that she had worked with some of the relevant files.<\/p>\n
Martin explained by telephone that Susan had left the accounting firm years earlier and now worked independently as an office consultant. He did not recommend contacting her immediately. First, he wanted to obtain the actual correspondence and establish whether her role had been clerical, supervisory, or something in between. A name in an index was a lead, not a basis for putting someone under suspicion.<\/p>\n
Claire accepted the caution, though she found it difficult to wait. She had begun to see how easily an incomplete account could survive when every person involved assumed that someone else had checked the details. She wanted to know whether Susan had simply processed documents or whether she had known that Peter\u2019s objections were being left out.<\/p>\n
Eleanor reminded her that the same distinction applied to Mark. Receiving a packet was not the same as knowing that it was incomplete. Preparing a summary from that packet might have been careless, but carelessness and deliberate deception required different explanations. They would need to discover what each person had been told and what each person had chosen to do with that information.<\/p>\n
The first batch of archived correspondence arrived the following morning. Martin brought the copies to Eleanor\u2019s house so that she and Claire could review them under his guidance. The documents had been numbered and placed in a sequence that reflected their original file references. He instructed them not to write on the copies or remove the labels, explaining that the originals remained with the archive provider and might need to be compared against the copies later.<\/p>\n
The folder labeled \u201cOutstanding Queries\u201d contained several pages of questions about the payment schedule. Most concerned routine accounting details, but three referred directly to the disputed transfer. One asked why the amount differed from the figure in the original schedule. Another asked whether client approval had been received before the payment was released. The third requested the supporting invoice and the authorization permitting the change.<\/p>\n
The questions were dated before the later invoice had been created. That did not establish who knew the invoice would be added afterward, but it showed that the discrepancy had been identified while the project records were still being assembled. The question about client approval was particularly important because it matched the ledger entry showing that approval remained outstanding.<\/p>\n
Claire read the page twice. \u201cSomeone knew the payment was not properly supported.\u201d<\/p>\n
\u201cSomeone asked why it wasn't supported,\u201d Martin corrected gently. \u201cThat is evidence of a question being raised. It doesn't yet tell us what the person who received it knew, or what answer was given.\u201d<\/p>\n
Eleanor appreciated his precision. They had spent too long relying on statements that collapsed several different events into a single confident conclusion. Now they were learning to separate the person who noticed a discrepancy from the person who could resolve it, and both from the person who later presented the transaction as settled.<\/p>\n
A reply appeared in the same folder, although it had been filed under a different reference. It stated that the revised schedule was being checked and that the approval question should remain open until the supporting documents had been received. The message was brief and did not identify the person who had authorized the payment. It did, however, confirm that at least one person in the administrative chain had recognized that the approval issue was unresolved.<\/p>\n
The next document was a handwritten routing note. It instructed the administrator to send the revised schedule to the accounts manager and to hold the final reconciliation packet until the outstanding queries were answered. The initials at the bottom were difficult to read. Helen would need to examine the page before they could compare the handwriting with other known samples.<\/p>\n
Claire placed the routing note beside the later transmittal email. \u201cThe packet was supposed to be held.\u201d<\/p>\n
\u201cThat is what this note says,\u201d Martin replied. \u201cWe still need to determine whether the instruction was followed, who changed the status, and whether this particular packet was the one eventually sent to Mark.\u201d<\/p>\n
Eleanor felt the familiar tightening in her chest. The records now showed a more complicated sequence than a simple mistake. Questions had been raised, a hold had apparently been requested, and the later packet had nevertheless presented the accounting as settled. But the chain between those events remained incomplete. A missing answer could be the result of an intentional omission, an administrative shortcut, or a decision made by someone whose instructions had not survived.<\/p>\n
Martin suggested that Helen compare the routing note with the electronic file index. If the note could be associated with a specific version of the schedule, it might help establish whether the hold applied to the packet Mark later received. He also wanted to see the complete reply chain before deciding whether Susan Pike should be contacted.<\/p>\n
That afternoon, Helen examined the copies and returned a cautious preliminary assessment. The handwriting was consistent with several notes in the same administrative file, but the sample was too limited to identify the writer reliably. The initials could not be assigned to a particular person. She advised them to treat the note as evidence of an instruction recorded in the file, not evidence that a named individual had issued it.<\/p>\n
The archive provider\u2019s next release included a short email from Susan Pike to the accounts manager. It referred to the outstanding queries and asked whether the reconciliation packet should remain on hold. The reply instructed her to prepare the materials for review but did not explicitly authorize the final payment or resolve the approval question. The message was dated before the later transaction summary, and it contained no indication that Peter\u2019s objections had been withdrawn.<\/p>\n
Claire stared at the screen. \u201cShe asked whether the packet should remain on hold. Someone answered, but the answer didn't settle the question.\u201d<\/p>\n
\u201cCorrect,\u201d Martin said. \u201cWe need the surrounding messages, and we need to know what \u2018prepare for review\u2019 meant in that office. It may have been a routine step. It may also have been interpreted more broadly than intended.\u201d<\/p>\n
Eleanor asked Martin whether Susan could help clarify the office\u2019s procedure without being asked to explain the entire transaction. He agreed that a carefully worded request might be appropriate once they had reviewed the complete correspondence. Susan could be asked about the document routing system, the meaning of the hold notation, and the process by which a final packet was assembled. Those were factual questions that did not require them to accuse her of anything.<\/p>\n
Martin contacted Susan through her professional email address. He explained that he was reviewing historical records relating to the development and asked whether she would be willing to clarify several administrative procedures she had handled at the time. He did not disclose Eleanor\u2019s suspicions or suggest that Susan had done anything improper. He attached a short list of neutral questions and offered to arrange a meeting if she preferred.<\/p>\n
Susan replied the next day. She remembered the project and was willing to speak with him, but she asked to see the specific documents first. She explained that many years had passed and she did not want to rely on a vague memory of an old transaction. Martin sent her the relevant pages, preserving the original file references and explaining that the documents were copies from the archive.<\/p>\n
Her response came later that afternoon. She recognized the routing note as the kind of instruction used by the project administration team, but she could not confidently identify the handwriting from the copy. She also remembered that the project had been under pressure to complete its closing paperwork before a scheduled review. She did not recall the disputed payment specifically, and she warned that her memory of individual files was incomplete.<\/p>\n
Then she added a sentence that made Eleanor sit forward in her chair: she remembered that Peter had repeatedly asked for a complete copy of the payment schedule and had become frustrated when different versions circulated.<\/p>\n
Susan did not claim to know why the versions differed. She did not say who had changed them or whether anyone had acted deliberately. She remembered only that Peter had asked for the complete schedule and that the office had struggled to determine which version should be treated as current.<\/p>\n
Claire read the message in silence. \u201cDad wasn't simply refusing to let the project end. He was asking for the same document everyone else was supposed to be using.\u201d<\/p>\n
\u201cIt appears he was asking for a consistent, complete version,\u201d Eleanor said. \u201cThat is different from knowing why he wasn't getting one.\u201d<\/p>\n
Martin thanked Susan for the response and asked whether she would be willing to discuss the filing process in more detail. She agreed to a short meeting the following week, provided the conversation remained focused on the records she had handled. Martin accepted those terms and told Eleanor and Claire that they could attend if Susan was comfortable with it.<\/p>\n
For the first time, Eleanor felt that someone outside the family might help explain how the documents had moved through the office. Susan\u2019s recollection did not solve the central mystery, but it supported the possibility that the inconsistencies had been visible before the transaction summary was written. The next task was to discover whether the missing answers had been overlooked, lost, or deliberately bypassed.<\/p>\n
That evening, Claire asked her mother whether she thought Peter had known the records might be used against him. Eleanor considered the question before answering. Peter had clearly worried that the file was incomplete. He had written repeatedly for the supporting documents and had preserved copies of correspondence that other people might have discarded. But Eleanor could not know whether he anticipated deliberate manipulation or simply feared that the administrative process would bury his objections beneath a stack of finished paperwork.<\/p>\n
\u201cI wish I had asked him more,\u201d she admitted. \u201cI thought the business dispute was something he would resolve when he was ready to talk about it.\u201d<\/p>\n
Claire reached for her hand. \u201cYou couldn't have known what you didn't know.\u201d<\/p>\n
Eleanor squeezed her fingers, grateful for the kindness but unwilling to let it become an excuse to stop searching. Peter had left a trail that was incomplete but not useless. Every recovered document narrowed the possibilities, and every careful question helped them avoid turning uncertainty into accusation.<\/p>\n
When Martin called the next morning to confirm the meeting with Susan, he also mentioned that the archive provider had located one more item: a draft of the transaction summary with handwritten edits. The file reference suggested it had been saved before the final version was sent to Mark. Martin had requested a copy, along with any notes identifying who had made the edits.<\/p>\n
Eleanor wrote the reference number on the chronology. The draft might show whether the claim of final approval had appeared from the beginning or had been added during revision. It might also reveal whether someone had removed a qualification that the final summary no longer contained.<\/p>\n
She looked at Claire, who had been following the conversation from the other side of the table. Neither of them spoke for several seconds. They had begun this search hoping to prove that the records had been misunderstood. Now they were approaching a more difficult question: whether the final account had become misleading through a series of small decisions that each person could excuse as someone else\u2019s responsibility.<\/p>\n
Martin Shaw\u2019s next update arrived three days after the accounting firm acknowledged their expanded request. The archive provider had located additional correspondence, including an earlier draft of the transaction summary … <\/p>\n","protected":false},"author":1,"featured_media":17482,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-17503","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-feel-every-story"],"_links":{"self":[{"href":"https:\/\/feeleverystory.online\/index.php?rest_route=\/wp\/v2\/posts\/17503","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/feeleverystory.online\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/feeleverystory.online\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/feeleverystory.online\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/feeleverystory.online\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=17503"}],"version-history":[{"count":1,"href":"https:\/\/feeleverystory.online\/index.php?rest_route=\/wp\/v2\/posts\/17503\/revisions"}],"predecessor-version":[{"id":17538,"href":"https:\/\/feeleverystory.online\/index.php?rest_route=\/wp\/v2\/posts\/17503\/revisions\/17538"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/feeleverystory.online\/index.php?rest_route=\/wp\/v2\/media\/17482"}],"wp:attachment":[{"href":"https:\/\/feeleverystory.online\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=17503"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/feeleverystory.online\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=17503"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/feeleverystory.online\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=17503"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}