runbookify
← All plans
Accounting & Finance / Bookkeeping & Journal Entries

AI Transaction Categorizer: Code Hundreds of Bank Lines in Minutes, Not Hours

Import a bank or credit-card CSV and let AI propose the GL account and class for every line — rules plus memo reading, low-confidence lines first, transfers flagged — then your bookkeeper approves the batch before it becomes journal entries.

IntermediateA weekendBuilds onNext.jsSupabaseResend
What you'll build

A web tool where you import a bank/card CSV, AI proposes the GL account and class/department per line with a confidence score, your bookkeeper reviews low-confidence lines first and approves the batch, every correction feeds back into your rules, and the tool exports coded journal entries as a CSV in your GL's exact format.

Gated download

Enter your email — the plan downloads instantly and a copy lands in your inbox.

By submitting your email you'll also receive the weekly runbookify newsletter. You can unsubscribe at any time.

Before you start

  • A Supabase account (free)
  • A Vercel account (free)
  • A Resend account (free)
  • A bank/credit-card transaction CSV (date, memo, amount)
  • Your chart of accounts (account numbers + names)
  • An optional keyword→account rules list
  • Claude Code or any AI coding agent

The problem this kills

Every month a bookkeeper sits down with a bank export and a credit-card export and starts coding lines. "AMZN MKTP US*2K4…" — office supplies or software? "SQ *THE COFFEE BAR" — meals, or owner's draw? "Online Transfer to Savings" — not an expense at all. Hundreds of these, one at a time, dropping each into the right GL account and tagging the right class or department, then re-keying the survivors into the accounting system as journal entries.

It's repetitive, it's slow, and it's where small errors creep in: a transfer booked as an expense, a vendor coded three different ways across three months, a personal charge that slips into the P&L. The patterns barely change month to month — the same vendors land in the same accounts — yet you re-decide every line by hand. You don't need to keep doing this manually, and you don't need to be a developer to fix it.

What you'll build

A simple internal web tool. You import a bank or credit-card CSV (date, description/memo, amount) and your chart of accounts. The tool reads each line, applies your keyword rules first (DELTA → Travel, GUSTO → Payroll), and for anything the rules don't catch, it uses AI on the memo text to propose the most likely GL account and class/department — each with a confidence score. It flags likely transfers (money moving between your own accounts) so they don't get booked as expenses, and it dedupes on a bank-line fingerprint so the same transaction can't be coded twice.

Your bookkeeper opens the batch with the low-confidence lines first, fixes any wrong guesses, and clicks Approve. Only then does the tool turn the batch into coded journal entries and export them as a CSV in your GL's exact column layout. Every correction the bookkeeper makes is remembered — the next time that memo shows up, the tool already knows the answer.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — which accounting system you export from and import back into, exactly how your bank CSV columns are named, what your chart of accounts and class/department lists look like, which keyword rules you already apply in your head, how you tell a transfer from an expense, your typical and peak monthly volumes, and your messy edge cases — and then it tailors the data model, the categorization logic, and every later step to your answers. This is not a generic template; the agent reads a short spec back to you and waits for your thumbs-up before it builds anything.

From there it walks the agent through the import, the rules-then-AI categorization engine, the confidence scoring and low-confidence-first review queue, the transfer detection and duplicate guard, the bookkeeper review-and-approve screen, the learn-from-corrections loop, and the journal-entry CSV export — each step with a ready-to-copy prompt. There's also a fallback so you can build and use the whole thing today with no integration to your accounting system at all.

The governance it includes (this is the point)

This is real bookkeeping tooling, so it ships with the controls a finance team needs: login so only your team can use it, row-level security so you only ever see your own organization's books, a complete audit trail of who categorized, corrected, and approved which lines and when, a hard human-approval gate so nothing is ever auto-posted — the AI drafts, the bookkeeper reviews and approves, and only then does a batch become journal entries — and duplicate guards keyed on a bank-line fingerprint so the same transaction can't be coded into the books twice. Low-confidence and transfer-suspect lines are surfaced for review instead of quietly slipping through.

Who it's for

Bookkeepers, fractional controllers, and small-business owners who hand-code hundreds of transactions a month across one or many entities. If you can describe how you decide which account a charge belongs in, you can build this.

You've got this — start with the plan, paste the first prompt, answer the interview, and you'll see your first batch coded and queued for review the same afternoon.

Gated download

Enter your email — the plan downloads instantly and a copy lands in your inbox.

By submitting your email you'll also receive the weekly runbookify newsletter. You can unsubscribe at any time.