He Came Back Running (Maya and Mason) novel Chapter 95

Chapter 95

Maya’s POV

The archive request went through Lila at nine-forty. Not the full request I had been specific about that.

Specific enough to get what I needed without announcing what I was looking for. Three years of historical financial records, framed as governance review, the kind of request that arrived regularly from majority shareholders asserting their oversight function

Routine. Unremarkable. Exactly as I intended….

The files came through to my secure drive at ten-fifteen

I locked the office door.

And began.

The first hour produced nothing unusual

Standard operational records… the kind that existed in every company’s archive, the accumulated evidence of a business doing its business. Quarterly reports. Vendor payments. Board resolutions documented in the careful, formal language of people who understood they were creating a paper trail and had arranged the trail accordingly.

I read systematically, the way I read everything…. sequentially, noting the patterns before the anomalies, establishing the baseline before looking for the deviation from it.

The baseline, for Mason Empire in the three years before my father died, was orderly

Which was the first thing that was wrong.

I knew this company like the back of my palm….

I had spent at least seven years inside it, learning its rhythms, its operational tics, the specific ways it moved money and made decisions and managed the gap between what the records showed and what the rooms knew. No company this size was orderly across three consecutive years

There were always corrections, reversals, the small untidiness of real operations encountering real conditions.

These records were clean in the way things were clean when someone had been through them.

Not falsified… not obviously. But smoothed. The quality of a room that has been tidied before a guest arrives.

I pulled the vendor payment files…..

Went through them line by line.

Missing signatures appeared first in the second year.

Not on major transactions… on the smaller ones, the category of payment that fell below the threshold requiring full board approval and therefore required only departmental sign-off. Three separate payments across six months, each below the threshold, each missing the second approval signature that the company’s internal policy required.

Individually, each one was an administrative oversight

Together, they formed a pattern

1/4

+25 Bonus

I wrote the amounts on the legal pad.

Added them.

The total, across three transactions, was not small.

I pulled the account references….

Each payment had gone through a different account…. not the company’s primary operational accounts, but subsidiary accounts that existed in the corporate structure for specific project purposes. I cross-referenced the project codes.

Two of the three project codes were legitimate….. ongoing operational initiatives that I could verify against the corresponding project documentation.

The third code appeared nowhere in the project registry.

It had a code. It had an account. It had three payments processed through it over six months.

It had no project.

I sat very still.

Then I pulled every transaction associated with that account code across the full three-year period.

Fourteen transactions

The same pattern… below threshold, administrative sign-off, the second signature either missing or appearing as a signature I didn’t recognise from any other document in the archive.

I photographed the signature on my phone

Sent it to Marcus with three words: Identify this name.

By noon I had stopped noticing the time.

The legal pad had four pages of notes. The laptop screen showed six open documents, cross-referenced with three separate spreadsheets I had built in the past two hours to map the transaction flows.

The money had moved.

Not out of the company directly….that would have been too visible. It had moved laterally, through the phantom project account, into a structure I was still mapping. The structure had the specific, deliberate architecture of something built by someone who understood corporate finance well enough to hide within it.

My father had understood corporate finance

The thought arrived and I let it sit.

He had understood it well enough to build a trust structure that had survived a divorce, a governance challenge, and three legal firms attempting to find its edges. He had understood it well enough to annotate a single transaction page with a sentence in the margin and know that the sentence was the key.

Some truths destroy families….

He had been looking at these records

He had found the phantom account.

2/4

+25 Bonus

He had kept the page

And then he had died.

The structural changes appeared in the third year.

Twelve months before his death, a series of board resolutions that had been passed in closed session, outside the standard calendar of meetings, with a reduced quorum that the articles of association technically permitted but that I had never seen used in any other context in the company’s history.

The resolutions restructured the reporting lines for two subsidiary divisions.

Both subsidiaries were in the geographic region where the phantom account’s transactions had been concentrated.

The restructuring had been approved by four board members.

I cross-referenced the four names against the transaction records.

Three of the four appeared as approval signatures on the phantom account’s payments.

I wrote their names on the legal pad.

Then I went back to the closed-session resolutions and looked at the date again.

Fourteen months before my father died

I looked at the names of the board members who had approved the resolutions.

Looked at the list of the fourteen transactions.

Started cross-referencing the timing… which transactions had occurred before the restructuring, which after, whether the pattern changed.

The pattern didn’t change.

Which meant the restructuring hadn’t been about the divisions.

It had been about creating cover for something that was already happening….

I was three pages into a new document when the transaction report loaded.

The final year…. the twelve months before his death. I had been working forward chronologically, and this was the last section, the period I had been approaching with the specific, controlled attention of someone who understood that whatever they were about to find had weight.

I went through it line by line

Most of it was consistent with the pattern I had already mapped….

And then…. third page, fourth column, a transaction dated the night before he died.

I read it.

Read it again

The amount was larger than the others. Not so large as to be immediately flagrant…. large enough, in context, to be significant. The project code was the phantom one

The approval signature was not the unknown one.

3/4

+25 Bonus

It was a name I recognised.

A name I had seen this week, in a family dining room, attached to a man who had looked at me all evening with cold assessment and had called Zara that night to tell her she was the better choice for his son’s future.

Richard Voss….

I sat at my desk with the transaction report on my screen and my father’s annotated page beside it and the legal pad full of four hours of work, and I felt the cold arrive in the specific way it arrived when a fact settled into place and the room around it changed shape

Richard Voss had approved a transaction through a phantom account the night before Edwin Hargrove my father

died.

I looked at the date.

I looked at Richard’s name.

I looked at the window, where the city was doing its ordinary afternoon

My hand found my stomach.

Comments

Support

Share

4/4