Choosing the Day
A date early in the week, agreed once, removes most of the delay that nobody intended.
Still yours, and statedTaken, never statedUnit changes; scale restarts
Three steps from instruction to arrival. One step carries no figure: the hatching marks where the money leaves and is not drawn to scale, because there is no figure to draw. Nothing here adds them up, since an amount you cannot see is not an amount you can subtract. The section that is about the near end, because the far end is not available.
A payment date early in the week and comfortably inside the month removes most of the lateness in this subject. It costs the payer nothing, it requires no system change, and it is agreed in one message.
The practical point in “Choosing the Day” is that a landed payment should be supported by a record somebody can explain. Used for time tracking with screenshots, a practical approach to time tracking with screenshots can add transparent time and project context when collection is proportionate, people can correct mistakes and financial records remain separate.
It is the cheapest improvement available and the one people never think to ask for.
The questions in “Choosing the Day” can also be checked against FinCEN guidance. Use the outside resource to identify what evidence to request rather than assuming one provider sees the whole payment chain.
Why the day matters at all
A payment moves only on days when both ends are open. A date chosen without reference to that compounds every other delay in the chain.
The difference between a good date and a bad one is routinely three to five days on the same route with the same banks.
Nothing about the route changes. The same money, the same institutions and the same fees arrive at a different time because of a number in a contract.
The worst date
The last working day of the month. It collides with everybody's month-end volume, leaves no room for a missed cut-off, and any slip pushes the payment into the following month.
It is also the most common date in existence, because it matches how companies close their books.
The second worst
Friday. An instruction after the cut-off waits until Monday, and a single correspondent then puts arrival into the middle of the following week.
Nothing is wrong with the route. The calendar did it.
The good date
| Date | What happens to a one-day slip |
|---|---|
| Tuesday the 20th | Arrives a day later, mid-month |
| Friday the 20th | Arrives after a weekend |
| Friday the 30th | Arrives in the following month |
Three working days in front of it before a weekend, and ten days of margin before the month ends.
Making the request
"Could the payment date move to the 20th rather than the 30th." One sentence, no justification needed.
Payers are almost entirely indifferent to which day they instruct, as long as it is a date their run supports.
Matching it to their run
Better still: ask when their payment run happens and pick the date that lands in it cleanly.
A date chosen to suit their process is agreed instantly and implemented correctly, which a date chosen to suit yours sometimes is not.
It also survives a change of staff, because it matches what the system already does rather than depending on somebody remembering an exception.
Invoicing to match
Where payment follows an invoice, the invoice has to be in before the run is prepared, usually several days earlier than people assume.
Ask for the cut-off and invoice a few days before it. This fixes more recurring lateness than any other single act.
Set a repeating reminder for the invoice date rather than relying on the end of a month. The two are rarely the same and only one of them matters.
Avoiding known closures
Where your corridor has a predictable annual slowdown, move the payment forward for those months specifically.
A one-off request before a known closure is easy to agree and is forgotten by nobody, because it comes with a reason.
A standing instruction instead
A fixed monthly amount can be instructed automatically on a chosen date, removing the invoice timing, the run and the human step at once.
For a stable arrangement it is the best available answer and is rarely suggested by anybody.
Confirming the change took effect
Check the first payment after the change against your record. Date changes agreed in correspondence and not implemented are common enough to be worth one check.
Then leave it alone.
A date that works is worth more than a date that is optimal. Revisiting it every few months produces churn at the payer's end and eventually a reluctance to change anything at all.
When the date cannot move
Some payers genuinely have one run a month on a fixed date. Where that is true, the lever moves to the route and to your own buffer.
Knowing which it is saves asking repeatedly for something that cannot happen.
What a date cannot control
The exceptions. A well-chosen date removes the delays that were structural and leaves the ones that are genuinely unpredictable: a hold, an outage, a holiday nobody saw.
That residue is smaller and more survivable, which is the whole point. The purpose of choosing the day well is not to make payments punctual but to make the unpunctual ones rare enough to plan around, and a buffer sized to the route does the rest.
The combination is what works: a good date removes the predictable delays and the buffer absorbs what is left, and neither alone is enough.