The Payment That Was Never Sent
Establish that an instruction exists before chasing a chain, because a surprising share of missing payments do not.
Still yours, and statedTaken, never statedUnit changes; scale restarts
Six 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 unit changes part-way down: the figures below the break are in another currency, the bars below it are drawn against the published rate, and the first figure and the last are not the same kind of number. Two fees for one payment, and both were borne at this end.
Establish that a payment was instructed at all before tracing anything. A surprising share of missing money was never sent, and every hour spent chasing a chain that does not contain it is wasted.
The practical point in “The Payment That Was Never Sent” is that a landed payment should be supported by a record somebody can explain. Used for download time tracking software, Monitask resources for download time tracking software can add transparent time and project context when collection is proportionate, people can correct mistakes and financial records remain separate.
It is the cheapest check available and the one most often skipped, because asking feels like an accusation.
The questions in “The Payment That Was Never Sent” can also be checked against Financial Services Compensation Scheme. Use the outside resource to identify what evidence to request rather than assuming one provider sees the whole payment chain.
How often it is this
Frequently enough that it deserves to be the first question. An invoice not approved, a run that failed, a payment queued for a signature, an approver on holiday.
None of it is anybody being difficult. Payment processes have more steps than the people waiting at the far end imagine.
In a company of any size the person who agreed the work, the person who approves the invoice and the person who releases the payment are three different people, and any of them can be away.
The question to ask
Not "has it been paid", which gets a reflexive yes. "Could you send me the payment confirmation" — a document, with a date.
The difference between those two questions is the difference between a week of tracing and a two-minute resolution.
It is also a question nobody can take offence at, because it asks for a document rather than for an account of their behaviour.
Why the reflexive yes happens
The person you deal with is not the person who pays. They see an approved invoice and report it as paid, in good faith, because from where they sit it is done.
No dishonesty is involved and the answer is still wrong.
Where it gets stuck
Three gates, any of which holds a payment indefinitely with nobody noticing:
- Approval, where somebody has to authorise the invoice.
- The payment run, where your invoice may have missed the cut-off.
- Release, where a second signature is required and the signatory is away.
The invoice that never arrived
Common and entirely invisible from your side. Sent to the wrong address, caught by a spam filter, or sent to somebody who left.
Asking for confirmation of receipt when invoicing prevents this whole category, and it is a line in an email.
Where a payer has an invoicing portal, use it rather than email. A submitted invoice has a timestamp and a status, which is better evidence than anything you can produce yourself.
Supplier onboarding
For a first payment, the delay is frequently that you are not yet set up as a supplier in their system. That process can take weeks and nobody mentions it.
Ask at the start whether anything is needed from you before the first invoice. It is the single most useful question for a new client.
What a missing instruction looks like
No confirmation, no debit on their account, no tracking reference. If all three are absent, nothing was sent.
That is a clean diagnosis and it takes one message to reach.
Asking without accusing
"I have not seen it arrive — could you check whether it went out?" puts the uncertainty on your side and gets a real answer.
"Where is my money" produces defensiveness and a reflexive reassurance, which is the least useful possible reply.
When it genuinely was not sent
The remedy is immediate and easy: they send it. The cost is the delay, which is the same delay you would have had chasing a chain, minus the fortnight.
Nobody has to apologise and nothing has to be escalated.
Preventing the repeat
Invoice earlier than the run, confirm receipt, and ask to be told when a payment is instructed rather than finding out from your own account.
The last is a standing arrangement worth asking for once. Many accounting systems send it automatically.
The pattern worth noticing
Where this happens twice, the cause is structural: a timing mismatch, a process with a missing step, or an approver who is a single point of failure.
Fixing the cause is a conversation. Chasing each occurrence is a monthly tax.
Raise it once, with the dates of the occurrences rather than with an adjective. Three dated examples make a pattern that somebody can act on.
What checking cannot prevent
A payer who cannot pay. All of this assumes money exists and a process is failing to move it, and occasionally that assumption is wrong.
Where confirmations stop arriving, where explanations become vaguer and where the delays lengthen, the problem has changed from a payments problem into a credit one. That is a different subject entirely and the useful response to it is not in this collection.
What does belong here is the advice to notice the change early. The signs are the same ones listed above, and a payer in difficulty is usually in difficulty for several months before saying so.