Chapter 2 - The Percentage He Shouldn't Have Known

“What?”
Daniel looked at me across the kitchen island, his fork suspended above a cardboard container of pad Thai. For a second, he seemed almost surprised that I had heard him.
“My share,” he said. “Twenty-five percent. I just assumed spouses usually put each other first.”
I set my fork down. We had been married for nine years, and Daniel had managed most of our household bills for almost as long. He knew which utility payments came due on the fifteenth. He knew the interest rate on our mortgage and the exact amount in our joint savings. But I had never given him the password to my employer's benefits account.
“How do you know the percentage?” I asked.
He shrugged. “You must have told me.”
“I don't remember doing that.”
“Well, I work in financial planning, Claire. I pay attention to things like that.”
It was a reasonable answer delivered just a little too quickly.
I looked down at the food between us. My sister Emily was the primary beneficiary because she was the person I trusted to carry out the instructions I'd written for my goddaughter, Hannah. I had made those arrangements years earlier, before Daniel's business took on its current shape. They weren't punishment. They were promises to people I loved.
“Emily gets half,” Daniel said, confirming precisely what I was thinking. “Hannah gets a quarter. And I get what's left.”
He knew all three allocations.
The conversation might have been different if he had asked me about them. Instead, he spoke as though my decision required his approval.
“Those are the instructions I chose,” I said.
“Years ago. Things change.”
“Some things do.”
Daniel pushed his container away. He wasn't shouting. We rarely shouted. Our arguments had always sounded like meetings at which one person had forgotten to circulate an agenda.
“I just don't understand why your sister needs more protection than your husband.”
“Emily has responsibilities to Hannah that I want covered. You and I also have assets together.”
His jaw tightened. Then, as suddenly as the tension had appeared, he smiled and asked whether I wanted the remaining spring rolls. I said no. He carried the containers to the refrigerator, and our ordinary evening resumed.
But I couldn't make the question ordinary again.
Three months earlier, my insurance administrator had emailed me about a beneficiary change I had never requested. I had checked the account, found my original percentages intact, and deleted the message. Until that dinner, I had convinced myself the notice was an error. Now I wondered whether an error could explain how Daniel knew information I hadn't shared.
The following morning, I sat in my car outside the office and opened my benefits account again. The allocations were still fifty percent to Emily, twenty-five to Hannah, and twenty-five to Daniel. The portal showed no completed amendment.
I nearly closed the browser.
Then I noticed a separate section labeled pending requests.
One item was marked incomplete. It had been opened on the same date as the deleted email. The site offered only a reference number and a link to contact the administrator. No copy of the document was available to me.
That distinction mattered. An unchanged account was not proof that nobody had tried to change it.
I wrote down the reference number on the back of a parking receipt. It felt ridiculous, hiding an insurance number in my own car. But after that conversation with Daniel, I didn't want a reminder appearing on the computer we sometimes shared at home.
At work, I spent the morning reviewing vendor risk reports. I could identify weaknesses in companies I'd never visited. Yet I kept losing my place in the same spreadsheet because I was thinking about a question my husband had asked over Thai food.
Near lunchtime, I called the number printed on my benefits statement. After a long wait, a representative confirmed that the item was still pending and could not take effect without additional verification.
“Who submitted it?” I asked.
“I can't disclose every detail over the phone,” she said. “But you can request an activity history through our secure process.”
“Please send the instructions.”
“Is there reason to believe this request wasn't yours?”
I looked at the glass walls of the conference rooms around me. People moved between meetings with coffee cups and open laptops. Nothing in the office reflected what I was beginning to feel.
“I didn't submit it,” I said.
The representative went quiet for a moment. When she spoke again, her voice had become formal. She explained how to place an administrative hold on beneficiary changes while the history was reviewed. I asked her to do it.
That afternoon, Daniel texted to ask whether I wanted reservations for Saturday. I stared at his message until the screen dimmed. Then I answered that Saturday was fine.
I didn't ask him why he knew the percentages. I didn't tell him about the hold.
There was a time when silence between us meant neither person had anything urgent to say. That week, it meant I was listening more carefully than I ever had before.
When I got home, Daniel was at the dining table with his laptop open. A folder of financial statements lay beside him. He closed the computer as I came through the doorway, something so small I might not have noticed it a month earlier.
“Busy day?” he asked.
“Ordinary,” I said.
He smiled. “Those are the good ones.”
I put my keys in their usual bowl and looked at the closed laptop. I had no idea what was in it, and no right to invent an explanation simply because I was frightened.
But I knew one thing now. Someone had tried to alter a document involving almost two million dollars. My husband knew exactly how the money was divided. And the request was still there, waiting for a verification I had never agreed to give.
That night, as Daniel slept, I saved the reference number in an encrypted note on my work phone. I made a second note of what he'd said at dinner, including his exact words.
May you like
I wasn't building a case against my husband. Not yet.
I was making sure that if the next question came, I wouldn't have to depend on memory alone.