Business & Strategy
Payment Request Verification: Callback and Two-Person Approval Against Fake Emails and Calls
Intermediate | 4 whiteboard pages · Task board: 4 columns (4 parent tasks, 12 subtasks)
Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.
This payment request verification template helps finance teams set rules for transfer requests that claim to come from a supplier or an executive. Requests like “our bank details changed” or “send it today” get a callback to a registered number and two-person approval. A sender name, a voice or a face on a video call is not proof on its own, so call the number in your vendor ledger, not the one in the request, and set approval levels by amount and urgency. Start by reviewing recent bank detail changes, pick the 5W1H checks and set a four-step callback. Four pitfalls (calling the number in the email, skipping approval when rushed, exempting executives, keeping no record) are closed by calling only registered numbers and keeping records. Adjust the $3,000 threshold in the examples to your payment size. The 4 whiteboard pages cover risky requests, how to verify, removing exceptions and running the rules. The task board has 4 columns, 4 parent tasks and 12 subtasks.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Payment Request Verification Board
How to use (4 pages): ① On page 1, write the goal and the requests to check (boards①–⑤) → ② On page 2, decide what to check and the 4 callback steps (boards⑥⑦) → ③ On page 3, check the pitfalls and set the levels and the pledge (boards⑧–⑫) → ④ On page 4, set the approver table, records and review (boards⑬–⑮)
1/4 Spot risky requests
① Why we are making these rules (start here)
- What to protect e.g. Never send company money because of a spoofed request
- Who and which requests e.g. 4 people in finance and admin. Every transfer, remittance and purchase request
- Deadline e.g. Decide by the end of next month, then try it for a month
② Requests that need checking (write how you do it now)
| How it arrives | How it is checked now | Who checks | |
|---|---|---|---|
| Bank detail change | e.g. An email in a supplier contact's name, or a notice attached to an invoice | e.g. Only replying to the email and asking | e.g. A finance clerk and the finance manager |
| Urgent transfer | e.g. Email, chat, phone or video call in the CEO's name | e.g. Not decided. If it is urgent, we send first | e.g. The one finance clerk who was asked |
| New supplier | e.g. A registration request from sales and the first invoice | e.g. The account is registered from the application form alone | e.g. A finance clerk and the sales manager |
| Gift card purchase | e.g. Email or chat in a boss's name | e.g. The person who was asked decides alone | e.g. The one admin clerk who was asked |
③ Do not judge by how an email looks
- A sender name, signature or company logo does not prove who sent it
- Even if it looks like a continuation of earlier messages, do not trust it for that reason alone
- e.g. Even for the usual contact name, always call back about a bank detail change
④ Do not judge by voice or video
- A voice on the phone or a face on a video call that seems real cannot settle who it is
- Prepare for fake audio and video by trusting the procedure over how the person looks
- e.g. Even if the CEO appears on video and says it is urgent, call back a registered number
⑤ The more urgent, the more you follow the steps
- Treat a demand for “today” or “tell no one” as a signal to follow the steps
- A sender who is truly in a hurry can wait a few minutes for a callback
- e.g. For an urgent request, first tell the manager, then check
2/4 Decide how to verify
⑥ 5W1H: what to check for the requests in ②
- Request to check
- What What changes e.g. The payee account changes. The amount is $3,000 per transfer
- Why The reason e.g. Ask the registered contact why they switched banks
- Who Who asked e.g. Is the person asking the same person registered in the ledger?
- When The timing e.g. Is it the usual payment date? If it is “today”, use the urgent level in ⑪
- Where The channel e.g. Where it came from (email, phone, chat) and where you call back
- How How it is checked e.g. Who checked it, with which number, and where it was recorded
⑦ The 4 steps to call back a registered contact (ask the ⑥ questions)
- Pause first Put the payment on hold e.g. Do not use the numbers or links in the request. Reply that you will check before going ahead
- Find the ledger number Use a contact registered earlier e.g. A number in the vendor ledger, the contract or the card from the first meeting. Even if the incoming caller ID matches the ledger, call back yourself
- Call back and ask Ask the six questions in ⑥ e.g. Ask the contact why the account changed and whether there is a written notice
- Record and approve Keep what you confirmed and pass it on e.g. Write the date, the number called and who you spoke to, then send it to the second approver
3/4 Remove exceptions
⑧ Pitfall: calling the number in the email at step 2 of ⑦
- What happens: e.g. The number comes from the same source as the request, so you think you checked but never reached the real person
- How to check: e.g. Look at the past 3 months of records and see whether the numbers called match the ledger
- How to prevent: e.g. Write in ⑦ that numbers and links inside a request are never used
- Step to fix: e.g. Add “Never call a number that is not in the ledger” to step 2 of ⑦
⑨ Pitfall: skipping approval because it is urgent
- What happens: e.g. Told “today”, one person decides and sends first
- How to check: e.g. Count how many payments in the past 6 months had only one approver
- How to prevent: e.g. Keep two approvers even when urgent, and never lower the levels in ⑪
- Step to fix: e.g. Add “Even if urgent, hold first” to step 1 of ⑦
⑩ Pitfall: exempting only executives
- What happens: e.g. Because the CEO asked, the money is sent without a callback
- How to check: e.g. See whether any executive request skipped the 4 steps of ⑦
- How to prevent: e.g. Get a pledge in ⑫ that executives go through the same steps
- Step to fix: e.g. At step 3 of ⑦, call executives back on their registered numbers too
⑪ Approval levels (decide by amount and urgency, using ⑧ to ⑩)
Vertical axis: Amount (small → large) / Horizontal axis: Urgency (low → high)
- Large amount, not urgent Level 2: callback and two approvals. The second approver also opens the ledger and checks it. e.g. $3,000 or more, usual payment date
- Large amount, urgent Level 3: Level 2 plus the department head checks again on another registered number. The check takes priority over the deadline. e.g. $3,000 or more, asked for “today”
- Small amount, not urgent Level 1: approve with two people as usual. Always call back when bank details change. e.g. Under $3,000, usual supplier
- Small amount, urgent Level 2: urgent does not lower the level. Do not send until the callback is done. e.g. Gift card purchase under $3,000 asked for “right now”
⑫ Pledge: executives are no exception
- Pledge e.g. Requests from the CEO and executives go through the callback in ⑦ and the approval in ⑪ in the same way
- One line executives pass on to staff e.g. “Even if an urgent request comes in my name, check it by the steps”
- What staff may say e.g. “It is the rule, so I will call back a registered number before going ahead”
4/4 Run the rules
⑬ Approvers and checks for each level in ⑪
| First person (checks) | Second person (approves) | How to check | OK to send when | |
|---|---|---|---|---|
| Level 1 | e.g. Finance clerk | e.g. Finance manager | e.g. Compare the invoice with the order record | e.g. After both approvals are in |
| Level 2 | e.g. Finance clerk | e.g. Finance manager | e.g. Call back the ledger number, and the second person opens the ledger too | e.g. After the record is kept as in ⑮ |
| Level 3 | e.g. Finance manager | e.g. Department head | e.g. Level 2 plus the department head checks on another registered number | e.g. After the department head has checked |
| Bank detail change | e.g. Finance clerk | e.g. Finance manager | e.g. Call back the ledger number and receive a written notice of the change | e.g. Before the first payment to the new account |
⑭ Twice-a-year review (using the table in ⑬ and the records in ⑮)
- Gather records Line up six months of check records e.g. In the first week of April and October, collect the ⑮ records in one place
- Look at pitfalls See whether ⑧ to ⑩ happened e.g. Count cases of calling a number not in the ledger and cases with one approver
- Fix the table Fix the thresholds in ⑪ and the table in ⑬ e.g. Update the rows where staff changed and the amount threshold
- Tell everyone Share what changed e.g. Tell all of finance, admin and the executives what changed in 3 lines
⑮ How to keep records (pitfall: no record of checks)
- What happens e.g. Later nobody knows who checked what and how, so review and handover are impossible
- How to check e.g. Once a month, match the payment list with the check records one by one
- How to prevent (what to write in the record) e.g. Date, how it arrived, the number called and its source, the person spoken to, and both approvers, in the check log in the finance shared folder
Task board contents
Not started 16 items
Spot risky requests
On page 1, write the purpose of the rules and how you currently check the 4 kinds of requests that need checking. You are done when you can see where the checks have gaps, and that becomes the material for page 2 onward. Press Ctrl+F (⌘F on Mac) and search for “3/4” to jump to page 3.
Review bank changes
This is the first step, and you only need to look at a list and count. Open the payee list in your online banking or accounting software, count the suppliers whose account changed in the last 3 months (if the list has no change date, count from change request emails or forms), and write who checked each one and how in the “Bank detail change” row of board ②. Done when that row is filled.
Fill in the table
Fill in the remaining 3 rows of board ② (urgent transfer, new supplier, gift card purchase) with how the request arrives, how it is checked now, and who checks. Done when no more than 2 cells are empty.
Write goal and why
Write the purpose, scope and deadline on board ①, read boards ③ to ⑤, and add one example likely to happen at your company to each as a sticky note. Done when everyone on the team has read them.
Set up verification
On page 2, decide what to check when a request arrives and the steps for calling back a registered contact. These steps are the heart of the rules, so try them on one real request before you finalize them.
Set the 5W1H checks
Under the six questions of board ⑥, write what to ask for the requests in the table ②. Done when they are short enough to read aloud during a callback.
Check ledger phones
For the 10 suppliers you pay most, check the ledger phone number and where that number came from (contract, business card from the first meeting). Done when step 2 of board ⑦ can be used.
Set 4 callback steps
Rewrite the 4 steps of board ⑦ in your own words and try them in order on one past request. Done when the clerk can reach the last step without hesitating.
Remove exceptions
On page 3, check the pitfalls where the steps tend to break, set approval levels by amount and urgency, and get executives to agree to be no exception. If you skip this, the steps get skipped on exactly the urgent and executive requests.
Check the 3 pitfalls
In each frame of boards ⑧ to ⑩, write what happens, how to check, how to prevent it and the step of ⑦ to fix, using your own examples. Done when the preventive step is decided in all 3 frames.
Set approval levels
In the 4 cells of board ⑪, write the amount threshold and how to approve at each urgency. Done when the level does not drop even when a request is urgent.
Get executive pledge
Show the pledge on board ⑫ to the CEO and executives, and have them tell the company that requests in their name should also be checked by the steps. Done when you write the date they told staff on a sticky note.
Run the rules
On page 4, put the approvers and checks for each level in a table, and decide how to keep records and how to review twice a year. Try the rules for one month in the Trying it out column of the task board, then move them to Decided and shared.
Build approver table
In the table of board ⑬, write the first person, second person, how to check and when sending is allowed for each level. Done when you have also written a stand-in for people on leave on a sticky note.
Set record keeping
On the sticky notes of board ⑮, write what goes in the check record and where it is kept. Done when the next request is recorded.
Schedule reviews
Choose the months for the twice-a-year review using the 4 steps of board ⑭, and put it in the calendar. Done when a person's name is on it.