How it works

It uses a browser, the way you would.

That is the whole trick. Clerk.AI is a Mac app that points an AI at a real Chrome window and has it do the routine, repetitive half of your month: log in, download, search, match, name, attach. Everything you already do, except you are not the one doing it.

Three moves, and the month is ready to send.

01
It opens the sites you use

Your bank, your card, your suppliers’ billing portals, your mail. A real browser on your Mac, on a profile kept just for this. When it meets a login only you can pass, it leaves the tab open and asks.

02
It reads what it finds

Statements, invoices, the photos of receipts on your phone. It works out which document belongs to which transaction, names them the way your accountant likes, and checks its own count against the statement.

03
It asks you the rest

Was that lunch a client’s? Which company was this for? A handful of questions a month, answered by speaking a sentence — and most of them are just “let me in”.

Which is why it works with everything: there is no integration anywhere in it. If you can reach a receipt in a browser, so can Clerk.AI — no connector to wait for, no vendor that has to support us first, and nothing for your accountant to change.

See a month go past.

Below is one period, screen by screen. It is quicker to look than to read.

Clerk.AI on first launch: three sentences saying what it is, then a single question — tell me about your business and what you send your accountant — with a text field, a microphone for holding to speak, and an example answer underneath.
It asks you one question. No form, no fields, nothing to look up. Say what your business is and what you send your accountant, in a sentence. If you keep books for more than one company, say that too — each gets its own tab, and its own periods.
Clerk.AI reading back what it understood: your sentence quoted at the top, then the business, how often, who it goes to and what to send, each on its own row; a note saying it does not know the accountant’s email address yet and will ask when it gets there; a green button reading “That’s right — start on July”; and a box to correct it in.
It says it back before it starts. Correct anything it misheard. This is the only place a period ever gets chosen — after this, when a period ends, it starts the next one itself.
Clerk.AI part-way through June, scrolled to the letter: the sites still waiting on a sign-in listed above it, then the letter to the accountant part-written — greeting, sign-off and signature real, three grey placeholder bars where the body has not been found yet, and an attachment list headed “Attached — 3 so far” with the first receipt named.
Then the letter writes itself. Grey means not found yet, and it goes solid as things arrive. When it needs you it says so right there — usually just to sign in somewhere, which is the one thing it cannot do for you.
Clerk.AI offering twenty photos that look like receipts, as a grid of thumbnails. Each has a chip saying what kind of thing it is, a line saying what was read off it, and Include and Drop buttons; above the grid sit Include the rest and a count of how many are still undecided.
It casts a wide net over your photos, and you say what counts. Anything that looks like a receipt is offered; you include or drop each one, and dropping is remembered so the same photo is never offered twice.
The same sign-in nudge on an iPhone: Clerk.AI saying three sites want you to sign in — Hallo Mobilfunk, Bürobedarf Kern and Meridian Business — with a button to go and do it on the Mac and, beneath that, a text field and a hold-to-speak control for answering from wherever you are instead.
Everything reaches your phone. That is the same nudge as the screen above, arriving while you are somewhere else. Walk to the Mac and sign in — or answer from where you are: “skip that one, the invoice is in my mail”, and it goes and looks there instead.
The finished letter in Clerk.AI: no grey left, every attachment named and real, and a plain line saying everything on both statements has a document behind it except the one you explained.
Nothing missing. Every line on the statement has its document, or the letter says why not, in your own words. It cannot decide a period is finished — only you can.
A filed period in Clerk.AI: the letter that was sent, collapsed under a block of facts about the period, what the accountant asked for afterwards, your spoken answer to it, and one box to type or talk into.
You send it, and it keeps listening. The letter goes from your own mail, and stays there afterwards — a filed period still shows exactly what was sent. When your accountant writes back asking for one more thing, paste it in: it fetches it, and remembers so it never asks you that again.

Your part is small, and it is the part that should be.

A close runs in the background over days, not in one sitting. It stops when it reaches something only a person can settle, waits however long you take, and picks up where it left off.

Most of what it asks is not judgment at all — it is a login it cannot pass on your behalf, because strong authentication is yours to approve. That is a feature, not a shortcoming.

You approve the logins

It gets as far as the strong-authentication step and stops with the tab on the right page. Ten seconds, not ten minutes working out where it got to.

You make the calls only you can

Personal or business, which company, what that lunch was. It asks rather than guessing, because a guess means you check every line — which is the whole job again.

You read it before it goes

Clerk.AI cannot mark your books closed. It stops at “ready for you to read”.

And it gets shorter

Every correction is kept and applied next period. The first close teaches it your banks and vendors; the second is the one worth having.

The things people ask at this point.

Does my accountant have to do anything?

No. No account, no portal, no new software, no change of format. They get an email from you with a named folder attached, in the language they work in. There is a page you can forward them.

What if it cannot get into something?

Some sites cannot be automated, and that is expected rather than broken. It tells you which, you drop the file into your books folder, and it carries on from there.

Do I have to sit and watch it?

No — that is the point. Your Mac does need to be awake and online for it to make progress; it cannot work with the lid shut. Questions come to you as cards, and to your phone if you want them there.

Is it going to invent numbers?

It is built not to, fairly aggressively: it counts its rows against your statements, re-opens each file to check it really is the invoice it claims, and names anything unresolved instead of quietly dropping it. It is still a draft for you and your accountant to check.

I have tried AI things that did not work.

Usually because you were handed a general tool and left to build the workflow yourself. This is one job with the workflow already built — including the awkward parts, which are the two sections below.

Can’t I just use Claude Code for this?

Yes, and if you already live in a terminal, go ahead — that is exactly how these books were done for nine months. Clerk.AI is that workflow with the sharp edges taken off: the browser automation set up for you, somewhere to steer it mid-run, questions that find you on your phone, and a packet you can read before it goes. It exists so people who are not versed in Claude Code can still get the benefit.

What does it cost?

Whatever you decide, including nothing — there is a slider. The AI is your own arrangement and is the real cost: a Claude subscription.

What it needs from your Mac.

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. Clerk.AI opens its own Chrome window on a separate profile kept just for this — not your everyday browsing. You sign into your banks and portals in there once, and those sessions stay put.

A Mac that stays awake. The work happens on your machine, in a browser window on it. 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 your 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 sessions you signed into — in a Chrome profile of its own, apart from your everyday one. 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.
3It already runs in its own Chrome profile — separate from your everyday browsing, so it can only reach accounts you signed into inside it. Sign in there to as few as you're comfortable with; everything else is out of reach entirely, and that's the cheapest, most effective control you have.
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 your browser.
✓There is no Clerk.AI server holding your books. The only copy of your folder outside your Mac is whatever your own iCloud backs up.
✓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 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.

Get your next month prepped.

It signs in where it can, collects the statements, finds the receipts that go with each line, and hands your accountant a folder and a drafted email you read before it goes.

Download for Mac
Apple Silicon or Intel · macOS 14+ · v0.4.2