Suspense / Clearing Account Sweeper
Import a suspense or clearing account's activity, let AI net the offsetting items, age what's left, assign an owner and a proposed reclass for each open item — then book the clearing entries only after the controller approves, driving the balance to zero.
A web tool where you import a suspense/clearing account's activity, and AI nets offsetting items, ages every open item, dedupes on reference, and proposes a reclassification and an owner for each one. The controller reviews and approves each clearing entry, and the tool exports GL-ready reclass journals that zero the account plus an aging of whatever remains.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A Resend account (free)
- A suspense/clearing account activity export (CSV is fine) and an owner-routing list
- Claude Code or any AI coding agent
The problem this kills
Every close, the same accounts haunt you: the suspense account, the clearing account, the "we'll sort it out later" account. They're supposed to be temporary holding pens — money parks there for a day until it lands in the right place — but they never quite empty. A wire hits before you know the invoice. A payroll clearing line doesn't net. A reference gets fat-fingered. By month-end the balance is a pile of stragglers, some of them months old, and the auditors want to know why a "temporary" account has a permanent balance.
So you export the activity into a spreadsheet and start the detective work by hand: sort by amount to find the debits and credits that cancel each other out, eyeball the dates to see what's gone stale, guess who owns each leftover, email them one by one, and then build the reclass entries to sweep everything to where it belongs. It's slow, it's repetitive, and it's never quite the same twice — so the account drifts back up the moment you stop watching it.
This is exactly the kind of rules-based, high-stakes cleanup that a small internal tool does better than a spreadsheet — and you don't need to be a developer to build it.
What you'll build
A simple internal web tool for clearing your suspense and clearing accounts. You import the account's activity — date, memo, amount, reference — and an owner-routing list. The tool automatically nets the items that offset each other (a +$4,200 and a −$4,200 with the same reference cancel out), ages everything still open by how long it's sat there, dedupes on reference so a re-imported line isn't counted twice, and proposes a reclassification entry and an owner for each remaining item. Anything past your age threshold gets escalated.
The controller reviews each open item on one screen — the proposed reclass account and the assigned owner — edits anything that's wrong, and clicks Approve. Owners get an email about the items routed to them. Only after approval does the tool produce GL-ready reclass journals that drive the account to zero, plus a clean aging of anything that genuinely can't be cleared yet.
What's inside the Implementation Plan
The plan is a single file you paste into an AI coding agent. It opens by interviewing you about your business — which accounts you sweep, how your activity export is laid out, what your reference convention looks like, your aging buckets and escalation threshold, your reclass accounts, and your nastiest edge cases — and then tailors the data model, the netting logic, and every later step to your answers. This is a build shaped around your accounts, not a generic template.
From there it walks the agent through the database schema, the activity import with its duplicate guard, the auto-netting and aging engine, the owner-routing and reclass-proposal logic, the controller's review-and-approve screen, the owner notification emails, and the export of the reclass journals and the remaining-items aging. Every step ends with a ready-to-copy prompt. Because the whole thing runs on CSV in and GL-ready CSV out, you can build and use it this weekend even if you have no direct connection to your GL.
The governance it includes (this is the point)
This touches the general ledger, so it's built like it matters: login so only your finance team can use it, row-level security so you only ever see your own entity's data, and a complete audit trail of every import, net, edit, approval, and export — who did what, and when. Nothing posts automatically: every proposed reclass is a draft until the controller approves it, and approval is the hard human-in-the-loop gate before anything becomes a journal entry. A duplicate guard on the reference means the same activity line can't be imported and cleared twice.
Who it's for
Controllers and staff accountants who have to clear suspense and clearing accounts every close and want the sweep to be fast, defensible, and the same every period. If you can explain how you decide what nets, what ages, and where each leftover should go, you can build this.
You've got this — open the plan, paste the first prompt, and let it interview you about your accounts.