AI for Australian accountants: Claude vs ChatGPT for Xero, MYOB and BAS work

This guide is for Australian accounting and bookkeeping practices in 2026, sole practitioners through to 10-staff firms. We work with several Australian accountants via DotVA; this is the playbook we’ve watched work.

Setup at a glance. Total time to first useful workflow: about 1 hour for chat-based work, ~30 minutes more if you want the Xero MCP connection wired up (we can do that for you on a Quick Start, or you can follow the MCP setup linked below). No coding required for any of this. You paste transactions, you review suggestions, you accept or reject. Tier for client data: Claude API or Bedrock Sydney, not consumer chat. See the AI privacy guide for the three-tier framework.

Disclaimer up front: AI does not replace TPB registration, professional indemnity, or judgment. It removes manual grind. The accountant is still on the hook.

What each model is actually good at

For accounting-specific work, the model breakdown looks like this:

Most practices we work with end up running both, Claude in the back office for the heavy work, ChatGPT or Copilot inside Office for the day-to-day.

Five workflows worth building first

1. Xero coding suggestions

Pull last month’s unreconciled transactions. Feed to Claude with your chart of accounts. Get suggested account codes + GST treatment.

Hit rate at a typical Australian small practice (general business, not specialised): ~85% correct first time. The 15% that Claude gets wrong, it usually gets wrong consistently (e.g. all subscriptions to a specific software vendor), easy to add to your prompt as a rule.

Time saved per client per month: 30-90 minutes. At $150 AUD/hour billed, this pays for the entire AI stack at the practice in week one.

2. Monthly client report drafting

End of month: pull Xero P&L + balance sheet + cashflow. Ask Claude to write a 1-2 page client report. Variance analysis, callouts on unusual movements, plain-English summary.

Prompt template:

You are drafting a monthly management report for {client name}, an Australian
{industry} business with annual revenue of ~{$X AUD}.

Data: P&L for {month}, comparison to prior month and same-month-prior-year.

Audience: the business owner. Not an accountant. Plain English. No jargon
without immediate explanation.

Sections:
1. Headline (1 sentence: how was the month)
2. Revenue (what's working, what's not)
3. Expenses (top 3 movements)
4. Profit + cashflow
5. Watch-outs for next month
6. Suggested questions for our next catch-up

Keep under 600 words. Use AUD with thousands separators. No em dashes.

Edit lightly. Send.

3. BAS sanity check

After your usual BAS prep workflow, feed the completed BAS draft to Claude with the underlying Xero data and ask:

Verify this BAS draft against the source data. Check:
- GST collected matches sales × applicable GST rates
- GST paid matches purchases that should attract GST
- PAYG withholding matches payroll
- W1, W2 numbers are internally consistent
- Anything suspiciously round (suggests manual entry rather than calc)

Flag anything that doesn't reconcile. Do not change the BAS.

It catches roughly one error per 30 BAS submissions, in our experience. One error per 30 quarters is enormously cheaper than missing one and getting an audit.

4. ATO ruling research

For client questions like “is this expense deductible?” or “how does this work for an SMSF”:

• Open ChatGPT with browsing
• Ask: “Find the most recent ATO ruling or interpretive decision on [topic]. Cite the ruling number. Summarise in plain English. Note any 2025-2026 updates.”

ChatGPT’s web search beats Claude’s for current ATO content because the ATO website’s structure plays better with Bing-style indexing. (Claude has web search via the API, but for accounting research specifically, ChatGPT wins on freshness.)

Always verify the ruling number against the ATO website before relying on it.

5. Bookkeeping triage agent

For practices doing volume bookkeeping: an overnight agent that reads each client’s Xero, identifies transactions that need attention, and writes a “todo” list per client for the bookkeeper.

Build pattern: same as our nightly inventory agent, but pointed at Xero MCP instead of Shopify MCP. Roughly 90 minutes to build, ~$15 AUD/month per client to run.

The bookkeeper opens Slack at 8 AM with a per-client work list. Saves the morning triage. Especially valuable for practices with offshore bookkeepers, the agent works in their morning, the work is queued when they start.

What not to do

• Don’t auto-post journals. Even with high confidence. Always human-approve before write.
• Don’t feed Claude.ai (consumer) anything client-identifiable. Use the API or a paid Anthropic Console seat where the data-retention policy is contractual.
• Don’t replace your final review. AI-drafted client reports go out signed by you. Read them.
• Don’t use AI for the client conversation. The math, yes. The relationship, no. Your clients pay you because you’re a human they trust.

Cost calibration for a typical 3-person AU practice

Against the time saved per client per month, this pays back inside the first client.

Where to start tomorrow

Pick one client. Run last month’s transactions through Claude with the coding-suggestions prompt above. Compare to what you (or your bookkeeper) actually coded. Measure the time difference and the accuracy.

If it lands, scale to the next 5 clients. Don’t try to roll across the whole practice at once.

If you’d like us to set up the workflow for your practice, DotVA does this for accounting firms regularly, book a free audit and we’ll map your specific workflow first.