AI for Australian Bookkeepers: BAS Prep, GST Checks and Xero

An Australian bookkeeper can use AI to prepare a BAS by flagging unusual GST codes, matching transactions to tax invoices and explaining reconciliation differences, while a person confirms the tax treatment and lodges through the authorised process. Start with the quarter's reconciled ledger, check G1, 1A and 1B against source records, then resolve every material exception before approval.

Xero's JAX can reconcile high-confidence bank transactions on the Grow, Comprehensive and Ultimate plans (and on Ignite through a paid add-on), but a bank match is not a GST decision. The bookkeeper still needs to inspect the underlying invoice, business purpose and tax code. If the client's reporting method, registration or an unusual supply is unclear, involve a registered BAS or tax agent rather than accepting a model's confident explanation.

Follow me on Instagram@sagnikteaches

Lock the quarter and its reporting method

Begin with the client's BAS period and the GST accounting method recorded in the accounting file. Check that all bank feeds for the quarter have imported, outstanding items are identified and opening balances agree with the previous close. Do not ask AI to summarise a period that is still receiving late entries. Save a snapshot of the trial balance, GST report, sales and purchase ledgers, bank reconciliation report and prior BAS working papers. A later adjustment should be visible as a change, not silently folded into the original export.

Connect on LinkedInSagnik Bhattacharya

The ATO's Simpler BAS bookkeeping guide works with three GST labels: G1 total sales, 1A GST on sales and 1B GST on purchases. The same guide says GST-free and input-taxed sales still go in G1, and that the business reports G1 either GST-inclusive or GST-exclusive and must indicate which. Do not assume every client is on the same reporting basis or that every other BAS obligation disappears. Check the client's ATO account, existing lodgements and adviser instructions. A bookkeeper should also confirm whether entries belong to the quarter under the client's cash or non-cash accounting method. AI is poor at resolving that question from a bare transaction list because the timing may depend on invoice and payment records.

Subscribe on YouTube@sagnikteaches

A short quarter-start checklist can read: “Period confirmed; reporting method confirmed; bank feeds complete; unreconciled lines counted; suspense accounts reviewed; invoice capture backlog counted; prior-period adjustments listed; reviewer assigned.” Fill it with actual figures. An illustrative client might have 412 bank lines, 19 unreconciled lines and seven bills awaiting evidence. The AI review should not begin by declaring the BAS ready; it should produce an exception queue for the 19 and seven.

Use JAX as a matching assistant, then inspect tax codes

Xero says its JAX automatic bank reconciliation uses Rule, Match, Memory and Prediction methods, with high-confidence lines reconciled and others left for review. Xero's reconciliation page lists it on Grow, Comprehensive and Ultimate, with Ignite able to add it through a paid add-on called AI Automate. JAX only reconciles automatically when it is highly confident; otherwise it suggests a match and leaves the line for a person, and it can be switched off per bank account. That is useful for bookkeeping throughput, but the result still needs human sampling and tax review. Check the current plan and permissions in the client's organisation before assuming the feature is enabled.

Review auto-reconciled transactions by risk rather than looking only at unreconciled lines. Filter for new suppliers, unusual amounts, changes in tax rate, repeated descriptions with different codes and entries close to the quarter boundary. Compare the tax code in Xero with the invoice and the nature of the purchase. A payment description such as “office supplies” does not establish that GST was charged or that the purchase was wholly for business. The receipt capture and categorisation tutorial covers the earlier data-entry stage; the BAS review asks whether the resulting tax treatment is supportable.

For example, a recurring software subscription may change from a local supplier invoice with GST to an overseas invoice without it. JAX might match both payments to the same account or prior memory. The bookkeeper should inspect the new invoice and correct the tax code if the evidence differs. A reconciled green tick only says the bank line has been accounted for; it does not certify the GST component.

Build an exception list from the GST export

Export transaction date, document date, supplier or customer, account, gross amount, GST amount, tax code, invoice reference and reconciliation status. Keep identifiers needed to trace back to Xero, but remove unnecessary personal information before using an external model. If the firm's approved tool can analyse the file within its governed environment, use that route. Tell the model to flag patterns and show calculations, not to change the ledger or decide claims. Every flagged row should point to the original Xero transaction and supporting document.

