GC 1099-NEC Workpaper for Construction Subcontractors

The One Big Beautiful Bill Act (OBBBA) raised the 1099-NEC reporting threshold from $600 to $2,000 per payee per calendar year, effective for calendar-2026 payments filed in January 2027; the IRS 2026 information-return threshold guidance reflects that post-2025 floor. The $600 threshold still governs calendar-2025 payments filed in January 2026. For GCs, that means the early-2026 workpaper runs on the old floor, while the early-2027 close is the first one under the new $2,000 threshold. Subcontractors paid between $600 and $1,999 in 2025 land on the 1099 file; the same payments in 2026 do not. Subs hovering near $2,000 need monitoring through December because a single late retainage release can push them over.

Other controls still matter. The GC still issues 1099-NEC to non-corporate subcontractors at or above the applicable threshold, files with the IRS by January 31, and gives recipients a copy by the same date. The corporate exemption, service/material classification, backup withholding, and IRS B-Notice cycle still apply. This article is sized to a general contractor's reality: a 30-to-200-subcontractor vendor master, December payments across ACH, check, wire, and occasional card activity, an LLC-heavy vendor mix, and a year-end close that overlaps retainage release and final-lien-waiver reconciliation. Single-property landlords cutting checks to two contractors should read the small-scale rental-landlord 1099-NEC workflow instead.

W-9 Box 3 and the single-member LLC reporting trap

Reportability turns on a single field. On Form W-9, Box 3 (Federal tax classification) tells the GC how the IRS treats the subcontractor for federal tax purposes, and that classification — not the legal name, not the d/b/a, not the AP clerk's intuition about the entity — decides whether each vendor lands on the 1099-NEC list.

Box 3 has the following federal-tax-classification options (Individual / sole proprietor / single-member LLC are grouped on a single line of the form, which is why the bullets below total six). For 1099-NEC purposes at this stage, here is what each means.

• Individual / sole proprietor / single-member LLC. Reportable. The W-9 may list a TIN that is either the owner's SSN or the LLC's EIN, but the federal classification governs.
• C corporation. Generally exempt under the corporate exemption.
• S corporation. Generally exempt under the corporate exemption.
• Partnership. Reportable. Partnerships are not corporations and the corporate exemption does not reach them.
• Trust/estate. Reportable. Trusts and estates are not corporations either.
• Limited liability company. This is the field that requires the closest read. An LLC checking this box must enter C, S, or P in the adjacent field to indicate how the LLC has elected to be taxed. C and S route to the corporate exemption; P (partnership) is reportable. If the field is blank, the W-9 is not complete — the GC should request resubmission rather than guess.
• Other. Read the explanation field. The vendor is reportable unless the entity it describes is a true corporation.

The trap that catches GCs at scale is the single-member LLC. An LLC with one owner that has not affirmatively elected to be taxed as a corporation defaults to disregarded-entity status under federal tax rules, which means the IRS treats the LLC as a sole proprietorship for federal tax purposes. A subcontractor invoicing as "Smith Mechanical LLC" with one owner and no S-corp election is, for 1099-NEC purposes, a sole proprietor — and therefore reportable. The "LLC" suffix on the legal name reads as corporate to anyone who has not internalized the matrix, and the workpaper bug shows up as missing 1099s for entities the GC assumed were exempt. At a vendor count of 30 to 200 subcontractors, where LLCs dominate the mix, this is the single most common error.

The correct read for the SMLLC W-9 is mechanical: confirm that Box 3 is filled in as Individual / sole proprietor / single-member LLC (not the LLC line with C, S, or P), and treat the vendor as reportable regardless of what the legal name implies. If a single-member LLC has actually elected S-corp taxation, the W-9 will show the LLC line with "S" entered alongside it; that vendor moves to the corporate-exemption side of the workpaper. The election state lives on the W-9, not in the GC's head.

