Chapter 3: The Approval I Never Gave
Jo kept her hand on the phone after she asked June to freeze the file Daniel had opened. I watched the conference-room screen, where June’s name sat beside a muted microphone icon.
“Can you preserve the copy as it stands right now?” Jo asked.
“IT is doing that,” June said. “I don’t want to touch the file while they’re capturing it.”
“Good. We’ll wait.”
For the first time since I had placed my paycheck on Miranda’s desk, waiting felt harder than speaking. Daniel had opened the exception file after Jo told him the records were being preserved. Then he had opened the local HR support file linked to it. I could think of reasons for him to do that. None of them stopped me from watching the screen.
When the IT analyst called back, Jo put him on speaker.
“We have copies from before and after the two access events,” he said. “The saved contents match. I see an open, not a save.”
June let out a breath.
“So nothing was deleted?” I asked.
“I can’t say that,” he said. “These copies tell us the files didn’t change between the times we captured them. They don’t tell us whether something was missing before we started, or whether a related record lives somewhere else.”
Jo wrote that down. Daniel’s access remained suspicious to me, but it had not answered the question I wanted it to answer.
“We’ll keep the access logs,” she said. “Please finish preserving the linked records.”
The analyst agreed and disconnected. June said she would continue looking for the advance requests in other approved storage locations. She also had Emma’s—my—timekeeping gaps to reconcile, and a secure list of other workers to send Jo. There were enough questions to fill the afternoon without inventing one more.
I set my phone beside the original paycheck. The check was folded where I had gripped it in Miranda’s office.
“You said you refused to change a vendor report,” Jo said. “Can we go through that now?”
“Yes.”
“Start with what you were assigned to report.”
I had expected her to ask what Miranda said to me. Instead, she asked about columns, dates, and who could check my work. It was a relief to begin somewhere solid.
The report covered shipment discrepancies from two weekend inventory audits. I had compared receiving totals with the warehouse count sheets and flagged several pallets whose movement I could not account for. That did not prove they were lost. A shipment could have been entered late or recorded under the wrong reference. The report was supposed to tell the vendor what we knew and what we still needed to verify.
I showed Jo the calendar entries and messages I had already sent her about the audits. The timekeeping export did not show a matching shift for the first weekend. It had no Saturday entry for the second. Those were problems of their own; I did not want them confused with a claim about the pallets.
“Who else worked those audits?” Jo asked.
“Nia Brooks was on the warehouse floor for parts of both. She can tell you what we counted, if she’s willing. But please don’t ask her through a supervisor.”
Jo looked up.
“Has someone threatened her?”
“Not that I know of.” I thought about how much a posted shift could mean to a person. “I don’t want my name to become a reason someone calls her into an office.”
“I’ll contact her privately if we need her account,” Jo said.
That was as much as she could promise. It was also more care than I had seen anyone take when a report crossed my desk.
Jo asked about the figures Miranda had wanted changed.
“The missing pallets were supposed to be listed as a warehouse count correction,” I said. “If I put them there, the vendor would see a balanced shipment report. Anyone looking later would think the warehouse team had counted wrong.”
“What did you do?”
“I told Miranda I couldn’t support those numbers. I left the discrepancies open in my draft and sent it for review.”
“Do you still have that draft?”
“It should be in my project folder. I saved the PDF there before I sent the review request.”
Jo called IT again. She did not ask anyone to restore my account. She asked for a preserved copy of the company folder and the associated work email, with its dates and file information intact. While they arranged it, I drew the report layout on a blank page: the vendor’s shipment figure on one side, our count on the other, and a narrow column for the explanation.
I knew that column too well. Miranda had stood at my desk with one finger resting on it.
“Fix it before the client sees it,” she had said.
“There isn’t a confirmed warehouse correction,” I had told her.
“Then confirm one.”
At the time, I had gone back to the count sheets instead of answering. I had thought more checking might settle the argument. When it didn’t, I sent the draft with the discrepancies still marked.
Jo listened without turning my memory into a finding.
“Did she put the requested changes in writing?”
“Not to me.”
“Who received your review request?”
“Miranda. The project mailbox too.”
“And you didn’t approve a final version?”
“No.”
She set down her pen.
“I need to tell you why I’m asking so precisely. Someone may have a different account. The files may not say what either of you expects. I have to establish what was submitted, not just what should have been.”
“I understand.”
I did. Understanding did not make the thought easier to bear.
While we waited for the folder, Jo told me corporate compliance had approved an outside auditor for the overlapping payroll and shipment questions. Her name was Ruth Ellis. She would examine records independently, though the company had retained her. Jo was careful about that distinction too.
June joined us again by phone. She had located the submitted vendor report in the company’s reporting system. Jo asked IT to capture its stored copy and history before anyone opened it for review.
On the screen, the report appeared in the same familiar grid I had spent nights trying to make accurate. I found the shipment rows at once. The discrepancy column no longer showed the pallets as unresolved. Each had a warehouse count correction beside it.
My face went hot.
“Those are the numbers she wanted,” I said.
Jo leaned closer to the screen. “Tell me which rows.”
I read the references aloud. Jo marked them without agreeing that Miranda had entered anything. She asked me to compare the remaining rows as well. Some matched what I remembered; others were too ordinary for me to recall. Seeing the altered figures had not made the whole document familiar.
Then I saw the approval field.
My name was there.
Not just on the preparation line, where it belonged. Beside the final figures, the report displayed “Approved by Emma” and a time I could not read clearly at that screen size.
“I never approved that,” I said.
June was quiet. Jo enlarged the section.
“It attributes approval to you,” she said. “We need to find out what that field means in this system. It could record an account action, an imported name, or something else.”
“I wouldn’t have approved figures I refused to put in.”
“I hear you.”
It was a small sentence. She did not ask me to calm down. She also did not call the field a forgery because I had asked her to.
I looked at the check on the table. The memo line named Miranda. The report named me. In both places, a few printed words threatened to stand in for something no one had actually asked me.
IT delivered the preserved project-folder copy through Jo’s secure workspace. My PDF was there, dated before the submitted report. The disputed rows were marked unresolved, exactly where I had said they would be. Beside them, I had typed a note requesting confirmation from receiving.
Jo compared it with the submitted version. Then she compared the email requesting review with the date on the saved PDF. The two supported my account of what I had sent. They did not show who had approved the later report.
“Can we see who changed those rows?” I asked.
“Ruth has requested the version history,” Jo said. “IT is collecting it with the system’s audit records.”
June spoke from the phone. “And we should keep the payroll work separate until we can test a connection. The deduction code and this report may have nothing to do with each other.”
I wanted to argue. Miranda had disciplined me after I refused the figures, and my check carried her authorization in its memo line. But I could see the distance between those facts and an explanation. Fourteen other workers had checks with the same exception code. If I insisted every answer began and ended with my report, I might miss theirs.
Ruth arrived by video late in the afternoon. She had a plain desk behind her and a marked-up list of records in front of her. After introductions, she asked me to describe the work as though she had never seen a shipment report. When I finished, she asked Jo for the draft, the submitted copy, the approval-field documentation, and the complete version histories.
“Until I see how that field is populated, I won’t call it an authentic approval or an inauthentic one,” Ruth said.
She asked whether I had been in the building when the final report was submitted. I could remember leaving on that Tuesday. I had texted a friend from outside while waiting for a ride, but I did not want a memory or a message to do more work than it could.
Jo requested the building’s badge records for that evening. IT returned an exit entry under my badge at 6:06 p.m. Ruth checked that the badge record and the report used the same local time setting. Then she opened the approval detail Jo had sent her.
May you like
She looked at it long enough that I wondered whether my name was missing after all.
“Nine seventeen p.m.,” Ruth read aloud. “Three hours and eleven minutes after Emma left the building.”
