About

Finance shaped around your business.

Arfiti is a finance system for teams and agents. One shared foundation for the books, the operations and the plan, which people and agents work on through the same controls. We build it so that the way a company runs its finance belongs to the company, and what a finance person knows belongs to the person.

01 · What Arfiti is

A financial foundation, an optional agent layer, and the procedures that connect them.

The records.

A double-entry ledger with subledgers, periods, entities, currencies and dimensions. Posted history is immutable; every change leaves an attributed activity row.

The operations.

Payables, billing, expenses, close, planning and multi-entity work, each defined as a workflow with its own validation, risk lane and approver.

The controls.

Roles and entity scope, approval routes, thresholds the company sets, and an audit trail that people and agents share.

The agents.

Optional built-in agents for recurring work. External assistants and your own procedures can use the same underlying operations.

The procedures.

Skills, plugins and editable business policies that capture how a particular team does the work.

The interface.

Your assistant. Arfiti is an MCP server; Claude, Cowork, Codex or another connected tool is where the work happens. The dashboard is for setup, inspection and review.

02 · What we believe

Six commitments. They are written down so you can hold us to them.

Trust is the product.

The system is only useful if a controller can sign the result without re-doing the work. Everything else is in service of that.

Your policy governs execution.

An agent prepares a bill, a match or a journal. A proposal is not a payment. What crosses the line into the ledger is decided by the policy the company wrote.

The same rules for people and agents.

There is no side door. An agent posts through the workflow gateway with its own role and entity scope, and its run is on the record.

You can read the rules that run your business.

Approval routes, thresholds, posting profiles and procedures are settings and documents, not code you cannot see.

Work that repeats should move, not be re-learned.

Anything that happens every bill, every statement or every month belongs in a skill, a plugin or an agent, so nobody learns it twice.

Software you can leave is software you can trust.

Your data exports. Your procedures are documents. Your plugins are packages you hold. Staying should be a choice.

03 · Why it exists

Finance is Sisyphus work. We want to put the stone down.

A finance function runs on a dozen systems from a dozen vendors, each with its own idea of what a vendor is, how an approval works and where a procedure lives. None of them was built for this business, and the business changes faster than any of them can be changed. Everything people complain about is downstream of that: the re-learning, the adjusting, the fixing, the procedure written three times in three tools. Every new system, release, entity or job rolls the stone back down.

A controller should not spend a career learning software. The time belongs to the work that needs a mind: judgement, exceptions, the decisions no system can make.

For repeating work to move and stay moved, three things have to exist: the intelligence to carry it, an interface that is a conversation, and a place where finance is done and recorded the same way in every company, so that the skill for it can be the same too. The first two now exist. Arfiti is the third.

04 · How we build

Infrastructure first. Internals published, not pitched.

The ledger is guarded at the database.

Balance, period, immutability and attribution are enforced by the database at commit, not by convention in application code.

One write path.

Supported financial operations share authorization, validation and applicable approval controls, whether requested by a person, agent or plugin.

Agents are pipelines of tested blocks.

The block engine, per-organisation patches, dry-run mode and the effect guards are documented in the “Building the Agent Platform” series, with the incidents that shaped them.

Procedures are files.

Skills and plugins are plain packages you can read, version and carry. Check the license included with each package.

Honest about what is planned.

SOC 2 Type II and ISO 27001 are planned, not held. We say so on the Security page.

05 · Who builds it

Built by the person who had to close the books.

Arfiti is founded and built by Andrew Rudchuk, who has worked on every side of the problem this page describes. As an accountant, an auditor and a business analyst, doing the work. As an SAP consultant for eight years, implementing and supporting the systems the work ran on. At Accenture, transforming finance functions and building products on machine learning and RPA. As founder of Hala.ai and Solution Director at Teampay, building the software itself. And at Starship Technologies, Dott and Impress, running and building finance across entities and countries.

The same lesson from every seat: the tools were never the problem, and the tools were never the solution. Judgement got the leftovers, and every automation attempt either forked into unmaintainable custom code or died as a demo. Arfiti is the attempt to build the ground that makes the move easy, so the next finance team does not have to.

06 · The company

Based in Tallinn, Estonia.

Legal entity.

Arfiti Technologies OÜ · registry code 17266831

Where.

Estonia, Tallinn

Write to us.

hello@arfiti.com

Disagree with the thesis? Good.

Write to us, or watch it run on your own books first.