Corporate-exemption status belongs in the same W-9 pass. Payments to a C-corp or S-corp subcontractor for ordinary trade work are generally exempt from 1099-NEC reporting, but only when a current W-9 supports that classification. If the W-9 is old, was furnished under a prior legal name, or predates a known restructure, request a refreshed W-9 before applying the exemption flag.

The construction-relevant carve-out is direct attorney payment. If the GC pays a subcontractor's law firm under a mechanics-lien dispute or settlement, legal fees can remain reportable even when the law firm is a corporation. Flag those payments for CPA review before the workpaper closes; they are not the same as routine trade payments to a corporate sub.

Foreign-vendor classification runs on a different track entirely. Subcontractors that are foreign persons or foreign entities provide the W-8 series rather than W-9 and route to Form 1042-S rather than 1099-NEC; the rate, the withholding mechanics, and the filing path are all separate. If your subcontractor list includes any cross-border vendors, the cross-border counterpart for foreign vendors using Form W-8 and Form 1042-S covers that workflow. The rest of this article assumes US-person subcontractors with W-9s on file.

Splitting materials and labor on subcontractor invoices

For 1099-NEC, do not default to a labor-only figure. The IRS Form 1099-MISC and 1099-NEC instructions treat payments for services by nonemployees as Box 1 compensation, including parts or materials when those parts or materials are incidental to performing the service. The workpaper question is not "what labor line can I isolate?" It is "was this payment for subcontractor services, a true merchandise purchase, or a separately paid supplier?"

That distinction changes the construction workflow. A mechanical sub that furnishes and installs an RTU on one invoice is normally being paid for a service contract, even though equipment and ductwork sit inside the price. A concrete sub that delivers and places ready-mix under one scope has the same issue: the material is part of the performed work. Suppressing the equipment, fixture, or material amount just because it is visible on the invoice can understate Box 1 if those items are incidental to the subcontractor's service.

True merchandise-only payments are different. If the GC buys panels, pipe, drywall sheets, or fixtures directly from a supply house, that vendor is evaluated on its own W-9 and payment facts. Many distributors are corporations and exempt under the corporate exemption; if they are not exempt, the payment still may be a merchandise purchase rather than nonemployee compensation. The point is that the supply-house invoice is not a labor/material split inside the subcontractor's service payment.

Reimbursements need the same discipline. Separately stated, receipt-backed reimbursements can be excluded when they are not payment for the subcontractor's service. A vague "materials" line inside a labor invoice is not enough by itself. Escalate unusual mixed contracts, owner-purchased materials, and large pass-throughs before suppressing amounts from Box 1, and document the reason in the workpaper.

Back-allocating after the fact is the red flag. If an invoice says "labor and materials per scope — $22,500" and the GC estimates 40% labor in January, the workpaper now contains an unsupported tax position. If the business needs labor visibility for cost coding or certified payroll, require better invoice structure in the subcontract terms going forward; do not invent a labor-only number during 1099 close.

Filtering the December payment register: method, retainage, and lien waivers

The payment-aggregate column on the workpaper is the year-to-date sum of payments to each subcontractor for the calendar year, filtered to include only the payments that count toward 1099-NEC. Pulled straight from the GL payment register without filtering, those totals double-count card-paid amounts and miscount any retainage release that landed across the calendar-year line. Two filters and one reconciliation get the totals right.

The first filter is payment method. ACH, check, and wire payments count toward the 1099-NEC aggregate. Credit-card payments and amounts settled through third-party payment networks (PayPal, Stripe-routed payments, marketplace payouts) are excluded because the processor reports those amounts to the IRS on Form 1099-K instead. The practical impact is small for most GCs since subcontractors are rarely paid by card, but the filter still has to run — an unfiltered register lumps card-paid amounts into the 1099-NEC aggregate and duplicates them against the processor's 1099-K.

