Skip to main content

Jarvis as your accounting clerk

If your operator has set up Jarvis with the accounting-clerk persona, this is the shape it takes. This page reflects the default template; your operator may have added local rules on top.

Daily tasks it handles​

  • Expense logging. Send it a receipt image, tell it the category. It files the entry and (if configured) posts it to your accounting system.
  • Invoice review. Attach an invoice PDF. Jarvis extracts vendor, amount, due date, PO reference, flags anything that looks off.
  • AR / AP follow-up. Ask "which invoices are more than 30 days overdue?" — Jarvis pulls from the KB (if the operator wired up your ledger) and drafts polite reminder emails you can approve before sending.
  • Month-end checklists. Say "start month-end for October". Jarvis walks the standard checklist your operator wrote into its persona, ticking off each step as you confirm.
  • Currency conversions and quick calculations. Reliable to two decimal places using live FX (via the web_search tool). Always double-check when the number matters.

Things it will not do without a human​

  • Approve payments. Jarvis can prepare a payment run but will not submit it. Every payment above your operator's threshold needs a second human confirmation.
  • Sign contracts or NDAs. It can draft. It cannot bind you.
  • Move money between accounts. Read-only access, always.

Correcting mistakes​

Accounting mistakes compound, so we err on the side of asking Jarvis to double-check. If it gets an entry wrong:

You: 呢張發票 amount 錯咗，係 HK$12,450 唔係 HK$14,250
Jarvis: 對唔住，改正咗。你要唔要我 undo 之前入帳嗰單？

If it references an old fact that has changed (e.g. an old bank account number), tell it plainly and it updates its memory for this group.

The KB​

Jarvis reads the documents your operator uploaded to its KB. Ask "who is the finance contact at Acme?" and it should return the answer with "📚 source: <filename>". If it answers without citing a source, treat the answer as a guess — the KB probably does not have that fact.

When to escalate​

  • The number Jarvis quoted differs from your ledger by more than a rounding error.
  • Jarvis cited a document you know is out of date. The operator needs to refresh the KB.
  • A vendor calls asking about an invoice Jarvis handled — always confirm with a human before responding.

Ping your operator via the escalation shortcut your team uses (usually @operator in the group, or a Slack DM).