Finance Operating SystemDocs
Guides

AI Copilot

What the Finance Operating System Copilot can do, the tools it has, and how the confirmation flow protects you from mistakes.

AI Copilot

The Copilot is a sidebar in every page of Finance Operating System. You can ask it anything — natural language — and it will either answer from your books, or propose a change for you to confirm. Behind the scenes it is Claude, with a tool kit scoped to your organisation. This page documents what it can do, how it stays grounded in your data, and the confirmation flow that prevents it from making unintended changes.

What you can ask

Three broad categories of question work well today:

  • Lookup questions. "What was revenue last month?" / "Show me unpaid invoices over 30 days." / "Which expense category grew the most year-over-year?" The Copilot will call our reporting tools, summarise the answer, and offer to drill in.
  • Compose questions. "Draft an invoice for Acme for $1,500 for May consulting" / "Categorise the latest 10 bank transactions" — these end in a proposed change. Nothing is written until you click Confirm.
  • Workflow questions. "How do I close the books?" / "What's the difference between a bill and an expense?" — these get prose answers using the documentation you are reading right now as the grounding source.

Tool inventory

The Copilot has the following tool families:

Read tools (run automatically)

  • query_invoices, query_bills, query_expenses, query_contacts — scoped list/filter
  • get_account_balance, get_account_history
  • run_report — trial balance / P&L / balance sheet / cash flow
  • search_transactions — full-text + date range
  • read_doc_page — grounded retrieval over this docs site

Write tools (require confirmation)

  • create_invoice, update_invoice, send_invoice, void_invoice
  • create_bill, update_bill, record_bill_payment
  • create_expense, categorise_expense
  • categorise_bank_transaction, match_bank_transaction
  • post_journal_entry (manual JEs only — and only if you are an admin or accountant)
  • create_contact, update_contact

Each write tool produces a diff preview before any database write. You see exactly which records will change.

The confirmation flow

When the Copilot decides a write tool is needed, the conversation pauses and a confirmation card appears in the chat. The card shows:

  1. The action. "Create invoice for Acme Corp"
  2. The diff. Every field that will be written, exactly as it would be persisted.
  3. The reasoning. A short paragraph explaining why the Copilot chose this action.
  4. Two buttons. Confirm writes the change and continues; Edit lets you tweak fields inline before confirming; Cancel abandons the action.

What it cannot do

  • It cannot manage billing, change your subscription plan, or cancel your account.
  • It cannot manage team membership, invite users, or change roles.
  • It cannot manage API keys.
  • It cannot post directly to closed fiscal periods.
  • It cannot perform bulk destructive operations (deleting >10 records in one go is blocked).

For any of these, use the corresponding settings screen directly.

Audit trail

Every action taken by the Copilot — read or write — is recorded in Settings → Audit log with the actor labelled as Copilot (acting on behalf of <your name>). The full conversation that led to the action is linked. Auditors can replay it.