How it works

It does the fetching. You make the calls.

Clerk.AI is a Mac app that supervises an agent working through your period, in a browser profile of its own, on your own machine. It runs in the background over days — you are not meant to sit and watch it.

Who does what, honestly.

Taken from the session logs of two real closes on our own books, not from a diagram. Across 23 days it acted about 1,389 times and needed a human roughly nine — seven of those nine were "log me in".

Measured while the app was still being built underneath those runs, so some of those actions are re-runs and recovery. It is an honest count of that period, not a clean estimate of what your month will cost.

It does
Works out what your accountant needs and lists it before collecting anything.
Downloads statements from each bank, card and payment processor.
Searches your mail for invoices, follows hosted-invoice links, logs into supplier portals — and can pull a one-time code out of your own inbox to finish a login.
Reads the receipts already sitting in your Photos library, in your language.
Matches each document to the movement it belongs to, and re-opens what it downloaded to check the file really is what it claims.
Counts its own rows against your statements and names anything still missing.
Assembles a flat, correctly named folder and drafts the email in your accountant's language.
Writes itself a note about where things actually live, so next month starts closer.
You do
Get it past your bank. It opens the login and stops at the strong-authentication step. Bank ID, an app tap, a passkey, a QR — that's you, on the Mac.
Answer what only you know. Client lunch or personal? Which project? By voice or text, from the Mac or your phone.
Keep or drop what it found. Discovery casts a wide net on purpose.
Read it and send it. Then mark the books closed — it is not allowed to do that itself.

One interruption end to end — the only complete arc short enough to read, and not a typical one: it hits a bank-ID wall, leaves the tab open on the right page, asks in your own language, and waits. Fifty minutes later you answer in one sentence. Seven minutes after that the packet is finished.

Six phases, and a period is usually in the middle of one for weeks.

01 · Setup

Who your accountant is, what country and scheme you file under, which accounts to collect. Asked once, as cards, then remembered.

02 · Collect

Statements from every bank, card and processor. This is where most of the "log me in" moments happen.

03 · Receipts

Mail, supplier portals, scanned post, and the photos on your phone. You keep or drop the candidates.

04 · Match

Every movement gets its document. Where it can't decide, it asks rather than guessing.

05 · Assemble

A flat folder, files named your accountant's way, reconciled against the statements.

06 · Draft

The email, in their language, with every attachment numbered in date order. Then it stops and waits for you.

A finished close in Clerk.AI: all six phases ticked, four of four deliverables ready, the packet assembled and the accountant's email drafted — with two transactions flagged as having no receipt, and a ledger showing the source of each figure.

What it needs from your machine.

Claude Code. The app installs and configures it with you on first launch. It takes a few minutes, it involves a terminal, and it is the single step where people get stuck — so we'd rather say it here than let you find out the night before a deadline.

Google Chrome, but not the one you browse in. Clerk.AI opens a separate Chrome with its own profile, and you sign into your banks and portals inside that profile once. Your everyday browsing, tabs and logins are never involved — and because it is still a real browser driven by a real login, it works with sites nobody has integrated with.

A Mac that stays awake. The work happens on your machine, in that browser session. It progresses whenever the lid is open — not while it's shut.

The model is plumbing, not the product. When something local or open is good enough to do this work, Clerk.AI will use it and this section gets shorter.

Where everything lives
Statements, receipts and the finished packet sit in a folder you chose. There is no Clerk.AI cloud holding your books.
Plain markdown and real files — you can open, edit and version them yourself, and the app copes if you do.
We never ask for a banking password. Logins happen in that browser, by you.
Reading receipts and transcribing your voice happen on the Mac.
It stays inside your books folder and Downloads. It won't go browsing your Desktop or iCloud Drive.
iPhone sync, if you use it, goes through your own iCloud.

The agent step that reasons about your books does go to a model. Which one, and under whose agreement, is your choice: your own Anthropic subscription today, or at-cost credits through us once that is built.

Read this one properly

Is it safe to let this near your bank?

The honest answer is: it is as safe as you decide to make it, and the decision is genuinely yours. The reason Clerk.AI works with everything is that it drives a real browser using real logged-in sessions — its own profile, which you sign into yourself. That is real power, and power of that kind deserves plain language rather than reassurance.

While a session is open, the agent can read what you can read and click what you can click. It is instructed to fetch statements and invoices and nothing else — but the capability is there, so treat it like handing your unlocked laptop to a very fast, very literal assistant.

Which is why you get to draw the line yourself. Give it everything, or keep your bank to yourself and hand it only the portals and the drudgery. It works either way, and the second option still removes most of the work.

Risk · prompt poisoning
Web pages and emails can try to give it instructions.

An agent that reads your inbox and browses supplier sites is reading text written by other people. Text can contain instructions aimed at the agent rather than at you — hidden in an email, a PDF, or a page. Clerk.AI is scoped to reduce this, but no one in this industry has solved it, and anyone claiming otherwise is selling you something.

Risk · the 2FA reflex
Never approve a prompt you weren't expecting.

This is the one that matters most. Because Clerk.AI legitimately asks you to approve bank logins, you will get used to tapping approve. Read every prompt. If it names an amount, a payee, or an action you did not ask for, reject it and stop the run. A strong-authentication prompt is a decision, not a formality.

Risk · it can be wrong
It is a draft, not a filing.

It reconciles, it flags its gaps, it refuses to close your books — and it can still mis-read a receipt or match the wrong document. Everything it produces is for you and your accountant to check. Nothing here is accounting or tax advice.

What we recommend
1Only let it do what you're comfortable with. This is the real answer, and it's entirely yours to set. If handing it your bank feels wrong, don't — log in and download the CSV yourself, drop it in the folder, and let the agent handle the tedious half instead: the SaaS portals, the invoice hunting, the matching, the naming, the email. That is still most of the work and most of the misery.
2Watch it, at least at first. The run view shows every step in readable language. Keep it visible while it is working on a bank, and read the log occasionally rather than never.
3Sign into only the accounts you've decided it may touch. The separate profile is automatic, so this is the one part left to you — and anything you don't sign into there is out of reach entirely. The cheapest, most effective precaution available.
4Prefer read-only where your bank offers it. Many banks issue a viewer-level login or a read-only user. If yours does, use that one here.
5Don't leave it running unattended on accounts that can move money, and check your statements as you always would.
6Stop it if anything looks odd. Quitting the app ends the session. Nothing is lost — a close survives being interrupted and picks up later.
What is genuinely not a risk
We never receive, store or transmit a banking credential. You type them; they stay in that browser profile, on your Mac.
There is no Clerk.AI server holding your books, and no copy of your folder anywhere but your Mac.
It is scoped to your books folder and Downloads. It will not read your Desktop, your Documents or your iCloud Drive.
Nobody at Augmented Mind AB can see your session, your screen or your files.
Where responsibility sits

Clerk.AI runs on your computer, under your account, in a browser profile you signed into, at your instruction. You remain responsible for your own accounts, your own approvals and your own filings — including anything the agent does with a session you authorised, and anything you approve when prompted.

The software is provided as-is, without warranty, and Augmented Mind AB accepts no liability for financial loss, incorrect bookkeeping, missed deadlines or unauthorised transactions arising from its use. It is not accounting, tax or legal advice. If that trade isn't one you want to make, this isn't the right tool for you — and we'd rather say so here than after you've bought it.

Try it on a month you already know.

The first close teaches it your banks, your vendors and your quirks. The second is the one worth having.

Apple Silicon or Intel · macOS 14+ · v0.3.0