The Payment That Is Late Every Month
A recurring delay has a cause that can be found, and usually the cause is a date somebody chose once.
Still yours, and statedTaken, never statedUnit changes; scale restarts
Five 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. Bars here are days remaining, not money: the one that took longest has no stated duration at all.
A payment that is late once is an event. A payment that is late every month is a property of the arrangement, and properties have causes that can be found and usually fixed.
The timing problem in “The Payment That Is Late Every Month” is easier to investigate when approval and payment events have separate timestamps. When teams assess consult the current platform page for 7 minute rule payroll, time and project records can identify whether work was approved before the payment cut-off without pretending to explain delays inside the banking route.
The cause is almost always a date somebody chose once, years ago, without considering anything downstream of it.
As a separate reference point for “The Payment That Is Late Every Month”, see Wolfsberg Group principles. Confirm broad guidance against current provider disclosures and qualified financial or tax advice where needed.
Distinguishing the two
Three months of your own record. A payment arriving on the 6th, the 7th and the 5th against a due date of the 1st is not late by accident.
Consistency is the diagnostic. Random lateness and reliable lateness have entirely different explanations and different fixes.
Three months is the minimum. Two can be coincidence and one is an event, and acting on either produces a conversation that goes nowhere.
The commonest cause
The payment date and the payment run do not coincide. The contract says the 1st; their finance team runs payments on the 3rd; the route takes four days.
Nothing is wrong at any step and the money arrives on the 7th every time.
That is worth saying to yourself before raising it, because the tone of the conversation depends on whether you think somebody is being slow or a calendar is.
The second commonest
The invoice arrives after the run is prepared. Payment then waits a whole cycle, which on a monthly run is a month.
This one produces the worst version of the problem and is entirely within your control to fix.
Finding out which
Ask the payer two things:
- When is the payment actually instructed?
- What is the cut-off for an invoice to be included in that run?
Two sentences in reply usually explain everything.
Most people have never been asked either question.
Recalculating backwards
From your own record: expected arrival minus actual transit equals the real instruction date. Compare that with the contract date.
Where they differ by a consistent number of days, you have found it without asking anybody.
Fixing it at your end
Invoice earlier. Where the run is on the 3rd and invoices must be in by the 25th of the previous month, invoicing on the 20th solves the whole problem.
This costs nothing, requires nobody's agreement and resolves a large share of recurring lateness.
It is also the only fix in this note that you can make today without asking anybody for anything, which is why it is worth trying before the conversation rather than after it.
Fixing it at their end
Ask for the payment date to be moved earlier, or for the run to include your invoice in the current cycle rather than the next.
Both are ordinary requests and the first is almost always granted, because the payer is indifferent to which day they instruct.
When the route is the cause
Where the instruction date is right and the transit is long, the problem is the route rather than the calendar.
That belongs with the earlier section on who chose the route, and the same measured record makes the argument.
Adjusting the due date instead
Where nothing else moves, change the contractual date to match reality. A payment due on the 7th that arrives on the 7th is on time.
That sounds like giving up and is often the right answer. It regularises the arrangement and removes a monthly irritation that was never going to be resolved.
Standing orders
For a fixed monthly amount, a standing instruction removes the invoice timing, the run timing and the human step at once.
It is the single most effective fix available and is underused because nobody suggests it.
It suits a fixed monthly figure and not a variable one, though a standing base plus an occasional top-up covers most arrangements that vary a little.
Telling them what you found
With the arithmetic. "The payment is instructed on the 3rd and takes four working days, so it arrives on the 7th. Could it be instructed on the 28th instead."
A specific request with a stated cause gets acted on. A complaint about lateness gets sympathy.
What a fixed date cannot promise
Consistency through the exceptions. A corrected arrangement still meets holidays, held payments and the occasional slow month, and a payment that is reliably on time for eight months will miss the ninth.
The point of fixing the recurring cause is not to eliminate lateness but to reduce it to the genuinely exceptional — which is a far smaller set, and one you can actually plan a buffer around rather than living inside permanently.
The test of whether it worked is the record rather than the feeling. Three months after a change, the dates either moved or they did not.