Why the same payment run settles on four different days

Five payments go out on a Tuesday morning. One lands before the coffee is cold. One arrives on Wednesday. One arrives on Thursday, short by forty dollars. One is a card payment that shows as paid at once and reaches the acquirer on Friday. The fifth is pulled back before lunch.

Nothing went wrong. Four rails behaved as published, plus a recall.

Sending is not settling

Sending is the instruction leaving your side. Settlement is the moment the money is irrevocably the supplier’s. On Faster Payments those are seconds apart. On SWIFT through one correspondent, two business days. That gap is where the awkward supplier calls live.

The four gaps

• Faster Payments clears in seconds and runs at weekends. There is no cut-off to miss.
• SEPA credit transfer cuts off at 14:00 CET. Miss it and the payment takes the next business day, which over a Friday means Monday.
• SWIFT through one correspondent lands on the second business day. A second correspondent adds a day and a fee you cannot see in advance. That is the missing forty dollars.
• A commercial card authorises instantly and settles to the acquirer last of all. The rail that confirms first finishes last.

Recalls are an outcome, not an error

A payer can pull a payment back before it settles, and there is then no settlement date to report. Showing it as “pending” forever is not caution, it is wrong: a ledger cannot close against a line that will never resolve. Report it as recalled. That is a finished state.

What to do with this

Ask for the settlement date at approval, not a send confirmation afterwards. If your provider will not give you one, the information exists and they have chosen not to show it. You can see how Kelvern shows it on the currencies and rails page.