PART 12 – A Hidden Ledger Revealed the Real Cost of the Financing Deal, but the Most Damaging Entry Carried Ethan’s Approval

The independent examiners spent the next several days comparing the bank statements with the foundation's internal ledger. Their work was slow because the records had been created by different systems, and some entries used abbreviated descriptions that did not match the wording on the invoices. Each discrepancy required a separate check against the original source.

I helped identify the entries I had recorded months earlier. Whenever an amount matched one of my notes, I provided the date and the document reference. I did not tell the examiners what I thought the transaction meant. I showed them what I had seen and allowed them to decide whether the new records supported my recollection.

On Thursday afternoon, Daniel called to say that the examiners had located a second ledger in an archived finance folder. Unlike the main accounting ledger, which summarized payments by category, this file tracked balances among the foundation and several related companies. It appeared to have been used to monitor temporary transfers and outstanding obligations.

“Does it identify who maintained it?” I asked.

“Not conclusively. The file properties point to the finance department, but the original workstation records haven't been recovered yet.”

“What's in it?”

“Several entries that explain why the repayment figures didn't match the bank statements.”

I asked whether Rebecca could review it with me. Daniel arranged a meeting for the following morning.

When I arrived, the ledger had been printed and divided into sections. The examiner began with the credit facility. The main ledger showed that the outstanding balance had declined after several payments. The second ledger, however, recorded those same payments as temporary advances from other accounts.

The entries did not necessarily mean the transactions were improper. A company might legitimately borrow money from an affiliate and use it to repay another creditor. But the records should identify the source of the funds, the terms of the transfer, and the obligation created by the movement.

Here, several entries lacked supporting agreements.

The examiner showed me a sequence of transfers that matched the dates I had recorded six months earlier. Money moved from the foundation to a related company, then from that company to Southern Meridian Consulting. A payment was subsequently returned to the foundation and recorded as a repayment against the credit facility.

On paper, the balance appeared to have been reduced.

In the second ledger, the same amount remained outstanding as a temporary advance.

“So the debt was reduced in one record but carried forward in another,” I said.

“That's what the entries appear to show,” the examiner replied. “We need to establish whether the second ledger was intended to record a separate obligation or whether the main ledger was incomplete.”

Rebecca made a note. “And we need the supporting agreements before characterizing the transfers.”

The examiner turned to the next section.

Several entries were marked with a code that did not appear in the foundation's standard accounting manual. The code was used when a temporary advance was carried forward beyond its original repayment date. In the second ledger, the amounts accumulated over several months.

I felt a familiar unease. The code might have been an internal shorthand, but it suggested that the finance department had been tracking unresolved obligations while the main accounts presented a more reassuring picture.

“Who approved these entries?” I asked.

The examiner pointed to the approval column.

Several entries carried the initials of a finance manager. Others carried Ethan's electronic approval reference.

I leaned closer.

The earliest entry bearing Ethan's approval concerned a transfer made before the guarantee was submitted. The description identified it as an advance to cover an outstanding commercial obligation.

The next entry showed a similar transfer, followed by a repayment that had been funded through another account.

Then came the entry that changed the atmosphere in the room.

It was dated shortly after the lender's credit review. The description read: “Carry forward pending external receipt.” The amount matched a payment that had been recorded in the main ledger as settled.

Beside it was Ethan's approval reference.

I looked at Rebecca.

“Does this establish that he knew the repayment hadn't come from the expected source?”

“It establishes that his approval reference is attached to the entry,” she said. “We need to verify the electronic record and determine what he was approving. An approval code does not tell us, by itself, what information he saw.”

I understood the caution, but the discovery mattered. Ethan had repeatedly told me that he did not know the details of the accounting entries and had relied on the finance office. The ledger showed that his approval reference appeared beside several transactions related to the unresolved balance.

The examiner moved to a later section. There, the second ledger recorded an amount transferred to an account associated with a company Victor Hale had used in the earlier project. The entry was marked as a temporary advance, but no repayment date or supporting agreement was attached.

“Was this the money that appeared in the charitable program account?” I asked.

“The amount is similar, but we cannot establish that they are the same transaction without the underlying bank reference,” the examiner said.

We added the entry to the list of records requiring further examination.

By the end of the meeting, the examiners had identified several outstanding advances that did not appear in the main ledger as liabilities. They had not established the full amount of any loss, and they had not determined whether the differences resulted from deliberate concealment, poor accounting, or a combination of factors.

But the ledger made one thing clear: the financing arrangement had been more complicated than Ethan's description of a temporary loan suggested.

When I returned home, Ethan was waiting in the dining room. He had received notice that the trustees wanted a formal interview about the approval records.

“What did they show you?” he asked.

“A second ledger.”

His face tightened.

“What second ledger?”

“One that tracks temporary advances among the related accounts.”

He looked at me for several seconds.

“Where did they get it?”

“From the archived finance records.”

He turned away, walked to the sideboard, and poured himself a glass of water.

“That ledger was never intended to be a formal accounting record.”

“Then what was it intended to record?”

“Internal movements. Temporary balances. Things that weren't reflected in the main ledger until they were reconciled.”

“Some of those balances remained unresolved for months.”

“Because the expected payments were delayed.”

“Then why did the main ledger show the credit facility as repaid?”

He set the glass down.

“It showed payments being made. The accounting treatment was handled by the finance department.”

“The second ledger carries your approval reference.”

He did not respond immediately.

