usebot.net

Working playbook

Expense Manager

Reconcile receipts and flag exceptions. Leave reimbursements untouched.

Updated August 27, 2026

Finance Bots fail when they “helpfully” recategorize or chase people. Keep it to a reconciled pack a person can send.

What this Bot owns

Weekly expense reconciliation and missing-information follow-up drafts.

Connect: Expense system, email, shared drive, and finance spreadsheets.

If no structured plugin exists, the Bot can still operate the website from the shared cloud computer. Prefer a plugin when one exists; use computer use for everything else.

First task

Run this once. Do not schedule it or enable send access until the result is something you would actually review.

Copy-ready first task

Build this week's expense summary from the expense system and attached policy. Match receipts from the finance inbox, flag missing categories or policy exceptions, and draft one follow-up per owner.
Return the summary and drafts.
Do not send messages or change reimbursements.
Cite the policy section on every exception.

How to inspect the result

Totals should tie back to the expense system. Every exception needs a policy citation. Drafts should still be unsent.

Where it must stop

Messages to employees, reimbursement edits, and policy exceptions wait for finance review.

  • Do not send follow-ups.
  • Do not change reimbursements.
  • Do not store card numbers or government IDs in chat.

Failure rule: If receipts and the expense system cannot be matched, mark the gap. Do not invent a category.

When to make it a routine

Weekly, after one close matches finance’s numbers and every exception cites policy.

You can also ask the Bot to follow along once, then save the path as a routine. See teach a Bot the job.

Bot profile

Put this in the Bot profile. Keep this week’s list, dates, and files in the conversation.

Profile template

Name: Expense Manager
Job: Weekly reconciliation and exception drafts
Sources: expense system, finance inbox, attached policy
Working style: match receipts; cite policy; keep originals unchanged
Approval boundary: never send or change reimbursements
Failure rule: stop and list unmatched items

Use the bot roster builder to generate a paste-ready version, or return to the playbook hub.

Sources: xAI use cases · approvals · how Bots work