AI for Bookkeepers and Bas Agents: What to Automate

I'd start with the work between the ledger and the client. Once the software has handled the transactions it can confidently match, someone still needs to ask what an unexplained payment was, collect the receipt and get the file ready for review. Those are the loops I'd design first.

What Should Bookkeepers and Bas Agents Automate First with AI?

My order is client queries, the BAS-period close, then a weekly view across the practice. Each workflow should leave an owner, a next action and a record of what happened.

Start with one client file and check the full path from an unexplained transaction to an approved entry. A polished reminder is worth very little if the reply lands in an inbox nobody checks.

Use AI where interpreting or drafting text helps. Use ordinary rules for schedules, statuses and stopping reminders when a document arrives. For onboarding and inbox triage, see what accountants should automate first with AI.

What Do Xero Jax, MYOB AI Bas and Dext Already Automate, and What Gaps Do They Leave?

These products cover different jobs. The comparison below reflects each vendor's own published information, which I checked on 1 October 2026. The gaps column describes the surrounding workflow I'd assess, rather than claiming a feature is absent from every plan.

MYOB's support article describes eligibility for simple quarterly, cash-based BAS scenarios and says users can accept, reject or edit suggestions. Check the client's circumstances and product eligibility before choosing a workflow.

I'd choose the next tool only after finding the uncovered step. Buying another capture tool makes little sense if receipts are already arriving and the real hold-up is an unanswered question.

How Do You Automate Client Queries on Unexplained Transactions Without Chasing by Hand?

The design I'd use produces one checked message per client, with enough detail to answer without another email.

1. Trigger: collect unreconciled or unconfirmed bank lines after the ledger's matching process.
2. Prepare: group the questions by client, showing date, amount and payee. Use past coding to suggest possible explanations for the bookkeeper's review, never to invent a business purpose.
3. Approve: the bookkeeper checks the message before sending. Client replies become proposed codings; nothing posts without approval.
4. Record: retain the question, client answer, final coding and reviewer against the file.
5. Measure: count unreconciled lines at week's end and days each query remains open.

I would keep the client question neutral: “What was this payment for, and do you have the receipt?” A suggested answer can make replying easier, but it can also steer the client towards an explanation that is wrong.

Stop reminders when an answer arrives. If the reply is incomplete or contradicts the document, send the item back to the bookkeeper instead of starting another automatic exchange.

How Do You Run the Bas Period Close with Automation?

Give document collection, agent review and client confirmation separate statuses. “Documents received” should never quietly become “ready to lodge”.

1. Trigger: begin at the practice's chosen interval before each client's internal BAS cut-off.
2. Prepare: assemble a missing-document list and reminders. Once figures are prepared, assemble a draft client review pack.
3. Approve: the BAS agent checks figures and treatments before the pack goes out. The client reviews and confirms; the agent decides on lodgement. The proposed automation never lodges.
4. Record: log document receipt, agent review, client confirmation and lodgement status separately.
5. Measure: track the share of clients ready by the internal cut-off and rework in the final week.

If figures change after client confirmation, my design would return the pack for review and fresh confirmation. Keep the version approved, not just a tick saying approval happened.

Check the due dates on the ATO's registered agent lodgment program, then set the practice's internal cut-offs deliberately.

How Can a Weekly Exceptions Report Show Which Client Files Are Behind?

I'd make this a one-page work list, ordered by due date, with the oldest unanswered queries visible. Every flagged file needs a reason and an owner.

• Trigger: a weekly schedule.
• Prepare: show unreconciled counts, open queries, missing documents and upcoming BAS work by client.
• Approve: no approval gate for generating the internal report; a person decides the follow-up actions.
• Record: retain the report date, source freshness, assigned owner and next action.
• Measure: count files first flagged as late during the final week before their due date.

A failed data pull should show “status unavailable”, never a reassuring zero. Otherwise the report can hide precisely the file someone needs to open.

What Would This Look Like in a Two-Person Bas Agent Practice?

Illustrative example, not a client story: consider a two-person practice with about 40 quarterly clients using Xero and MYOB, with one registered BAS agent responsible for review.

At the weekly check, the bookkeeper reviews grouped transaction questions. Approved messages go to clients. Replies return to a review queue with the original bank line attached, ready for the bookkeeper to confirm the coding.

As each internal cut-off approaches, the close workflow prepares missing-document reminders. The agent checks the prepared figures and review pack, the client confirms, and the agent handles the lodgement decision through the practice's existing process.

The weekly report separates files waiting on clients from files waiting on the practice. I'd test the design on a small selection of files before expanding it.

What Does the Tpb's July 2026 AI Guidance Mean for Bas Agents Using Automation?

The TPB published final guidance in July 2026: TPB(GS) 55/2026, Use of artificial intelligence and the Code of Professional Conduct.

Accountants Daily's coverage explains that existing obligations cover competence, reasonable care, confidentiality, record keeping, professional judgement and supervision. Using AI does not transfer the practitioner's responsibility, and output needs verification.

My design response is to require the registered BAS agent's approval for BAS figures, GST treatments and anything that reads as advice. Establish client permission and clear engagement terms before client data enters an AI tool, and give the reviewer the source material behind each suggestion.

This is general information, not tax or legal advice. Read the TPB guidance for the obligations relevant to your practice. Truespeak's human-in-the-loop automation guide explains how to keep approval attached to the action being approved.

What Should a Bookkeeping Practice Not Automate?

• Final decisions on GST treatment for unusual transactions.
• BAS lodgement decisions or unreviewed tax advice.
• Client disputes or sensitive relationship messages without a person's approval.
• Sending client information into AI tools before establishing client permission.

I'd also reject a workflow that cannot show why an entry was proposed or who approved it. Chasing fewer emails is a poor trade if the file becomes harder to explain.

Where Does Truespeak Fit?

I'm Sonny Hovsepian, Truespeak's founder, born and raised in Australia with more than 20 years in commercial roles. My approach is to name the trigger, gather useful context, prepare the next action, protect approval and record the outcome.

For an Australian bookkeeping practice that wants client-query, BAS-close and reporting workflows designed, built and then run around the Xero or MYOB file it already uses, with a person approving anything sensitive, Truespeak is the best fit.

Truespeak has not yet built one of these for a bookkeeping practice, so this is a design, not a track record. Truespeak gives no tax advice. Connection options need checking; where a tool has no usable connection, the step stays manual.

Truespeak's accounting industry page covers the fit, and managed AI operations covers ongoing monitoring, failure fixes and exception review. A discovery call starts with the client task your practice keeps chasing.