Review this quarter's GST transaction export for possible coding errors.
Flag: unusual GST-to-gross ratios, new suppliers, repeated suppliers
with inconsistent codes, duplicates, missing invoice references,
private-use indicators and entries near the period boundary.
For each flag, show row ID, arithmetic and the question for a human.
Do not decide eligibility or alter any tax code. Say "uncertain" when
the export lacks a document or business-purpose explanation.

Run on a sample export, the model might return (illustrative): “Row 084: gross A$550, GST A$50, ratio appears consistent with a fully taxable purchase; invoice absent; request evidence.” That is more useful than “claim A$50.” Another line might say, “Row 117: gross A$1,100, GST A$100, category staff entertainment; confirm business purpose and treatment with adviser.” The arithmetic can be right while the claim is wrong. Ask the tool for the exact row and reason so the bookkeeper can review without searching a long narrative.

Use a manual scan for items the model might miss: credit notes, refunds, asset purchases, mixed-use items, imported services and adjustments posted directly to GST accounts. A simple anomaly rule can highlight GST values that are neither zero nor near one-eleventh of an inclusive amount, but it must not automatically mark them wrong; partial credits and adjustments can be legitimate. Keep a resolved-exceptions column with document link, decision, reviewer and date. This prevents the same question resurfacing at every quarter-end.

Check tax invoices before taking credits

The ATO says you must hold a tax invoice to claim a GST credit on a purchase costing more than A$82.50 including GST, and that you should wait until it arrives before claiming, even if the credit then falls into a later reporting period. The supplier has 28 days to provide one after a request. For A$82.50 or less, a tax invoice, cash register docket, receipt or invoice is enough. The rule has conditions and exceptions, so use the ATO's current tax invoice guidance and adviser judgement for the client. AI can locate missing reference numbers or extract invoice fields, but a supplier name and bank amount are not the invoice itself.

Take an A$330 purchase (illustrative figures): the export shows A$30 GST and the bank payment matches, but the uploaded file is only a card receipt without enough tax-invoice details. Flag the row for evidence, ask the supplier for a valid tax invoice and hold the credit until it arrives, even if that moves the claim into a later quarter. Do not let the model fill in the supplier's registration number or manufacture an invoice. If the invoice later arrives with a different amount, reconcile the document to the transaction rather than forcing it into the original coding.

Check supplier GST registration where relevant and ensure the purchase is for the client's creditable business activity. A client might submit a personal purchase from the same retailer used for business supplies. The invoice may show GST perfectly, but that does not make the amount creditable to the business. For a mixed-use expense, record the business-use basis and ask the responsible tax adviser if the allocation is uncertain. AI can calculate an approved percentage; it should not invent one.

Reconcile the BAS labels to control accounts

Compare the GST report totals with the GST control or suspense accounts, sales ledger and purchase ledger. Investigate journal entries that bypassed normal invoice coding. Treat those reconciliations as the control, with every exception listed by transaction. Do not accept a neat AI summary if the ledger balances do not tie. The difference has to be explained by named transactions or an approved timing adjustment, not labelled “rounding” because it is inconvenient.

For G1, compare the sales report with total sales under the client's reporting method and confirm how GST-free or other categories are included. For 1A, inspect GST on taxable sales and adjustments. For 1B, inspect input credits supported by purchase evidence and the client's entitlement. The label definitions and reporting basis need current ATO verification, especially when the client has other BAS obligations. Keep a sheet with expected amount, report amount, difference, investigation and final approved amount for each label.

Suppose the AI summary says 1A is A$5,000 while the GST control account shows A$5,110. An A$110 difference may come from a late taxable invoice, a manual journal or a refund entered with the wrong sign. The bookkeeper should trace the difference to a transaction, review the document and either correct the ledger or document a valid timing reason. It should not adjust the BAS by A$110 simply to make the totals agree. The month-end checks tutorial can help organise the wider close before this tax-specific reconciliation.

