Must read stuff · No. 17
The payment run and the promise it cannot see
The accounting system schedules payments by the date printed on the invoice. The bookkeeper schedules them by the date she promised on the phone. Both are real, only one lives in the software, and the firm's reputation depends on the one that does not.

It is a Thursday afternoon in March, and the radiators in the office have gone quiet. Margareta is erasing a pencil mark on her desk calendar. The calendar is a freebie from a building supplier, a week to a page, and every square has a name and an amount written in pencil. She rubs out the sixteenth and writes the same name and amount into the eighteenth, pressing hard enough that the paper puckers. On the screen in front of her, the accounting system shows the same invoice as approved and scheduled. The two do not agree. She is fixing the one that has a memory.
The queue and the call
The payment run is a queue. Every invoice that has been entered, approved and given a due date sits in it, and on the appointed morning the software pays what is in the queue. It is fast, it is auditable, and it does not forget an invoice. I have set up dozens of these runs for small firms, and I have watched owners relax when they see the list of payments go out on time. The relief is real. The queue does what a queue does.
What the queue cannot hold is the phone call. The call where a supplier agrees to wait until the fifteenth because the firm’s biggest customer pays late every February. The call where the owner promises a plumber that the check will go out on Friday, not Tuesday, because that is when the money lands. The call where a supplier says, take your time, I know you. Those promises have no field. They live in Margareta’s calendar, in pencil, and she reconciles them by hand every week.
She has been doing this for nineteen years. The calendar is the record of what was said, and the software is the record of what was typed. When they disagree, she trusts the calendar, because the calendar is where the promise lives.
The dignity of the pencil mark
There is a temptation to call this a workaround, a legacy habit that should be retired. I have called it that myself. But watch her work for an hour and the word that comes to mind is care. She knows which suppliers will call if a payment is a day late, and which ones will not. She knows which promises were made by the owner in a site meeting and never written down anywhere else. She knows that the firm’s reputation lives in the phone calls, and the phone calls are in her calendar.
The system is better at the parts that can be counted. It does not lose an invoice. It does not forget a due date. It produces a clean audit trail. The calendar is slower, private, and it remembers the conversation. That is the tradeoff, and it is not a small one.
The strongest opposing view
A promise that lives only in one person’s calendar is a promise waiting to be broken by a vacation, an illness or a memory. The firm would be better served by a notes field on the invoice that everyone can see. I have argued for exactly that in other offices, and I have been right. Visibility is how a small firm survives the week when the bookkeeper is out.
Margareta has never missed a payment she promised. She has also never taken a three-week vacation. The calendar works because she is there. That is a person, not a system. And a person is a single point of failure with a pencil.
What the portal cannot see
Small firms are being pushed toward automated payment runs and supplier portals that promise visibility. The visibility is real. The portal shows every invoice and every due date. What it cannot show is the phone call, and the phone call is often the thing that keeps a supplier from putting the firm on stop. The portal is a record that can be quoted back. Sometimes that is exactly what a small firm wants. Sometimes it is not. A promise made on the phone can be renegotiated. A promise written into a portal is a commitment with a timestamp.
I might be wrong about the calendar being the right place. Margareta’s system works because she is the one holding it, and that is not a system at all. It is a person, and persons take vacations. The fix is not to take the calendar away. It is to ask what happens when she is not there, and to write that down somewhere the software can see.
She closes the calendar at the end of the afternoon. The pencil mark for the fifteenth is still there, smudged where her hand rested. The screen behind it shows the invoice as scheduled for the twelfth. She will fix that on Monday, the way she has fixed it every Monday for nineteen years, and the supplier will be paid on the day she promised, not the day the system chose.
#Essay #bookkeeping #smallbusiness #accounting #small business #payment run #promises #accounting software