Recognising Phishing and Fake Regulator Messages
Learn to assess unexpected email, SMS and QR-code requests, including false notices that claim to come from Singapore regulators.

Xian Hui
9 November 2026 · 9 min read

In brief
How can an accountant spot a fake ACRA or IRAS message?
Look for unexpected requests for credentials, personal data or payments, changed website destinations, inconsistent sender addresses, unusual attachments and pressure to act quickly. A familiar logo or correct filing details do not prove authenticity. Check through an established official portal or independently obtained contact route, and report suspicious messages.
What you'll learn
- Identify warning signs in purported regulatory messages
- Distinguish a familiar logo from verified sender identity
- Choose an independent verification route
Recognising Phishing and Fake Regulator Messages
A junior accountant is closing a filing checklist when an urgent email appears to come from a government agency. It claims a client's company is at risk unless a document is reviewed immediately. The message has an official-looking header and a button to open a form. The accountant is under time pressure, but the appearance of the message is not proof that it is genuine.
Phishing is an attempt to persuade someone to disclose information, sign in to an imitation service or open harmful material. The message may arrive by email, text message, messaging application or a printed QR code. These channels look different, but the judgement is similar: verify the source before taking the action requested.
What makes an official-looking message suspicious?
A message can be convincing because it includes a real company name, a filing deadline or a reference to legislation. Attackers can copy public information. A familiar name, logo or email display name proves little on its own.
The Accounting and Corporate Regulatory Authority (ACRA) warned in March 2026 about scam emails claiming that companies might be struck off or had received compliance warnings. The Inland Revenue Authority of Singapore (IRAS) also maintains advisories about false tax-demand and filing messages. These are genuine regulator warnings about impersonation, not evidence that every unexpected message is fraudulent.
Look for a combination of signals:
| Warning sign | What to look for |
|---|---|
| Unexpected action | A link asks for credentials, identity details or a payment outside the normal portal. |
| Changed destination | The message directs the reader to a site that is not the established service. |
| Pressure | An unusually short deadline discourages checking with colleagues. |
| Different sender | The actual address or domain is inconsistent with the claimed organisation. |
| Unusual attachment | An unsolicited file asks the user to enable content or install software. |
No single warning sign is conclusive. Equally, an error-free email with an authentic-looking domain can still be unsafe if an account has been compromised.
How should an accountant inspect links and QR codes?
Treat an embedded link as a claim about where to go, not as an instruction to follow. On a computer, a link's displayed wording may differ from its destination. On a phone, the small screen can hide part of a long address. A QR code also conceals its destination until scanned.
If a supposed IRAS message says a tax filing must be corrected, open a new browser window and navigate independently to the established official portal. If a purported ACRA notice concerns a company, check through official channels already used in the practice. Do not rely on the contact number or new website supplied inside the suspicious message. When uncertain, ask the firm's designated reviewer.
Consider an original example: a message says 'Payroll submission failed' and offers a QR code to recover the account. The accountant should not scan the code from the message to sign in. They should instead open the payroll provider through their saved application entry point and review the status there.
What do scam messages in chat apps look like?
Scams also arrive inside messaging apps. The examples below are based on real messages received on WhatsApp.
Example: a warning that your account will be banned
This one claims to come from the app's security team. The sender's name and number are replaced, and the app's logo is left out. If you see a message like this, do not tap the button.
The warning signs in this message:
- The sender is a shop. A message about your account's security comes from a business account with an unrelated name, not from the app itself.
- The logo and banner prove nothing. Anyone can paste the app's logo into an image.
- It greets you by phone number. The sender knows your number, not your name.
- The deadline keeps changing. It says 24 hours, then 12 hours, and adds that appeals will not be accepted. The pressure is meant to stop you checking.
- The button is the trap. "Start verification" leads away from the app to a page that can ask for your verification code or sign-in details.
- The system notice is not an endorsement. A notice saying the business uses a service from Meta describes how that business account is run. It does not mean the app sent the message.
What to do: do not tap the button or reply. Use Block and report the chat in the app. If you are worried about your account, check it only from the app's own settings. If you have already tapped the button or entered a code, tell the firm's security contact straight away and check the message with ScamShield or the 1799 helpline.
Example: a request to vote for a friend's child
This message arrived from a contact on WhatsApp, written in French. The names and link are replaced.
In English: "Hi! Could you take a moment to vote for [name]? She is a friend's daughter, and the first prize is a scholarship for her studies. Every vote really counts. Thank you very much!"
- It uses your name and a kind cause. Helping a child win a scholarship feels harmless, so people tap without thinking.
- The language and timing are off. A message in a language the sender does not usually use, sent at 2:24 am, is a reason to pause.
- The link goes to an unfamiliar site. A genuine contest is run on a site you can find yourself, not on an unknown address ending in .sbs.
- A vote should never need a sign-in. If the page asks for your phone number, a verification code or your chat app login, close it. Never share a verification code that arrives by SMS.
If the message came from someone you know, their account may already be in someone else's hands. Call them on a number you already have to tell them, and do not reply in the chat.
Why are urgency and familiarity powerful?
Accounting work is deadline-driven. Staff recognise recurring topics such as corporate filings, payroll, goods and services tax and annual returns. Attackers can place false requests inside this familiar context. A message asking for immediate action may seem like another item on a busy month-end checklist.
Create a deliberate pause for requests involving credentials, personal data, downloads or money. The pause need not be long. It can be a consistent step in the practice's workflow: check the destination, verify independently and document what you did. The FBI's business email compromise guidance also recommends checking information through an independently obtained contact number.
What should the team do with a suspicious message?
Do not click, open or forward a suspicious attachment. Use the firm's established reporting method so the security contact can review it. If the message was merely received, say so. If a link was opened or credentials were entered, say that clearly as well. Early accurate reporting helps the firm distinguish a harmless attempt from a possible incident.
A staff member does not need to prove an email is malicious before reporting it. Their job is to recognise uncertainty and avoid turning it into an unverified action.
Key takeaways
- Regulator names, logos and apparently correct filing details do not verify an email.
- Inspect the request, then use a separate trusted route for any important action.
- Treat links, QR codes and attachments as possible routes to the same impersonation attempt.
- Report a suspicious message and disclose any action already taken.
Last source check: 9 November 2026.
Next in the course: How to Inspect Email Headers in Gmail and Outlook
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.


