Clerk.AI · by Augmented Mind AB
Clerk.AI pulls your bank statements, hunts down the matching receipts in Gmail and billing portals, and hands your accountant a clean bundle.
On‑device. EU‑first. Agentic.
Apple Silicon (M1–M4) • Also available for Intel
Local-first • EU-first • Your books stay on your machine
If you operate a Finnish Oy or any other small EU company, the last Sunday of every month tends to look something like this:
It's not hard. It's not even interesting. The real cost isn't the two to six hours every single month — it's the constant background pressure of having to do something labour-intensive but boring, and the occasional late fee when something slips past a tax authority's deadline.
Clerk.AI does it for you.
Four phases, on your machine, in roughly the order you'd do them by hand — except the app does the boring parts.
Clerk.AI signs into each bank with you (you authenticate once via the bank's own login), then downloads the period's CSV and PDF statements for every account.
The app reads each transaction, then goes looking for the proof — inside your Gmail (vendor-specific searches per merchant) and across the billing portals you've connected. Stripe-hosted invoices download in one click. Email-only receipts get printed to PDF. Photographed receipts get matched by OCR.
Brokerage and exchange statements via API where the platform offers one, via signed browser sessions where it doesn't. Balance certificates as of the last day of the period, automatically.
A flat folder of every file, named in your accountant's convention. A draft email in the language they read — Swedish, Finnish, English, whichever — with one structured table per category (transactions with receipts, out-of-pocket expenses, your own outbound invoices, bank statements and investment reports). You review, you press send.
The underlying tech is local browser automation. If your bank, your billing portals, your accountant's tool has a web UI, Clerk.AI can probably reach it — same way you would, with your saved logins. We've tested it against the major EU corporate banks, Stripe-hosted invoices across common SaaS subscriptions, mail-only receipts, brokerage APIs, signed-session statement exports, and a long tail of other vendors. That list isn't a promise — it's just where we've been.
For the receipts that didn't arrive in an inbox — the cash-register printout you photographed, the supplier note your colleague AirDropped — Clerk.AI also watches your Photos library and your Voice Memos. Snap or AirDrop a receipt and it lands in the same index as everything else; record a voice note next to it ("client lunch, the Acme deal") and Whisper transcribes it locally so the context is searchable.
Clerk.AI is built for the small EU company operator who is doing their own monthly prep and would rather not be.
Your bank credentials, your Gmail inbox, your crypto API keys, your photographed receipts — these are the most sensitive things in your digital life. Clerk.AI keeps them where they belong: in your local data folder, in macOS Keychain, behind your OS-level permission boundaries. Augmented Mind AB doesn't operate a cloud store of your bookkeeping records and never holds them. The AI provider you point Clerk.AI at is the only entity outside your machine that gets a glimpse of the data — during inference, for the duration of the query — so pick one whose privacy posture matches yours, or run everything locally.
This is the same on-device-first philosophy as our sister apps Remember This and My Transcriber — both run a private local LLM and store everything in a folder you control. Clerk.AI is the financial-paperwork variant of the same playbook.
Clerk.AI is operated by Augmented Mind AB, a small Helsinki studio. Built by Fred Wollsén, a software engineer who has been working at the frontier of human-AI collaboration for over a decade. Clerk.AI is the financial-paperwork app he wishes had existed when he started his own company — so he built it.
Same studio that ships Remember This (long-term personal memory) and My Transcriber (on-device transcription). All three apps share the same on-device-first stack: macOS native, private local LLM, your data in folders you own.