Part of our series on Claude for finance teams. The surface map is in Claude Has Four Surfaces.
Accounting is where Claude's surfaces land hardest, for a structural reason: the inputs are text and structured data (statements, invoices, CSVs, PDFs), the outputs are deterministic (an entry balances or it doesn't), and the volume work follows rules that were always meant to be written down. Of all the teams in this series, accounting gets the most of its week back — and keeps the most important part of its job.
Here's the honest division: agents do volume, accountants do judgment, and every posting carries a human signature.
Scenario 1: The bookkeeping that stops being anyone's morning
Three recurring agents cover the bulk of transactional bookkeeping:
Bills. Vendors email invoices to a dedicated address (bills@…). The bill-processor agent reads each one, extracts vendor, amount, dates, and line items, matches or creates the vendor record, codes the expense, and routes the result through the approval workflow — with the source PDF linked to the posted entry as evidence. Unclear documents don't get guessed at; they get flagged for a human with the extraction shown. (Real run here.)
Bank lines. Statements sync from connected banks; the bank-transaction agent classifies each line, resolves counterparties (including learning that "AMZN Mktp DE*2K4" is Amazon), and posts through the same gated workflow. When it can't identify a counterparty confidently, it delegates to a master-data process instead of inventing a vendor.
Reconciliation. The 3-pass matcher confirms exact matches automatically, scores fuzzy ones for review, and surfaces true exceptions. Typical runs clear ~90% of lines untouched.
What's left for the team each morning is the exception queue — the 4% of lines that genuinely need an accountant — with context attached.
Scenario 2: Posting anything else, in plain language
For everything the agents don't originate, the interface is a sentence:
Post the October Anthropic invoice — USD 4,800 — allocate across Tech, Sales, Finance by headcount.
Claude routes it through the same validation pipeline as everything else: the payload is checked, the entry must balance, the period must be open, and the risk-based approval lane decides whether it flows immediately or waits for sign-off. A junior can't fat-finger a debit into the wrong decade, because the workflow won't accept what doesn't validate. There is no journal-entry form. There was never a good reason for one.
Scenario 3: A close that's a checklist, not a fire drill
Month-end in conversation: verify all statements imported and reconciled, chase unposted documents, run the accrual entries, produce the trial balance and statements, review, lock the period. Each step is a question or an instruction; the period lock is an action with a signature. (Watch a real close.)
The Skills layer is what makes outputs consistent: report formats, accrual conventions, and close checklists live as readable text, so the close looks the same in March as it did in February regardless of who ran it.
Scenario 4: Payroll and VAT, where the logic is readable
This is the part accountants don't believe until they see it: the country logic ships as Plugins you can read. Estonian payroll — income tax 22%, social tax 33%, unemployment insurance, TSD output for e-MTA — is text. The KMD VAT declaration logic is text. Your accountant can audit it like a junior's working papers; if your policy differs, you change the text and the change is versioned.
/calculate-payroll April 2026 — 12 employees, Tallinn entity /prepare-vat-declaration May 2026
What's real today — and what isn't
Real, shipping now: bill processing from email with document evidence; bank classification and 3-pass reconciliation as scheduled agents; 46 transaction types posting through validated, risk-gated workflows; multi-entity, multi-currency double-entry with per-row audit trail; financial statements, trial balance, aging reports; Estonian payroll and VAT as readable Plugins, with year-end bookkeeping and the annual report covered; revenue recognition and fixed assets (acquisition from bills, depreciation runs) in the ledger core.
Not there yet — and we'd rather tell you: country Plugins beyond Estonia are roadmap, not shipping — the architecture is built for it (the logic is forkable text), but if you need Finnish payroll today, you'd be writing or commissioning the fork; inventory accounting and manufacturing COGS are not the sweet spot — service businesses, SaaS, and agencies fit best today; complex PO-driven procurement with three-way matching isn't the focus; and no agent ever posts without the workflow gate — if you want a fully unattended black box, that's a different product and we think a worse one.
The role that's left — and why it's better
Strip out the typing and what remains is the actual profession: judging the exception, signing the close, deciding the treatment, telling the founder the hard truth about runway. We wrote about why we build for that accountant — validator, not operator — in The Thinking Behind Artifi. The short version: the work that disappears is the work nobody's career was built on.
Start in bridge mode beside your current ledger — here's how the two options work — or see the walkthroughs for real runs.