FRAUD PREVENTION / BUSINESS CONTROLS
Stop the diversion.
Protect the decision.
Fraud follows the way a business makes decisions. Restore the evidence, recognise the transaction risks and build verification into ordinary work.

An apparently routine request can be the point at which fraud becomes a business loss: a supplier changes bank details, a customer resets an account, an executive asks for an urgent transfer or an unfamiliar company offers an attractive payment arrangement.
National fraud indicators become useful when they inform everyday decisions. Read the figures with their dates and definitions, then examine the exposure in your own workflows. Businesses do not all face the same loss.
FRAUDSCAPE 2025 / CASES RECORDED DURING 2024
The scale behind the warning.
421,002
National Fraud Database cases
Up 13% from 2023. Filings by Cifas members, not the total number of UK fraud offences.
+76%
Account-takeover filings
74,256 cases in 2024. This is a change in recorded cases, not an individual business’s risk.
48%
Mobile-phone share of takeovers
Of recorded account-takeover cases—not 48% of all fraud.
86%
Identity-fraud cases online
Share of identity-fraud filings through online channels, not the share of every fraud type.
Cifas Fraudscape 2025 release and Cifas-authored report, pages 4–8 and 13–16 (hosted copy). Historical 2024 data; these are different measures and must not be added together.
THE EXECUTIVE BRIEF
Protect the decision that releases money or access.
- Verify sensitive changes through a known, independent route before acting.
- Connect finance checks to account security and incident response.
- Give every control an owner, an exception process and evidence that it works.
01
The same incident can cross finance, identity and technology.
A payment diversion can start with an email account, a convincing telephone call or a compromised supplier. The person approving the transfer may see a plausible invoice rather than a technical warning. That is why fraud prevention needs finance, operations and security working from the same picture.
AI-assisted writing and synthetic media can make impersonation more convincing or easier to repeat. They do not establish that every persuasive message is AI-generated, and they do not remove the value of a verification process that does not rely on the incoming message being authentic.
Company accounts can also be used to move illicit funds. Cifas’s 2025 report records 6,744 company-current-account cases indicative of money muling in 2024, up 212% from 2,163. That is a particular filing category—not a 212% rise in all business fraud.
For an owner or finance director, the practical point is to examine unexpected money movement in both directions. A request to receive and pass on money, an unusual refund or a new counterparty can require scrutiny even when the business is not initially being asked to pay an invoice.
02
Four transaction stories worth testing.
ILLUSTRATIVE BUSINESS SCENARIOS
Different work. Familiar pressure points.
Digital business
A reset becomes an account takeover.
An attacker persuades someone to change an account’s recovery details, then uses the account to request a payment or obtain information.
Control to examine: Test identity verification, privileged access and notifications when important details change.
Retail or e-commerce
A real account becomes a different customer.
Delivery addresses, refunds or contact details change after an account is compromised. A familiar account name can conceal a new transaction pattern.
Control to examine: Test unusual changes, refund approval and a trusted route for customer confirmation.
Professional services
The familiar invoice has new bank details.
A convincing message appears in a legitimate business relationship and pressures a colleague to update the payee record.
Control to examine: Test independent verification, separation of payee changes from payment approval and the ability to pause.
Supply chain
An attractive payment request creates exposure.
A new counterparty, unusual intermediary or changed payment arrangement asks the business to bypass its normal checks.
Control to examine: Test onboarding, due diligence, unexpected receipts and approval for changes to payment routes.
Fictional scenarios for discussion, not client case studies or measured sector risk rankings. They do not assign numerical probabilities to sectors.
The useful question is where trust is being borrowed. A recognised name, an existing supplier record or a real customer account can make an instruction feel safe. Controls should verify the consequential change rather than treating familiarity as authorisation.
Avoid assuming that a particular sector’s position in a chart gives a reliable numerical probability of loss. Your own transaction patterns, privileged accounts, customer information and supplier dependencies provide a better starting point for deciding which controls need attention.
03
Make verification part of the payment workflow.
A SENSITIVE PAYMENT OR PAYEE CHANGE
Pause. Verify. Approve. Reconcile.
PAUSE
Make it acceptable to stop an unusual request.
Urgency, confidentiality or apparent seniority should not remove the check. Record why an exception is being requested.
VERIFY
Use contact details already held and trusted.
Confirm the change independently. A reply to the incoming message or a call to a number supplied in it may reach the same attacker.
APPROVE
Separate the change from the release of funds.
Use proportionate dual control and an agreed exception owner. Preserve the verification evidence with the transaction.
RECONCILE
Check what actually happened.
Review new payees, unusual movements, failed checks and suspicious requests. Escalate quickly when the result does not match the authorisation.
CyberSolace workflow illustration. Set approval thresholds for your business and keep change-of-bank-detail verification effective below any numerical threshold.
A fixed financial threshold can be useful for approval levels, but it should not become a safe route around verification. An attacker may test the process with a smaller payment or split requests. Build controls around the kind of change and the risk as well as the amount.
Give colleagues a realistic route when a senior person is unavailable. If the procedure exists only on paper and the only alternative is to hold up an essential service, staff will be tempted to improvise. Define who can resolve an urgent exception and how the decision is recorded.
Rehearse the workflow with finance and the people who routinely receive supplier or customer requests. Look for unclear ownership and awkward handoffs, then improve them. A training completion figure does not show whether a real request would be checked independently.
04
Account security and culture support the financial controls.
Strong authentication, controlled administrative access, timely removal of access and monitoring of important changes reduce opportunities for a compromised account to carry a believable instruction. They complement finance controls rather than replacing them.
Cifas’s separate Fraud Behaviours Survey 2024 found that 48% of respondents considered at least one tested form of first-party fraud reasonable. It surveyed 2,000 UK adults in May 2024 using hypothetical scenarios. This is an attitudes finding—not evidence that 48% of employees commit fraud.
The management implication is to make standards and reporting routes clear, including when the suspicious conduct is inside the business or involves a regular customer. Combine proportionate approval, reconciliation and segregation of duties with fair investigation. Do not use a population survey as a reason to presume individual wrongdoing.
Protect information that makes impersonation convincing: customer records, payment details, executive identity and access to shared mailboxes. Review backup and recovery arrangements too. Fraud can be accompanied by account compromise or data loss, and the response may depend on information that is no longer available in the affected account.
Insurance may help with particular losses and response costs under the policy. Check notification and approval requirements with the insurer or broker; do not assume every payment authorised under deception will be covered.
05
A calendar that turns concern into work.
A PRACTICAL STARTING PLAN
This week. This month. This quarter.
01
THIS WEEK
Remove the easy bypass.
- Confirm bank-detail changes through trusted contact details.
- Review urgent payment exceptions and access to finance accounts.
- Publish a short route for reporting a suspected diversion.
02
THIS MONTH
Test the supporting controls.
- Rehearse a supplier-payment scam with finance and operations.
- Review important MFA, account recovery and administrative access.
- Check response contacts, recovery evidence and supplier responsibilities.
03
THIS QUARTER
Keep the process honest.
- Review exceptions and independently verify a sample of changes.
- Retest identified gaps and report what improved.
- Reassess customer-data exposure, business dependencies and relevant insurance terms.
Illustrative prioritisation, not permission to delay an urgent control gap or an active incident.
If you suspect a payment has been diverted, use the bank’s established urgent fraud route promptly and activate the incident plan. Preserve relevant messages and transaction evidence, obtain specialist support where needed and assess any affected accounts or personal information. A recovery plan should not depend on continued access to the compromised mailbox.
READ THE STATISTICS IN CONTEXT
The statistical illustrations describe 2024, with the measurement year made explicit. They are not current 2026 totals, whole-economy loss estimates or numerical sector probabilities.
THE CYBERSOLACE PERSPECTIVE
A convincing request still needs an independent check.
Select one real workflow—supplier onboarding, a bank-detail change or a customer-account reset—and test where the business relies on trust without verification. Fix the weakest handoff first.
Contact CyberSolace about a fraud-risk discussion and practical improvements to your verification and response arrangements.
SOURCES & EDITORIAL REVIEW
Original publication date retained. Research and presentation reviewed 20 October 2026. Scenarios are illustrative, not client claims. Control recommendations are CyberSolace guidance; numerical measures retain their original scope and period.