Claude can analyze finance. Artifi lets it operate finance.
Through Artifi, Claude works with your live financial data, your procedures as plugins, controlled workflows and a finance-native ledger. Run the work interactively in Claude, or let Artifi agents run it on schedules and events under the same rules.
Artifi is an independent company and is not affiliated with or endorsed by Anthropic.
01Connect
It starts as a connector in Claude.
Artifi is an MCP server. In Claude it appears as a connector with its finance tools listed, and you decide per tool whether Claude may use it freely, must ask first, or is blocked. The same server connects Claude Desktop, Claude Code, Cursor and any other MCP client, and every call carries the identity and entity scope of the person behind it.
One connector, 16 tools, a permission per tool
OAuth or an API key; nothing is shared through the chat
Claude · Artifi as a connector: its tools, and the permission you give each one
02Act
Connected, you can ask for 300+ things.
Every bubble is one action the connector exposes: a workflow definition with its own required fields, risk lane and approver. Post a bill, release a payment batch, close a period, create a vendor, run payroll, file a return. Claude picks the right one from what you say; the definition decides what is validated and who signs off. Hover any bubble to read it.
One definition per action, cloned from the template and editable per organisation
New actions are added as definitions, not as code
03Analyze
Ask for the view. Keep the Artifact.
With the ledger connected, Claude answers from your postings rather than from files you paste in. Ask for spend by category, an aging, a variance against plan, and it can build the report as a Claude Artifact you keep, refine and return to. The numbers come from the same records your accountant closes on.
Live financial context, scoped to the entities you may see
Reports, tables and Artifacts, not screenshots of a dashboard
Claude · a SaaS-spend report built as an Artifact from Artifi postings (sample data)
04Execute
Turn a decision into a controlled action.
Say what should happen and Claude prepares it: it reads the accounts involved, asks the one question it cannot answer itself, and shows the proposed entries before anything is written. The submission goes through the same workflow definition a person would use, so the lane, the approver and the audit row are the organisation's, not the model's.
A preview with balanced debits and credits before submission
Low-risk work runs through; anything unusual waits for the reviewer your policy names
Claude · a cost allocation requested; Claude reads the context and asks for the allocation basisThe preview · debits and credits balance at €2,400; nothing posted yet
05Operate
Run it repeatedly, under the same rules.
Work that repeats does not need a person in the chat. Artifi agents run the same logic on a schedule or when something arrives: an emailed bill, a bank line, a billing date. Each run is a session you can open: what it read, what it decided, what it submitted, what it left for a person, with duration and model cost on the record.
Same tools, same workflow lanes, same ledger as the interactive work
What an agent cannot resolve becomes a task for the right person
Admin app · one Bill Processor run: an emailed invoice posted, its receipt correctly left alone, 29 seconds, two steps
Analysis vs operation
The same intelligence. A different operating environment.
Dimension
Claude as an analysis tool
Claude operating through Artifi
Context
Files and context supplied in the conversation
Governed access to live financial context
Instructions
Prompts recreated for each task
Versioned skills and reusable plugins
Output
Analysis, explanations and recommendations
Controlled workflow actions and financial records
Execution
User initiates each interaction
Interactive, scheduled or event-driven operation
Controls
Review managed outside the conversation
Permissions, policies, approvals and evidence
Record
Output remains in chat or a file
Actions are traceable to workflow and ledger records
Claude remains the intelligence and the interface. Artifi is the financial operating environment beneath it: the tools, the rules and the record.
What you can run
What finance teams operate through Claude.
Start with one workflow. Run it interactively in Claude, then hand the same logic to an agent once the process is ready to run on its own.
EXAMPLE REQUEST
“Process the new vendor bills. Hold anything with a new supplier or no purchase order.”
WHAT ARTIFI DOES
Reads each bill, resolves the vendor, validates the accounting and prepares entries and payment proposals through governed workflows.
WHERE HUMAN CONTROL REMAINS
New suppliers, policy exceptions and payment releases wait for the reviewers policy requires.
Artifi operates across the finance stack you already have. Expenses, cards, billing and payment tools do not need replacing before the work around them can be automated. See the platform, layer by layer.
Adoption paths
Beside your ERP, or as the ERP.
Claude and the agents work the same way in each mode. What changes is which system keeps the ledger.
MODE 01 · BRIDGE
Operate around the existing stack.
Artifi connects Claude and agents to existing finance systems while the current ERP remains the system of record.
SYSTEM OF RECORD: YOUR EXISTING ERP
INTERFACE
Claude
Where the team works
OPERATOR
Artifi
Runs the workflow
RECORD
Your ERP
Keeps the ledger
Questions finance teams ask
Claude and Artifi, in practice.
No. Artifi is an independent company and is not affiliated with or endorsed by Anthropic. Claude connects to Artifi as a governed operating surface for finance work.
No. Claude acts through governed Artifi tools and permissions. Proposed actions pass policy checks and any required approvals before anything reaches the ledger.
Yes. Bridge mode connects Claude and agents to the systems you already run, with your current ERP remaining the system of record.
Yes. In Native mode Artifi is the governed financial system, operational layer and accounting ledger — adopted when workflow evidence and organizational readiness support it.
Customers, partners and the broader ecosystem. Plugins are business-owned logic — payroll, accruals, allocations, billing rules, tax procedures and company-specific workflows — not vendor-hardcoded packages.
Cowork is interactive: a person initiates work, investigates results and approves. Agents run the same plugins on schedules, events or defined autonomous conditions. Both act through the same controls.
Approval and evidence requirements are set by policy and workflow configuration. Every run records its inputs, decisions, approvals and postings, traceable from the request to the financial record.
Your team, your rules
See Claude run one of your processes.
Bring one real workflow. In a working session we connect Claude to a demo ledger and run it end to end, with your approvers and your thresholds.