When the IRS reads your next year's filing

The rule

Two ideas are stacked here. The first is the second responsible-manner question, whether the filer took steps to prevent recurrence, which the examiner answers from your next filing if you do not (IRM 4.19.25.8(7)). The second is the compliance-history rule: history "must be considered whether or not the filer specifically requests abatement on this basis," it "can benefit a filer who shows they acted in a responsible manner" but has no external event, and it cuts the other way when it shows a pattern (IRM 20.1.7.12.1(11) to (12)). There is a floor: if you show responsible conduct plus an event beyond your control, "a penalty in a prior year must not be used as cause not to abate" (IRM 20.1.7.12.1(13)).

What the examiner sees

Before deciding a TIN-failure waiver the examiner "Research[es] IDRS to determine Notice 972-CG history and related actions taken on the account" (IRM 4.19.25.8.3(7)). The Payer Master File shows, year by year, how many returns you filed, how many had missing, unissued or mismatched TINs, and which years you received a CP2100 (IRM 4.19.26.7.2.8 describes the same screen from the backup withholding side). Prior 972CGs, whether they were waived, and whether a de minimis exception applied (those "are not considered to have been penalized") are all visible. Assume the examiner knows your history better than the person writing your response does.

The declining-rate test

The handbook's instruction is to check "whether the error rate decreased year over year" (IRM 20.1.7.12.1(12) to (13)). Rate, not count: a payer that doubled its vendor base and held the number of bad TINs flat has improved. The comparison the examiner can make from the file is bad TINs divided by returns filed, so make that the comparison you present. Where the rate did not fall, the same paragraph directs the examiner to "consider the intentional disregard provisions," which is how the tiered penalty becomes the uncapped one; the intentional disregard guide covers that path.

How to document the improvement

1. The change, dated. The day TIN matching was adopted, the day vendor onboarding started requiring a completed W-9 before setup, the day the filing calendar moved the internal deadline. Contracts, system logs or policy memos with dates.
2. The population it applied to. New vendors from that date; existing vendors cleaned up by a stated date, with the count.
3. The next filing's numbers. Returns filed, failures by type, and the rate, from your own filing acknowledgment and the following CP2100 if one arrived. If the next season has not happened yet, the pre-filing match results (how many pairs were checked, how many failed, how many were fixed before filing).
4. Annual solicitations by mail or phone, logged. The prior-year weakness most often found on a second look is an electronic annual solicitation, which is denied on sight (IRM 4.19.25.8.3(5)). Show the method changed.
5. B-Notices on time. For every CP2100 line in between, the mailing date within 15 business days.

What the statement should say

Lead with the fraction and the change: "For returns due in 2025 the notice listed 212 TIN failures on 6,140 returns, 3.5%. Since March 2025 every new payee is matched against IRS records before payment and existing payees were re-matched in a project completed June 30, 2025. For returns due in 2026, 41 of 7,020 returns, 0.6%, were listed." Then the responsible-manner facts for the current failures (reacted timely, with dates), the factor from the list, and the solicitation schedule. The examiner's-checklist template has a section for exactly this.

What not to say: the same paragraph as last year. If the prior response blamed a software conversion, and this year's does too, the examiner has been told what to conclude.

Questions people ask