agentos.guide › blog

Grok Bot For Accounting: Five Copy-Paste Prompts For Receipts, Reconciliation, A Weekly Routine And The Month-End Pack In Your Agent OS

By Julian Goldie · 6 November 2026 · agentos.guide

Grok Bot for accounting fits an Agent OS as the hands, not the brain: your agent writes the finance briefs and rules, and Grok Bot gathers receipts, preps the reconciliation and drafts the chasers on its cloud computer.

Below you get a quick start, five copy-paste prompts and a weekly rhythm.

Everything maps to the official use cases page, the files and results docs and the skills and routines docs.

To be clear from the start: this is workflow, not accounting, tax or legal advice, so the Bot prepares and a person signs off.

Fancy a hand mapping it to your own books? Book a free SEO strategy session with my team.

Quick start: five checks before the first receipt

1. Confirm access: on The X Subscription, Grok Bot is part of Premium, Super and Ultra but not Plus (see the plan page).
2. Connect Gmail, Google Sheets and Google Drive from Connect apps.
3. If you use QuickBooks Online, connect its sandbox company first; Zoho Books is the other accounting app the docs name.
4. Ask the Bot to claim its own mail.grokbot.com address, and choose carefully, because it is yours for good.
5. Add Ask first rules for external email, payments and any change in the accounting app.

Who plans, who does the work

Your Agent OS is the planner: it knows your expense policy, your category names and your bookkeeper's preferred layout.

Grok Bot is the worker: every Bot you own works on the same cloud computer, on a screen of its own, and routines keep going after you shut the laptop.

Grok Bot is also where approval cards land, so nothing your Agent OS drafts reaches a supplier or the ledger without a click.

Prompt 1: have your Agent OS write the Bot's brief

The docs say a durable Bot starts with a description holding the job, sources, output format and boundaries.

Give your Agent OS this:

Write a Grok Bot description for an "Expense manager" role for my business.
Job: weekly matching of receipts and invoices to the transactions sheet, flagging missing items and policy exceptions, and drafting one chaser per person.
Sources: Gmail label "Receipts", the Bot inbox alias +receipts, the "Transactions" sheet, our expense policy PDF.
Output: a new spreadsheet with Matched, Missing, Exception and Questions tabs, plus a five-line summary.
Boundaries: never send email, never edit the original sheet, never change anything in the accounting app, never pay or approve anything.
Use UK spelling. Keep it under 180 words.

Paste the result into the Bot's description and read it once before saving: a vague boundary stays vague.

🔥 Want these prompts tuned to your own books on a live call?

Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members building agent workflows.

→ Join the AI Profit Boardroom

Prompt 2: set up the receipts inbox

A plus alias keeps receipts apart from everything else; the apps and email docs say a routine on an alias only runs for mail sent to it.

Paste this into Grok Bot:

Use your mail.grokbot.com address with the alias +receipts for supplier receipts and invoices.
Create a routine that runs when email arrives at that alias, but only from these senders: [your staff domain], [supplier domains].
For each message: save the attachments to Drive folder "Finance/Receipts/[YYYY-MM]", renamed as sender_date_reference.
Add one row per document to the "Receipts in" sheet: sender, date, reference, file link.
If a field is unreadable, write "check". Do not reply to anyone.

Sender filters matter: the docs call an alias a label, not a lock.

Keep the attachment cap in mind as well: ten files per message, and anything over the size limit is skipped.

Prompt 3: the weekly reconciliation from attached files

xAI's file docs include a sample built on a signed policy and a spreadsheet of the month's transactions; this is the weekly version.

Attached: our expense policy (PDF) and last week's transactions (XLSX).
Match each transaction to a document in the "Receipts in" sheet.
Return a new spreadsheet with Matched, Missing, Exception and Questions tabs.
For every exception, quote the policy section.
Confirm your totals tie back to the source sheet.
Draft one chaser per person with missing items. Do not send. Do not modify the originals.

The two checks your bookkeeper should run are the ones xAI recommends for this role: a policy citation on each exception and totals that reconcile to the source.

Prompt 4: save it as a skill and schedule it

Once two manual runs look right, lock the process in.

Save the last task as a skill called "Weekly reconciliation".
Include the tab names, the file naming rule and the rule that emails stay as drafts and the accounting app is read-only.
Then create a routine: every Monday at 8:00 AM, run that skill on the previous week.
If the Transactions sheet has not changed since the last run, or a source is missing, report it and stop.
Post the sheet link and summary in this chat.

Press Test to run it now; a new routine otherwise waits for its first slot.

Email from a routine always waits as a draft until you press Send.

Prompt 5: the month-end pack for your bookkeeper

