Your client paid 14 contractors via ACH this year. The 1099s are due January 31. You need to pull every payment over $600 from the bank statement, and the accounting system has the wrong categories.
1099 contractor bookkeeping is the #3 pain point for bookkeepers. This page covers the $600 threshold, the 4 columns you need, the payee rollup from the recon cutoff tool, and the 1099-NEC vs 1099-K distinction.
The IRS 1099-NEC threshold is $600 in a calendar year. Most bookkeepers pull 1099 data from the bank statement, not from the accounting system (where it’s often miscategorized). The recon cutoff tool’s year-end export includes a payee rollup that shows the total paid per payee across all transactions. This is your 1099 source of truth.
The 4 columns needed: payee name, total paid, date of last payment, address. The recon cutoff tool’s year-end export includes all 4. The 1099-NEC form is what you file with the IRS. The 1099-K is what payment processors (Stripe, PayPal, Venmo) issue for transactions over the threshold (currently $5,000, dropping to $2,500 in 2025, $600 in 2026).
For the broader bookkeeper workflow, see the bank statement workflow for bookkeepers pillar. For audit prep (the year-end archive), see the audit prep guide. For multi-entity (when the client has multiple entities paying contractors), see the multi-entity guide.
The $600 Threshold
The IRS 1099-NEC threshold is $600 in a calendar year. Any payee who received $600 or more in a calendar year from the client gets a 1099-NEC. The threshold is per payee, not per transaction. A payee who received 5 transactions of $150 each ($750 total) gets a 1099-NEC.
What most guides miss about crypto tax reporting is that the quality depends on the mechanism, not on the tool. Two tools that look different on the surface often run the same 4-step process underneath: read, find, parse, verify. The difference is in how well each step handles edge cases (merged cells, missing balances, non-standard date formats, scanned vs digital input).
Choosing between tools based on UI alone misses the actual quality lever.
The threshold is $600 in aggregate, not per payment. The bookkeeper needs to total all payments to each payee across the year. The recon cutoff tool’s year-end export includes the payee rollup that does this totaling automatically.
What Counts Toward the Threshold
All payments count: ACH, check, wire, credit card, PayPal, Venmo. The payment method doesn’t matter. The threshold is the total amount paid to each payee, regardless of method.
Reimbursements don’t count. If the client paid a contractor $1,000 for services and reimbursed $200 for materials, only the $1,000 for services counts toward the 1099-NEC threshold. The reimbursement is a separate accounting entry.
The 4 Columns You Need
The 1099-NEC form has 4 columns: payee name, total paid, date of last payment, and address. The recon cutoff tool’s year-end export includes all 4. The export is a CSV file that imports into the 1099 software (e.g., QuickBooks 1099, Tax1099.com, or manual IRS forms).
Payee name. The legal name on the contractor’s W-9. Most bookkeepers have a W-9 on file from the contractor. The recon cutoff tool’s payee rollup matches the bank statement payee to the W-9 list.
Total paid. The sum of all transactions in the calendar year. The recon cutoff tool’s year-end export calculates this from the converted bank statement. The total is the 1099-NEC box 1 amount.
Date of last payment. The date of the most recent payment in the calendar year. The recon cutoff tool’s year-end export includes this date. It’s used to confirm the contractor was active in the year.
Address. The contractor’s address from the W-9. The recon cutoff tool’s payee rollup matches the address from the W-9 to the bank statement. The address goes on the 1099-NEC form.


