I'm Testing an AI Bookkeeper Against My CPA. Here's the Setup.
Unable to add items
Add to basket failed.
Add to wishlist failed.
Failed to remove from Wish List.
Adding to library failed
Unable to follow podcast
Unable to unfollow podcast
-
Narrated by:
-
By:
For the month of September, Scott has been running an AI bookkeeping agent in parallel with his existing accounting system and team. Nothing has been cut over. At month end, he's comparing both sets of financials.
The setup, in five steps:
Bank feed. BankSync.io (~$7/month) pulls daily transactions from connected accounts via Plaid.
Daily ingest. At 8am, Stu — Scott's bookkeeping agent — grabs the prior day's transactions, filters out anything already processed, and ingests what's new.
The queue. New charges wait to be categorized. Nothing posts automatically.
Human confirmation. Stu proposes a category and the rule it believes applies. Scott confirms or corrects. Only then does it post to the ledger.
Portability backup. The ledger copies to Dropbox, so the books can move to whatever agent platform comes next.
The rule: The agent doesn't spend money and doesn't post anything unconfirmed.
A second test inside the test: Grok recently released a Grok Finance plugin with read-only bank access — also via Plaid. Scott is comparing it against BankSync to see if both produce the same result, since Grok Finance is free.
On the CPA question: The accounting team isn't going away. The CPA still oversees the work. The question is whether the low-level coding work can move, freeing people for higher-value work.
Currently running three companies through the system. More advanced land-investing accounting is being tested separately — Accounting for Land Investors students should watch their class LMS.
Before you try this: Vet any repo you connect to your financial data. Check the maintainer, the update history, and what the code does with your information.
Got a business question? Ask Scott here: scotttodd.net/ask