Why notice questions go wrong
EA candidates and newer practitioners often treat every IRS letter as if it asked the same question:
- do I owe this amount right now?
That framing is too shallow. A better notice workflow starts with a narrower question:
- what type of mismatch caused this letter?
If you classify the mismatch first, the response path becomes much clearer.
Step 1: Separate the notice from the underlying tax issue
A notice is not the same as the final tax answer
A notice is the IRS telling the taxpayer that its system believes something is unresolved. That could reflect:
- a real omission
- a timing lag
- an incomplete information match
- a processing error inside the IRS
Exam framing
On the exam, the trap is paying attention to the scary amount but ignoring the category of notice. A `CP2000` is not the same kind of event as a `CP14`, and neither should be handled like an automatically correct refund check.
Step 2: Identify the four recurring notice patterns
Pattern 1: Basis or substantiation mismatch
This often appears when the IRS sees sales proceeds but does not have full basis support. The system may assume the gross proceeds are taxable gain.
Pattern 2: Payment-posting mismatch
This happens when the taxpayer did pay, but the notice cycle outran the payment-posting cycle. It is common with third-party processors and late batch updates.
Pattern 3: IRS-generated adjustment that benefits the taxpayer
A favorable notice can still be wrong. If the IRS releases a refund by ignoring a limitation or misreading a return, the taxpayer may face a later reversal.
Pattern 4: Misapplied account activity
Refunds and payments can sometimes land on the wrong account or take time to reverse after a correction request. A practitioner needs a paper trail, not just a phone call log.
Step 3: Use a notice-reconciliation checklist
When a taxpayer receives a notice, work in this order:
1. Verify the notice type
Read the notice number and the tax year before doing anything else.
2. Pull the taxpayer's own records
That may include:
- broker basis detail
- payment confirmations
- account transcripts
- certified-mail receipts
- prior IRS correspondence
3. Compare the IRS claim against the real mismatch
Ask:
- Is the IRS missing basis?
- Did the payment post after the letter was generated?
- Is the IRS proposing a change or asserting a final balance?
- Is the refund amount based on an incorrect IRS adjustment?
4. Respond through the channel the notice instructs
A notice response is usually stronger when it matches the notice workflow rather than when the taxpayer sends an unrelated amended return or duplicate payment without context.
Step 4: Worked examples
Example A: CP2000 with missing stock basis
Assume Monarch Ridge Design LLC sold securities with `48,000` of gross proceeds and `41,200` of basis. The return omitted the broker detail.
The IRS proposes additional tax as if the full `48,000` were gain.
The correct first move is not to file a blind amendment and not to pay the notice in full. The correct move is to respond with the basis support and explain the actual gain computation.
Example B: CP14 after an online payment
Assume Rafael paid `6,300` through an approved card processor on April 12. On April 26, the IRS issues a balance-due notice, but the online account shows `0`.
That fact pattern points to a posting or notice-timing mismatch. Paying again without reconciling the account creates avoidable risk.
Example C: IRS-generated refund appears too favorable
Assume Harborline Studio receives a notice-driven refund because the IRS system ignored a passive-loss limitation attachment.
The practitioner should not tell the client to spend the money just because the IRS initiated the refund. The better approach is to evaluate whether the refund rests on a substantive IRS error and respond accordingly.
Step 5: Know when escalation is procedural, not technical
Some issues are not solved by a better tax computation alone.
Delayed refunds
If the return and support are already on file and the issue is aging without movement, the next useful question may be whether the taxpayer qualifies for a taxpayer-advocate escalation, especially when the refund delay creates real hardship.
Misapplied checks or payments
If the taxpayer already returned the check or already paid the liability, the main risk becomes documentation failure. Dates, copies, mailing proof, and account tracking matter more than repeating the same explanation in a different tone.
Common distractors to reject
Distractor 1: "The IRS notice amount must be right because the IRS issued it"
Reject this because notice systems often operate from incomplete data.
Distractor 2: "Any notice should be solved by filing an amended return immediately"
Reject this because some notices ask for direct substantiation or explanation instead of a separate amended filing.
Distractor 3: "A favorable IRS refund is safe to accept if the IRS created it"
Reject this because the IRS can later reverse an erroneous adjustment.
Distractor 4: "If a payment was made, a later balance-due notice should simply be ignored"
Reject this because payment proof and account status still need to be preserved and monitored.
Exam takeaway
Do not start with the amount. Start with the mismatch category. When you know whether the notice reflects missing basis, a posting lag, a misapplied account entry, or an IRS-generated error, the right response path becomes much more defensible.