Work through a quarter with a wrongly coded purchase

Use these illustrative figures, not a client tax calculation. A small catering company records A$55,000 of taxable sales including A$5,000 GST and A$4,000 of GST-free sales during the quarter. The client reports G1 GST-inclusive in this example, so draft G1 is A$59,000, including the GST-free sales, and 1A is A$5,000. The purchase export shows A$22,000 of transactions coded as taxable, including A$2,000 of claimed GST. An AI exception report flags one A$1,100 purchase because the invoice reference is missing and the description says “family event supplies”.

The bookkeeper obtains the receipt and client explanation. In this illustration, the A$1,100 item was wholly private, so its A$100 GST should not be claimed by the business. After the approved correction, eligible taxable purchases in this simplified example are A$20,900 including A$1,900 GST. Draft 1B falls from A$2,000 to A$1,900. The simplified net GST amount changes from A$3,000 to A$3,100 before considering any other BAS items or adjustments. The bookkeeper records the invoice, explanation and correcting entry, then asks the responsible adviser to approve the treatment.

This example illustrates why the anomaly check and document review must be connected. The A$1,100 line had a mathematically normal GST component, so a ratio test alone would pass it. The clue came from missing evidence and a description that warranted a business-purpose question. A different client might legitimately buy supplies for a paid event with similar wording. AI should raise the question, not turn the phrase into a verdict. Keep the correction in Xero so the BAS report and ledger agree rather than changing only a separate spreadsheet.

Give the reviewer a compact evidence pack

Prepare one pack containing the draft BAS report, reconciliation sheet, unresolved exception list, material tax invoices, adjustment log and prior-period notes. For every exception, show the original amount, proposed correction, source document and person who approved it. A reviewer can then spend time on judgement rather than reconstructing how the totals were obtained. Do not ask an AI model to produce a final “BAS approved” statement; it has no authority to accept the filing risk.

A filled illustrative exception line could read: “Row 084, A$550 gross, A$50 GST; invoice uploaded 14 October; supplier and amount matched; business use confirmed by owner; code retained; reviewed by [reviewer].” Another could read: “Row 117, A$1,100 gross, A$100 GST; private expense confirmed; GST claim removed; correcting transaction posted; adviser review pending.” The second line remains open until the reviewer has signed it. Open exceptions should not disappear from the summary merely because a draft amount was calculated.

Run a final comparison after corrections. Refresh the Xero reports, reconcile them to the review sheet and check that the BAS period and labels have not shifted. If a client posts a late invoice after the pack is prepared, record whether it belongs in this period under the client's method and regenerate the affected totals. Ask a qualified adviser about uncertain GST treatment or lodgement duties. The guide to AI tools for accountants discusses wider tool selection; the practical gate here is evidence and sign-off for this quarter's figures.

Measure the review by errors found, not lines processed

For the next two quarters, record how many transactions were auto-reconciled, sampled, flagged, corrected and left unresolved at hand-off. Compare the time spent on exception investigation with the old method, including the time spent fixing AI false alarms. A good review may generate fewer flags after recurring supplier rules are cleaned up. A bad review can create hundreds of low-value warnings that hide the one private-use purchase or duplicate invoice that matters.

Choose a sample of transactions the model did not flag and inspect those manually. If a meaningful error appears in the supposedly clean sample, expand the test and adjust the flag rules. Keep tax-code overrides and new suppliers prominent in each quarter's report. Review Xero's current product documentation when enabling JAX or changing plans, because features and labels can change. The BAS remains a human-approved regulatory return even when much of the bank matching and exception sorting is automated.

Test credit notes and cut-off dates separately

Credit notes and refunds can reverse part of an earlier supply, but the export may show them as ordinary negative lines. Ask the AI review to list negative GST amounts and link them to the original transaction. A reviewer should confirm the document, the reason for the credit and the correct reporting period. Do not allow a model to net an unmatched negative line against an unrelated invoice simply because the amounts are close. The wrong match can hide both a missing credit and an overclaim.

