The Computer That Sent My Client a $15,000 Bill for a Mistake Nobody Made

cp2000-audit

A computer in Kansas City decided my client owed $15,000. It never asked why. It just compared two numbers, found a mismatch, and mailed a letter.

Nobody broke any law in this story. The retailer did nothing wrong. The tax preparer did nothing wrong. My client did nothing wrong either. Yet the IRS still demanded payment on income that should never have counted as taxable. It took real, undeniable evidence, laid out the right way, to undo a mistake the agency’s own software created.

This is the story of how IRS computer matching works, why doing everything correctly on paper can still land you a scary letter, and why one call for help beats months of confusion. If you run a business, collect a legal settlement, or ever receive a 1099 you did not expect, this applies to you.

The Machine That Never Sees the Whole Picture

The IRS runs a system called the Automated Underreporter Program, often shortened to AUR. Every W-2, every 1099, and every 1098 that a bank, employer, or business sends out also lands in an IRS database. When you file your return, the system compares your numbers against those third-party filings.

The AUR system exists mostly for one reason: resources. The IRS does not have the staff to manually read every return filed each year. Automated matching lets a much smaller team focus only on the returns that show a mismatch, instead of reviewing millions of filings by hand.

That trade-off makes sense from a budget standpoint. It also means correct returns get flagged from time to time, and the agency knows it. My client’s case was not a rare glitch. It was the system doing exactly what it was built to do, catching a mismatch first and sorting out the nuance later, if anyone bothers to push back.

The IRS itself calls this a proposal, not a bill. A CP2000 simply flags a discrepancy between what you reported and what a third party told the agency you earned. That distinction matters, because a proposal starts a conversation instead of ending one.

Here is the part most people miss. The computer does not know your story. It cannot tell a genuine unreported paycheck from a reimbursement check that was never taxable in the first place. The system is programmed to detect two numbers that do not match and generate an automatic letter and hit print and send. From the IRS’ perspective, the system did what it was meant to do. The program didn’t care either. It never loses sleep over the difference.

A Roof, a Retailer, and a Check With No Instructions

A client of mine needed a new roof on a home she already owned. She hired one of the large national home improvement retailers, the kind of big box store you would recognize instantly. That was a smart move on her part. Companies that size are not going anywhere, and paying a little more for a major job like a roof, through a name you can actually hold accountable, is often worth it.

The retailer subcontracted the installation to a third-party crew, which is standard practice in that industry. The install did not go well. Water got in, materials warped, and repairs became necessary before the damage spread any further.

She hired a lawyer, and the case settled. The retailer agreed to pay her enough to fix the roof and make her whole again. This was not a windfall. It was a reimbursement for damage a subcontractor’s poor work caused.

Here is where things got complicated. The retailer issued a Form 1099 for the settlement, standard practice for many companies closing out a claim. Settlements that simply return you to where you started are often not taxable at all. Tax professionals call this a return of capital. The IRS has ruled on this exact type of construction defect payment before. It treats these payments as a reduction to the property’s basis, not as taxable income.

Her preparer understood the law and made a reasonable call, leaving the settlement off her return rather than reporting income that was never really income. I want to be clear about this part. The preparer was not wrong. The return simply needed one more piece: a short explanatory statement attached to the filing, spelling out why the 1099 did not belong on the taxable income lines. Nobody attached one. That small gap is where this story turns.

Correct on Paper, Flagged by a Computer Anyway

Without that explanation attached, the IRS computer saw only one thing. The retailer reported a payment. My client’s return did not show it. The system flagged the mismatch and generated a CP2000. A $15,000 tax bill appeared in her mailbox.

Here is a small silver lining for anyone keeping score. The preparer was right about the tax law. My client was right to expect no tax on money that simply made her whole again. The problem was never the law itself. The problem was a system built to catch cheaters. It cannot tell fraud from a missing footnote.

I run this kind of documentation review with clients before they file, not after a letter shows up. It takes minutes and it prevents exactly this kind of headache. A missing sentence can quietly turn into months of stress over a debt that does not legally exist.

When “I’ll Handle It” Turns Into 90 Days

My client tried to resolve this herself before she called me, and I understand the instinct completely. Nobody wants to pay a professional to explain something that feels obvious.

She wrote back to the IRS explaining the settlement. Her letter used casual language instead of the specific terms an examiner looks for. She also left out documents an examiner needs to close a case. That meant the settlement agreement, repair receipts, and a clear basis calculation.

The IRS did not buy it, and the case moved forward. Eventually she received a Notice of Deficiency, commonly called a 90-day letter. Once that letter arrives, the clock becomes unforgiving. Under Section 6213 of the Internal Revenue Code, a taxpayer gets exactly 90 days to petition the United States Tax Court. Nobody can extend that deadline, not even the IRS.

Here is what most people do not realize about that window. Had she let it pass without filing a petition, the IRS would have assessed the full $15,000 automatically. At that point, her only realistic option would have been paying the disputed amount first, then suing for a refund in federal court, a slower and far more expensive road. Filing the petition did not win her case on its own. It simply kept the door open long enough for the real argument to happen.

I have written before about why self-representation in front of the IRS is a bad idea. This case is exactly the kind of situation I meant.

The Difference Between Being Right and Sounding Right

By the time she reached out to me, the stakes had grown a lot. She had already spent weeks trying to fix this alone, and the IRS had already treated her explanation as unconvincing.

My job at that point was not to invent a new argument. The underlying facts had not changed at all. What changed was how I presented the case. I organized the settlement agreement, basis documentation, and legal citations into a package an examiner could not easily argue with.

The Tax Court petition was never what changed the IRS’s mind. It only bought us time. What actually moved the needle was the evidence itself, laid out clearly enough that disagreeing with it stopped being a reasonable option. The IRS conceded once I presented the case that way, and my client walked away owing nothing on the disputed amount.

She still spent significant money securing proper representation to get there, money that would never have been necessary if the original return had included one short explanatory statement.

That is the quietly frustrating part of this work. A five-minute fix on the front end can prevent a costly fight years later.

Why a 2023 Return Showed Up in 2026

One detail surprises almost everyone who hears this story. My client filed the return for the 2023 tax year, yet the notice did not arrive until 2026. The IRS generally has three years from the filing date to assess additional tax. This timing was unusual only in how slowly it played out.

Matching programs can take time. They flag a discrepancy, generate a notice, and work through correspondence before anything escalates further. I covered how these statute of limitations clocks actually work in a previous article on the IRS audit clock. This case is a perfect example of why old returns are never quite as finished as they feel.

If you assume a filed return is fully behind you the moment you hit submit, you are giving yourself false comfort. Keep your documentation for years, not months. Treat every settlement or unusual payment like it might resurface later.

What Every Business Owner Should Take From This

You do not need a construction defect settlement to learn something here. Anyone who receives an unexpected 1099, sells an asset, settles a dispute, or collects insurance proceeds runs into the same risk.

The lesson is simple, and it is one I give every client who hands me their documents. Report every 1099 you receive, every single one, even the ones you are confident are not taxable. Then offset that number with a clear, documented adjustment and a short explanation of why it does not belong in your taxable income.

This is why seasoned preparers ask for every 1099 and every scrap of supporting documentation before they ever start your return. Reporting the number, even to immediately zero it back out, keeps your return in sync with what the IRS already has on file. It removes the mismatch before it ever has a chance to exist.

Leaving a 1099 off your return entirely, even for a completely valid reason, still creates a gap the AUR system can catch. Reporting it and explaining it closes that gap for good.

Here is a soundbite worth remembering.

Being right about the tax law does not protect you from a computer that only checks whether two numbers match.

Maybe you have received a notice that made no sense. Maybe you are sitting on a settlement, insurance payout, or unusual 1099 right now. Either way, a short conversation early on saves a much longer one later.

Pulling It All Together

My client did nothing wrong, her preparer did nothing wrong, and the retailer did nothing wrong. Still, one missing sentence on a tax return turned into a Notice of Deficiency and a Tax Court petition. It also cost her significant money to fix a debt that was never real to begin with.

The IRS’s matching system is not going away. It is only getting faster at flagging mismatches like this one. The best protection is not avoiding every discrepancy, because some are simply unavoidable. It is making sure your return tells the whole story the first time, matching numbers included, so a computer in Kansas City never has to guess.

That is why I treat every 1099 as a documentation project, not an afterthought. It is exactly the kind of gap I built my practice to catch, before it becomes someone’s Tuesday afternoon crisis.

Welcome to the New Age of Accounting. Let’s begin.

P.S. If you found this article helpful, you’ll love my new book S-Corp Mastery: How Smart Business Owners Maximize Tax Savings & Build a Lasting Legacy. It’s now live and available in a sleek, easy-to-read PDF version. Grab your copy here