# The Boss Remembers Is Not a Control

> That was the number in the draft note to my bookkeeper, in a column labeled "outstanding," next to the name of a client who, I was pretty sure, did not owe me twelve thousand dollars.

By MCAFax · Published September 9, 2026 · Updated October 2, 2026
Section: Markets & Main Street › Small Business · Series: Confessions (https://mcafax.com/notebook/series/confessions)
Canonical: https://mcafax.com/notebook/the-books-said-eleven
Source: MCAFax, The Broker's Notebook (https://mcafax.com/notebook). MCAFax is not a lender or a law firm.

---

$12,000.

That was the number in the draft note to my bookkeeper, in a column labeled "outstanding," next to the name of a client who, I was pretty sure, did not owe me twelve thousand dollars.

I was pretty sure because I remembered the phone call. Their finance guy, a cheerful man who ends every sentence with "boom," had called two weeks earlier to argue the fee down. We settled at seven. He wired it the same afternoon. "Boom," he said.

The books never heard about any of it. The note had matched the client on the amount instead of the name, and the amount was from before the argument. So there it sat: a number that had been true once, quoted like it was taken this morning.

I caught it because I remembered the money. Hold onto that sentence, because it is the scariest one in this post.

In every shop I have ever worked, "the boss remembers" is not a control. It is a coin flip that has been landing heads.

Years ago I watched an underwriter price a nail salon off a statement that was ninety days old. Beautiful file. Steady deposits. He approved a big number. What the statement didn't show was that the landlord had raised the rent in month two and the owner had quietly stacked two other advances in month three. By the time the first debit hit, the beautiful file was a photograph of a business that no longer existed.

The underwriter wasn't stupid. He just trusted the picture without checking the date on it.

So I went back through my own books like a stranger would. It was ugly in small ways.

A government fine I had been carrying at three hundred dollars cost three hundred and eighty when I finally paid it. Nobody explained the extra eighty. Carrying charges never introduce themselves.

A client listed as "quiet for twenty-six days" had actually been silent for forty-eight. The date on the file was the last time we wrote to them, not the last time they answered. The file looked half its age.

A client the books said hadn't started had been live for a week. Twelve grand back on the table, in the other direction.

Every number in a file is a photograph, and the date on the photograph is the last time somebody actually looked. Files don't lie, exactly. They age, quietly, while everyone keeps quoting them.

The last thing I checked was the one I was most confident about. My to-do list said I had eleven unsent drafts sitting in my outbox. Eleven. I had been saying "eleven" out loud for days, like a man who knows his own business.

I opened the folder and counted with my finger on the screen.

Sixteen.

---

## Questions readers actually ask

### Why does my accounting software show different numbers than my bank account?

Files do not lie so much as they age the moment you stop updating them. A client balance can sit at twelve thousand dollars on paper even after a seven-thousand-dollar settlement wire clears, simply because an adjustment never got entered. When systems match on amounts rather than transaction details, manual drift quickly replaces reality.

### Is relying on memory an acceptable internal control for business finances?

Relying on the owner's memory is an accident, not a control. If catching a multi-thousand-dollar receivable error or an unrecorded payroll addition depends on personal recall, your reporting infrastructure has failed. Once operations get hectic, memory slips and those invisible variances turn into permanent losses.

### How do outdated records impact day-to-day business decisions?

Every number in a file represents a photograph dated the last time someone looked. Treating a client silence as twenty-six days instead of forty-eight, or carrying a fine at three hundred dollars when penalties pushed it to three-eighty, means making commitments on stale data. Before pricing a deal or forecasting payroll, confirm the actual timestamp on the entry.

*Confessions is a series of stories from inside the MCA world. Names and details are changed, and some are dramatized.*

## Questions readers ask

**Why does my accounting software show different numbers than my bank account?**

Files do not lie so much as they age the moment you stop updating them. A client balance can sit at twelve thousand dollars on paper even after a seven-thousand-dollar settlement wire clears, simply because an adjustment never got entered. When systems match on amounts rather than transaction details, manual drift quickly replaces reality.

**Is relying on memory an acceptable internal control for business finances?**

Relying on the owner's memory is an accident, not a control. If catching a multi-thousand-dollar receivable error or an unrecorded payroll addition depends on personal recall, your reporting infrastructure has failed. Once operations get hectic, memory slips and those invisible variances turn into permanent losses.

**How do outdated records impact day-to-day business decisions?**

Every number in a file represents a photograph dated the last time someone looked. Treating a client silence as twenty-six days instead of forty-eight, or carrying a fine at three hundred dollars when penalties pushed it to three-eighty, means making commitments on stale data. Before pricing a deal or forecasting payroll, confirm the actual timestamp on the entry.
