Accounting infrastructure
for the AI-operated era.
The ledger is the product. Country logic ships as open Plugins. The work happens inside Claude — agents execute, accountants validate.
You used to have two options. Now there's a third.
For thirty years, your options for finance have been hire people or buy software. Both expensive. Both slow to scale. Neither runs while you sleep — and both leave you doing more management than you signed up for.
Agents do the work
Bank import, classification, posting, reconciliation, payroll math, VAT calculations, accruals, allocations, close steps, intercompany. All automated. All running inside Claude. Most of your books post themselves — overnight, on schedule, or on demand.
CPAs validate
Our accountants review every agent posting before it lands in your statutory books. They handle judgement — capex vs opex, unusual transactions, period close. Real qualifications. Real accountability. Every entry has a name attached.
You supervise the outcome
You don't manage agents. You don't manage accountants. You answer two questions a week and sign the close. Audit any line back to its source — agent, CPA, timestamp, decision.
This is why our services cost a fraction of a traditional firm. We're not paying accountants to post journal entries. We're paying them to judge. Agents do the volume. Humans do the work that requires being human.
Three layers. Read them. Fork them.
Not nine modules. Not a feature grid. The product is three layers and the seam between them is open. If you have ever read a Plaid doc or a Stripe API reference, this will look familiar.
The boring part.
Double-entry, multi-entity, multi-currency, audit-trailed. PostgreSQL. Period locking, posting profiles, dimensions. This is the surface every Plugin and every agent posts against.
The product.
Everything that traditionally lives in separate tools — accounting, expenses, billing, time, payroll, close, VAT, FP&A. All Plugins on one ledger. The integration problem disappears because there is nothing to integrate.
The room you pick.
Where the work actually happens. Claude.ai for finance ops. Cursor for plugin editing. MCP for legacy tools. Artifacts in any surface. Managed Agents for recurring work that hand off to each other without humans in the loop.
One ledger replaces six tools.
And the team that operates the seams.
When the ledger is open and the logic is code, the perimeters between these categories dissolve. They existed because six companies needed six perimeters to defend.
Plus the controller, bookkeeper, AP specialist, and half-time FP&A analyst you'd hire to operate the seams between them. The headcount is the line item that doesn't show up on most pricing comparisons — but it's where the real spend is.
Three doors. Pick the one that fits.
We run your finance function on AR-TI-FI.
The operating model above. Agents do the work, our CPAs validate, you supervise. Bookkeeping, month-end close, payroll, VAT, statutory filings, FP&A. A controller-grade finance team without the headcount.
- Cohort engagements · scoped per entity
- 2-week onboarding · documented playbook
- Baltics + Nordics · serving from Tallinn
Operate AR-TI-FI directly inside Claude.
For technical founders and finance teams. Full ledger, all Plugins, agents, MCP bridge into existing tools. Bring your accountant — they get a validator role with full access.
- Self-serve · pricing finalised on request
- All Plugins MIT · forkable · open source
- Bring your own accountant · validator role
Operate AR-TI-FI for your client book.
Wholesale pricing, plugin forking per client, MCP bridge into existing client systems. Cohort onboarding — we document the playbook with you.
- Wholesale rates · cohort onboarding · Q3 2026
- Plugin authoring · co-built playbook
- No exclusivity — multi-firm channel
You don't have to throw out QuickBooks to try this.
An Arfiti connector syncs your books — QuickBooks, Xero, Merit, and the rest — into Arfiti's ledger. From there, Claude, Cursor, and any MCP-compatible tool see one unified book of record with your existing data already loaded.
QuickBooks stays where it is. Arfiti runs on top — plugins, agents, and an AI-native interface — without asking you to move the system you already trust.
“Firms don't switch ledgers. They route work.”
Agents that hand work to each other.
When the Bank Transaction Processor finds a payment it can't classify, it asks the Master Data Agent to create the missing vendor. When that completes, a callback re-runs the Bank Processor. Agents handle the routine handoffs. Humans gate the controls that matter — opening fiscal periods, posting large adjustments, signing filings — and every gate is wired into the same trace.
Bank-import chain
BTP → unknown IBAN → MDA · auto · low risk → no fiscal period → CFG asks → controller approves → CFG executes → BTP re-runs · 100% match.
Chasing-bills loop
Recon → unmatched payment → Collector emails vendor → reply → Bill Processor posts → Recon closes the loop.
Prepaid pipeline
Bill Proc → MDA creates contract → callback → Bill Proc creates 13-line schedule → Amortization recognizes monthly · controller signs the schedule.
Specificity is the currency of trust.
Every claim on this page links back to something you can read. Plugins are MIT and on disk. Documentation is markdown. Long-form essays are public. Below: the most recent eight pieces.
// 35+ posts · medium · substack · linkedin
Read all posts →Join the closed beta waitlist.
We'll email when we open onboarding slots. Tell us a paragraph about your finance function — entities, current stack, what's painful — so we can match you to the right cohort.