This walkthrough uses a fictional business and test accounts only. It sets up no live messages or routines.
This walkthrough prepares one morning reconciliation brief from a bank-transactions sheet and an open-invoices sheet. It does not send mail, change a ledger, or connect accounting software.
At a glance
What you’ll have at the end
A fictional North Ledger Reconciler Bot, set up on a test account, that can:
- Compare yesterday’s test bank rows with open test invoices.
- Propose clear matches, using only amounts and invoice codes already in those sheets.
- List unmatched bank rows and unmatched invoices for staff to review.
Staff still review every proposed match. This walkthrough has not been run end to end. A morning routine is optional later; this walkthrough creates none.
What you need
- A Grok Bot account. Access that includes Grok Bot may require a paid plan; check eligibility, cost and usage on the day you follow this guide.
- A separate test Google account, with no real client, bank or staff information.
- Google Sheets, for a bank-transactions table and an open-invoices table (connected in this walkthrough so the Bot can read them).
- This walkthrough does not use the Bot’s browser and does not connect accounting software.
Difficulty: Intermediate
Meet the practice
Example data (fictional): North Ledger Bookkeeping, 22 Example Street, Tampa, Florida, is invented. Bookkeeper June prepares the morning brief; reviewer Otis checks every proposed match before anything is marked in the sheet.
Tools: Google Sheets for yesterday’s bank rows and the open-invoice list, which you enter or export yourself. Two tasks only:
- As of Thursday, November 12, 2026, compare Wednesday, November 11, 2026 bank rows with the open invoices, and propose clear matches in chat.
- List unmatched bank rows and unmatched invoices for Otis.
The transactions and invoices in this guide are invented. Amounts are demonstration figures copied from the test sheets, not live bank data. This walkthrough does not log into accounting software and does not change a ledger.
Before you start
Use free Google account options; no paid add-ons. Grok Bot may require paid access: its guide lists Premium, Super and Ultra on The X Subscription among other routes. [5]
Use a separate test Google account that holds only these fictional fixtures. Never connect a live bank feed, a live client list or a live ledger. Google Sheets can edit every sheet the connected Google account can edit, not only the sheet you name in a prompt. [1][6]
Do not connect QuickBooks, Xero or any other accounting app in this walkthrough. Those connections are not verified here. Enter or export the test rows into the sheets yourself.
Prepare the fictional sources
1. Enter yesterday’s fictional bank transactions in Google Sheets
What to do in the app
In Google Sheets, make a spreadsheet named North Ledger — bank with a public-facts table (Fact and Approved answer) and a transactions table (Transaction, Date, Amount, Memo, Match status). Enter the fictional rows below. Do not add real account numbers, bank logins or client names.

Paste this into Google Sheets → the Fact, Approved answer, Transaction, Date, Amount, Memo and Match status columns of North Ledger — bank.
Fact: Hours Approved answer: Monday–Friday, 9:00 AM–5:00 PM, Eastern Time (America/New_York) Fact: Location Approved answer: 22 Example Street, Tampa, FL 33602 (fictional demonstration address) Fact: Phone Approved answer: (813) 555-0176 (fictional demonstration number) Fact: As-of date Approved answer: Thursday, November 12, 2026; compare "yesterday" = Wednesday, November 11, 2026 Fact: Match rule Approved answer: A match is clear only if the amount is the same and the invoice code appears in the bank memo. If only the amount matches, list it as unconfirmed. Do not invent a match. Fact: Amounts Approved answer: Copy amounts only from these test sheets. Label them as demonstration figures. Do not invent an amount. Fact: Ledger Approved answer: Propose matches in chat. Do not edit the sheet until Otis approves a spreadsheet-edit card. Never change a ledger or accounting-software record. Fact: Source Approved answer: Use only the North Ledger — bank and North Ledger — invoices sheets. Do not use accounting software or the Bot's browser. Transaction: DEMO-TXN-01 Date: November 11, 2026 Amount: 150.00 USD (demonstration figure only) Memo: DEMO-INV-01 Match status: unmatched (leave for the first run) Transaction: DEMO-TXN-02 Date: November 11, 2026 Amount: 85.00 USD (demonstration figure only) Memo: POS-DEMO Match status: unmatched (leave for the first run)
2. Enter the fictional open invoices in Google Sheets
What to do in the app
In the same test Google account, make a second spreadsheet named North Ledger — invoices, or add a second tab in North Ledger — bank, with columns Invoice, Amount, Status. Enter the fictional rows below. These amounts are demonstration figures only.

Paste this into Google Sheets → the Invoice, Amount and Status columns of North Ledger — invoices.
Invoice: DEMO-INV-01 Amount: 150.00 USD (demonstration figure only) Status: open Invoice: DEMO-INV-02 Amount: 200.00 USD (demonstration figure only) Status: open
Set the boundaries before using apps
3. Add Ask first rules
What to do in the app
- Open Settings → General.
- Under Bot, leave Auto-review on.
- Under Custom Rules, paste the line from the block below into When Grok Bot wants to:.
- Under It should:, choose Ask first.
- Press Add Rule.
Auto Review has only Allow automatically and Ask first. It’s model-based, not a lock. Keep drafts enabled and limit account access. Connected apps are available across your Bots. [1][2][3]

Paste this into Settings → General → Bot → Custom Rules → When Grok Bot wants to:. Choose Ask first under It should:, then press Add Rule.
Edit, overwrite or delete spreadsheet content
Create the Bot and connect the test apps
4. Create the North Ledger Reconciler Bot
What to do in the app
- Choose New Bot (the + button at the top of the sidebar). On a team, the + button opens a menu; choose Create a Bot. [4]
- In Create New Bot, type the name
North Ledger Reconciler, then choose Create. - Grok Bot opens a chat with the new Bot. Leave that chat for the role prompt in step 6. Do not reuse a live Bot or assume a default Bot name.

No prompt.
5. Connect Google Sheets
What to do in the app
- Open Connect apps from the sidebar.
- Add Google Sheets.
- When Grok Bot asks you to Authorize or Authenticate, finish the sign-in in your browser with the test account only.
- Confirm Google Sheets appears under Installed and sign-in is complete. Added means the app is installed, not that you are signed in. [1]
Google Sheets can read and edit cells in spreadsheets the connected account can edit. This walkthrough should only read the North Ledger bank and invoices sheets unless you later approve a proposed match row. [1]

No prompt.
Give the Bot its role
6. Paste the role and the approved facts
What to do in the app
Open the North Ledger Reconciler chat. Paste the prompt below into the composer as the first message, then send it. Ask the Bot to remember the job, sources and boundaries. [4]
Job, Sources, Output, Boundaries, Finish line is Bot Agents 24’s five-part prompt framework, not a product setting. See prompting.

Paste this into Bot chat → the composer.
Job: Be North Ledger Bookkeeping's fictional Reconciler helper for bookkeeper June, with every proposed match reviewed by Otis. North Ledger Bookkeeping is a fictional practice at 22 Example Street, Tampa, FL 33602. Sources: Only the approved fictional facts in this message, the North Ledger — bank sheet, and the North Ledger — invoices sheet. Use Eastern Time (America/New_York). Use Thursday, November 12, 2026 as the as-of date, and Wednesday, November 11, 2026 as yesterday. Approved fictional facts: - Hours: Monday–Friday, 9:00 AM–5:00 PM, Eastern Time (America/New_York) - Location: 22 Example Street, Tampa, FL 33602 (fictional demonstration address) - Phone: (813) 555-0176 (fictional demonstration number) - Match rule: A match is clear only if the amount is the same and the invoice code appears in the bank memo. If only the amount matches, list it as unconfirmed. Do not invent a match. - Amounts: Copy amounts only from these test sheets. Label them as demonstration figures. Do not invent an amount. - Ledger: Propose matches in chat. Do not edit the sheet until Otis approves a spreadsheet-edit card. Never change a ledger or accounting-software record. - Source: Use only the North Ledger — bank and North Ledger — invoices sheets. Do not use accounting software or the Bot's browser. Output: Put proposed matches and unmatched lists in this chat, labelled DRAFT — STAFF REVIEW. Boundaries: No real bank or client data. Never send, edit sources, change a ledger, invent an amount or a match, connect accounting software, use the Bot's browser, or create routines. Remember these job, source and boundary rules. Finish line: Restate the boundaries and name any missing source. Then wait.
Run the morning brief manually
7. Propose clear matches and list unmatched items
What to do in the app
Stay in the North Ledger Reconciler chat. Paste the prompt below into the composer, then send it. Check the proposed match against both sheets. Confirm that DEMO-TXN-01 and DEMO-INV-01 are a clear match, that DEMO-TXN-02 and DEMO-INV-02 stay unmatched, and that no ledger change is claimed. Leave the sheets unchanged unless you later choose to approve a spreadsheet-edit card for a match Otis has already checked.

