Administration / Finance OS

Three layers: your source systems keep the transactions, a wiki holds the rules of your function, and Claude reads both before it prepares anything. You read it. Claude maintains it.

• Set up the Claude Code desktop app and point it at your workspace in the first session, guided click by click
• Supplier and client profiles, payment terms, approval rules and a deadline calendar, each rule marked with who decided it
• Your CLAUDE.md operating rules, including the never list: prepare and draft only, never move money, approve, post, or send
• The rule that keeps the wiki honest: live balances stay in your accounting system, the wiki holds the durable rules that make them readable

No terminal, ever. You work in the desktop app and describe what you want in plain language.

The brain starts reading where the work arrives, and the morning gets a rhythm that replaces the scan.

• Scoped, read-only connectors for your email and calendar, each with its own governance card, or a files-only path if your company says no connectors
• A daily control brief that surfaces only what changed, is at risk, or needs a decision, with a source cited on every line
• Escalation thresholds that turn "unusual" from a feeling into a written rule you can tune
• A confidentiality check you run before connecting anything, with banking read-only or export-based, never credentialed

Read only by default. Claude prepares and flags, and nothing is ever sent, paid, or posted.

Define what a correct result looks like first, then let the work run to it. No skill is built before its definition of done exists.

• A definition-of-done sheet for each task, written before the skill, so you never automate a guess
• A daily-control-brief skill that runs your tested morning brief as a one-line command
• An invoice-follow-up skill that chases receivables at the right escalation level and flags work delivered but not yet invoiced
• A decision log that records every prepared action and who decided it, the trail your audit pack is built from

Skills run on demand against your brain. The work you do every week, captured once, run to your standard.

The controls that catch the duplicate payment and the mismatched invoice before the money leaves.

• A payment-approval-prep skill that runs the three-way match, checks the bank for already-paid invoices, and flags every exception
• An expense-review skill that checks each claim against policy and drafts the note back to the employee
• An approval pack per payment that ends in an empty decision line only a human fills
• A personal task map that sorts your own recurring work into skill now, skill later, and stays human

The skill assembles the evidence and flags the exception. The yes belongs to a named person, every time.

The month-end close and the audit pack, where traceability and the decision log prove their compound value.

• A month-end-close skill that surfaces reconciliation exceptions, missing documents, and the handoff list for your accountant
• Owner commentary drafted to three paragraphs, every sentence carrying an amount and a source
• An audit-evidence-pack skill that assembles the full traceability chain for any transaction on request
• A close that prepares for the accountant and never posts, adjusts, or determines tax treatment

Audit readiness stops being a year-end scramble and becomes a property of how the function already runs.

One full operating cycle on a fresh month, then the loop that makes every future one start sharper.

• A full cycle run end to end on a new month, with every exception handled or consciously deferred
• A finance-retrospective skill that proposes what the rules, thresholds, and skills should permanently learn
• The Accept and Reject discipline for permanent changes: nothing becomes a rule without your explicit yes
• A written weekly and monthly operating rhythm, with which skill runs when and what stays manual

The cycle is done when the function has learned from how it ran.