AR-TI-FI · AGENTS · EVENT-DRIVEN FINANCE WORKERS

Finance agents that do the work, not just suggest it.

Artifi agents listen to finance events, process documents, classify transactions, prepare payments, reconcile accounts, ask humans for decisions, and write only through governed workflows.

Book a demo →Review controls
27implemented agents
17 + 10core + regional (EE, UK)
150+MCP tools behind controls
100%workflow and agent audit trail
OPERATING MODEL

Events become controlled finance actions.

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.

01Email, schedule, connector, manual request
02system.agent_events queue
03Event processor
04Agent instance
05Workflow, request, approval, ledger
EXECUTION MODES

LLM when judgment matters. Code when the work is known.

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.

LLM agents

Claude Agent SDK agents for unstructured work, judgment calls, email context, PDFs, and novel finance situations.

Code agents

Deterministic Python handlers for known operations such as bank matching, billing runs, delivery, and payment batches.

Hybrid agents

Mostly deterministic workflows with targeted Haiku calls for extraction, classification, fuzzy matching, and email composition.

AGENT CATALOG

Core finance work mapped to dedicated agents.

These are not generic chatbots. Each agent owns a clear slice of finance operations, its trigger events, allowed workflows, and completion behavior.

Accounts payable & spend

6 agents
Bill ProcessorHybrid agent

Reads vendor bills from email, extracts the data, resolves the vendor, classifies the lines, and drafts the AP invoice for approval.

View agent →
Payment ProposalHybrid agent

Builds payment batches from outstanding AP invoices and approved expense reports, grouped by method, currency, and source bank.

View agent →
Bills CollectorHybrid agent

Finds paid vendor transactions that are missing their bill and sends escalating documentation requests to the business.

View agent →
Expense ProcessorHybrid agent

Processes employee expense submissions from email — receipts, per-diem requests, and mileage claims — into expense reports.

View agent →
Receipts CollectorHybrid agent

Sends escalating reminders to employees with missing receipts on submitted expense reports.

View agent →
Asset CreatorHybrid agent

Creates fixed asset records from capitalized AP purchases and schedules depreciation.

View agent →

Banking & reconciliation

3 agents
Bank Transaction ProcessorHybrid 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 →
Reconciliation AgentHybrid agent

Matches payment transactions to invoices across AP and AR using a six-pass matching pipeline.

View agent →
Stripe Transaction ProcessorCode agent

Processed Stripe payout and balance activity — now superseded by the Bank Transaction Processor, which owns card and connector processing.

View agent →

Revenue & billing

4 agents
Billing RunCode agent

Runs scheduled billing cycles for recurring contracts, generating AR invoices with per-contract isolation.

View agent →
Invoice DeliveryCode agent

Renders each AR invoice as a PDF and delivers it to the customer by email.

View agent →
Payment CollectionCode agent

Collects payment for AR invoices through the customer's configured method and posts the AR payment.

View agent →
Amortization RecognizerCode agent

Posts amortization journal entries for revenue and prepaid-expense schedules on a recurring cadence.

View agent →

Platform & control

4 agents
Master Data AgentLLM agent

Creates or updates vendors, customers, and required records when another agent can't complete its work with the data on hand.

View agent →
Configuration AgentLLM agent

Creates the missing setup — posting profiles, tax codes, accounts, payment terms — that a workflow needs before it can safely continue.

View agent →
Triage AgentLLM agent

Catch-all router for unknown error classes from other agents — it decides where each one should go.

View agent →
Agent ArchitectLLM agent

Meta-agent that diagnoses and proposes fixes to other agent definitions during a weekly health review.

View agent →
REGIONAL AGENTS

Country logic, shipped as agents.

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.

Estonia

  • Estonian PayrollRuns Estonian gross-to-net payroll — income tax, social tax, unemployment insurance — and prepares the TSD declaration.
  • Estonian VATPrepares the Estonian KMD VAT declaration and supporting annexes from posted ledger activity.
  • Estonian Corporate TaxHandles Estonia's distribution-based corporate income tax on profit distributions.
  • Estonian Compliance CalendarTracks Estonian filing deadlines and surfaces what's due before each statutory date.
  • Estonian Annual ReportPrepares the Estonian annual report (majandusaasta aruanne) for filing with the business register.

United Kingdom

  • UK PayrollRuns UK payroll with PAYE income tax, National Insurance, and pension contributions.
  • UK VATPrepares the UK VAT return under Making Tax Digital from posted ledger activity.
  • UK Corporation TaxHandles UK corporation tax computation and filing requirements.
  • UK Compliance CalendarTracks UK filing deadlines across HMRC and Companies House obligations.
  • UK Annual AccountsPrepares UK statutory annual accounts for filing with Companies House.
HUMAN-IN-THE-LOOP

Agent requests are the control surface.

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.

GOVERNANCE CHECKS
  • Each agent has explicit allowed workflows and allowed tools.
  • Every run becomes an agent instance with status, input, output, progress, cost, and error history.
  • Human review requests are first-class records, not Slack side threads.
  • Completion callbacks return control to the creating agent so it can continue safely.
  • Risk-based workflow lanes decide whether a proposed write auto-executes or waits for approval.
FROM AGENT TO LEDGER

Agents propose and execute. Finance stays in control.

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 →