Why the same payment settles on four different days
Four rails, one payment run, four settlement dates. The reasons are not technical, and knowing them is most of the job.
A finance team sends five payments on a Tuesday morning. One is in the supplier’s account before the coffee is cold. One arrives on Wednesday. One arrives on Thursday afternoon and is short by forty dollars. One is a card authorisation that shows as paid immediately and does not reach the acquirer until Friday. The fifth is pulled back by the payer before lunch and never arrives at all.
Nothing went wrong. That is four rails behaving exactly as published, plus a recall.
Sending is not settling
The word “sent” is doing a lot of work in most payment tools. Sending is the instruction leaving your side. Settlement is the moment the money is irrevocably the supplier’s. On Faster Payments those two moments are seconds apart. On a SWIFT payment through one correspondent they are two business days apart, and the gap is where every awkward conversation with a supplier lives.
If your system only tells you a payment was sent, it has told you the easy half.
The four gaps, briefly
- Faster Payments clears in seconds and runs at weekends. There is no cut-off to miss.
- A SEPA credit transfer has a cut-off, usually mid-afternoon central European time. Miss it and the payment takes the next business day, which over a Friday means Monday.
- SWIFT through one correspondent typically lands on the second business day. A second correspondent adds a day and a fee you cannot see in advance, which is where the missing forty dollars came from.
- A commercial card authorises instantly and settles to the acquirer last of all. It is the rail that confirms first and finishes last, and that inversion catches people out more than any of the others.
Recalls are an outcome, not an error
A payer can pull a payment back before it settles. When that happens there is no settlement date to report, because there will not be one. Systems that show the payment as “pending” forever are not being cautious, they are being wrong, and a ledger cannot close against a pending line that will never resolve.
Report it as recalled. It is a finished state.
What to do with this
Ask your payments provider for the settlement date at the point of approval, not the send confirmation afterwards. If they will not give you one, the information exists and they have chosen not to show it to you.
Kelvern draws every payment run against the same settlement table, and you can watch the four rails come apart on it.