Accountants guide · Tax-time vishing

ATO impersonation, myGov lures and the “client” who calls your practice.

Tax time creates believable reasons to call, click and change refund details. Protect clients in both directions: from the fake authority and from the fake client.

One season, two directions

The same tax context can deceive a client or a practice.

Scamwatch warns that criminals impersonate the Australian Taxation Office and myGov through calls, texts, emails and websites. The lure may promise a refund, claim an account is suspended, allege a tax debt or demand identity information. Tax time gives each story a familiar setting.

The reverse attack receives less attention. Someone calls the accounting practice pretending to be a client. They may know names, tax details or the existence of a refund because an inbox or document has been compromised. Their goal is to change the bank account before the refund is paid, alter contact details or extract information that supports another fraud.

Caller ID, a familiar voice and knowledge questions are weak evidence. Caller ID can be spoofed, voices can be imitated and private facts can be stolen. The useful question is whether the person can complete a check through the trusted contact point the firm established before the suspicious request.

01 · Tax-time threat calendar

Prepare before EOFY urgency becomes normal.

The methods are not confined to one month, but the stories track the tax cycle. Use this calendar as a communication and training rhythm, not as a claim that scams stop outside the dates shown.

  1. 01 · May–June

    Pre-EOFY setup

    Fake tax-preparation offers, myGov sign-in lures and calls warning of an urgent account problem begin to meet genuine EOFY planning. Firms should brief staff and publish client warnings before the volume rises.

  2. 02 · July

    Refund expectations

    Clients expect ATO messages and may act quickly on a supposed refund, debt or identity alert. Fraudsters can also call practices asking to replace the bank account recorded for a refund.

  3. 03 · August–September

    Peak lodgement activity

    Busy inboxes and queues make urgency effective. Messages may imitate the ATO or myGov, while callers use real tax context to sound like clients and pressure staff to skip normal checks.

  4. 04 · October and later

    Deadlines and follow-up

    Deadline anxiety, delayed refunds and amendment conversations create another reason to respond. Keep the same verification rule after the campaign has faded from staff attention.

Schedule the staff refresher and client message for May or June. During the season, use short queue reminders and discuss real attempts without exposing client information. After October, review failed checks and exceptions while the operational detail is still fresh.

02 · Follow the direction of trust

ATO to client. Fraudulent “client” to practice.

The fake authority

The criminal borrows the ATO or myGov identity to create urgency. They direct the client to a false sign-in page, ask for credentials or codes, demand payment, or use a conversation to collect identity data.

Safe response

Stop contact, avoid links and attachments, and navigate independently to the official service. If uncertain, contact the ATO or the practice through a trusted, independently sourced channel.

The fake client

The criminal borrows the client's identity to influence the firm. They ask reception to “quickly” replace refund details, update a mobile number first, reset access or disclose enough information to make a later attempt stronger.

Safe response

Pause the request, disclose nothing further and return to the trusted mobile number already held on file. A failed independent check is a reason to escalate, not to keep testing the caller with more private questions.

The load-bearing rule

Never verify through the channel that delivered the suspicious request. Do not use a link in the message, reply to the email or trust the incoming caller ID. Start again from an official service or a contact record established independently.

03 · Front-desk verification script

Give reception words that work under pressure.

“To protect every client, we independently verify requests that change bank or contact details. I can't complete the change during this incoming call. I'll use the mobile number already recorded in our practice system and send a Vericode SMS. Please read that Vericode code back when we reconnect. We will never ask for your myGov, ATO or bank security code. If the recorded number is no longer available, I'll pause the request and have an authorised team member follow our alternate verification process.”

01

Recognise the trigger

Treat changed refund accounts, contact numbers, authorities, email addresses and urgent requests for disclosure as high-risk, even when the caller knows the client's file.

02

Pause without accusing

Tell the caller the firm applies the same protection to every consequential change. Do not confirm private file details to establish rapport.

03

Return to the trusted number

Use the mobile number already held in the practice system. Do not use the incoming caller ID or a replacement number supplied during the call.

04

Complete the check

Send a one-time SMS code to the trusted mobile number. Ask the person reached to read it back; never ask them to send the code by email or disclose a myGov code.

05

Handle a mismatch

Stop the request, reveal no further information, preserve the call details and follow the firm's escalation and suspicious-activity process.

06

Record the decision

Connect the original request, trusted contact source, verification result, escalation, approval and final action in the client record.

Print this section beside the phone or adapt it to the firm's approved procedure. A standalone downloadable script pack is planned; the complete working script and procedure are provided here in the meantime.

04 · A check the firm can review

Keep the verification event separate from the client's secrets.

Staff highlight a phone number already visible in a browser-based practice system, tax portal or email client, right-click and send a one-time SMS code. The person reads the code back. Verification messages are sent through Australian SMS provider MobileMessage, using Vericode's ACMA-registered sender ID, VERICODE.

Each authorised-contact check creates a timestamped, hash-chained record of who requested it, the masked target, method and outcome. Compliance-authorised users can export the result as PDF or CSV. The record can support the firm's procedure, but it does not prove bank-account ownership, replace professional judgement or complete customer due diligence.

Customer and verification data (recipient details, messages and verification records) is hosted in Australia. Staff sign-in is handled by our identity provider, WorkOS, in the United States; see the subprocessor information below.

05 · EOFY newsletter copy

A client-ready warning you can use.

Tax-time scam reminder

Tax time brings an increase in messages and calls impersonating the ATO, myGov, accounting firms and their clients. A scam may promise a refund, threaten an urgent debt, link to a fake sign-in page or ask you to reveal a security code.

We will never ask for your myGov, ATO or bank password or one-time sign-in code. If you receive an unexpected request that appears to come from us, do not rely on the message's reply address, link or phone number. Contact our office using the number published on our website.

We independently verify requests to change sensitive contact or payment details using information already held in our records. This brief pause protects both you and the practice. If a request feels urgent or unusual, stop and check through a trusted channel.

  • Pause when a caller or message creates urgency, threatens arrest or demands immediate payment.
  • Do not click a sign-in link in an unexpected tax message. Navigate to myGov independently using the official app or a saved address.
  • Never share a myGov sign-in code, password or one-time security code with a caller.
  • Confirm an unexpected request using a trusted number sourced independently, not the contact details in the message.
  • Call the practice through its published number if an invoice, refund account or staff request seems unusual.
Sources

Public guidance is cited for context. No government or CPA Australia endorsement of Vericode is implied.

Make the safe response routine

Give every suspicious tax-time call the same calm pause.

Brief staff before EOFY, warn clients through a trusted channel and independently verify consequential changes before the practice acts.

General information only. This guide is not legal, tax, cybersecurity, AML/CTF compliance or incident-response advice. Follow official ATO, Scamwatch and firm guidance for your circumstances.