How to Verify an Unexpected Request Safely
Use an independent verification process when a client, colleague or service provider appears to request an unusual action.

Xian Hui
9 November 2026 · 4 min read

In brief
How can I verify an unexpected request from a client or colleague?
Pause the requested action and contact the claimed requester through an established telephone number, approved portal or authorised contact already on file. Confirm exactly what is requested and whether the person can authorise it. Record the decision and report any password entry, download or disclosure through the practice's approved channel.
What you'll learn
- Separate a message from the authority it claims
- Verify unusual requests by an established channel
- Record and escalate the result without sharing sensitive data
How to Verify an Unexpected Request Safely
A client emails a new payroll administrator and asks them to upload a bank statement to an unfamiliar portal. The signature looks familiar. The message also references a real client project. None of those details establishes whether the request was authorised.
A verification process should answer three questions: Who is asking, what exactly is being requested, and is the requested change normal and authorised? This is useful for suspicious regulatory notices, payment instructions and client-data requests.
Why is replying to the same message insufficient?
If an email account has been compromised, a reply can return to the person controlling it. If the sender address is imitated, the reply may go to another address altogether. A second email from the same conversation does not necessarily create independent evidence.
The Singapore Police Force's May 2026 advisory advises businesses to verify unexpected payment-account changes through a different medium. The principle also helps with requests to export accounting data or grant access to a client folder, even though those are different types of decisions.
In practice, use a telephone number, approved portal or designated company contact already on file. Do not copy a phone number from the suspect message into the verification record. If the usual contact is unavailable, follow an escalation rule rather than accepting the message because it seems urgent.
What does a repeatable verification process look like?
Take a fictional request to change the destination of a management report:
| Step | Check | What to do |
|---|---|---|
| 1 | Stop the requested change | Keep the report in its approved storage location. |
| 2 | Identify the claimed requester | Record the name, the stated reason and the requested destination. |
| 3 | Use a trusted route | Contact the authorised client representative using established details. |
| 4 | Confirm the exact action | Ask what file, destination, recipients and purpose were intended. |
| 5 | Check approval | A real requester may still lack permission to approve the disclosure. |
| 6 | Record the decision | Keep a short note of who confirmed it, when and which action was authorised. |
This procedure is a proposed firm control, not a mandatory statutory sequence. Adjust it to the firm's authorisation matrix and data protection obligations.
What if the requester is a partner or senior manager?
Authority and identity are separate. A partner may genuinely authorise a task, but a message displaying their name is not proof that the partner sent it. The same independent confirmation rule should apply to exceptional requests from senior people. Otherwise, the highest-pressure requests receive the least scrutiny.
Consider the phrase 'I am in a meeting and cannot take a call'. That may be true, but it cannot remove a control designed to protect money or client information. Use an alternative authorised reviewer or postpone the action until confirmation is available. The FBI warns that criminals can exploit requests framed as urgent and familiar.
How should staff report a doubtful request?
A useful report contains the original message, date and time, any link or attachment encountered, the attempted action and what the employee did. Avoid repeatedly forwarding a harmful file to colleagues. Use the approved internal reporting channel and preserve the message for the person assigned to investigate.
If an employee entered a password, downloaded a file or disclosed data, do not hide that fact because the initial action feels embarrassing. It changes what the response team must assess. Move from 'Is this message genuine?' to 'Could an account or record now be exposed?'
For consumers uncertain whether a request is a scam, Singapore's ScamShield helpline provides a check channel. It does not replace the practice's own authorised reporting and incident procedures.
A short practice exercise
A client director appears to send a message asking for two months of employee salary records to be sent to a new personal mailbox. Before acting, list the contact on record, the client's authorised recipient list, the stated business purpose and who must approve disclosure. A message can be genuine yet still request an inappropriate disclosure.
Key takeaways
- Confirm the person and the specific action independently.
- An authentic identity does not by itself establish authority to access or receive data.
- Apply the control consistently, including for senior staff and urgent requests.
- Keep a clear record, and escalate immediately if an unsafe action has already happened.
Last source check: 9 November 2026.
Next in the course: Passwords, Passkeys and Multi-Factor Authentication for Accountants
Sources
Frequently asked questions
This information has been prepared for general informational purposes only and is not intended to be relied upon as accounting, tax, or other professional advice.


