Explaining a Tax Law Change to Accounting Clients Without Sounding Like a Compliance Memo

01 September 2026·6 min read

Quick answer: The trick to explaining a tax law change without sounding like a compliance memo is separating the technical record (which stays precise, and lives on file) from the client-facing update (which follows a simple four-part formula: what changed, who it affects, what it means for them, what they need to do). Send the plain-English version first, keep the detailed version one click away, and never make a client work out whether the change applies to them. Below is the exact formula, three worked examples, and the mistakes that make clients switch off before they finish reading. 📈

Every tax season, someone in the firm drafts a beautifully accurate update on a legislative change, sends it to the whole client list, and wonders why nobody reads it. The problem usually isn't the accuracy — it's that the email reads like it was written for the ATO, not for a cafe owner trying to figure out if this affects their BAS. Here's how to translate a change into something clients actually finish reading. 💖

What most accounting firms get wrong

Leading with the legislation, not the impact — clients don't care what schedule or ruling changed; they care whether it changes what they owe or what they need to send you.
One email for every client — a change that matters to trusts gets sent to sole traders too, who skim it, feel vaguely anxious, and ring the office to ask "does this affect me?" (which is the exact call you were trying to avoid).
No clear action — the update explains the change beautifully and then just... stops. If there's nothing for the client to do, say so explicitly, or they'll assume there is and worry.
Treating "plain English" as "vague" — simplifying the language isn't the same as being non-specific. You can be plain and precise at the same time.

Please note: general information, not tax advice — check current official guidance before relying on it. This article covers how to communicate a change to clients, not the technical detail of any specific change.

The plain-English translation formula

Keep your technical file note exactly as precise as it needs to be. For the client-facing version, run it through this structure:

1. What changed — one sentence, no section numbers, no "the amendment to..."
2. Who this actually affects — name the client type, not "all taxpayers" or "some businesses."
3. What it means for you — the practical outcome, in admin terms or ballpark impact, not compliance language.
4. What you need to do — a specific action, a document to send, or plainly: "nothing — we're handling this for you."
5. Who to ask — a named person and a direct way to reach them, not "our office."

Three worked examples

Hospitality client (small cafe owner): "There's a change to how a certain type of business expense gets treated this year. It applies to businesses running a mix of eat-in and takeaway trade like yours. In practice, it may change how we categorise a portion of your costs at tax time — nothing changes for how you run the till day to day. You don't need to do anything right now; we'll flag it during your next quarterly check-in. Questions in the meantime? Reply here or call Sarah direct."

Medical practice (specialist with a practice trust structure): "A change affecting trust distribution arrangements has come through this year. This one is relevant to your structure specifically, not every client on our books. It could affect how distributions are documented before year end. We'd like to book 20 minutes before your usual EOFY review to walk through what it means for your setup — here's a link to grab a time with James."

Property investor client: "There's an update to record-keeping requirements for a category of deduction some investors claim. If you own an investment property, this is worth five minutes of your time. Short version: we may need one extra document from you this year that we haven't asked for before. We'll send a checklist closer to lodgement — no action needed from you today."

Choosing the right channel and the right list

Not every change deserves an email blast. A rule of thumb: if it affects a specific client segment (trusts, a particular industry, a particular structure), segment your list and only send it to them — everyone else gets silence, which is a relief, not a gap in service. If it affects almost everyone, a short GBP post, a newsletter item, or a line in your EOFY campaign can do the job without a dedicated email. Save the one-to-one email or a booked call for changes that genuinely need a document or a decision from that client. And if a change is complex enough that plain English risks losing something important, that's the signal to book a conversation instead of writing a longer email — some things are actually clearer said out loud.

💡 Heads up: Keep a second, fully technical version of every client-facing update in the client file or your practice management system. The plain-English version is what the client reads; the technical version is your record that the advice given (or the update sent) was accurate and complete. Never let the simplified version become the only record.

Mistakes that quietly undermine trust

Sending the same update to everyone "just in case" — it trains clients to skim, which means they'll skim the one that actually matters to them too.
Burying the action in paragraph four — if there's something to do, it should be obvious within the first two sentences.
Using the update as a sales pitch — clients can tell when "here's what changed" turns into "and that's why you need our new advisory package." Keep the two separate, even if there's a genuine opportunity to raise later.
No named sign-off — "The Team" doesn't answer questions. A name and a direct contact method does.

Frequently asked questions

Will simplifying the language put us at risk if a client misunderstands?

It's a fair concern, and it's the reason the technical record matters — keep a precise, complete note on file for every update you simplify externally. The plain-English version should still be accurate, just less dense; it's a translation, not a dumbing-down. If a change is genuinely complex or client-specific, that's a reason to book a call rather than compress it further into an email.

How do we know which clients a change actually applies to?

Segment your client list by structure and industry ahead of time (trusts, sole traders, specific industries) so that when a change lands, you're filtering an existing list rather than guessing under deadline pressure.

Should every update go out as an email?

No — match the channel to how many people it affects and how urgent it is. Broad, low-urgency changes suit a newsletter item or a GBP post; narrow or urgent ones suit a direct email or a booked call.

What if a client still doesn't read it?

Some won't, no matter how well it's written — that's honest reality, not a writing problem. A short subject line naming the action (or lack of one) and a follow-up prompt at the next scheduled touchpoint catches most of the rest.