Outstanding Checks & Stale-Date Tracker: Know What Hasn't Cleared

The problem this kills

You cut a check. Weeks later it still hasn't cleared the bank. Was it lost in the mail? Sitting in someone's drawer? Voided and never reissued? Multiply that by every check your organization writes, and you have a quietly growing pile of money that's technically still owed — some of it old enough that the state expects you to report it as unclaimed property.

Outstanding checks are one of those things everyone means to stay on top of and almost nobody does cleanly. The register lives in one system, the bank's cleared-checks file lives in another, and matching them by hand at month-end is tedious enough that aging and stale-date review get skipped. Then a check goes stale, gets re-cashed after you thought it was dead, or ages past your state's escheatment window and turns into a compliance headache. The clues are all sitting in two CSVs — your register and the bank's cleared list. You just need something that lines them up, ages what's left, and tells you what's gone stale. You do not need to be a developer to build that something.

What you'll build

A simple internal web tool for your AP and treasury staff. You import two files: your check register (check #, payee, amount, issue date) and the bank's cleared-checks export. The tool matches them, marks each check cleared or outstanding, and ages every outstanding check from its issue date. It then flags checks that have crossed your stale-date thresholds (commonly 90 or 180 days, often driven by state rules) as candidates for void, reissue, or escheatment review. Each candidate lands on a review screen with its age and history. Your accountant reviews and clicks Void, Reissue, or Escheat-review — and only then is the action recorded. The tool exports an updated register (with new statuses) plus an action list of everything approved, and keeps reissued checks linked to the originals.

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 — how you cut checks and reconcile today, the systems and CSV exports involved, the exact columns and naming in your register and bank files, your typical and peak check volumes, your stale-date thresholds (and which states drive them), and your messy edge cases like partial check numbers, voids, and re-cashed checks. 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 two CSV imports, the match-and-age engine, the stale-date flagging, the review-and-approve screen, the human gate, and the updated-register and action-list 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 checks, a complete audit trail of every void/reissue/escheat decision (who, what, when, and why), a hard human-approval gate so nothing is ever auto-voided — the tool drafts the candidate, a person decides — and duplicate guards so the same register or bank file can't be imported and processed twice. Reissued checks stay linked to their originals so the trail is never lost.

Who it's for

AP managers, treasury staff, controllers, and accounting leads who own bank reconciliation and carry the abandoned-property risk. If you can describe how you decide a check is stale and what you do about it, you can build this.

You've got this — open the plan, paste the first prompt, and you'll be aging your first real outstanding-checks list this afternoon.