Claude for Small Business arrives with a set of ready-made connectors, and the default accounting hookup is QuickBooks. That fits the United States, where QuickBooks is the common choice for small business books. In Australia it opens a gap, because most local businesses keep their accounts in Xero, with MYOB a close second. If you run an Australian company and want Claude reading your numbers, the out-of-the-box list will not match your stack. Here is what actually connects today, what needs a bridge, and how to set it up without handing over more than you should.
Why QuickBooks is the default
The connector list in Claude for Small Business reflects the software that US small businesses reach for most, and QuickBooks holds a large share of that market. So it sits near the top of the defaults. Xero tells a different story here at home. Across Australia and New Zealand, Xero is the dominant cloud accounting platform, used by hundreds of thousands of small businesses, while QuickBooks trails well behind. MYOB rounds out the local picture.
So the mismatch is not a fault in the product. It is a question of which market the defaults were built for first. Once you see it that way, the fix is straightforward: give Claude a path to your Xero or MYOB data, and the rest of the experience works the same as it would for a QuickBooks user in the States.
What Xero users can do with Claude today
You do not need an official one-click Xero connector to get value. A few paths work right now:
Xero API bridge: Xero publishes a full API, and a small connector or MCP layer can let Claude read invoices, contacts, and reports on request. This is the closest thing to a native hookup.
Report exports: Export a Profit and Loss, Balance Sheet, or Aged Receivables report from Xero as CSV or PDF, then hand it to Claude to read, summarise, and flag.
Scheduled pulls: A short automation can fetch a Xero report on a set day each month and drop it where Claude can pick it up, so your reconciliation prompt always has fresh figures.
Manual paste: For a one-off question, copy the numbers straight from Xero into the chat. Low effort, no setup, fine for quick checks.
For most owners the API bridge is the option worth setting up. It turns a monthly chore into a question you can ask in plain language: which invoices are overdue, how does this month compare with last, what does my cash position look like heading into the quarter. Claude answers from the live figures rather than a stale export, and you skip the copy and paste every time. A bridge like this is usually a small piece of work to stand up, and once it exists every other Claude workflow can read from it.
MYOB users have similar options through its API and report exports. The pattern is the same across both: give Claude the figures in a form it can read, and it will do the analysis, the drafting, and the chasing.
A practical setup for an Australian business
Say you run a Sydney cafe turning over about $850,000 a year, with books in Xero. A workable setup looks like this. Each month a small automation exports your Profit and Loss and Aged Receivables from Xero. Claude reads them, tells you which customers are late, estimates your GST position for the BAS, and drafts polite reminder messages for overdue invoices. You approve before anything is sent. The accounting stays in Xero. Claude sits on top as the reader and drafter, not the system of record.
A point worth being clear about: an estimate is not a filing. Claude can give you an early read on the numbers so nothing surprises you at BAS time, but your accountant or bookkeeper still signs off the return. The value is in seeing the position weeks ahead, not in replacing the professional who lodges it.
Owners who try this often find the first win is time, not insight. If you were spending several hours a month wrangling reports, getting that back is worth a few thousand dollars a year at a modest hourly value, before you count better decisions. And a single missed follow-up on a $45,000 invoice can outweigh the whole setup cost on its own.
What to watch before you connect anything
Accounting data is sensitive, so treat the connection with care. A few rules worth keeping:
Know where the data goes. Understand what leaves Xero and where it is processed before you wire anything up.
Keep payroll and STP data out of scope unless you have a clear reason. The less sensitive data in play, the smaller your risk.
Mind the Privacy Act. If customer details flow through the setup, your obligations under Australian privacy law still apply.
Keep a human in the loop. Claude should draft and suggest; a person approves any message, payment note, or filing.
The short version
QuickBooks is the default because of the market Claude for Small Business was built for first, but Australian businesses on Xero or MYOB are far from locked out. With a light bridge, Claude can read your books, watch your receivables, and draft the follow-ups, while your accounting stays exactly where it is. If you want help setting that up for your own stack, book a short call and we will map the fastest safe path.
