For most of the last decade, 1099-K filing obligations were a background concern for vertical SaaS platforms — the $20,000 threshold combined with the 200-transaction requirement meant that only sub-merchants with substantial payment volume triggered a reporting obligation. The American Rescue Plan Act changed that calculus materially. The threshold reduction to $600 — phased in through IRS implementation notices over 2023 and 2024 — means that any sub-merchant who receives more than $600 in payments through your platform in a calendar year generates a 1099-K obligation.
For a healthcare staffing platform with 300 contractor sub-merchants, or a property management platform with 150 property owner sub-merchants, that's a large portion of the portfolio triggering a year-end filing obligation. The operational machinery to handle it — TIN collection at onboarding, threshold tracking throughout the year, IRS FIRE system e-filing in January, and B-Notice response procedures — is not trivial to build, and the penalties for non-compliance are not trivial to absorb.
Who Is the Payer of Record
The 1099-K obligation attaches to the entity that settles funds to the payee — the payer of record. In a standard payment facilitation arrangement, the PayFac (or the platform operating under a PayFac-as-a-Service structure) settles directly to sub-merchants. That makes the platform — not the card network, not the acquiring bank — the payer of record for 1099-K purposes.
This distinction is operationally important because it determines who collects TINs (Taxpayer Identification Numbers), who files with the IRS, and who is exposed to penalties for missing or incorrect filings. Under IRS Publication 1220, which governs information return filing, the payer of record must collect a valid TIN from each payee before payments exceed the threshold, file the 1099-K via the IRS FIRE (Filing Information Returns Electronically) system by January 31 for paper and by March 31 for electronic, and send a payee copy by January 31.
Platforms that route funds through a payment gateway without holding a PayFac arrangement — where the settlement relationship is directly between the acquiring bank and each merchant — are not the payer of record. The acquiring bank holds that obligation. This is one of the less-discussed reasons that taking on the PayFac relationship changes the platform's operational profile: you gain the interchange economics and sub-merchant control, and you also take on the information reporting obligation.
TIN Collection and W-9 at Onboarding
The practical starting point for 1099-K compliance is TIN collection during sub-merchant onboarding. For a business entity (LLC, S-corp, C-corp), the TIN is typically the Employer Identification Number (EIN). For a sole proprietor or individual, it's typically the Social Security Number (SSN), though some sole proprietors with an EIN can use that instead.
Platforms should collect a W-9 (or the equivalent data elements) during the sub-merchant onboarding flow, before the merchant processes their first payment. Collecting TIN after the fact — when year-end approaches and you're trying to prepare 1099-K forms — is operationally painful and often incomplete. Sub-merchants who have left the platform, changed their bank account, or been deactivated are difficult to reach for W-9 collection in December.
The TIN should be validated at collection time through IRS TIN Matching — a free IRS service that allows bulk validation of name/TIN combinations before submitting information returns. A TIN mismatch at filing generates a CP2100 or B-Notice from the IRS, which requires the platform to send a backup withholding notice to the sub-merchant and, if the TIN isn't corrected within 30 days, to begin withholding 24% of subsequent payments. Backup withholding creates operational complexity that TIN matching at onboarding largely prevents.
Threshold Tracking Through the Year
With a $600 threshold, platforms need to track cumulative settled amounts per sub-merchant on a calendar-year basis. The tracking needs to account for refunds — IRS guidance indicates that 1099-K amounts should reflect gross payments, not net of refunds, but the question of how partial-year refunds affect the threshold calculation requires careful implementation.
The tracking system should flag sub-merchants approaching the threshold before year-end — not as a courtesy to the sub-merchant, but as an operational check that the W-9 on file is current and valid before the obligation triggers. A sub-merchant who crosses $600 in November without a valid TIN on file is a compliance problem, not an accounting problem. The fix at that point (collecting a W-9, validating the TIN, re-running TIN Matching) can still be completed before the February filing deadline, but it adds operational overhead that threshold alerts prevent.
For platforms with seasonal transaction patterns — a landscaping service platform where most GMV runs April through October — the threshold may be crossed in July for a large share of the sub-merchant portfolio. Year-end scrambling isn't necessary if the tracking system is running throughout the year and the TIN collection workflow is embedded in the onboarding flow from day one.
The IRS FIRE System: What Filing Actually Requires
IRS FIRE (Filing Information Returns Electronically) is the submission portal for electronic 1099-K filing. It accepts files in the IRS Publication 1220 format — a fixed-width ASCII record layout that has been largely unchanged for years. The format includes a transmitter record (T-record), a payer record (A-record), payee records (B-records, one per sub-merchant), and end-of-payer and end-of-transmission records (C- and F-records).
Generating a valid FIRE submission file requires assembling these records correctly, including proper TIN formatting (no dashes), correct payment amount fields (amounts in cents, no decimal point), and accurate record counts in the C-record. A format error in the submission file causes the IRS FIRE portal to reject the entire submission — not just the affected records. Testing submissions in the IRS FIRE test environment before the live filing deadline is strongly recommended for any platform filing for the first time.
The filing deadline for electronic submissions is March 31 of the year following the calendar year being reported. Penalties for late or missing 1099-K filings under IRC Section 6721 start at $60 per form for filings up to 30 days late and scale to $310 per form for filings not submitted by August 1, with a maximum penalty cap for small businesses. At 300 sub-merchants exceeding the threshold, a missed filing is a meaningful penalty exposure — and the IRS matches 1099-K data against income reported on payee tax returns, so errors or omissions generate downstream inquiries.
State-Level Filing Requirements
Federal 1099-K filing is the floor, not the ceiling. Many states have separate 1099-K filing requirements with their own thresholds, formats, and deadlines. Some states have adopted the federal threshold; others retained the prior $20,000/200-transaction threshold; a few have set thresholds lower than federal. States that participate in the Combined Federal/State Filing (CF/SF) program receive their 1099-K data automatically from the IRS FIRE submission, which reduces the duplicate filing burden for multi-state platforms. However, states not participating in CF/SF — including some with significant vertical SaaS platform populations — require separate direct filings.
For platforms with sub-merchants operating across multiple states, the state filing mapping needs to be part of the compliance infrastructure, not a last-minute research project in January. The mapping between sub-merchant state of residence (or state where business income is earned) and applicable state 1099-K requirements is a non-trivial data problem for platforms with geographic diversity in their sub-merchant portfolio.
Where Automation Pays for Itself
This is not to say that 1099-K compliance is unmanageable. For platforms with well-structured onboarding data — W-9 collected at enrollment, TIN validated via IRS matching, cumulative payment tracking running throughout the year — the January filing is a largely mechanical exercise: generate the FIRE format file from the year's settled payment data, submit to FIRE, and distribute payee copies.
Where the automation investment pays for itself is in the failure cases: W-9 expiry reminders, TIN mismatch remediation, B-Notice response workflows, and backup withholding implementation when a sub-merchant doesn't respond. These edge cases are uncommon on a per-sub-merchant basis but aggregate into significant operational load at portfolio scale. A platform with 500 sub-merchants where 3% require TIN remediation is managing 15 active compliance cases simultaneously in December — during the same period when year-end close is consuming the finance team's attention elsewhere.
The infrastructure investment in automated threshold tracking, TIN collection workflows, and FIRE-format generation is recoverable within the first filing cycle for any platform with more than 50-100 sub-merchants crossing the $600 threshold annually. Building it after the first January filing cycle — when the scope of the manual work becomes clear — is the more common path, and it's an avoidable one.