The second filter is the calendar-year cutoff, which becomes operationally interesting at year-end because of retainage. Retainage is held back across the life of the contract and released either at substantial completion or at final acceptance. A retainage release wired or cut on December 30 lands in the calendar year just ending and adds to that subcontractor's payment aggregate; the same release dated January 2 lands in the next year. Controllers releasing retainage in late December should be aware that those late-year releases sometimes push subs over the $2,000 threshold who would otherwise have been below it, especially in the early-2027 cycle when the threshold is new and several mid-tier subs are running close to it. The reverse is also legitimate: holding a retainage release across the calendar-year line for cash-flow or scheduling reasons is a real timing decision, but it has 1099 consequences for the sub on both sides of the cut, and the workpaper has to reflect the actual payment date, not the contract event the release relates to.

The third piece is the final-lien-waiver reconciliation, which the same controller is usually running in the same January window. A final unconditional lien waiver from a sub identifies the total contract amount paid to date — a number the sub stands behind in writing in exchange for the final release. That figure should reconcile against the workpaper's payment-aggregate column for that vendor. Gaps in either direction (lien waiver higher than workpaper, or vice versa) usually trace to a missed retainage release, a payment posted to the wrong vendor in the GL, or a payment recorded under a parent company name when the sub bills under an affiliate. Some discrepancies trace further upstream to a schedule-of-values line misallocated when processing G702 and G703 pay applications from subcontractors earlier in the year, in which case the resolution is to walk the affected pay applications back to the schedule of values.

One last exclusion: reimbursements separately stated on the invoice and supported by receipts (per-diems, travel, materials passed through with documentation) are excluded from the 1099-NEC aggregate; reimbursements bundled into a labor invoice without separate identification are not.

Backup withholding, Form 945, and configuring AP for missing W-9s

When a subcontractor has not furnished a valid W-9, or when the IRS has notified the GC that the TIN on file is incorrect, the GC has to withhold from each reportable payment and remit the withheld amount to the IRS. According to the IRS's 24% backup withholding rule, when a payee fails to furnish a correct taxpayer identification number to the payer, the payer is required to withhold backup withholding at the current rate of 24 percent on reportable payments. That is the operative number every AP supervisor needs to know going into a new vendor relationship: no W-9, withhold 24%.

The mechanic that determines whether the GC actually does this is a vendor-record setting. Most construction accounting systems carry a 1099-eligibility flag and a backup-withholding flag. When a vendor's W-9 is missing or invalid, the backup-withholding flag should be set so every payment run withholds 24% from gross before issuing the net check or ACH. The vendor receives 76% of the invoice; the IRS receives the rest.

Where this breaks down is when the configuration is not maintained. A new sub onboarded mid-year without a W-9, with the backup-withholding flag left off and the 1099-eligibility flag left at default, has been paid gross all year. The GC carries the liability for the unwithheld amount, and the discovery usually happens in January when the controller is building the workpaper and notices that several vendor records have neither a W-9 in the file nor a withholding history. At that point the underwithheld amount is the GC's, not the sub's.

Backup-withheld amounts are remitted to the IRS using Form 945 (Annual Return of Withheld Federal Income Tax). Form 945 is filed annually by January 31 of the following year, and the same withheld amounts are also reported in Box 4 of the recipient's 1099-NEC so the sub can claim credit for them on their own return. Deposit timing during the year depends on the GC's deposit schedule (monthly or semi-weekly under the same rules that govern other federal-tax deposits); a GC with substantial backup-withholding volume usually lands on a semi-weekly schedule. The deposits are made through EFTPS, not with the Form 945 itself.

The prior-period correction path depends on timing. If the missed withholding is discovered before the next payment to the same vendor and within the same calendar year, the GC catches up by withholding the underwithheld amount from subsequent payments, up to the IRS-permitted catch-up limit. If discovery happens after the year-end close, the GC owes the underwithheld amount as a payor liability and faces failure-to-deposit and failure-to-file penalties on top. Box 4 of the 1099-NEC reports only what was actually withheld and remitted, not what should have been, so the corrective filings have to be sequenced before the 1099-NECs transmit.

