The following morning, Daniel arrived at Meridian Global Enterprises before eight.
He preferred working during the quiet hours because they allowed him to review complicated documents without constant interruptions. After making a cup of coffee, he opened the financial reporting archive and began comparing quarterly performance figures across the previous eighteen months.
At first, everything appeared ordinary.
The department had met most of its targets, and several business units had reported steady improvements in efficiency. Management presentations celebrated reduced operating costs, stronger productivity, and faster project completion.
However, the supporting documents told a more complicated story.
In three separate quarters, the final performance reports showed substantial improvements that were not reflected in the original data submitted by operational teams.
Daniel examined the first case.
A regional distribution unit had originally reported an efficiency rate of seventy-eight percent. The final executive presentation showed eighty-nine percent.
A revision of that size was not impossible. New calculations, corrected data, or changes to measurement methods could explain the difference.
Yet the supporting notes contained no explanation.
Daniel checked the approval history.
The original report had been submitted by Marcus Reed. Two days later, the figures had been changed by a senior operations account with administrative access. The final version had been approved by Victoria Hayes.
Daniel moved to the second quarter.
Again, the original figures were lower than the final figures.
Again, the changes had been made after the initial submission.
And again, the documentation was incomplete.
He leaned back in his chair.
The pattern was concerning, but he reminded himself not to confuse suspicion with proof. A responsible investigation required context, corroboration, and an opportunity for the people involved to explain their decisions.
At nine fifteen, he contacted Marcus Reed.
They arranged to meet in a small conference room near the records department. Marcus arrived carrying a folder filled with printed spreadsheets.
He was a broad-shouldered man in his late thirties, with tired eyes and the cautious manner of someone who had learned to measure every sentence before speaking.
"Thank you for meeting with me," Daniel said.
Marcus placed the folder on the table.
"I hope this is worth the trouble."
"That depends on what the records show. I'm here to understand what happened, not to confirm a conclusion I've already reached."
Marcus opened the folder.
"These are the original quarterly figures I submitted over the past year. I kept copies because I noticed discrepancies between my calculations and the numbers presented during management reviews."
"Did you raise the issue?"
"Twice."
"What response did you receive?"
"The first time, Ms. Hayes said the executive team wanted a more consistent presentation. She told me that some figures had been adjusted to reflect management's interpretation of operational efficiency."
"Was the adjustment method documented?"
"Not in the reports I received."
"And the second time?"
Marcus exhaled slowly.
"She told me that I was focusing on minor technical details instead of understanding the department's strategic objectives."
Daniel looked at the spreadsheets.
"Did she instruct you to change the numbers yourself?"
"No. I was told to submit the original figures. The revisions happened after that."
"Do you know who made them?"
Marcus pointed to the printed audit trail.
"The system shows that the changes were made through an account assigned to the operations management office. I can't tell you who physically entered them. Several people may have had access."
Daniel nodded.
"That's an important distinction. We need the access logs before identifying an individual."
Marcus looked relieved that Daniel had made the distinction himself.
"I was worried you would think I was trying to get Ms. Hayes into trouble."
"Reporting a discrepancy is not the same as accusing someone of misconduct. If the adjustments were legitimate, the records should help establish that. If they weren't, we need to understand why."
Marcus slid another document across the table.
"This is the email I received after the second meeting."
Daniel read it carefully.
The message instructed Marcus to stop circulating alternative figures and direct any further questions through his manager. It also warned that repeated challenges to approved reporting procedures could be considered a failure to follow management direction.
The wording was not necessarily proof of wrongdoing, but it raised a question about whether legitimate concerns had been discouraged rather than investigated.
"Did you keep the original files?" Daniel asked.
"Yes. They're stored in the departmental archive, and I have copies of the emails."
"Please don't alter or delete anything. I'll ask the compliance team to preserve the relevant records through the formal process."
Marcus nodded.
After the meeting, Daniel contacted the company's compliance officer, Priya Shah, and requested an independent review of the reporting changes. He provided the dates, document references, and relevant approval histories, making clear that the review should establish whether the adjustments were authorized and supported by evidence.
Priya agreed to begin the review that afternoon.
At eleven thirty, Daniel received an unexpected invitation from Victoria Hayes.
Subject: Clarification Regarding Departmental Reporting
She requested a meeting to discuss his access to the quarterly reports.
Daniel accepted.
When he entered her office, Victoria was standing beside the window with a stack of documents in her hands.
"Mr. Brooks," she said. "I understand you've been reviewing historical performance reports."
"That's correct."
"Those reports have already been approved by management."
"I'm aware of that."
"Then I assume you understand that revisiting completed reporting periods can create unnecessary confusion."
Daniel sat down.
"Reviewing an approved report doesn't automatically invalidate it. I'm examining the supporting documentation to understand how the final figures were calculated."
Victoria placed the documents on her desk.
"The adjustments were made to improve consistency across business units."
"Could you explain the methodology used?"
"The details are technical."
"I can work with technical documentation."
Her expression tightened.
"The executive team wants accurate reporting. So do I. But accuracy also requires understanding the business context."
"Agreed. That's why I've requested an independent review."
Victoria's eyes narrowed.
"You've involved Compliance?"
"Yes. Given the discrepancies between the original figures and the approved reports, an independent review is appropriate."
"You should have discussed this with me first."
"I am discussing it with you now. You're welcome to provide any supporting records or explanation that would help establish the basis for the adjustments."
For several seconds, Victoria said nothing.
Then she pulled out a chair.
"I want to make something clear. The figures were not changed arbitrarily. We were under pressure to deliver consistent results across the division, and certain calculations needed to be standardized."
"That's useful context," Daniel replied. "Please provide the relevant methodology and approval documentation to Compliance."
Victoria stared at him.
"You don't trust my explanation?"
"I trust that the explanation should be supported by records. That protects you as well as the company."
She looked away.
Daniel rose to leave.
At the door, Victoria spoke again.
"Mr. Brooks, you're new here. You don't understand how much pressure this department faces."
He turned.
"You're right. I don't understand all the pressures yet. That's why I'm asking questions."
He left before she could respond.
Back at his workstation, Daniel found a message from Priya Shah.
The compliance officer had identified additional revisions in another reporting period, including changes made shortly before a major executive presentation.
The investigation was becoming more complicated.
Daniel opened the black portfolio and reviewed the formal scope of his appointment.
The first section emphasized one principle above all others: follow the evidence, regardless of rank or reputation.
He closed the folder and returned to the documents.
Somewhere inside Meridian's reporting system was an explanation for the numbers that didn't add up.
He intended to find it.