Building an accounting team with Grok Bot
SpaceXSI assigned five Grok Bots to own accounting jobs end to end, from provisioning a customer account to collecting payment. A person steps in only when the work needs judgment. The authors estimate the same work would otherwise require more than doubling the team’s headcount.
Published 2026-11-16 by Annay (Paul) Bains, Will Smerdon, and Erin Jenks. Article
The five jobs
Each Bot owns one existing, scoped process, not a pile of ad hoc tasks. They sit on the accounting org chart: Provisioning Bot reports to Paul, Billing Bot and Billing Support Bot report to the Billing Lead, and Cash Applications Bot and Collections Bot report to the Collections and Support Lead.
- Provisioning Bot checks the executed contract against CRM records, enables or removes entitlements through an internal app, and tells the sales rep in Slack.
- Billing Bot checks billing records against the contract, fixes discrepancies so the invoice can go out, and alerts the team to fix the source record. Invoice time dropped from about 24 hours to minutes. It also chases missing VAT or GST IDs before the invoice is sent. Credits and rebilling need extra approval.
- Billing Support Bot answers go-to-market billing questions and makes routine updates, such as changing a billing email after checking the domain. Estimated savings: about eight hours a day across the accounting team.
- Cash Applications Bot checks the payment feed twice a day, matches exact payments, looks up remittance advice when they don’t match, writes off bank fees, and flags short payments. A 3–4 hour accountant task now takes about 30 minutes.
- Collections Bot is the first to email customers. It answers billing questions and coordinates refunds with the other Bots, but an authorized person must approve a refund. Training took about three months because it has to verify the sender against approved contacts. A lookalike domain is not enough.
What made them reliable
A Bot cannot run a process people have not already made reliable. They built structured apps (Grok Build, and Cursor for the provisioning app) so the Bot operates a defined interface with an audit trail, rather than inventing the steps.
Each job has a Notion operating manual. The Bots reread it nightly and flag conflicts with their instructions. They cannot edit the manual. People who know the job still define how it is done.
Permissions are tighter than read access. Lower-risk work runs alone. Credits, refunds, and billing-record changes need a designated approver. Internal systems are reached through Tailscale, with access tied to the person who authorized the connection.
Onboarding is the same shape as for a new hire, now about three weeks: week one, knowledge base and observation; week two, the Bot proposes and a person approves; week three, routine work runs and exceptions escalate. The first Bot, Billing Support, took four to five weeks. Later ones were faster. Coaching continues after launch.