Before you worry

Money in transit between banks is not lost. It is either sitting in a batch waiting for the next processing window, or held by one of the two banks for a check. If a transfer has genuinely gone to the wrong account because details were entered incorrectly, that is a different problem and speed matters — contact your bank immediately rather than waiting, because recovery gets harder once the money has been moved on. This page explains ordinary delays, not misdirected payments.

There is no single thing called "a bank transfer"

The phrase covers several completely different systems that happen to share an interface in your banking app. The one your payment used decides almost everything about how long it takes.

Instant rails versus batch systems Instant payment systems settle in seconds and run continuously including weekends. Batch systems collect payments and process them in scheduled runs on business days only, so a payment submitted after the cut-off waits for the next run. Instant rails Seconds, running all day, every day. UK Faster Payments; US RTP and FedNow; most in-country app-to-app payments. Cut-off times mostly do not apply. Batch systems Collected up, processed in runs. US ACH; UK Bacs; most direct debits and payroll. Business days only. Cut-offs matter. Your app rarely tells you which one it used. The clue is the estimate: "instantly" versus "1–3 business days" are different systems, not different moods. A third category exists: wires. Same-day, expensive, and manually handled. Fast because a person is involved, not because the technology is quicker.
"1–3 business days" is not a bank being slow. It is a batch system doing exactly what it was designed to do.

Two practical consequences follow. First, a transfer between two accounts at the same bank is usually an internal book entry and lands immediately, because no external system is involved at all. Second, when people say "my last transfer was instant and this one is taking days", the usual explanation is that the two payments went by different routes — often because one was to an existing payee and one was not.

Cut-off times

Batch systems have a daily deadline. Payments submitted before it join today's run; payments submitted a minute after it wait for tomorrow's.

The cut-off is usually well before the end of the working day — often mid-afternoon, sometimes earlier for certain payment types — and it is set by your bank rather than by the clock. Two things about this catch people out:

A payment sent at 4pm on a Friday can therefore be a Monday payment for cut-off reasons and a Tuesday arrival for weekend reasons, without anything having gone wrong at any point.

Weekends and holidays

Batch systems run on business days. They do not run on weekends, and they do not run on public holidays.

The complication is whose holidays count. For a domestic transfer, your country's banking holidays. For an international one, potentially three sets: the sending country, the receiving country, and any country a correspondent bank sits in. A transfer can be held up by a public holiday in a country neither you nor the recipient live in.

This is also why "3 business days" is longer than it sounds. Sent on a Thursday afternoon after cut-off, three business days lands the following Wednesday — six calendar days for a transfer that was quoted as three.

The first payment to a new payee

This is the delay people are least warned about and most surprised by.

Many banks apply a hold to the first payment to a newly added recipient, and sometimes to the first few, or to any payment above a threshold to that recipient. The hold exists because a very large share of authorised push payment fraud involves a victim being persuaded to add a new payee and send money quickly. A deliberate delay gives the customer time to reconsider and the bank time to intervene.

What you might see:

None of this is visible as a reason in the transaction record. It simply appears as a payment that has not arrived yet.

What "pending" actually means

Pending means your bank has accepted the instruction and the money has not settled at the other end. That is all. It does not tell you which of several things is happening:

The last one is worth knowing about because it is invisible from your side. Your bank shows the money as sent; the recipient's bank has it and has not released it. Neither party's app explains this, and both are telling the truth.

One useful signal: has the money actually left your balance? If it has been debited, the instruction is real and in transit. If it is showing as pending but the balance has not moved, the payment has not been released yet — and in most banks it can still be cancelled at that stage.

Amount, pattern and fraud checks

Banks screen payments automatically, and a payment can be pulled out of the flow for reasons that have nothing to do with you doing anything wrong.

Banks are generally not allowed to explain compliance holds in detail, which is why the answer to "why is it held?" is sometimes genuinely unavailable to the person on the phone.

International transfers are a different animal

A domestic transfer moves between two banks. An international transfer often moves through several.

Where there is no direct relationship between the sending and receiving bank, the payment passes through correspondent banks — intermediaries that each hold the money briefly, take a fee, and pass it on. Each hop adds its own processing window and its own working hours. This is why international transfers are quoted in days rather than hours, and why the amount arriving can be less than the amount sent.

Additional sources of delay specific to international payments:

Money-transfer specialists are frequently faster than banks for these, not because they have better technology on the day, but because they pre-position funds in destination countries and pay out locally rather than actually sending your money across a border.

What to check, in order

  1. Has the money left your balance? If not, the payment has not been released and may be cancellable.
  2. What did the app estimate? "Instantly" and "1–3 business days" are different systems. The second is not late until the estimate has passed.
  3. Count business days, not calendar days, starting from the next business day if you sent after the cut-off.
  4. Was this a new payee? First payments are commonly held deliberately.
  5. Check for a message in the app or an unread security notification. Held payments usually generate one, and it is easy to miss.
  6. Confirm the recipient details against what you were given — sort code and account number, or IBAN. A digit wrong is a different problem and needs immediate action.
  7. Ask the recipient to check their pending or incoming transactions, not just their balance. It may be sitting there uncredited.
  8. After the estimate has passed, ask your bank to trace it. For international payments there is a formal tracing process and a reference number for it.
The short version

"Bank transfer" covers several different systems, and the one used decides everything. Instant rails settle in seconds and run at weekends; batch systems run in scheduled windows on business days only — so a payment sent after the afternoon cut-off on a Friday is a Monday payment at the earliest. The delay people are least warned about is the hold banks place on the first payment to a new payee, which exists to disrupt fraud and is not shown as a reason anywhere. "Pending" only means accepted-but-not-settled, and it can equally mean your bank is holding it or the recipient's bank is. The first useful check is whether the money has actually left your balance: if it has not, the payment has not been released and can often still be cancelled.

Sources