The supplier who calls on day thirty-two
The invoice is dated the first of the month, on thirty-day terms. It is coded and entered on the third, with the due date recorded correctly, and nothing else happens. The purchasing manager next opens the accounting system on the second of the following month, finds the invoice two days overdue and approves it on the spot. The supplier had called the day before: day thirty-two. The invoice was never lost and the date was never wrong. The information lived where nobody looked.
The ledger is right and nobody is reading it
Every accounting system has a payables calendar. It is complete and accurate, and it is opened by the people who enter invoices, not by the people who approve payments. The purchasing manager, the general manager, the owner who signs above a certain amount: none of them browse the ledger. They wait to be asked.
So the asking has to be organised. It has to be a message that arrives on its own, on a schedule, whether or not anyone thought about payments that morning. A reminder somebody has to set, or a report somebody has to open, is the same problem in a different place.
What the message contains
The payment list is a short email with three sections and a one-line summary at the top. It is built from the accounting system’s own open items, so it never becomes a second set of books. The ledger remains the only source of truth; the email is how that truth reaches the person who acts on it.
- Due today: supplier, invoice reference, amount, currency. One line each.
- Due this week: the same, so cash can be planned rather than found out about on the day.
- Overdue, with the number of days, because an invoice three days late and one thirty days late are different conversations.
- The summary line: how many in each section, so the reader knows at a glance whether today needs their attention at all.
Each amount in its own currency
A resort that sells in one currency and buys in several does not have a total payable. It has several. Add them together at whatever rate somebody last typed in and you have a number no treasurer will act on.
So the list groups by currency, shows each group’s own total, and stops there. It looks less tidy than a single figure. It is the only version that is true, and a finance director will trust a list that refuses to invent a number long before they trust one that does.
A stream of its own
From the purchasing manager’s side, the list has nothing to do with the revenue summary that goes to the general manager or with the alerts that go to whoever maintains the feeds. It has its own schedule, its own recipients and its own channel. A late night audit at one property is irrelevant to it. If the accounting export itself is late, the list says so instead of sending a stale one.
Every send is recorded: when, to whom, what was in it, whether it arrived. When somebody says they were never told an invoice was due, the answer is a lookup rather than an argument. And when the message does not arrive on a morning it should have, the silence is itself a signal, and the source monitor treats it as one.
Add the currencies together and you have a number no treasurer will act on.
What changes on the other end of the phone
Suppliers do not remember the invoices that were paid on time. They remember the ones they had to chase, and they adjust their terms accordingly: shorter credit, less flexibility in a busy month, the polite refusal when the resort needs something delivered on a Sunday.
A payment list that arrives every morning does not make the hotel richer. It makes it predictable, and terms are priced on how predictably you pay. A small habit, and it shows up in next year’s terms.