Contractor Payment Ledger: Know Your 1099 List in October, Not January

The problem this kills

Every January, finance plays detective. Someone exports a year of contractor payments, sorts by vendor, eyeballs who crossed $600, and only then discovers which vendors need a 1099 — usually missing a W-9 for half of them and scrambling under a deadline. The information was sitting in the AP system the whole time; nobody was watching the running total.

It's avoidable. The reason a vendor crosses the 1099 reporting threshold isn't a surprise — it's the sum of payments you already made. If you keep a running year-to-date total per contractor and flag the crossing the moment it happens, finance knows in October exactly who needs a 1099 and can chase the missing W-9s with months to spare. You don't need to be a developer to build the tool that does this.

What you'll build

A simple internal web tool. You import your AP payments (or enter them as you go): vendor, date, amount, payment type. The tool keeps a running year-to-date total per vendor, applies your reporting threshold (the standard $600 for 1099-NEC, or whatever you set), and flags every vendor that has crossed it — or is within a "watch" margin of crossing. It drops the payments that don't belong on a 1099-NEC (anything paid by card or third-party processor settles on a 1099-K, reported by the processor, not you). Then finance opens the threshold-crossing list, confirms which of those vendors are genuinely 1099-reportable — excluding corporations and other exempt payees — and clicks Confirm. Out comes a clean 1099-candidate list and a per-vendor payment summary, ready to hand to year-end prep.

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 AP or accounting system you export from, exactly what your payment columns are named, how you tell card payments apart, how you key a vendor, your threshold and "watch" margin, your typical and peak payment volumes, and the messy edge cases — and then it tailors the data model, the totals, 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 running-total and threshold-flag logic, the early-warning watch list, the finance confirm-reportable screen, and the candidate-list export — each step with a ready-to-copy prompt. There's also a fallback so you can build and use the whole thing today even with no API to your AP system.

The governance it includes (this is the point)

This feeds tax reporting, 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 vendors and payments, a complete audit trail of who imported, confirmed, and exported what and when, a hard human-confirmation gate so a vendor is never marked reportable until finance signs off, and duplicate guards keyed on vendor + payment reference so the same payment can't be counted twice and inflate a total.

Who it's for

AP teams, bookkeepers, and controllers who only discover their 1099 list at year-end and want the running total watching itself all year. If you can describe how you decide who gets a 1099, you can build this.

You've got this — start with the plan, paste the first prompt, answer the interview, and you'll watch your first contractor's year-to-date total build the same afternoon.