The IRS March 2026 Rule, Part 3: A Step-by-Step Compliance Plan You Can Finish in an Afternoon

A 2026 freelancer-and-W-2 compliance afternoon runs about four hours and reconciles every pay record, platform export, invoice, and 1099 against what the IRS will receive through the Information Returns Program database. Per Publication 583, IRS recordkeeping guidance, and the IRS Self-Employed Tax Center, the cleanest defense against a 2027 CP2000 notice is the same six-step pass any sole-proprietor audit defense uses: gather, sort, check, regenerate, cross-check, file. The plan is the same whether the reader has a single W-2 with one side platform or, like Carlos Santiago, a mixed picture covering 26 biweekly Saguaro Marketing paystubs, four freelance platforms, and direct invoiced clients.

Part 1 of this series walked through what changed and why. Part 2 walked through what counts as a documentation-grade paystub. Part 3 is the action plan. The same Carlos numbers thread through every step: $1,846.15 biweekly × 26 = $48,000 W-2 from Saguaro; $9,390 platform gross ($3,400 Fiverr + $2,650 Upwork + $1,920 Stripe + $1,420 Etsy) plus $3,600 direct invoiced = $12,990 Schedule C line 1; $1,140 expenses → $11,850 net Schedule C profit; $59,850 total 2026 income; AZ resident at the 2.5% flat state rate. By the bottom of the page Carlos has every gap closed, every record cross-checked against the two 1099-Ks he'll receive, and a maintainable folder structure that carries him into 2027 without rework.

The six steps with time-boxes:

• Step 1 — Gather (30 minutes): every paystub, bank statement, invoice, 1099, screenshot for the last 12 months into one folder
• Step 2 — Sort by source (30 minutes): W-2 stack, four platform stacks, direct-client stack, bank-statement stack
• Step 3 — Compliance check (60 minutes): run every paystub through the Part 2 quality checklist; every freelance receipt through the platform-export reconciliation
• Step 4 — Regenerate broken paystubs (60 minutes): replace missing or non-compliant stubs from real payroll data (never from imagination)
• Step 5 — Cross-check against IRS expectations (30 minutes): the IRS Information Returns Program will receive the W-2 and the two 1099-Ks; reconcile Carlos's records against that subset
• Step 6 — Build a sustainable filing system (30 minutes): folder structure for 2027 and beyond, with retention windows tagged

The strongest 2026 compliance file usually includes:

• Every paystub for every W-2 period in the year (Carlos: 26 biweekly stubs from Saguaro)
• 12 months of business bank statements (or personal-account statements if no separate business account exists)
• Year-end export from every payment platform that handled freelance income
• An invoice register for every direct client paid outside a platform
• Every 1099 form received (W-2, 1099-NEC, 1099-K, 1099-MISC, 1099-INT)
• A short reconciliation memo bridging total reported income to the IRS Information Returns Program subset
• A maintainable folder structure with retention windows tagged (3yr, 7yr, indefinite)

Carlos is in Phoenix and runs the plan on a Saturday afternoon. The total time clock starts at 1:00 PM and lands at roughly 5:00 PM with everything filed.

#The Six-Step Plan With Carlos's Real Numbers

Each step below has a time-box, the deliverable, the documents involved, and Carlos's specific table for that step. By Step 6 every document is filed and every dollar is reconciled.

#Step 1 — Gather Every Pay Record (30 min)

The first 30 minutes are not analysis. They're collection. Pull every paystub, bank statement, invoice, screenshot, 1099, and payment-app summary from the last 12 months into one folder named "2026 Compliance — Carlos Santiago." Don't worry yet about whether the records are complete or compliant — that's Step 3. The goal at 1:30 PM is to have everything in one place.

Carlos's gather table for 2026:

If anything's missing at this point, note it on a sticky note and proceed to Step 2. The missing-record fix happens in Step 4.

#Step 2 — Sort by Source (30 min)

The next 30 minutes are filing. Each income source gets its own subfolder. The reason this matters: under the new rule, the IRS will receive separate information returns from each of Carlos's income sources (one W-2 from Saguaro, two 1099-Ks from Fiverr and Upwork, possibly one or two 1099-NECs from direct clients). His records need to mirror that structure so the cross-check in Step 5 is fast.

Carlos's folder structure at the end of Step 2:

This step looks tedious but pays off in every subsequent step. The IRS will sort the same way through the IRP database. Carlos's folders should match.

