Vendor Banking Change Verification Checklist
The callback procedure that stops payment-redirect fraud, with red flags, script, record form and log.
• Automate faster • Collaborate better
• Pay with confidence
The most damaging AP fraud doesn’t hack anything. It emails. A routine-looking request to update a real vendor’s banking details, and the next legitimate invoice pays the wrong account.
The defense is one unbendable procedure: no banking change takes effect until someone calls a known vendor contact on an independently sourced number and documents it. This checklist is that procedure, ready to adopt, with no exceptions for urgency or seniority, because urgency is the attack.
IN THIS TEMPLATE
Eight mandatory verification steps for every banking-detail change
Nine red flags that should send you straight to the incident procedure
A word-for-word callback script, including what to do if the contact is unaware of the change
A per-change verification record and a running log, the evidence auditors and insurers ask for
The first-hour playbook if verification fails or fraud is suspected: freeze, recall, preserve, report
FAST FACTS
8 mandatory steps per banking change
9 red flags, any one of which means heightened care
1 hour to adopt: print, train, enforce
One procedure closes the payment-redirect door. Complete the form and we’ll send the PDF.
