CHAPS provides same-day sterling settlement, and transfers between direct participants are settled individually in RTGS with finality. This guide explains the mechanics, evidence, risks and controls a UK business should understand before relying on the process.
What CHAPS payment recalls means in practice
CHAPS provides same-day sterling settlement, and transfers between direct participants are settled individually in RTGS with finality. The practical question is whether the business can prove the condition was met at the moment money or authority was needed.
Because settlement is designed to be irrevocable between direct participants, a customer who sends money in error should contact its bank immediately, but recovery depends on what has happened downstream and cannot be guaranteed. That wording should be translated into a short internal test showing the trigger, deadline, decision owner and evidence required for the business to proceed.
How CHAPS payment recalls works from start to finish
The minimum decision pack is payment time, amount, beneficiary, bank reference, reason for recall, settlement status, receiving bank details, fraud indicators and every contact made with the bank. If any of those fields is uncertain, the transaction should remain open rather than being treated as complete.
Operational ownership should follow the transaction through to its final state. The person who initiates an action does not need to perform every later step, but the business must know who owns unresolved exceptions.
The data and evidence that matter
Records should be proportionate to the exposure. A routine low-value item may need a simple system trail, while a material CHAPS payment recalls decision should preserve the underlying calculation, approvals and any exception accepted by management.
An effective record should also make the exception path visible. If the normal rule cannot be met, the team should capture who approved the deviation, how long it applies and what evidence will close it. For CHAPS payment recalls, that distinction prevents a temporary workaround from becoming an undocumented permanent practice. For CHAPS payment recalls, the specific checkpoint is this: Use an incident procedure that contacts the bank first, preserves evidence, freezes any related future payments and separates mistaken-payment recovery from suspected fraud response.
Where the process can fail
A business may waste the first critical hours emailing the beneficiary while assuming the bank can reverse the payment later with one click. The financial exposure can grow quickly when the issue is discovered close to settlement, drawdown or payment day.
Deadline pressure can also weaken controls. If the process depends on an emergency override every month, the underlying timetable is wrong and should be redesigned rather than normalising exceptions.
Worked example: test the mechanics
A £650,000 CHAPS payment is sent to an old supplier account at 11:20. The error is noticed at 11:35. Treasury should call the sending bank immediately with the reference and beneficiary details; it should not wait until the afternoon reconciliation to start recovery.
This example is a method rather than a universal rule. The business should replace every illustrative figure with its own contractual terms, bank data and dates, then test the result before assuming that cash or authority is available.
Governance and controls for CHAPS payment recalls
Use an incident procedure that contacts the bank first, preserves evidence, freezes any related future payments and separates mistaken-payment recovery from suspected fraud response. The procedure should identify the primary owner, reviewer and escalation contact so an absence does not suspend a material payment or funding decision.
Changes to systems, bank services or finance documents require retesting from source instruction through reconciliation. A migration is not complete merely because the file transmits or the new document has been signed.
Senior review is most valuable where judgement remains. Automated controls can check limits and formats, but unusual legal, liquidity or counterparty issues still need an accountable person to decide whether the business should proceed.
Decision records should separate three layers: what the governing document or payment scheme allows, what the bank or counterparty operationally supports, and what internal policy permits. Those layers can produce different answers, and CHAPS payment recalls is safest when the difference is explicit before the transaction proceeds. In this workflow, the supporting record should cover payment time, amount, beneficiary, bank reference, reason for recall, settlement status, receiving bank details, fraud indicators and every contact made with the bank.
This makes the control decision-focused: staff know what evidence is sufficient, what is still unresolved and which person can accept an exception. The resulting record should be short enough to use during a live deadline but detailed enough for finance, audit or a replacement treasury colleague to reconstruct the reasoning later. Before approving a material CHAPS payment recalls action, the reviewer should challenge the assumption most likely to change the cash outcome rather than merely confirm that every box has been ticked. The review should use payment time, amount, beneficiary, bank reference, reason for recall, settlement status, receiving bank details, fraud indicators and every contact made with the bank and should identify which item would force the team to pause, obtain consent or change the planned date.
Editorial Verdict
BanksGB's editorial view is that CHAPS payment recalls should be managed as a practical cash-and-control issue. CHAPS provides same-day sterling settlement, and transfers between direct participants are settled individually in RTGS with finality. The strongest process connects the governing rule to the amount, timing, legal entity and external status instead of relying on the product label.
The final test is whether a second person could explain the transaction from the retained record: what triggered the action, which data was used, who approved it, what the bank or lender did and what remains outstanding. If that cannot be answered, the control around CHAPS payment recalls is weaker than it appears. The reason for that discipline is concrete: A business may waste the first critical hours emailing the beneficiary while assuming the bank can reverse the payment later with one click.
Sources
- Bank of England, CHAPS: https://www.bankofengland.co.uk/payments/chaps/
- Bank of England, Payment and settlement: https://www.bankofengland.co.uk/payments/payment-settlement