chapterone

Chapter 4 - Numbers Never Gossip

No one spoke.

Victor looked at the device record, then at Priya.

“That’s impossible.”

“The machine identifier belongs to your office laptop,” Priya said. “The altered report and the vendor-code changes originated from it.”

Victor’s face reddened. “My laptop was in this office. I did not make those changes.”

“Who else has access to this room?” Caroline asked.

“My assistant has a key. Facilities has a master key. The door is sometimes unlocked during business hours.”

“Where were you at 11:47 Monday night?”

“At home.”

Priya nodded. “Building security records show your badge exited at six-twelve. It did not return.”

The explanation should have made Victor look less guilty. Instead, the room seemed to tighten around him.

Caroline asked me to leave while they questioned him.

I returned to my desk with more questions than answers.

Brooke’s account had opened the payroll folder. Victor’s laptop had altered the report and created transactions under my name. Either two people were involved, or someone had gained access to both systems.

Brooke’s chair remained empty.

At noon, Caroline announced that she had been placed on administrative leave pending investigation. Employees were reminded again not to speculate.

Naturally, speculation became the only thing anyone wanted to do.

Some believed Brooke and Victor were working together. Others claimed Victor had framed both of us. Elena heard that federal investigators were coming, which was absurd. By two o’clock, someone had invented a secret affair between Brooke and Victor.

I refused to participate.

Numbers, unlike people, did not become more accurate when repeated.

I returned to the duplicate invoices.

Both involved North Star Freight Solutions, a small carrier Bellamy had used during a warehouse expansion. The legitimate invoices were real. The duplicates had slightly altered dates and routing numbers.

The total was not large enough to attract executive attention, but it was large enough to matter.

I searched prior months and found six more.

Together, the duplicate payments exceeded $140,000.

Victor had praised me for catching two duplicate freight payments during my first months. At the time, I assumed they were ordinary errors. Now I wondered whether I had stumbled into something intentional.

I documented each transaction without changing the records. Then I sent the list to Caroline, Priya, and Bellamy’s internal audit director.

Within an hour, I was called upstairs.

The internal audit director, Samuel Reed, occupied the chair beside Caroline. He had spent twenty years investigating financial misconduct and possessed the unsettling ability to remain silent until other people filled the space.

“Walk us through what you found,” he said.

I explained the repeated invoice numbers, altered vendor codes, and payment-routing changes.

“Why were you reviewing these transactions?” he asked.

“Because two duplicates appeared under my username.”

“And you’re certain you didn’t create them?”

“Yes.”

Samuel turned his laptop toward me.

“Do you recognize this approval note?”

The note read: Confirmed with J.M. Vendor exception approved.

“My initials are J.M., but I didn’t write that.”

“Who uses your initials at work?”

“Everyone who emails me.”

He nodded.

“Did Brooke know you had previously flagged North Star invoices?”

“Yes. She told me not to worry about them because freight vendors often rebill.”

Caroline looked up. “When did she say that?”

“About three weeks ago.”

Samuel asked me to repeat the conversation exactly.

I remembered standing beside Brooke’s desk with two invoices in my hand. She had barely glanced at them before saying, “North Star does that all the time. Mark the newer one as corrected and move on.”

Instead, I asked Victor, who confirmed one was a duplicate and thanked me for noticing.

“What happened after Victor corrected it?” Samuel asked.

“I don’t know.”

“You found the payment reentered under another code.”

“Yes.”

The room went quiet.

That afternoon, Priya discovered how Victor’s laptop had been used. The device was not physically opened Monday night. Someone had connected remotely through an administrative support tool normally reserved for IT maintenance.

Mason’s department controlled that tool.

Because of our relationship, suspicion shifted toward him immediately.

Caroline called him into a separate interview. I was not allowed to attend, and for the first time since the investigation began, Mason seemed afraid.

“I didn’t access Victor’s machine,” he told me before going upstairs.

“I know.”

“But someone used an IT credential.”

“Then they’ll find out whose.”

He gave me a tired smile. “Facts first?”

“Facts first.”

Two hours later, he emerged with his employee badge still attached to his belt, which I took as a good sign.

The remote session had been initiated with the credentials of an IT contractor named Colin Mercer—the same contract employee who admitted photographing Mason entering the HR meeting.

Security located Colin in a server room preparing to leave the building. Inside his backpack, they found a company laptop, two unauthorized storage drives, and printed copies of vendor-payment reports.

He asked for an attorney before answering questions.

By evening, the broad outline emerged.

Colin had helped maintain Bellamy’s vendor-payment system. He possessed enough technical access to manipulate exported audit reports and remotely enter authorized devices. Brooke had contacted him Monday morning because they had known each other from the marketing floor. She asked him to photograph Mason and later gave him information about my relationship, my account, and the HR complaint.

But whether Brooke knowingly participated in financial fraud remained unclear.

Colin had used her credentials to access payroll data. He had used Victor’s laptop to alter records. He had placed my name on the report because the public gossip made me a believable target.

The timing was not random.

Brooke’s complaint had created the perfect distraction.

The next day, Bellamy executives met behind closed doors. North Star’s payments were frozen. Outside forensic accountants arrived with rolling cases and serious expressions.

Brooke remained on leave.

Mason was cleared of involvement, but he was furious that Colin had exploited his department’s tools.

“I recommended him for an extended contract,” Mason said at home. “I told my manager he was reliable.”

“You couldn’t have known.”

“I should have reviewed his access more carefully.”

“That isn’t the same as causing this.”

He looked unconvinced.

We were both learning how quickly shame attaches itself to innocent people. It did not require logic. It only needed proximity.

Friday afternoon, Caroline asked me to attend one more meeting.

Brooke was already seated when I entered.

She looked different. Her hair was pulled back carelessly, and the confidence that once seemed permanent had disappeared. A lawyer sat beside her.

Caroline explained that Brooke had requested an opportunity to provide information concerning Colin.

Her lawyer placed a phone on the table.

Brooke looked at me.

“I didn’t know about the money,” she said. “But I gave Colin your employee information.”

My throat tightened.

“Why?”

“Because I wanted him to prove Mason was protecting you.”

She wiped her palms against her skirt.

“Colin told me he could find evidence that you had used Mason’s access. I sent him your schedule, your username, and the spreadsheet you had opened. I thought he would expose you.”

“You wanted me fired.”

Brooke lowered her eyes.

“Yes.”

Caroline’s expression remained controlled. “Tell Jenna what you discovered this morning.”

Brooke looked toward her lawyer, who nodded.

“I found messages Colin sent to someone at North Star,” she said. “They’ve been stealing from Bellamy for more than a year.”

“Who was he messaging?”

Brooke slid the phone toward me.

The contact name was not Victor.

May you like

It was someone I never would have suspected.

Caroline Price.

Related Stories

Other posts