AI subscriptions used to be a rounding error on the software budget. Now that Claude sits alongside Xero, Slack and the practice management system on the monthly card statement, bookkeepers across Sydney, Melbourne and Brisbane are fielding the same two questions every BAS cycle: can we claim the GST on this, and does it trigger FBT? The honest answer is that it depends entirely on who is using the subscription, and what for.
Claiming GST credits on AI subscriptions
If your business is registered for GST and the subscription is used for a creditable purpose in carrying on your enterprise, you can generally claim an input tax credit on the GST component, provided you hold a valid tax invoice. That's straightforward when the plan is billed by an Australian entity with an ABN on the invoice. It gets murkier when the AI vendor bills from overseas, which is common for many AI tools sold into the Australian market.
The business is registered for GST at the time the subscription is purchased
The subscription is used for a creditable purpose, meaning genuine business use rather than private use
The supplier is registered for GST and has issued a valid tax invoice for supplies over $82.50
The invoice actually shows a GST component, rather than being a net-of-GST offshore charge
Business-to-business supplies of digital services from an overseas AI provider to a GST-registered Australian business often fall outside the scope of Australian GST altogether, particularly when you've supplied an ABN at checkout. That means there's no GST on the invoice to claim in the first place, and coding the full amount to a GST-free or BAS-excluded tax code avoids an incorrect claim showing up at BAS reconciliation. When in doubt, check the tax invoice line by line, and confirm the treatment with your BAS agent or accountant rather than assuming every software subscription behaves like a standard local supplier.
When an AI subscription triggers FBT
FBT questions come up when the subscription benefits an employee personally, rather than the business as a whole. A company-wide Claude for Work licence, purchased centrally and used for work tasks, is an ordinary deductible business expense with no FBT implications. The picture changes when a business reimburses an individual employee for a personal AI subscription, or bundles a subscription into a salary package.
Company-owned licence, provisioned and used for work: no FBT, treated as an ordinary business expense
Employee reimbursed for a personal AI subscription under a bring-your-own-tool policy: potentially a fringe benefit, though the minor benefits exemption may apply
Subscription offered as part of a formal salary packaging arrangement: FBT generally applies and should be grossed up accordingly
Subscription used for a mix of work and personal chats on a personal account: apportionment and evidence of business use become important
The minor benefits exemption can cover an occasional, low-value reimbursement, typically under $300 including GST, provided it's infrequent and irregular. A one-off reimbursement for a $32.90 monthly Claude Pro subscription might qualify. A standing monthly reimbursement written into an employment agreement almost certainly won't, because it stops being infrequent the moment it's a recurring entitlement. This is exactly the kind of borderline call worth running past your tax agent before it becomes a pattern across the whole team.
None of this needs to be complicated, but it does need to be consistent. The Australian Taxation Office expects five years of substantiation for business expense claims, and a subscription that renews monthly for five years generates sixty small decisions rather than one big one. Getting the coding right in month one, and keeping it consistent as the team adds more AI tools, is far less work than untangling it during an audit or at year-end when the accountant asks why the software line jumped.
Bookkeeping treatment that keeps your BAS clean
A 25-person Sydney professional services firm running Claude for Work licences alongside a handful of specialist AI tools can clear $45,000 a year in software subscriptions without anyone noticing it happened. At that scale, "miscellaneous expenses" stops being an acceptable home for these transactions, and a dedicated coding structure earns its keep at tax time.
Code AI tools to a dedicated "AI & Software Subscriptions" account, not a general miscellaneous or entertainment line
Attach the tax invoice to the transaction in Xero for Division 900 substantiation
Note the business purpose in the transaction description: which team, which tool, what it replaced
Flag any subscription billed from an overseas entity so a GST credit isn't claimed on tax that was never charged
Review, each quarter, whether any subscription paid on an employee's behalf sits outside the company-wide licence
Where Claude fits into the reconciliation itself
There's a reasonable case for using Claude to help clean up the very transactions it appears on. Connected to Xero, Claude can scan the software and subscriptions account, flag anything coded inconsistently, and draft the quarterly note your accountant needs to confirm GST and FBT treatment, rather than leaving it to a end-of-year scramble. It won't make the tax call for you, and it shouldn't. What it can do is make sure nothing sits miscoded for six months because nobody had twenty minutes to look at the general ledger.
If you want a second set of eyes on how AI subscription spend is coded across your Australian business, book a short chat and we'll walk through what's currently on the books: book a brainstorm session.