The mid-year W-9 correction is the cleanest case. When a vendor furnishes a corrected W-9 mid-year that resolves the missing-data condition, backup withholding stops on the next payment going forward. Amounts already withheld in the same calendar year stay withheld, stay reported in Box 4, and stay remitted on Form 945; the sub reconciles them as a credit on their own return. The GC does not refund the withheld amounts. The sub files for them through the IRS via their own tax return.

IRS TIN-Match and the CP2100 B-Notice cycle

Every TIN/name pair on the workpaper has to match the IRS's records when the 1099-NEC file goes in. Mismatches do not bounce the filing, but they create CP2100 or CP2100A notices the following spring and put the GC on a short response clock. The cheaper move is to run IRS TIN-Match through e-Services before filing and fix bad W-9 data while the workpaper is still open.

The B-Notice cycle can stay short in this article. After a CP2100 or CP2100A, the GC generally has 15 business days to send the First B-Notice to affected payees. If a payee does not provide a valid W-9 within the response window, backup withholding starts at 24% on subsequent reportable payments. A repeated mismatch can trigger a Second B-Notice, where a refreshed W-9 alone may not cure the problem. Keep a log of notice date, B-Notice sent date, payee response, and withholding start date.

For the full spring response workflow, use the dedicated CP2100 B-notice AP workflow. In this workpaper, the important point is simpler: validate TIN/name pairs before filing, and make sure any unresolved B-Notice vendor is flagged before the next payment run.

Filing: e-file thresholds, January 31, and state requirements

Form 1099-NEC must be filed with the IRS and furnished to the recipient by January 31 of the year following the calendar year of payment. The IRS filing and recipient copy share the same deadline, and 1099-NEC does not have an automatic 30-day filing extension.

E-filing is mandatory for most GCs. Under current rules, any filer required to file 10 or more information returns in aggregate must e-file, and a 30-to-200-subcontractor GC is already above that threshold. The IRS's IRIS portal is the no-cost federal e-file route and accepts CSV uploads or direct entry; commercial 1099 software can bundle IRS filing, recipient delivery, and corrections into the same workflow.

State filing should be checked in December, not during the final transmit. Many states accept data through the IRS Combined Federal/State Filing program, but some require a separate state filing, have their own portals, or keep thresholds and deadlines that do not mirror the federal rule. Build a short state matrix for every jurisdiction where the GC pays subcontractors and reuse it each year unless the business expands into a new state.

Building the workpaper from W-9 PDFs, invoices, and the GL

The workpaper itself is straightforward at the structural level: a single-tab Excel workbook, or its equivalent inside the GC's accounting system, with one row per active subcontractor and columns for legal name, TIN, W-9 Box 3 classification, corporate-exemption flag, address, year-to-date payment aggregate, excluded payment amount with reason, reportability flag, backup-withholding flag, and Box 4 backup-withheld amount. Anything else — project codes, retainage status, B-Notice history — is useful context, not the core file.

Three data sources feed those columns. The W-9 PDF set holds legal name, business name where different, Box 3 classification, LLC sub-classification where applicable, TIN, address, and signature date. The subcontractor invoice corpus shows whether each payment is for services, true merchandise, reimbursement, or another excluded category. The GL payment register is already structured — vendor, date, amount, method, reference — and needs filtering and aggregation.

The math is not the bottleneck. The bottleneck is getting W-9 data points and invoice classification facts out of PDFs into rows the workpaper can join against. If those surfaces become structured tables, the rest is mechanical.

Extraction is useful where the workpaper depends on fields buried in PDFs: W-9 legal name, TIN, Box 3 classification, address, signature date, invoice line descriptions, payment method clues, and amounts that determine whether a payment is services, merchandise, reimbursement, or another excluded category. In Invoice Data Extraction, the user uploads the PDFs, describes those fields in a prompt, and downloads structured Excel, CSV, or JSON ready to join into the workpaper. You can extract W-9 PDFs and subcontractor invoice line items into the 1099 workpaper with the same workflow across both document sets.

Clean W-9s, classified payments, and a method-filtered GL register are what keep the 1099 close ahead of the deadline rather than chasing it.