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

Chart of Accounts Mapper & Cleanup: Build an Approved Old-to-New Crosswalk

Audit your chart of accounts for duplicates, inconsistent names, and inactive-but-used accounts — then build an old-to-new crosswalk a person approves before anything moves.

BeginnerAn afternoonBuilds onNext.jsSupabaseResend
What you'll build

A web tool where you import your chart of accounts, AI flags duplicates, odd names, and inactive-but-used accounts, proposes an old-to-new crosswalk, you approve every merge and mapping, and it exports an approved crosswalk CSV in your target system's format plus a cleanup checklist.

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 CSV of your current chart of accounts (number, name, type, active flag, YTD activity) and optionally a target/standard COA
  • Claude Code or any AI coding agent

The problem this kills

Every chart of accounts rots over time. Someone adds "Office Supplies," then "Office Supply," then "Supplies - Office." A consultant opens a new account in the middle of a number range that was supposed to be reserved. Accounts get marked inactive but still carry YTD activity. Twins, near-twins, and orphans pile up until nobody is quite sure which account is the "real" one — and posting drifts a little further off every month.

Then the day comes when you have to clean it up: a year-end tidy, a re-segmentation, or a full migration to a new accounting system. Now every one of those messy accounts needs a decision — keep it, rename it, or merge it into another — and every old account needs a clean mapping to its new home. Do it by hand in a spreadsheet and you'll miss the near-duplicates, fat-finger a mapping, and have no record of why you merged what you merged. You don't need to be a developer to build something that does the tedious flagging for you and keeps a human in charge of every call.

What you'll build

A simple internal web tool for controllers and bookkeepers. You import your current chart of accounts (account number, name, type, active flag, YTD activity) and, optionally, a target or standard COA you're mapping toward. The tool audits the whole list: it flags exact and near-duplicate names, inconsistent naming, overlapping or out-of-policy number ranges, and inactive-but-still-used accounts. Then it proposes an old-to-new crosswalk — which accounts to keep, rename, or merge, and where each old account maps. You review every proposed merge and mapping, edit or reject the ones you disagree with, and approve the final set. Only then does it export an approved crosswalk CSV in the exact format your target system expects, plus a cleanup checklist of the actions to take. No account with activity ever gets quietly dropped — it's always surfaced for a human.

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 — your current COA structure and numbering policy, the system you're cleaning up or migrating to, the exact columns and naming conventions in your export, your account-type scheme, how you tell a true duplicate from two legitimately separate accounts, and the messy exceptions you already know about. It reads a short spec back to you for a thumbs-up, then builds the tool around your answers instead of a generic template. From there it walks the agent through the data model, the COA import, the audit-and-flag engine (duplicates, naming, ranges, inactive-but-used), the crosswalk proposer, the review-and-approve screen with its human gate, and the approved-crosswalk and cleanup-checklist exports. Every step ends with a ready-to-copy prompt.

The governance it includes (this is the point)

This isn't a toy. The plan builds in the controls a real finance function needs: login so only your team can use it, row-level security so people only see their own organization's accounts, a complete audit trail of every mapping decision and override (who, what, when, and why), a hard human-approval gate so no crosswalk is exported until a person has signed off on every merge and mapping, and duplicate guards so the same COA file can't be imported and processed twice. Accounts that still carry activity are never proposed for deletion without an explicit flag and a human decision. The whole tool exists to make a careful human decision easy — the AI drafts the cleanup, a person approves it.

Who it's for

Controllers, bookkeepers, and accounting managers cleaning up a bloated chart of accounts or migrating to a new accounting system, who need a defensible, documented crosswalk instead of a fragile spreadsheet. If you can describe what makes two accounts "the same" in your world, you can build this.

You've got this — open the plan, paste the first prompt, and you'll be auditing your real chart of accounts this 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.