#Step 3 — Compliance Check Against the Quality Bar (60 min)

The full hour from 2:30 PM to 3:30 PM is the quality-check pass. Carlos runs the Part 2 paystub checklist (all eight high-weight fields plus the six quality dimensions) against every record in each subfolder. The W-2 stack and the freelance stacks each have their own check pattern.

W-2 paystub check (Carlos's 26 Saguaro stubs):

Out of 26 stubs, 25 pass cleanly and one (period 14, the July 5 pay date) is missing entirely. Carlos noted the gap during Step 1; Step 4 closes it from real payroll data.

Freelance compliance check (per-platform reconciliation):

Schedule C expense check:

At the end of Step 3, Carlos has one failure (the missing period 14 stub) and one note (Stripe and Etsy don't issue 1099-Ks because both fall below $2,500, but both belong on Schedule C line 1).

#Step 4 — Regenerate Broken Records From Real Payroll Data (60 min)

Step 4 is the most-misunderstood step in the plan. Regeneration is for records that document wages an employer actually paid where the original copy is unavailable. It is not for inventing wages an employer never paid (the cardinal sin from Part 2's Pitfalls list). The legitimate use case has three preconditions: real wages were paid by a real employer, the underlying data exists (bank deposits, W-2, prior YTD), and the original stub is genuinely unavailable.

Carlos's period 14 regeneration:

Carlos regenerates this stub from real payroll data using the MyStubs paystub generator. Every figure is anchored to a verifiable source: the bank deposit confirms the net, the prior period 13 YTD figures plus one period of standard withholding produce the period 14 YTD, and the W-2 issued in January 2027 will tie back to the 26-stub total. The stub Carlos creates documents wages Saguaro actually paid him on July 10, 2026. It is documentation, not fabrication.

The freelance side has no equivalent "regenerate" step — freelance income doesn't generate paystubs (covered in Part 2). If Carlos's Fiverr export is missing entirely, the right move is to log into Fiverr and re-download it, or contact Fiverr support for the year-end summary. Inventing freelance receipts would be the same cardinal sin in a different form.

#Step 5 — Cross-Check Against What the IRS Will Receive (30 min)

The IRS will receive five information returns against Carlos's SSN for tax year 2026: one W-2 from Saguaro, one 1099-K from Fiverr, one 1099-K from Upwork, and potentially up to two 1099-NECs from direct clients who paid him $600 or more individually. Step 5 reconciles Carlos's reported income against that subset.

Carlos's cross-check table:

The reconciliation memo Carlos writes (and files with his records) reads:

This memo is the file Carlos pulls out if a CP2000 ever arrives in 2028 questioning the gap. It explains the math in writing and ties every dollar to its source document.

#Step 6 — Build the Sustainable Filing System (30 min)

The last 30 minutes are forward-looking. Carlos sets up the 2027 version of the same folder structure and tags each folder with its retention window per IRS Pub 583.

Going forward, Carlos populates each subfolder on a rolling basis (every payday for the W-2 stack, every Friday for platform exports, every invoice issued for direct clients). The next December compliance afternoon takes 60 minutes instead of four hours because the filing already exists.

#What Carlos Has, What's Missing, What to Do

The cross-reference table below summarizes every income source Carlos has, the documents that should exist for each, what he actually had at the start of Step 1, and the corrective action by the end of Step 6.

#How Long Each Document Lives

Different documents have different retention requirements under IRS Pub 583 and the IRS recordkeeping guidance. The table below maps each document type to its required retention window.

Carlos's 2026 tax return and supporting records will live in his filing system through April 15, 2034 at minimum (7 years from the April 15, 2027 filing date). His Schedule C expense records (Adobe CC, supplies) follow the same 7-year window because they support the deductions on line 28.

#Eight Mistakes That Sink the Compliance Afternoon

The eight mistakes below are the most common reasons a compliance afternoon ends with an incomplete file rather than a defensible one.

• Incomplete gather (missing one platform's records). A reader who has paystubs, Fiverr, Upwork, and Etsy but forgets to download the Stripe annual export will be short $1,920 of receipts that belong on Schedule C line 1. The fix in Step 1 is the platform-by-platform checklist that names every source.
• Assuming missing means non-existent. A missing paystub doesn't mean the wages weren't earned; it means the document copy is unavailable. The right move is to request a replacement from the payroll system (Saguaro's payroll provider will issue replacement PDFs), not to skip the period. Carlos's missing period 14 stub gets regenerated from real payroll data in Step 4.
• No cross-check against the IRS Information Returns Program subset. A reader who reports $12,990 of Schedule C line 1 income without knowing that the IRS will receive 1099-Ks totaling $6,050 from Fiverr and Upwork has no way to defend the gap if a CP2000 arrives. The reconciliation memo in Step 5 is what prevents the surprise.
• Regenerating paystubs to inflate income (fabrication = fraud). This is the cardinal sin called out in Part 2 and reinforced here. Regeneration is for real wages an employer actually paid where the original document is unavailable. Inventing wages an employer never paid crosses into IRC §6701 civil penalties and possible §7206 criminal liability.
• No filing system going forward. A four-hour compliance afternoon every January is unnecessary if the filing system is built once and maintained on a rolling basis. Step 6 is the highest-leverage 30 minutes in the entire plan.
• Missing the quarterly estimated payment requirement for Schedule C income. Carlos's $11,850 net Schedule C profit generates roughly $1,674 of self-employment tax plus federal income tax on the marginal dollars. Without quarterly Form 1040-ES estimates on the 1099 side, the April 2027 balance plus an underpayment penalty under IRC §6654 is the avoidable own-goal. The IRS Form 1040-ES page frames the calculation. The IRS Tax Withholding Estimator handles the modeling.
• Treating bonus paystubs as separate from the regular stack. Carlos doesn't have any 2026 bonuses, but a freelancer who did get a $500 year-end bonus from Saguaro should make sure that period's stub shows the bonus on its own earnings line (not merged into regular pay) and the YTD continues correctly through the bonus.
• Ignoring AZ state filing. Carlos owes Arizona state tax on his combined $59,012.72 AGI minus the AZ standard deduction at the 2.5% flat rate, plus state-side Schedule C reporting. The Arizona Department of Revenue handles state filing through Form 140. AZ uses federal AGI as the starting point, so the federal reconciliation drives the state return.

Step 1 — Gather (30 min, 1:00-1:30 PM)

• All paystubs for the year downloaded into one folder
• All bank statements (personal + business) for 12 months downloaded
• Every payment platform's year-end export downloaded
• Every direct-client invoice PDF saved
• Every 1099 form received saved (W-2, 1099-NEC, 1099-K)
• Every business expense receipt saved (Adobe CC, supplies, equipment)
• Missing-document sticky notes attached

Step 2 — Sort by source (30 min, 1:30-2:00 PM)

• Subfolder for the W-2 employer
• Subfolder per payment platform
• Subfolder for direct clients
• Subfolder for bank statements
• Subfolder for expenses
• Subfolder for the reconciliation memo
• Subfolder for the tax return itself (filled later)

Step 3 — Compliance check (60 min, 2:00-3:00 PM)

• Every paystub run through the Part 2 quality checklist
• Every platform export reconciled to the bank-deposit log
• Schedule C expense receipts totaled
• Pass/fail flag on every record
• Missing-document list confirmed for Step 4

Step 4 — Regenerate broken records (60 min, 3:00-4:00 PM)

• Replacement paystubs requested from the payroll system (first preference)
• Regenerate from real payroll data only when the replacement request fails
• Every regenerated stub matches the verified bank deposit
• Every YTD figure continues correctly from the prior stub
• Every freelance export re-downloaded if missing (Fiverr, Upwork, Stripe, Etsy)

Step 5 — Cross-check vs IRS (30 min, 4:00-4:30 PM)

• IRS IRP database subset identified (W-2 + 1099-K stack)
• Reconciliation memo written
• Gap between reported income and IRS-visible income explained in writing
• Memo filed in the Reconciliation subfolder

Step 6 — Build sustainable filing system (30 min, 4:30-5:00 PM)

• 2027 folder structure created mirroring 2026
• Each subfolder tagged with retention window
• Permanent folder created for indefinite-retention documents
• Calendar reminder set for monthly platform-export downloads
• Calendar reminder set for quarterly 1040-ES estimated payments

Copy the structure below into Dropbox, Google Drive, or whatever cloud storage you use. Tag each subfolder with its retention window in the description field so retention is automatic.

The structure is the same every year. Only the year label and the platform list change as your income mix evolves.

#Official External Sources