Designing Payment Approvals That Resist Impersonation
Use clear payment roles, exception handling and immediate escalation to reduce business email compromise risks.

Xian Hui
9 November 2026 · 4 min read

In brief
How can a small accounting practice make payment approvals harder to exploit?
Separate supplier-record changes, payment preparation and bank-transfer approval where practical. Require approvers to inspect the supporting records and independent confirmation, with independent managerial review where full separation is difficult. Document how urgent or unusual requests are escalated, support holding unverified payments and act promptly if a transfer appears fraudulent.
What you'll learn
- Distinguish preparation from payment authorisation
- Apply additional checks to exceptional instructions
- Respond rapidly to a possible fraudulent transfer
Designing Payment Approvals That Resist Impersonation
A small accounting team performs the full accounts payable cycle. One person maintains suppliers, prepares payment files and sometimes logs in to approve transfers when the manager is absent. The arrangement may be convenient, but it creates a concentration of authority that a fraudster can exploit.
Payment security is not just a matter of detecting deceptive emails. It is also a question of who can change records, who can authorise money to leave and what evidence survives after approval.
Which duties should be separated?
Where practical, separate the ability to update vendor details, prepare payment instructions and approve bank transfers. A second person should not merely click 'Approve' without seeing the underlying change and confirmation evidence.
For a small practice, perfect separation may be difficult. A compensating control can be independent review by a manager who did not enter the bank details. The critical point is that a suspicious or incorrect instruction should not pass through a single unchecked action.
The Singapore Police Force's business email compromise advisory emphasises additional verification before unusual payment changes. The FBI's BEC guidance gives a similar warning about changes in payment arrangements.
For the checks before a vendor record is changed, see Verifying Supplier Bank-Detail Changes Before Payment.
What evidence should an approver inspect?
A useful payment approval record can include the following evidence:
| Check | Evidence to inspect |
|---|---|
| Business purpose | Invoice and business purpose. |
| Recipient | Approved supplier identity and account information. |
| Changes | Change history and independent confirmation. |
| Approval | Approval time. |
For material transfers, the approver should compare the beneficiary entered into the banking system with the verified vendor record rather than relying only on a spreadsheet total.
Consider an original fictional scenario: a client director asks for an urgent payment to a service provider in a new country. The company may genuinely have a new arrangement. The payment reviewer should first check the business purpose and authority, then verify the recipient using an independent source. A request to keep the payment secret is not a reason to avoid normal controls.
How should exceptions be handled?
The firm should document a clear escalation route for urgent payments, absent approvers and unusual supplier requests. Avoid a vague rule such as 'partner approval can override all checks'. Instead, specify who can review exceptions, which evidence remains mandatory and how the decision is recorded.
A robust procedure allows an authorised person to make a decision without quietly disabling the control. If an urgent payment cannot be verified, the process must support a hold decision and a transparent explanation to the client.
What if fraud is discovered after approval?
Escalate immediately to the firm and client contacts authorised for incidents. Preserve bank transaction references, timestamps, payment instructions, email headers and approval records. Contact the relevant financial institution as soon as possible. Make a police report promptly, as the Singapore Police Force advises for business email compromise, and assess whether any personal or confidential data was also exposed.
Singapore's ScamShield helpline can help with scam-related checks, but it does not replace contacting the bank and reporting suspected crime through the proper channels. A rapid response can matter, though recovery is never assured.
For the reporting process, see Reporting and Containing a Cyber Incident at Work.
How can a firm test its control?
Run a tabletop scenario using fictional supplier details. Ask who records the change, who finds the trusted contact, who reviews the evidence and who can stop the transfer. If the team cannot identify these roles, a written policy alone is not yet an effective control.
Record one or two improvements after each exercise. The goal is to make the correct action easy during ordinary work, not to create excessive paperwork for every routine invoice.
Key takeaways
- Split preparation, master-data changes and authorisation where possible.
- Require evidence of verification, not merely an approval click.
- Design a documented process for urgent or unusual payments.
- Preserve records and act quickly when payment fraud is suspected.
Last source check: 9 November 2026.
Next in the course: Reviewing Cloud Applications, Integrations and Vendor Access
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.