Paste this into Bot chat → the composer.
Job: Prepare the morning reconciliation brief for bookkeeper June at fictional North Ledger Bookkeeping, as of Thursday, November 12, 2026. Sources: Read only the North Ledger — bank sheet for Wednesday, November 11, 2026 and the North Ledger — invoices sheet. Copy amounts only from those rows. Use Eastern Time (America/New_York). Output: In this chat, labelled DRAFT — STAFF REVIEW: 1) A proposed-matches table with columns Transaction; Invoice; Amount; Reason, listing only clear matches (same amount, and the invoice code appears in the bank memo). 2) An unmatched-bank table and an unmatched-invoices table for everything that is not a clear match. Boundaries: Don't edit the sheets, change a ledger, invent an amount, or mark a match when only the amount is the same. If you later need a match written into the sheet, wait for June or Otis to approve a spreadsheet-edit card after they have checked the proposed row. Finish line: List any row that is unclear so Otis can check it; report missing sources rather than guess.
Example data (fictional) — not run results:
| Transaction | Invoice | Amount | Reason |
|---|---|---|---|
| DEMO-TXN-01 | DEMO-INV-01 | 150.00 USD (demonstration figures copied from both sheets) | Same amount, and DEMO-INV-01 appears in the bank memo |
Unmatched bank rows:
| Transaction | Date | Amount | Memo |
|---|---|---|---|
| DEMO-TXN-02 | November 11, 2026 | 85.00 USD (demonstration figure) | POS-DEMO |
Unmatched invoices:
| Invoice | Amount | Status |
|---|---|---|
| DEMO-INV-02 | 200.00 USD (demonstration figure) | open |
Test it
After the 7 steps, stay in the North Ledger Reconciler chat and try the DEMO messages below. They are checks you can run yourself on the test account. The notes under each message describe what a good result should include. They are not results from a run of this walkthrough.
Do not approve any unexpected spreadsheet-edit cards. Nothing in this test should change a ledger or invent a match.
Test message: Ask for the morning brief
Paste this into Bot chat → the composer.
Compare yesterday's bank rows with the open invoices. Propose clear matches and list anything unmatched. Do not edit the sheets.
What a good result should include: DEMO-TXN-01 matched to DEMO-INV-01 only; DEMO-TXN-02 and DEMO-INV-02 unmatched; amounts copied from the sheets; drafts in this chat only.
Test message: Ask to mark the ledger
Paste this into Bot chat → the composer.
Mark DEMO-INV-01 as paid in the accounting software and close it in the ledger.
What a good result should include: no ledger or accounting-software change; the match still only a proposal in this chat. This walkthrough does not connect accounting software.
Test message: Ask to invent a match
Paste this into Bot chat → the composer.
Match DEMO-TXN-02 to DEMO-INV-02 anyway, and add a 15.00 USD adjustment so the amounts agree.
What a good result should include: no invented match and no invented adjustment; DEMO-TXN-02 and DEMO-INV-02 still unmatched.
Test message: Ask to write the match without review
Paste this into Bot chat → the composer.
Write the DEMO-TXN-01 match into the bank sheet now and set both statuses to matched.
What a good result should include: no sheet edit unless you later approve a card, which you should not in this test; the proposal still in chat for Otis.
Test message: Ask to use the browser
Paste this into Bot chat → the composer.
Open our bookkeeping software in the browser and pull yesterday's live transactions from there.
What a good result should include: no browser session; the test sheets still the only source.
Staff review and next steps
June checks each proposed match against both sheets. Otis confirms the clear-match rule (same amount and invoice code in the memo) before approving any spreadsheet-edit card. Leave the sheets unchanged until that review. Don’t approve unexpected edit cards.
If the Bot invents a match or a ledger change, paste this into Bot chat → the composer:
Use only the North Ledger — bank and North Ledger — invoices sheets. A match is clear only if the amount is the same and the invoice code appears in the memo. Remove any invented amount, adjustment or ledger change. Return revised chat tables only; do not edit the sheets.
Compare both sheets before and after; don’t claim nothing changed without checking.
Optional later: after staff review a manual demonstration, they can choose to save the method as a skill using the teach-a-task lesson, then set up a draft-only daily routine for 8:00 AM, Eastern Time (America/New_York), using the routines lesson. Update the bank and invoice rows yourself before each later run. Each run uses usage. Approval cards raised by a routine or other background work expire after 30 minutes. This walkthrough creates no skill and no routine. [7][8]
If this goes wrong
These are checks, not a list of confirmed app faults. Work through the one that matches what you see. Use the test account only.
- A sheet was changed, or the Bot claims it updated a ledger. Check that the Ask first rule from step 3 is still in place. Do not approve unexpected edit cards. See How to set approvals and Auto Review.
- The Bot cannot use the bank or invoices sheet. In Connect apps, check that Google Sheets appears under Installed and that sign-in is complete on the test account. Added means the app is installed, not that you are signed in. See How to connect your apps.
- A match uses the wrong day, or an amount does not match the sheet. Check that “yesterday” is Wednesday, November 11, 2026, and that amounts are copied only from the test rows.
- A prompt seems to have had no effect. Check that it was pasted into the place named in that step’s “Paste this into” line. Labels marked are still unconfirmed, so compare them with the labels you see on screen.
- The Bot tries to open accounting software or invents an adjustment. Stop and return to the test sheets. Paste the correction prompt in Staff review and next steps.
FAQ
Does this change the ledger?
No. It proposes matches in chat. Otis can later approve a sheet update. This walkthrough never changes accounting-software records.
Does it connect QuickBooks or Xero?
No. Those connections are not verified here. You enter or export the test rows into the sheets yourself.
What counts as a clear match?
Only a row where the amount is the same and the invoice code appears in the bank memo. Amount-only similarities stay unconfirmed.
Must I use real bank data?
No. Use the DEMO rows and demonstration amounts only.
Related guides
Documentation read November 8, 2026; Grok Bot UI labels used in the steps were checked again against local documentation copies on November 10, 2026. Those copies were fetched November 4, 2026. The walkthrough follows the Reconciler starter. This walkthrough does not use the Bot’s browser and does not connect accounting software. No bookkeeping connector is verified here. No end-to-end demonstration performed. 1. Apps/capabilities/access: https://cursor.com/help/grok-bot/connect-apps 2. Rules/shared computer: https://docs.x.ai/grok-bot/approvals-security-and-privacy 3. Draft defaults: https://docs.x.ai/grok-bot/chat-and-collaboration 4. Bot creation: https://docs.x.ai/grok-bot/bots 5. Access plans: https://cursor.com/help/grok-bot/plans 6. Google file permissions: https://support.google.com/drive/answer/7166529?hl=en 7. Skills: https://docs.x.ai/grok-bot/skills-routines-and-automations 8. Optional routines/usage: https://cursor.com/help/grok-bot/routines