This one turns four weekly sheets into a single hand-over, and it is the prompt most owners will reuse.

On the first weekday of each month at 9:00 AM, build a month-end pack from the four "Weekly reconciliation" sheets.
List every item still missing a document, every open policy exception and every question still unanswered.
Add a tab of bills in the "Receipts in" sheet with no matching transaction.
Save the pack to Drive folder "Finance/Month-end" and attach it to a Gmail draft to our bookkeeper.
Leave the draft unsent. If any weekly sheet is missing, say which one and stop.

The Bot can attach a file it made to a Gmail or Outlook draft, which suits this hand-over well.

Ask your Agent OS to read the summary the Bot posts and compare it with last month's, so you spot a pattern of the same people missing the same receipts.

That comparison is planning work, so it belongs with the planner, not the worker.

Where to draw the line between prep and decisions

The routines docs give the rule in a sentence: automate the preparation before the execution.

Have the Bot draft, reconcile or recommend first, and keep sending, paying, deleting and publishing behind approval.

In practice that means the Bot never categorises a transaction for tax, never posts a journal, never approves a reimbursement and never pays a bill.

It also means the brief should say what to do when data is missing: stop and report, rather than reuse last week's numbers.

If your accounting app is Xero or NetSuite, note that the Grok Bot docs do not name a connector for either, so the Bot would work through its browser instead.

And remember that apps are account-wide: once QuickBooks Online is connected, every Bot on your account can reach it, so say in each other Bot's brief that it must leave finance apps alone.

Worked example: a café with two suppliers and a part-time bookkeeper

1. The owner's Agent OS writes the Expense manager brief in the café's own category names.
2. The bakery and the milk supplier email invoices to the receipts alias; the routine files each one.
3. On Monday the reconciliation skill matches card transactions to those documents and flags two missing receipts.
4. The Bot drafts a note to the shift manager who made those purchases.
5. The owner sends it from her phone, and the bookkeeper picks up the finished sheet on Friday.

At no point does the Bot edit the books or touch a card.

The same pattern works for a small design studio: swap the bakery for software subscriptions and freelancer invoices, and the routine files those instead.

The studio's Agent OS keeps the list of approved freelancers, so the routine's sender filter stays current when someone new joins a project.

📞 Want a second pair of eyes on your finance workflow?

Book a free SEO strategy session and we will map which admin jobs your Agent OS and Grok Bot should own.

→ Book your free call

Keep the Vault and approvals tight

The Vault page keeps passwords, card numbers and security codes out of the Bot's sight.

It also says a saved card fills in at checkout without asking each time, so a bookkeeping Bot should not have one saved.

Put API keys in the secure secret card rather than in chat.

Your Ask first rules always trigger an approval card, and text in an email never counts as your instruction.

The v0.78.1 changelog also notes the Bot offers a Gusto connector on Gusto sign-in pages; the docs do not describe its actions, so keep it read-only in your brief.

The weekly rhythm

• Monday: the routine runs; you review flags and send the chasers you agree with.
• Midweek: missing receipts arrive on the alias and get filed.
• Friday: your bookkeeper checks the sheet against the source documents and does the bookkeeping.
• Month end: your Agent OS reviews the month's summaries and updates the brief if the policy changed.

For more on scheduling, read our Grok Bot routines guide.

The full prompt library sits inside the AI Profit Boardroom, and if you would rather talk it through, grab a free call with my team.

FAQ

Which prompt should I run first?

Prompt 1, so the Bot's description holds the job, sources, output and boundaries. Then run Prompt 3 by hand on one week before you schedule anything.

Can my Agent OS post entries to QuickBooks Online through Grok Bot?

Keep the accounting app read-only in the brief and add an Ask first rule for any change. Your bookkeeper makes the entries.

Does the receipts alias need its own address?

No. A plus alias lands in the same inbox as your one mail.grokbot.com address, and a routine on the alias only runs for mail sent to it.

What happens if a source sheet is out of date?

Tell the routine to report missing or unchanged sources and stop. The routines docs recommend a no-data and stale-data policy.

Final word on Grok Bot For Accounting

Paste the five prompts, keep a person on every send, and join the AI Profit Boardroom to run Grok Bot for accounting in your Agent OS.

Related guides on agentos.guide

→ Grok Bot For Business: Write The Approval Rules, Inbox Wiring And Team Setup With 5 Prompts In Your Agent OS

→ Grok Bot Routines: How To Plan, Test And Review Every Routine In Your Agent OS, With Five Copy-Paste Prompts

→ Grok Bot AI Full Course (Step By Step)

→ The Ghost Team

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

← all guides on agentos.guide