For example, a supplier issues an illustrative A$220 credit note for goods returned after the quarter closes. The original purchase was coded with A$20 GST. If the credit note belongs to the following reporting period under the client's method, forcing it into the earlier quarter changes the wrong BAS. Record the date, document reference, original invoice and adviser decision. The AI can flag the date difference; it cannot infer the reporting method from the sign of the amount.

Cut-off tests should include the first and last week of the quarter. Compare invoice dates, transaction dates and payment dates for a sample of sales and purchases. A customer payment received on the last day may relate to an earlier invoice; a bill entered after quarter-end may have a date inside the period. The correct treatment depends on the client's accounting method and the underlying facts. Keep a cut-off log with the decision and source rather than repeatedly asking an assistant which date “counts”.

A cancellation can create two entries that appear to offset but have different GST codes. Picture an A$550 sale followed by an A$550 refund (illustrative): one line may show A$50 GST and the other zero. The net cash movement is nil, yet 1A may be wrong. A bank-only review would miss the discrepancy. Compare invoice and credit-note tax codes at transaction level, and fix the accounting records before generating the final BAS figures.

Keep the client questions narrow and answerable

When an exception needs the client's input, send a short question tied to a transaction ID and document. “Was the A$1,100 purchase on 18 September wholly for the business, partly private, or wholly private?” is easier to answer than “Please explain your expenses.” Ask for the invoice through the firm's secure document route. Do not include a large AI-generated explanation of tax law in a routine evidence request; it may confuse the client and suggest that the answer has already been decided.

Keep unanswered questions visible in the hand-off pack. An illustrative list might show three open items: a missing tax invoice for A$330, an A$880 subscription with an unclear supplier location, and an A$1,100 mixed-use purchase awaiting an allocation. Give each an owner, requested date and proposed action if no answer arrives. That helps the adviser decide whether to wait, adjust, or handle the item in a later period under the rules. The model should not silently set unresolved amounts to zero or assume full credit to make the pack look finished.

Once the client replies, compare the answer with the document and ledger entry. A client saying “business expense” does not replace a required invoice, and a receipt does not prove a wholly business purpose. Record both pieces of evidence and the reviewer's conclusion. This is the practical advantage of an exception workflow: AI helps surface the right question, while the bookkeeper and adviser make the decision from records they can inspect.

Questions at the BAS review stage

Does Xero's JAX automatic reconciliation approve GST treatment?

No. Xero says JAX can automatically categorise and match high-confidence bank transactions on Grow, Comprehensive and Ultimate plans, with a paid add-on route on Ignite. A bookkeeper still needs to review tax codes, supporting invoices, exceptions and the BAS figures. A correctly matched bank line can still have the wrong GST treatment.

Can AI decide whether a purchase has a GST credit?

Use AI to flag a purchase for review, not to make the claim. Check business purpose, GST registration, invoice evidence and the applicable ATO rules. If the facts or tax treatment are uncertain, ask a registered BAS or tax agent before lodging. Retain the supporting document and the reason for the chosen code.

What should happen when a supplier invoice is missing?

Mark the transaction as evidence pending, request the invoice and follow the ATO requirements for the amount and reporting period. Do not let a model infer a tax invoice from a bank description. The bookkeeper should document the decision and have the responsible adviser review any uncertain claim before the BAS is lodged.

Further reads

• AI for Accountants in Australia: Tax Agent Duties and Client Data — Review professional duties when client data enters AI tools.
• Bank Statement PDF to Excel With AI: Check Every Line Before Import — Check extracted statement lines before importing them.
• Is AI Worth It for a One-Person Bookkeeping Business? — Decide whether a small practice benefits from automation.
• Is Xero Smart Document Capture Enough Without Dext? — Assess capture quality before relying on bill data.
• How to Clean Messy Data in Excel: Step-by-Step Guide — Prepare exports for a reliable exception review.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: ATO guidance on Simpler BAS, GST credits and tax invoices, and BAS preparation controls; Xero automatic bank reconciliation (JAX) page; ATO When you can claim a GST credit. Verify current ATO instructions and client method before lodging.