Artifi agents listen to finance events, process documents, classify transactions, prepare payments, reconcile accounts, ask humans for decisions, and write only through governed workflows.
Agents do not run outside the system. Every run starts from an event, creates a tracked instance, uses allowed tools, and submits ledger changes through workflow gates.
The agent system uses the cheapest reliable runtime for the job: deterministic code for known finance operations, targeted model calls for extraction or ambiguity, and full LLM agents when unstructured reasoning is required.
Claude Agent SDK agents for unstructured work, judgment calls, email context, PDFs, and novel finance situations.
Deterministic Python handlers for known operations such as bank matching, billing runs, delivery, and payment batches.
Mostly deterministic workflows with targeted Haiku calls for extraction, classification, fuzzy matching, and email composition.
These are not generic chatbots. Each agent owns a clear slice of finance operations, its trigger events, allowed workflows, and completion behavior.
Reads vendor bills from email, extracts the data, resolves the vendor, classifies the lines, and drafts the AP invoice for approval.
View agent →Builds payment batches from outstanding AP invoices and approved expense reports, grouped by method, currency, and source bank.
View agent →Finds paid vendor transactions that are missing their bill and sends escalating documentation requests to the business.
View agent →Processes employee expense submissions from email — receipts, per-diem requests, and mileage claims — into expense reports.
View agent →Sends escalating reminders to employees with missing receipts on submitted expense reports.
View agent →Creates fixed asset records from capitalized AP purchases and schedules depreciation.
View agent →Classifies bank and card lines, resolves the counterparty, posts the GL entry, matches the line, and delegates anything it can't resolve.
View agent →Matches payment transactions to invoices across AP and AR using a six-pass matching pipeline.
View agent →Processed Stripe payout and balance activity — now superseded by the Bank Transaction Processor, which owns card and connector processing.
View agent →Runs scheduled billing cycles for recurring contracts, generating AR invoices with per-contract isolation.
View agent →Renders each AR invoice as a PDF and delivers it to the customer by email.
View agent →Collects payment for AR invoices through the customer's configured method and posts the AR payment.
View agent →Posts amortization journal entries for revenue and prepaid-expense schedules on a recurring cadence.
View agent →Creates or updates vendors, customers, and required records when another agent can't complete its work with the data on hand.
View agent →Creates the missing setup — posting profiles, tax codes, accounts, payment terms — that a workflow needs before it can safely continue.
View agent →Catch-all router for unknown error classes from other agents — it decides where each one should go.
View agent →Meta-agent that diagnoses and proposes fixes to other agent definitions during a weekly health review.
View agent →Ten regional agents cover payroll, VAT, corporate tax, compliance calendars, and statutory filings for Estonia and the UK — the local logic that closed ERPs hardcode and charge consultants to change.
When an agent needs missing master data, configuration, approval, a document, or a human classification, it creates a structured request. The answer routes back to the creating agent and drives the next action.
The point is not to create another automation layer beside the ERP. The point is to make agents the operating layer above a governed ledger, with approvals and audit trails built in.
Talk to us →