Grok Bot finance prompts that reconcile before they file
Official expense-manager use case: match receipts, flag policy exceptions with citations, draft follow-ups. Do not send. Do not change reimbursements. Totals must tie to the source.
In short: This page contains 21 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Expenses and receipts
4 promptsWeekly expense summary
1/21✨ What it does
The Bot builds this week's expense summary from [SYSTEM] and [POLICY], matches receipts, flags exceptions with a policy cite, and drafts one follow-up per owner. You send the follow-ups and you file.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build this week's expense summary from [SYSTEM] and [POLICY]. Match receipts. Flag exceptions. Draft one follow-up per owner. Do not send or change reimbursements. Sources: [EXPENSE SYSTEM], [FINANCE INBOX], [POLICY], [SHEET]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send messages or change reimbursements. Cite the policy line on every exception. Deliverable: Summary, exceptions with cites, drafts, totals that reconcile to the source. Review point: I send and I file.
Pro tip: Ask for totals that reconcile back to the source. A pretty table that does not tie is worse than nothing.
Missing-receipt chase list
2/21✨ What it does
The Bot lists transactions in [PERIOD] that still need a receipt, grouped by owner, with a draft nudge. You send the nudges.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List transactions in [PERIOD] still missing receipts, grouped by owner. Sources: [EXPENSE SYSTEM], [CARD FEED], [POLICY SLA]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Deliverable: Owner, transactions, age, draft nudge. Review point: I send.
Pro tip: One draft per owner, not a public shaming channel.
Policy exception pack for me
3/21✨ What it does
The Bot packs out-of-policy or unclear expenses for [PERIOD] with the policy cite, or writes "policy silent" if no rule exists. You decide approve or reject.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Pack of out-of-policy or ambiguous expenses for [PERIOD] with the policy cite or "policy silent". Sources: [EXPENSE SYSTEM], [POLICY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not reject or approve in the system. Deliverable: Item, cite or silent, draft decision note for me. Review point: I decide.
Pro tip: If the policy is silent, say silent. Do not invent a rule to be helpful.
Month-end receipt dump from mail
4/21✨ What it does
The Bot saves receipts from [FINANCE INBOX] for [MONTH] into [FOLDER], named by vendor, date, and amount. You upload them to the expense tool.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Save receipts from [FINANCE INBOX] for [MONTH] into [FOLDER] with vendor-date-amount names. Sources: [INBOX] via the cloud browser, [FOLDER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - If a full card number appears, stop and tell me. Do not email receipts onward. Deliverable: File list, missing-mail vendors, path. Review point: I upload to the expense tool.
Pro tip: Gmail connector may not download bytes. Use the browser. Do not store card PANs.
Prompts get you started. Tutorials level you up.
A growing library of 300+ hands-on AI tutorials. New tutorials added every week.
AP, AR, and cash
4 promptsInvoices due in 14 days
5/21✨ What it does
The Bot lists invoices due in [14] days and flags any new payment details versus last time. You pay, and you call the vendor if the details changed.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List invoices due in [14] days. Flag new payment details vs last time. Sources: [INBOX], [AP SHEET], [LAST PAYMENT METHOD]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not pay. Do not call a vendor. If payment details changed, mark "call vendor". Deliverable: Vendor, amount, due, method change (yes/no), link. Review point: I pay. I call if details changed.
Pro tip: New bank details on an invoice are a stop, not a helpful update.
Receivables aging with drafts
6/21✨ What it does
The Bot ages what customers owe from [AR SHEET] and drafts reminders for the 15 / 30 / 45 day buckets. You send them from the official mailbox.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Aging for [AR SHEET]. Draft reminders by bucket: 15 / 30 / 45. Sources: [AR SHEET], [INVOICES], [PRIOR REMINDERS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email customers. Do not mark invoices paid. Deliverable: Bucket tables and drafts. Review point: I send.
Pro tip: Tone by age. Day-5 is not day-45.
Stripe failed-payment triage
7/21✨ What it does
The Bot sorts [PROCESSOR] alerts for the last [7] days into failed charges, disputes, and noise, with draft notes. You click refund or retry.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Triage Stripe (or [PROCESSOR]) alerts for [7] days. Failed charges first. Sources: [INBOX], [STRIPE DASHBOARD] if signed in. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not refund, retry, or email the customer. Deliverable: Failed / disputed / noise, links, draft internal note, draft customer note if needed. Review point: I click refund or retry.
Pro tip: Refunds and retries stay behind approval even if the Bot can click Stripe.
Cash snapshot from sources
8/21✨ What it does
The Bot pulls today's cash from [ACCOUNTS] and cites each balance with an as-of time; if a source is down, it says so. You use the number in standup.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Cash snapshot as of today from [ACCOUNTS]. If a source is down, say so. Sources: [BANK / STRIPE / SHEET]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not move money. Do not download full statements to chat. Deliverable: Account, balance, as-of time, source, sum, caveats. Review point: I use it in the standup.
Pro tip: If a login fails, fail. Do not reuse yesterday's cash.
Packs and close
4 promptsCredit-committee pack
9/21✨ What it does
The Bot reconciles [MATERIALS] into one committee pack in [FOLDER] and leaves conflicts visible instead of blending the numbers. You send the pack.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Reconcile [MATERIALS] into one committee pack in [FOLDER]. Show conflicts. Do not invent a blended number. Sources: [FOLDER], [CRM], [FINANCE SHEET]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email the committee. Deliverable: Pack path, conflict list, source map. Review point: I send.
Pro tip: Box field case: write the pack back into the folder. Do not average two disagreeing numbers.
Month-end close checklist
10/21✨ What it does
The Bot builds a close checklist for [MONTH] from [CLOSE DOC] and the current systems, with an owner and blocker per item. You run close and post the books.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Close checklist for [MONTH] from [CLOSE DOC] and current systems. Sources: [CLOSE DOC], [GL OR SHEET], [BANK], [STRIPE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not post journals. Deliverable: Item, owner, status, blocker, link. Review point: I run close.
Pro tip: Name the close owner per item. "Finance should look" is not a close.
Budget vs actual one-pager
11/21✨ What it does
The Bot compares budget vs actual for [MONTH] at [LEVEL] and writes one cited sentence for each variance over [THRESHOLD]. You present it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Budget vs actual for [MONTH] at [LEVEL]. Explain variances over [THRESHOLD]. Sources: [BUDGET], [ACTUALS], [NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change the budget. Deliverable: Table plus a one-sentence cite per material variance. Review point: I present.
Pro tip: No storytelling without a line item. "We invested in growth" is not a variance note.
Vendor concentration risk
12/21✨ What it does
The Bot lists the top [15] vendors by spend in [PERIOD], plus any payment-detail changes. You pick who to renegotiate.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Top [15] vendors by spend in [PERIOD], plus any payment-detail changes. Sources: [AP], [CONTRACTS FOLDER], [BANK]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change vendors or pay anyone. Deliverable: Vendor, spend, concentration, contract end, payment-detail change. Review point: I pick who to renegotiate.
Pro tip: This is ops-finance. Pair with the AP list.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.
Refunds and merchants
3 promptsUnrefunded returns
13/21✨ What it does
The Bot finds returns in the last [60] days that never came back, with evidence and a draft note per merchant. You send the notes.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find unrefunded returns in [60] days. Draft one note per merchant. Sources: [INBOX], [ORDERS], [PROCESSOR]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send. Do not file chargebacks. Deliverable: Merchant, order, amount, evidence, draft, confidence. Review point: I send.
Pro tip: Field case: five merchant notes earned more than the seat. You still send them.
Chargeback evidence folder
14/21✨ What it does
The Bot builds an evidence folder for [DISPUTE ID] from [ORDERS + LOGS + COMMS], plus a draft narrative and a missing-items list. You submit the response.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build an evidence folder for [DISPUTE ID] from [ORDERS + LOGS + COMMS]. Sources: [PROCESSOR], [SUPPORT], [LOGS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not submit the response. Deliverable: Folder path, missing items, draft narrative. Review point: I submit.
Pro tip: Do not let it submit a chargeback response. Wrong packet loses the money.
Tax-doc request list
15/21✨ What it does
The Bot lists vendors still missing [TAX FORM] and drafts the request. You send it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List vendors missing [TAX FORM] and draft the request. Sources: [AP], [TAX FOLDER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email vendors. Do not invent tax IDs. Deliverable: Vendor, missing form, draft request. Review point: I send.
Pro tip: Tax is not a place to be helpful with guesses. Missing = missing.
Make the finance Bot durable
6 promptsFinance Bot description
16/21✨ What it does
The Bot writes a finance Bot description named [NAME] with systems, the reconcile rule, and never-pay / never-store-card-number. You create the Bot.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a finance Bot description named [NAME]. Sources: [SYSTEMS], [POLICY], [REVIEW DAY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Never pay, never file, never store PANs. Deliverable: Description, weekly jobs, never-do. Review point: I create the Bot.
Pro tip: Write "if two sources disagree, show both" in the description.
Monday expense routine
17/21✨ What it does
The Bot writes a Monday job that runs the weekly expense skill and posts the pack here, without sending follow-ups. You turn it on after a clean test.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Mondays, run the weekly expense skill and post the pack here. Sources: Current [SYSTEM + INBOX]. If the system is down, fail. Do not reuse last week. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send follow-ups during the routine. Deliverable: Routine card and failure policy. Review point: I enable after a clean test.
Pro tip: Test run on last week before you let it touch this week.
What finance Bots never do
18/21✨ What it does
The Bot writes a never-do list for finance Bots from your rules, such as [E.G. NO WIRES, NO NEW BANK ACCOUNTS, NO TAX GUESSES], plus what a human does instead. You paste it into every finance Bot.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write the never-do list for finance Bots on this computer. Sources: My rules: [E.G. NO WIRES, NO NEW BANK ACCOUNTS, NO TAX GUESSES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. Deliverable: 12 never-do items and the human substitute. Review point: I paste it into every finance Bot.
Pro tip: If it can click the bank, the never-do list is the product.
Stripe refund confirm queue
19/21✨ What it does
The Bot finds likely refunds in [STRIPE / SUPPORT] for [WINDOW] and drafts a confirm list with amount, reason, and evidence. You refund the ones you want.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find likely refunds in [STRIPE / SUPPORT] for [WINDOW]. Draft the confirm list. Do not refund. Sources: [STRIPE], [SUPPORT QUEUE], [POLICY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not issue refunds. Do not store PANs. Do not email the customer. Deliverable: Customer, amount, reason, evidence, confidence. Review point: I refund the ones I want.
Pro tip: A Bot that can refund is a Bot that can refund the wrong person. Queue only.
Credit-committee pack into the folder
20/21✨ What it does
The Bot reconciles [MATERIALS] into a credit pack in [FOLDER] and notes mismatches, without emailing the committee. You send it.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Reconcile [MATERIALS] into a credit pack in [FOLDER]. Do not send it to the committee. Sources: [FOLDER], [MODEL], [INBOX]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email the committee. Do not change the model assumptions. Deliverable: Pack path, mismatches, open questions. Review point: I send.
Pro tip: If two PDFs disagree, show both. Do not pick the flattering one.
Vendor invoice exceptions only
21/21✨ What it does
The Bot flags invoices in [AP] that are duplicates, over [PO], or show new bank details. You pay or you call the vendor.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Flag invoices in [AP] that are duplicate, over [PO], or show new bank details. Do not pay. Sources: [AP], [PO LIST], [VENDOR MASTER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not pay. Do not change vendor bank details. Stop if a full card number appears. Deliverable: Invoice, exception type, evidence. Review point: I pay or I call the vendor.
Pro tip: Duplicates, new bank details, and over-PO are the three that matter.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides