A CP2100 with 47 names: what happened, day by day

The company and the notice

A regional distributor with about 2,600 active vendors files roughly 900 Forms 1099-NEC and 1099-MISC a year. Accounts payable is three people; tax is one person who also handles sales tax. On Thursday, October 1, the tax manager opens a CP2100 dated September 28, listing 47 accounts: 41 name/TIN mismatches and 6 missing TINs, all from the 1099-NEC file submitted the previous January.

Day 0: log it and count it

The tax manager logs both dates, runs them through the deadline calculator, and gets: B-Notices in the mail by October 22; backup withholding on non-responders by November 9 (Columbus Day and the intervening weekends skipped). She puts both dates on the AP lead's calendar and hers, and exports the 47 rows from the notice into the solicitation log.

Days 1–3: the comparison

Publication 1281 says not to send a B-Notice to an account you've already fixed, so the AP lead compares each of the 47 against the current vendor master.

• 9 accounts already have a different, corrected W-9 on file, received after the January filing. These get no letter; the corrected pair is run through TIN matching to confirm it's a code 0, and the log notes "corrected before notice, date received."
• 3 accounts were the company's own keying errors: the W-9 on file has the right TIN, the 1099 didn't. No letter to the payee; a corrected 1099 is queued and the log says so.
• 2 accounts are foreign vendors who should never have received a 1099-NEC; they have W-8BEN-E forms on file. No B-Notice (you don't ask a foreign person for a W-9); the tax manager flags the classification error for correction.
• 33 accounts remain: 27 mismatches and 6 missing TINs that still need a letter.

Three days for 47 rows sounds slow. It isn't; each row is a lookup in the ERP, a check of the W-9 image, and a log entry, done between the day's normal payment runs.

Days 4–8: first or second notice?

A Second B-Notice is required when the same account appeared on a CP2100 within the previous three calendar years. The company keeps the last three notices in the tax folder, so the check is a name match against three PDFs. 4 of the 33 were on the fall notice two years ago. Those four get a Second B-Notice with no W-9 and the SSA-card / Letter 147C instructions; the other 29 get a First B-Notice with a blank W-9.

While reviewing, the AP lead notices that 19 of the 27 mismatches share a pattern: a business name on line 1 with an SSN-format number. Sole proprietors and single-member LLCs. She adds a sentence to the First B-Notice cover email pointing to the payee explainer and the line-1 rule, so the vendors don't send back the same wrong pair.

Days 9–12: the mailing

The letters are generated from the templates on company letterhead, with the account number, the name and TIN as filed, and the return-by date (30 business days from mailing). Envelopes are marked "Important Tax Information Enclosed." Where the company has an email on file, a copy goes by email the same day with a secure upload link; the mailed copy is the one that satisfies Pub 1281, the email is the one that gets answered. Everything goes out on Wednesday, October 14, eight business days before the deadline; the log records the mailing date per account. For the 6 missing-TIN accounts the letter also counts as the annual solicitation for the year, and the log says so.

Days 13–30: responses, and the withholding date

• By October 30, 17 corrected W-9s are back, 14 of them from the line-1 group; each new pair is run through TIN matching before the vendor record is updated, and two come back code 3 again (one vendor sent the LLC name a second time) and go back out with a phone call.
• One of the four Second B-Notice vendors sends a W-9. It's not a valid response to a second notice; the AP lead calls, explains Letter 147C, and the vendor calls the IRS.
• On November 9, the withholding deadline, 11 accounts have not responded. The AP lead sets the backup-withholding flag on each, so the next payment run withholds 24%, and notes the start date in the log. Two vendors call within a week of the short payment and send the W-9 the same day; the flag comes off for their next payment.
• By December 1, 30 of 33 are resolved. Three remain flagged; two are vendors the company no longer uses, one is still in the queue with the IRS for a 147C.

Afterward: the log, the file, and next spring

The tax manager files the notice, the comparison worksheet, the mailing list with dates, copies of the letters, the responses, and the withholding start and stop dates in the year's CP2100 folder, and notes the three still-open accounts in the tracking file for the second-notice rule. In January the corrected pairs go into the 1099 file and the two foreign vendors get 1042-S forms instead. Total effort: roughly 40 hours across two people, most of it in the comparison and the follow-up calls.

Eighteen months later a Notice 972CG proposes penalties on 12 returns from that filing: the 6 missing TINs and 6 mismatches that were still uncorrected at filing. The response, sent within the 45 days, attaches the solicitation log showing initial solicitation at onboarding, the B-Notice mailing dates, and the December sweep for the missing-TIN accounts. The waiver is granted for 11; one account with no initial solicitation on record (set up from an invoice in a hurry) is paid at $340, doubled under 6722.

What they'd do differently

• Verify at onboarding. 19 of the 27 mismatches would have been caught by matching the pair when the vendor was created, with the vendor still on the phone.
• Force the line-1 question. Asking "is this your SSN or the business's EIN?" on the W-9 request would have prevented most of the rest.
• Keep the three-year notice file in the log, not in PDFs. The second-notice check took a day it didn't need to.
• Never set up a vendor from an invoice. The one penalty that stuck came from the one account with no solicitation record.
• Email plus mail. Pub 1281 requires the mailing; the email is what produced 14 of the first 17 responses.