From Bank Statement to QuickBooks-Ready File
That manual cleanup you just read about? This tool skips it. Turn your PDF into QBO for QuickBooks without storing your data anywhere.
Start ConvertingThe Payee Rollup
The payee rollup is the recon cutoff tool’s year-end export. The rollup groups all transactions by payee, sums the totals, and lists the date of the last payment. The rollup is the 1099 source of truth.
The rollup takes 2 minutes to generate. Without the rollup, the bookkeeper would manually total each payee’s transactions, which takes 2-3 hours for a 14-contractor client. The rollup is the biggest time-saver in the 1099 workflow.
1099-NEC vs 1099-K
1099-NEC is what the client issues to contractors. 1099-K is what payment processors (Stripe, PayPal, Venmo) issue to the IRS. The two forms don’t overlap if the categories are right.
1099-NEC is for non-employee compensation. The client pays the contractor directly (ACH, check, wire). The client issues the 1099-NEC. The recon cutoff tool’s payee rollup covers this case.
1099-K is for payment card and third-party network transactions. Stripe, PayPal, and Venmo issue the 1099-K for transactions over the threshold. The 1099-K threshold has changed: $5,000 in 2024, $2,500 in 2025, $600 in 2026. The bookkeeper doesn’t need to issue 1099-K; the payment processor does.
When Both Forms Apply
If the client paid a contractor $10,000 via Stripe, the client doesn’t issue a 1099-NEC (Stripe issues the 1099-K). If the client paid the same contractor $5,000 via ACH, the client issues a 1099-NEC. The two forms cover different payment methods.
The bookkeeper needs to track both. The recon cutoff tool’s payee rollup covers the ACH/check/wire payments. The Stripe dashboard covers the Stripe payments. The bookkeeper reconciles the two to make sure the contractor doesn’t get a 1099 for the same payment twice.
The 1099 Workflow
The 1099 workflow runs in 6 steps. The recon cutoff tool’s year-end export compresses the data collection step from hours to minutes.
Step 1: Collect W-9s
Every contractor needs a W-9 on file. The W-9 is the source of the payee name, address, and TIN. The bookkeeper sends a W-9 request to each contractor in November. The W-9 goes in the client’s permanent file.
Step 2: Pull the Year-End Bank Statement
The year-end bank statement covers January 1 through December 31. The recon cutoff tool’s year-end export takes the full year and generates the payee rollup.
Step 3: Generate the Payee Rollup
The recon cutoff tool’s year-end export groups all transactions by payee, sums the totals, and lists the date of the last payment. The rollup is the 1099 source of truth.
Step 4: Match Payees to W-9s
The bookkeeper matches each payee in the rollup to the W-9 on file. The match is usually clean: the bank statement payee name matches the W-9 name. The mismatches are usually spelling differences (“ABC LLC” vs “A.B.C. LLC”) or name changes (the contractor got married and changed their name).
Step 5: File the 1099-NECs
The 1099-NECs are filed by January 31. The filing method is paper (IRS form 1099-NEC) or electronic (IRS FIRE system or 1099 software). The recon cutoff tool’s year-end export imports into 1099 software, which handles the electronic filing.
Step 6: Archive
The 1099-NECs are archived. The archive includes the W-9, the payee rollup, the 1099-NEC form, and the IRS confirmation. The recon cutoff tool’s archive feature stores all four in the client’s permanent file.
The Common Mistakes
3 mistakes bookkeepers make on 1099 prep.
Pulling 1099 data from the accounting system. The accounting system has the wrong categories. The fix: pull 1099 data from the converted bank statement, not from the accounting system. The recon cutoff tool’s payee rollup is the 1099 source of truth.
Missing the $600 threshold by counting per-transaction. The threshold is per payee, not per transaction. The fix: total all payments to each payee across the year, then check who crossed the $600 threshold.
Skipping the W-9 collection. The W-9 is the legal protection. Without it, the bookkeeper is filing a 1099-NEC with incomplete information. The fix: send the W-9 request in November, follow up in December, and don’t file the 1099-NEC for any contractor without a W-9.
The Year-End Timing
The 1099-NECs are due January 31. The bookkeeper needs the year-end bank statement by January 15. The recon cutoff tool’s year-end export takes the year-end statement and generates the payee rollup in 2 minutes.
The bookkeeper should run the year-end export in early January, not late December. The reason: the December statement might not be available until January 5-7. Running the export in early January ensures the December data is included.
For the broader bookkeeper workflow, see the bank statement workflow for bookkeepers pillar. For audit prep, see the audit prep guide . For multi-entity, see the multi-entity guide . The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.
The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.
Related:
This topic is part of the bookkeeper-resource cluster on this site. The consolidated hub, covering onboarding, monthly close, year-end, client deliverables, and multi-entity workflows, lives in the complete bookkeeper workflow guide.
For related reading on the broader clusters, the covers credit-card-side mechanics, and the covers bank-account-side mechanics. The expanded bank statement anatomy is a useful primer.
More on the broader cluster
For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.
When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal.
Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored.
The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes.
Decision framework for this topic
For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.
Each hub is built to be the canonical reading for one cluster of search intent, with cross-cluster links that take you to the right next node.
When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal. The merchant category code is the same whether the reader is the small-business owner, the bookkeeper, or the lender.
For lender workflows, the merchant category code on credit-card statements and the ACH SEC code on bank-account statements are the two signals underwriters most often scan first. Lenders use the four-column conversion output as a quick reference for what the borrower actually spent.
Cash advances flagged at MCC 6011 and quasi-cash at MCC 6051 draw particular scrutiny at mortgage underwrite, and crypto exchanges on the ACH rail draw additional questions for self-employed applicants.
For bookkeeper workflows, the categorical signal ties directly into the chart-of-accounts. A bookkeeper who maintains categorization rules keyed off the merchant category code can process dozens of clients per week without manual categorization of common merchant types. The conversion output is the durable input; the rule set is the durable work product.
Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored. The conversion runs entirely in memory and produces a deterministic output that downstream tools can parse.
The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes. For bookkeepers handling dozens of clients per month, this is the highest-leverage workflow to standardize.
Related reading and broader clusters
For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.
Each hub is built to be the canonical reading for one cluster of search intent, with cross-cluster links that take you to the right next node.
When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal. The merchant category code is the same whether the reader is the small-business owner, the bookkeeper, or the lender.
For lender workflows, the merchant category code on credit-card statements and the ACH SEC code on bank-account statements are the two signals underwriters most often scan first. Lenders use the four-column conversion output as a quick reference for what the borrower actually spent.
Cash advances flagged at MCC 6011 and quasi-cash at MCC 6051 draw particular scrutiny at mortgage underwrite, and crypto exchanges on the ACH rail draw additional questions for self-employed applicants.
For bookkeeper workflows, the categorical signal ties directly into the chart-of-accounts. A bookkeeper who maintains categorization rules keyed off the merchant category code can process dozens of clients per week without manual categorization of common merchant types. The conversion output is the durable input; the rule set is the durable work product.
Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored. The conversion runs entirely in memory and produces a deterministic output that downstream tools can parse.
The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes. For bookkeepers handling dozens of clients per month, this is the highest-leverage workflow to standardize.
From Bank Statement to QuickBooks-Ready File
That manual cleanup you just read about? This tool skips it. Turn your PDF into QBO for QuickBooks without storing your data anywhere.
Start Converting







