A callback only protects you if the number you dial didn't come from the request you're checking.
Callback verification means confirming a bank detail change or unusual payment request by phoning the requester on a number you already hold or found independently, never one supplied in the request. Use a short script, ask the contact to confirm details you hold rather than read them back, record the call in a log, and hold the payment until it passes.
Write the triggers into your procedure so nobody has to decide on the day. Typical triggers:
If a trigger applies, the payment is held until the callback is completed and logged. No exceptions for urgency: urgency is the most common pressure tactic in business email compromise.
This is the step that makes or breaks the control. Acceptable sources, in order of preference:
Never use a number from the email, letter or invoice that requests the change, or from an email signature in the same thread. A fraudster who controls the email can put their own number in it.
Keep it short and consistent so staff don't feel awkward asking:
If anything doesn't match, stop. Don't update the record, and treat it as a suspected fraud attempt.
A simple Excel log is enough. One row per callback:
Add a check column that flags when the caller and the updater are the same person:
=IF(AND(F2<>"",F2=H2),"SAME PERSON","")
And count unresolved requests before each payment run:
=COUNTIFS(B2:B500,"<>",G2:G500,"<>Confirmed")
The first condition ignores empty rows, so the result is the number of logged requests not yet confirmed. It should be zero before any affected payment is released.
UK teams often say "call-back" and check against sort code and account number; US teams verify routing and account numbers and may call it "out-of-band verification". The procedure is the same. Payee name checking services differ by country, so check what your bank offers.
Audits the supplier master file with an on-device AI and 28 tests: lookalike duplicates written differently, bank-detail changes before payments, vendors matching employees, and a risk score for every vendor. Runs in your browser on your own computer: nothing is uploaded.
Score a payment request against the warning signs of fraud. Free to use online.
The Invoice & Payment Fraud Defence Kit puts every payment through a Release, Hold or Pulled-from-run decision, with a bank detail change verification log, supplier checks, an incident log, a staff training record and a Fraud Defence Playbook (PDF). Excel, no macros, one-time price.
No. If the email account is compromised, a reply proves nothing. Use a phone call to an independently sourced number.
Keep the payment on hold and try again. A missed call is never a pass, however long it has been.
No. Call back when a trigger applies: new or changed bank details, unusual or urgent requests, or changes to contact details.
Last updated 28 October 2026. General guidance for finance teams; check it against your own policies, systems and local rules.