“I approved transactions based on the information presented to me.”

“Did you know the funds used for one repayment came from another account within the same network?”

“I knew we were moving money to cover obligations while we waited for the external receipts.”

The admission was quiet, but unmistakable.

I held his gaze.

“Then you knew the repayment hadn't come from the source identified in the schedule.”

“I knew the money had to come from somewhere.”

“That isn't what the schedule said.”

He rubbed his face.

“Charlotte, you are taking a complicated financial arrangement and reducing it to a series of accusations. We had a cash-flow problem. We moved money to keep commitments current. I believed the outstanding balances would be settled when the expected payments arrived.”

“Were the trustees told that?”

“No.”

“Why not?”

“Because the arrangement was temporary.”

“It was temporary for months.”

He raised his voice. “Because I thought it would be resolved!”

The sound echoed through the dining room.

For a moment, neither of us moved. Then he lowered his voice, as though volume had revealed more than he intended.

“I made decisions under pressure. I believed the money would come in. I believed Victor's company would recover. I believed we could repay the advances before anyone needed to examine the details.”

“And when the money didn't come in?”

“I kept trying to find a way to settle the balance.”

“By obtaining financing secured with my name?”

His face went pale.

“I did not tell anyone to forge your signature.”

“You told them the authorization had been confirmed.”

“I believed it had.”

“Did you ask me?”

He looked down.

“No.”

The word seemed to exhaust him. He sat in the nearest chair and covered his face with both hands.

For the first time, I saw him not as the man who could silence a room with a glance, but as someone confronting the consequences of decisions he had made while assuming he could control their eventual explanation.

I did not feel triumphant.

I felt tired.

“Ethan, I need you to understand something. Even if you never intended to steal money, you cannot make a financial obligation legitimate by deciding that the people whose names appear on it will eventually agree.”

He lowered his hands.

“I know.”

“Do you?”

He looked at me, and I could not tell whether the answer was sincere or simply the response he thought I needed to hear.

That evening, Rebecca called to discuss the ledger. She explained that the trustees were preparing to refer certain transactions for a more formal review because the discrepancies could not be resolved through ordinary reconciliation. The referral did not establish that a crime had occurred, but it meant the questions would no longer be limited to the foundation's internal procedures.

I asked whether Ethan's approval references would be central to the review.

“They will be relevant,” she said. “The examiners need to establish what he approved, what information was available to him, and whether the records were accurate when those approvals were given.”

“What about the guarantee?”

“That remains a separate but related issue. We still need the original document, the electronic submission history, and the lender's verification records.”

I thanked her and hung up.

I thought about the morning Ethan had struck me for asking where he had spent the night. At the time, I had believed the question concerned another lie in our marriage. I had not imagined that a much larger network of transactions might be hidden behind the same habit of secrecy.

Yet I refused to assume that the financial discrepancies explained his violence. The decision to hit me was his own, and no accounting problem could excuse it.

I made a note of that distinction in my private journal, then locked the notebook away.

The following morning, Daniel sent an update from the examiners. They had traced one of the transfers to an account associated with Victor Hale's earlier project. The account had received money from the foundation, then sent a portion onward to settle an obligation unrelated to the charitable program listed on the original invoice.

The payment had been recorded as program support, but the available documents did not establish that the program had received the money.

The examiner was seeking confirmation from the intended recipient.

I read the message twice, then forwarded it to Rebecca.

If the recipient confirmed that the funds had never arrived, the review would have a concrete discrepancy to investigate rather than another unexplained ledger entry.

A few hours later, Rebecca called.

“The organization says it never received the payment listed in the invoice,” she told me. “They have no record of the project being completed during that period.”

I sat down.

“Does that establish where the money went?”

“Not yet. It establishes that the invoice does not match the recipient's records. The examiners are tracing the payment now.”

I looked at the second ledger, which I had kept open on my desk.

The amount appeared there as a temporary advance, approved under Ethan's reference.

I could no longer accept his claim that the discrepancies were merely a matter of confusing descriptions. The records showed that money had moved through several accounts, that repayments had been funded from within the same network, and that at least one payment described as charitable support had not reached the organization named on the invoice.

Still, the identity of the person who prepared the invoice and directed the final transfer remained unresolved.

I called Daniel.

“Has Victor responded?”

“No,” he said. “But the examiners found a message sent from his office shortly after the disputed payment. It refers to a balance that needed to be cleared before the next review.”

“Cleared how?”

“That isn't explained in the message.”

I closed my eyes.

“Then we need the full correspondence.”

“We're requesting it.”

After the call, I added another line to my timeline. The financing had not merely been delayed. At least some of the money had been moved in ways that did not match the stated purpose of the payments, and the people responsible had failed to provide a complete explanation.

I still did not know whether Ethan had directed the questionable transactions, approved them without adequate scrutiny, or relied on information that had been deliberately withheld from him.

But I knew that the next stage of the review would have to answer a harder question than where the money had gone.

It would have to establish who knew the truth while the records were being prepared—and who had chosen to let everyone else believe the accounts were settled.


Click here to continue reading: PART 13: The Charity Director Denied Receiving the Money, and a Message From Victor Revealed Who Had Been Waiting for the Accounts to Close

Story Parts

The Question That Cost Me Blood, and the Secret My Husband Never Thought I Would Discover

Part 12 of 20

Previous: Part 11
Next: Part 13

Leave a Reply

Your email address will not be published. Required fields are marked *