Phishing protection Hampshire businesses can trust starts with one uncomfortable fact: the invoice that drains your bank account usually arrives inside a genuine conversation.
You receive an invoice from a trusted supplier. The amount is familiar. The purchase order matches. The email sits inside a genuine conversation your team has been following for weeks.
Then, just before payment, the supplier asks you to use new bank details.
Nothing looks obviously wrong. There is no strange attachment, no urgent demand from a random address and no obvious spelling mistake. The email may even have come from the supplier’s real mailbox.
That is what makes payment redirection fraud so dangerous.
The NCSC’s current phishing guidance continues to highlight how criminals impersonate trusted organisations to steal money and information. For Hampshire businesses, this threat is especially serious because many smaller finance teams rely on trust, personal relationships and one-person approval processes.
This is not generic phishing. It is often a real supplier conversation hijacked at exactly the right moment.
What is payment redirection fraud?
Payment redirection fraud is also known as:
- Invoice fraud
- Supplier impersonation
- Mandate fraud
- Business email compromise
- Man-in-the-email fraud
The criminal’s goal is simple: persuade your business to send a legitimate payment to the wrong bank account.
The invoice may be genuine. The supplier may be genuine. The amount may be correct. Only the destination account has changed.
That is why “the email looked genuine” is not a defence. The fact that it looked genuine is the point of the attack.
How does the attack work?
1. A supplier mailbox is compromised
The attacker may gain access to a supplier’s mailbox through:
- A stolen Microsoft 365 password
- A phishing page that captures login details
- Password reuse from another breached service
- An unprotected account without multi-factor authentication
- A stolen session token that allows access without the password
The attacker does not always send an immediate fraudulent invoice. That would attract attention.
Instead, they may quietly monitor the mailbox.
2. The attacker watches a live conversation
For days or weeks, the criminal may read messages between the supplier and your business.
They learn:
- Who normally sends and approves invoices
- Which members of staff are involved
- When payments are usually made
- Which invoices are still outstanding
- The supplier’s writing style
- The value and frequency of payments
- Whether someone is away from the office
This information allows the attacker to behave like a patient observer rather than an obvious scammer.
3. They choose the right moment
The most effective time to intervene is often just before a real invoice is paid.
The attacker may reply within the existing thread and write something such as:
“Please note that our bank details have changed. Could you use the new account for this month’s payment?”
The request may refer to the correct invoice number, the correct amount and the correct project.
The attacker may also create a plausible reason for the change, such as:
- A banking provider migration
- An internal accounting change
- A merger or restructuring
- A new payment platform
- A temporary problem with the old account
4. They exploit your approval process
Smaller businesses often have a finance team of one or two people. If the usual approver is on holiday, the substitute may be asked to process the payment quickly.
A single person may then:
- Receive the change request.
- Update the supplier record.
- Approve the invoice.
- Release the payment.
That is a complete payment process controlled by one person, often without an independent telephone check.
Once the money has been sent, it may move through several accounts within minutes.
Why are Hampshire businesses particularly exposed?
This type of fraud can affect any organisation, but it presents a clear risk for small and medium-sized businesses across Hampshire. That is why phishing protection Hampshire firms can apply in day-to-day finance work matters just as much as broader cyber security controls.
Many local firms have:
- Small finance teams with limited cover
- Single-approver processes for routine payments
- Long-standing, high-trust relationships with suppliers
- Informal approval through email
- Little or no documented payment verification procedure
- Limited time for finance-specific cyber security training
A business in Winchester, Basingstoke, Southampton or Portsmouth may have worked with the same accountant, contractor or wholesaler for years. That trust is valuable, but criminals know it can reduce scrutiny.
The answer is not to distrust every supplier. It is to introduce a simple verification step whenever payment details change.
Phishing protection Hampshire: how to prevent payment redirection fraud
Verify every bank detail change by telephone
Never verify a new bank account using the telephone number in the email or invoice. If the mailbox has been compromised, the attacker may have inserted a false number.
Instead, use a known number from:
- Your supplier contract
- Your finance system
- A previous invoice that was independently checked
- Your established supplier records
- The supplier’s official website, where appropriate
Ask the supplier to confirm the change verbally. Record who confirmed it, when they confirmed it and which number you used.
Pro tip: Do not rely on replying to the email. A reply may go directly back to the attacker.
Use dual authorisation
Require two people to approve:
- Bank-detail changes
- New supplier records
- Payments over a defined threshold
- First payments to a new account
The person who changes the supplier record should not be the only person who approves the payment.
Set a threshold that reflects your business. For some firms, that may be £1,000. For others, it may be £5,000 or £10,000. The important point is to make the rule clear and consistent.
Match the invoice to the purchase order
Do not approve an invoice simply because the supplier name and amount look familiar.
Check:
- The purchase order
- The original quote or contract
- The goods or services received
- The expected payment account
- Any recent changes to the supplier relationship
An invoice-to-PO match will not stop every attack, but it can expose an unexpected change in payment instructions.
Protect supplier records
Limit who can create or amend supplier bank details in your accounting system.
Keep an audit trail showing:
- Who requested the change
- Who verified it
- Which method was used
- Who approved it
- When the change was made
This is both a fraud control and useful evidence if something goes wrong.
Secure email accounts properly
MFA, or multi-factor authentication, requires more than a password to access an account. It significantly reduces the chance that a stolen password alone will lead to a mailbox takeover.
Also consider:
- Conditional access rules for Microsoft 365
- Alerts for unusual sign-ins
- Alerts when mailbox forwarding rules are created
- Reviews of inbox rules and deleted items
- Monitoring for automatic forwarding to external addresses
- Blocking legacy authentication where possible
- Strong email filtering and authentication controls
An attacker may create a hidden rule that forwards supplier conversations to an external mailbox or moves replies into a concealed folder.
Your IT provider should check for these changes during routine security reviews.
Train finance staff specifically
General cyber security awareness is useful, but finance staff need training designed around the decisions they make every day.
Train them to pause when:
- Bank details change
- A payment becomes unusually urgent
- A senior person asks them to bypass the normal process
- A supplier asks for confidentiality
- A familiar email thread contains a new payment destination
- A colleague is away and the approval process has changed
Make it clear that challenging a payment request is good practice, not an inconvenience.
Create a simple payment verification procedure
Your procedure does not need to be complicated. It could say:
- Pause any payment involving new or changed bank details.
- Check the request against the supplier record and purchase order.
- Call the supplier using a known, trusted number.
- Record the name of the person who confirmed the details.
- Obtain dual approval before updating the account or releasing the payment.
- Report anything suspicious to your manager and IT support provider.
Review the procedure at least annually and whenever your finance team, banking platform or accounting software changes. For many local firms, practical phishing protection Hampshire teams can follow starts with this kind of repeatable process.
The NCSC’s guidance on phishing scams also recommends reporting suspicious emails. You can forward suspected phishing messages through the NCSC’s Suspicious Email Reporting Service.
Hampshire example: a genuine invoice, a fraudulent bank account
Imagine a 30-person engineering firm in Winchester. It regularly pays £18,400 to a specialist supplier for materials.
The supplier’s finance manager is compromised through a stolen Microsoft 365 password. The attacker watches the conversation for three weeks. They see that:
- The invoice is due at the end of the month.
- The usual finance manager is taking annual leave.
- The managing director approves payments by email.
- The supplier and customer communicate through one shared thread.
On the morning the payment is due, the attacker replies within the genuine conversation. The invoice number and amount are correct, but the bank details have changed.
The temporary finance administrator updates the supplier record and asks the managing director for approval. The payment is sent before anyone phones the supplier.
The business only discovers the fraud when the real supplier sends a payment reminder several days later.
A ten-minute call to a known supplier number would probably have stopped the incident.
What should you do if payment redirection fraud happens?
Act quickly. Do not wait to gather every detail before taking the first steps.
- Contact your bank immediately. Ask the fraud team to attempt to recall or freeze the payment. Use the bank’s official number, not a number from the suspicious email.
- Tell the genuine supplier. Their mailbox may still be compromised, and other customers may be at risk.
- Report the crime to Report Fraud. This is the national reporting service for England, Wales and Northern Ireland.
- Report the phishing email to the NCSC.
- Preserve evidence. Keep the original emails, full headers, invoices, bank details, payment confirmations and relevant mailbox logs.
- Notify your cyber insurer or broker. Your policy may require prompt notification and may provide access to incident-response specialists.
- Check whether client or personal data was exposed. A compromised mailbox may contain contracts, employee information, customer records or confidential correspondence.
- Secure the affected account. Reset credentials, revoke active sessions, remove forwarding rules and enforce MFA.
The UK’s APP fraud reimbursement framework may cover qualifying authorised push payment scams. However, eligibility depends on factors such as the type of payment, the size and nature of the business, the payment provider and whether reasonable care was taken. The Payment Systems Regulator’s APP reimbursement guidance explains the framework.
Do not assume reimbursement is automatic. Contact your bank immediately and keep a record of your claim.
Why documentation matters for cyber insurance
Payment redirection fraud also connects directly to cyber insurance.
Policies vary, but insurers may question a claim if the business cannot demonstrate that it:
- Required independent verification
- Used dual authorisation
- Protected email accounts with MFA
- Trained relevant staff
- Followed a documented payment procedure
- Reported the incident promptly
A business may have insurance but still face difficulty if its actual controls do not match the answers given during the application process.
Read our guide to why cyber insurance requirements are becoming stricter and review your policy with your broker. You may also find our advice on choosing the right IT partner useful when assessing who is responsible for monitoring and protecting your systems.
Payment fraud is also a reminder that your supplier relationships and technology controls are connected. Our article on supply-chain cyber attacks explains why security weaknesses in a trusted third party can affect your own business.
Book a call about phishing protection in Hampshire
You do not need a large finance department to build effective payment controls. You need a clear process, secure email accounts and the confidence to pause a payment when something changes.
BITSmart provides phishing protection in Hampshire, email security and managed IT services that help businesses reduce avoidable disruption and financial risk.
If you would like to review your current controls, book a call with BITSmart. We can help you identify gaps, improve your verification procedure and strengthen your wider IT security for small business in Hampshire. Effective phishing protection Hampshire businesses rely on starts with clear checks, secure systems and support that makes those controls easier to maintain.





