Tag what you pay your contractors. LedgerMCP totals it for the year, flags who crossed the 1099 line, and shows whose W-9 you still need.
Nothing to install.
Coffee Company · 2026, through June 30
Net of refunds. Exports to CSV for your CPA.
01 · The year
None of them wait for January.
01 Tag · tag_transaction
Tag each contractor or vendor payment, or have your AI do it as it categorizes. A tag is just a name money rolls up against, so per-vendor totals build themselves through the year.
Tag the Acme Design, J. Rivera and North Signs payments as vendors.
3 vendors tagged.
02 Run · run_1099_report
Each vendor’s net total for the year, checked against the threshold for that year ($2,000 in 2026), with the W-9 status beside it. Anyone you paid but never tagged shows up under the list.
Run the 1099 report for 2026.
| Tag | Paid in 2026 | 1099 needed? | W-9 |
|---|---|---|---|
| Acme Design | $4,800.00 | Over $2,000, 1099 needed | Not collected |
| J. Rivera | $3,150.00 | Over $2,000, 1099 needed | Not collected |
| North Signs | $1,200.00 | Under $2,000 | On file |
Paid this year but not classified:
2 forms to file. 2 W-9s to collect.
03 Collect · update_tag
Attach each W-9 to its vendor tag, classify anyone the report flagged, and export the CSV. Year-end 1099 prep, minus the spreadsheet.
2 W-9s on file. Done for the year.
02 · The catches
Four things it flags before you file.
03 · Tags
The list lives in the books.
No vendor portal, no contact records. A payment can carry more than one tag. Tag as you categorize and the totals stay current.
The same tags power project and client reporting, so the work you do for taxes doubles as insight into where your money goes the rest of the year. And 1099s are only half of tax season: your Schedule C comes from the same year of books.
Schedule C tax prep →Coffee Company · June
1 payment tagged. Total updated.
Run the year-end report, classify a tag as a vendor, tag a payment. Your AI uses the same three.
Questions
Yes. Tag payments to a vendor and LedgerMCP totals what you paid them across the year. The 1099 report lists every vendor, flags those at or above the year’s reporting threshold ($2,000 for payments made in 2026, $600 for earlier years), and marks who is still missing a W-9.
It totals net payments per vendor and applies the right year’s threshold ($2,000 for 2026 payments), so anyone at or above it is flagged as reportable. Refunds from a vendor reduce their total, so you are not over-reporting money that came back.
Yes. Each vendor can hold a W-9 attachment, the same way receipts attach to transactions. The report flags vendors whose W-9 is not on file yet, so you know exactly who to chase before January.
The report catches it. Alongside your known vendors it surfaces unclassified payees, tags that received money out but are not yet marked as vendors, so nobody reportable slips through. Classify them and they roll into the totals.
No. LedgerMCP prepares the report, total paid per vendor with thresholds and W-9 status flagged, and you or your CPA handle the filing. It is the year-end summary that makes filing quick, not an e-file service.
Yes. Your AI tags vendor payments through the year, runs the 1099 report, and tells you who crossed the year’s threshold and who still owes a W-9. You get a clean list to act on instead of reconstructing payments from statements in April.
Tag your contractor payments, run the report, and hand your CPA a clean list.
Works with Claude, ChatGPT, Grok, Cursor, and any MCP client.
Demo book: Coffee Company, 2026 through June 30.