Vendor Statement Reconciliation: Catch Missing Invoices Before the Stop-Ship

The problem this kills

Once a month a key vendor emails a statement — every invoice and credit they think you owe. Somewhere in that list is the thing that bites you: an invoice you never received and never recorded, quietly aging toward "past due." Miss it, and one morning the vendor puts your account on hold and your line goes down. A stop-ship over a $900 invoice nobody saw.

Reconciling that statement against your own books is the job that catches it. But most AP clerks do it with two printouts side by side and a highlighter — eyeballing invoice numbers, ticking off what matches, squinting at the ones that don't. It's slow, it's error-prone, and it's the first task that gets skipped when month-end is on fire. So the unapplied credit the vendor still owes you sits there for a year. The duplicate they're chasing you for never gets disputed. The amounts that are five dollars off pile up until the difference is real money and nobody can remember why.

You don't need an expensive AP suite to fix this. You can build the reconciler yourself, this weekend.

What you'll build

An internal web tool your AP team logs into. You pick a vendor and import two things: the vendor's statement (the CSV or PDF they sent) and your AP ledger for that vendor (the export you already pull). The tool lines the two up by invoice number and does the comparison for you, handling the real-world mess — credits, partial payments, and the same invoice written INV-0042 on one side and 42 on the other.

Everything sorts into three clear buckets: on the statement but not in your books (the missing invoices and credits you may need to chase), in your books but not on the statement (things you've recorded that the vendor hasn't, like a payment in transit), and on both but the amount disagrees (the disputes). Open differences get aged so you can see what's been hanging for 30, 60, 90 days. Your clerk works the screen, decides for each difference whether to request it, dispute it, or record it, and clicks once to export a clean reconciliation — plus a ready-to-send email to the vendor asking for the missing invoices, drafted and waiting in their outbox.

What's inside the Implementation Plan

The downloadable plan is a single markdown file you paste into an AI coding agent. It opens by interviewing you about your own AP process — what your statement and ledger actually look like, how each vendor formats their invoice numbers, how you handle credits and partial payments, which differences you treat as urgent, and your messiest exceptions — and then it reads a short spec back for your thumbs-up before it builds a thing. That's the difference between a tool shaped to your vendors and a generic template you have to fight.

From there it walks the agent through the data model (statement lines, ledger lines, and reconciliation results), the importers for statement and ledger, a normalizer that makes INV-0042 and 42 match, the reconciliation engine that finds the three difference types and the amount diffs, the aging logic, the duplicate guard, the review-and-decide screen, the export, and the drafted vendor email. Every step ends with a ready-to-copy prompt. There's a full "No API yet?" path: import from CSV, export a clean reconciliation CSV, and you never have to touch your ERP's API to ship.

The governance it includes (this is the point)

This is AP — the controls are the product. The plan builds them in: a login so only your team can use it; row-level security so each organization only ever sees its own vendors and reconciliations; a complete audit trail of who imported, matched, decided, and exported, and when; a hard human-approval gate so no difference is acted on until a clerk reviews it and chooses request, dispute, or record; and duplicate guards (on vendor + invoice number) so the same statement can't be reconciled twice and the same invoice can't be counted twice. Nothing leaves the tool — not a vendor email, not a recorded entry — until a person signs off. That's the audit story your controller wants.

Who it's for

AP clerks, AP leads, and controllers who reconcile statements from their key vendors and never want to be surprised by a stop-ship again. If you can explain to a new hire how you tick a statement against your books and what makes a difference worth chasing, you can build this — no developer required.

You've got this — open the plan, paste the first prompt, answer a few questions about how your AP actually runs, and you'll watch your first vendor statement reconcile itself.