We did the GST with the crew in a day. Here is what the humans still had to do.

Morning.

This is the first Beanz Brief, so a sentence on what it is: once a week, what changed in AI that matters if you run a service business in New Zealand or Australia, what we actually did with it in our own business, and what it cost. No “ten tools you must try”. No screenshots of a demo that nobody has run on a real company. If we didn’t do it, it isn’t in here.

This week: the GST.

The job

Our New Zealand company’s GST had drifted. Not dramatically, the way it does when you are running something else with your whole attention. Subscriptions billed in US dollars, some with a New Zealand GST number on the receipt and most without. Two bank accounts, one card, one business card on Wise, an accountant’s invoice that had been paid but nobody could say exactly when. Four two-monthly GST periods since April.

The usual answer is a weekend, a spreadsheet, and a bad mood. We gave it to the crew instead.

“The crew” is a handful of AI workers running on a server under one human approver. They do not have a login to anything they were not given. They do not file anything. They cannot move money. They read, build, and ask.

What the crew did

Copied the source files read-only: the bank exports, the card export, the receipts folder, a fresh read-only pull of the accounting ledger.
Built one schedule of every bank, card and invoice line since 1 April. 295 lines, each tagged: GST claimable, business but no GST, personal or unclear, or “belongs to a different company”.
Read every supplier’s invoice text for the thing that matters and nobody checks: does this offshore supplier actually show a New Zealand GST number? The biggest AI vendor we pay does. Two other household names did not, on the receipts as downloaded.
Swept a year of the inbox for tax invoices. 1,185 emails matched to lines. That part was a person’s job with the crew’s help; the mailbox access stayed with a human.
Found the recurring charges by merchant, amount and rhythm, which is how you discover the storage unit you forgot and the two overlapping AI subscriptions.
Rebuilt the whole thing from a script, so when the missing statement turns up, you run it again instead of starting again.

What the humans still had to do

This is the part I want you to read, because it is the part the vendors skip.

Rulings. Is a phone account in a trading name from a business I sold still this company’s expense? (Yes, I said, and the crew applied it everywhere.) Do we claim the offshore subscriptions that charge NZ GST? (Yes, every line.) Is a charge billed to the other company but paid from this one ours? (Only if it carries NZ GST.) Is the storage unit business? (No. Personal. Keep it out.) Five rulings. Each one took me thirty seconds. Each one changed dozens of lines.
Access. The crew had no mailbox. It asked, in writing, and stopped. A person did the sweep.
The thing that was never in any system. One bank account’s statements stopped at 30 April. No software finds a PDF nobody downloaded. That is still the biggest unknown and it is mine to fix.
Signing. The output is a working schedule for me and the accountant, not a return. Nobody filed anything.

The number

GST to claim since 1 April: NZ$989.20, of which NZ$721.17 has the invoice and the payment proof attached and is ready today. The rest is waiting on receipts.

Not life-changing money. The point is what it cost to find: about a day of crew time, and my part was mostly answering the five questions above. The previous method cost a weekend and still missed the storage unit.

What this means for you

The crew is good at breadth and bad at authority. It will read 1,185 emails without complaint. It cannot decide whether your trading name is your company. Design the job so the machine does the reading and you do the ruling, in writing, once.
Offshore AI subscriptions are a GST question now. Check whether the receipt shows an NZ (or AU) GST number. Some of the biggest names do, some don’t, and the “doesn’t” pile is where your claim quietly dies.
“Rebuild from script” beats “clean spreadsheet”. The first time your source data changes you will know why.
Give the crew read-only everything and write-access nothing, and make it stop and ask when it hits a wall. Ours did, twice. Both times it was right to.

Next week

The day I switched the whole crew off.

Beanz