How long does a BACS payment take?

Short answer

Three working days, not three calendar days, so a payment submitted before a bank holiday weekend can take the better part of a week. The money leaves your account on the third day, not the day you submit, so for two days it is committed and still showing in your balance.

The three days

1. Day one, input. The payment file is submitted. Submission windows run through the working day up to a cut-off in the evening; a file submitted after the cut-off is treated as submitted on the next working day, which quietly adds a day.
2. Day two, processing. The files are processed and delivered to the receiving payment service providers.
3. Day three, entry. Accounts are credited and the paying account is debited, usually in the early morning.

BACS operates on UK working days only. Weekends and bank holidays are not part of the cycle, they extend it.

Why the debit timing matters

The money leaves your account on day three, not day one. That is convenient, and it is also the reason BACS ruins forecasts: for two days a payment is real, committed, and still sitting in the balance. Once the file has passed the cut-off it cannot be cancelled, and a recall after the money has moved is a request rather than a right.

This is the strongest argument for treating committed money as a distinct state rather than as a footnote to a balance. A business that looks at its balance on day two and commits the same money twice has not made a mistake. They have been shown a number that does not mean what it appears to mean.

When BACS is the right rail, and when it is not

• Use BACS for payroll, supplier runs, and anything high-volume and predictable. It is cheap per item and built for batches.
• Use Faster Payments when it needs to arrive today, for a single payment, or when the recipient is waiting on it. Near-immediate, with per-transaction and per-institution limits.
• Use Direct Debit when you are collecting rather than paying and the amount or timing varies. It is a different instrument from a standing order, not a variant of one.

What “pending” usually means

A BACS payment showing as pending is normally just inside the cycle. The cases worth investigating are a submission that missed a cut-off, a file rejected at processing, or details that failed validation. Each of those has a different answer, and “pending” tells you none of them.

Tervra’s position on this is narrow and firm: if the outcome of a payment is not yet known, it is reported as unknown rather than as failed, and it is never quietly resubmitted. A duplicated payment is a worse outcome than an uncertain one. How payments work in Tervra.