Draft Response To Irs Notice Of Deficiency

Skill: Draft Response to IRS Notice of Deficiency

2. Failure modes the skill is correcting

• Responding to the notice with a blanket objection instead of a targeted challenge to each proposed adjustment, including the IRS’s stated computation and the taxpayer’s competing position.
• Omitting the statutory deadline to petition the Tax Court or otherwise allowing the response strategy to ignore the deficiency notice timeline.
• Failing to preserve procedural objections where the notice or record suggests a penalty-approval defect, notice defect, or other preassessment issue.
• Addressing the response to the wrong recipient or failing to copy the persons identified in the notice, which weakens the record of delivery and receipt.
• Treating partnership adjustments as purely narrative disputes when the issue turns on entity-level inputs, partner-level effects, timing, characterization, or allocation mechanics.
• Stating conclusions without anchoring them to controlling authority, leaving the letter unsupported as a legal response.
• Asking for review in the abstract without expressly requesting an Appeals conference and preserving that request before the petition deadline.

3. Legal frameworks / domain conventions that apply

• Notice of deficiency framework: A statutory notice of deficiency under the Internal Revenue Code starts the period for filing a petition in Tax Court. The response should identify the notice, state the challenged deficiency, and prominently state the filing deadline referenced by the notice or governing statute.
• Tax Court petition timing: The letter should recognize the applicable petition period under the Internal Revenue Code and any deadline mechanics that affect the taxpayer’s rights. The response is not a substitute for a petition unless the notice procedures allow otherwise.
• Partnership adjustment mechanics: For partnership-related items, analyze whether the proposed adjustment is partnership-level or partner-level, identify the relevant return position and underlying inputs, and test the IRS computation against the books, workpapers, and return reporting.
• Character, timing, and allocation rules: Where the adjustment depends on character, holding period, basis, allocation, or timing, apply the controlling statutory or regulatory test to the correct measurement period and factual predicate.
• Penalty and procedural defenses: If penalties are asserted or implied, evaluate whether the record reflects the required supervisory approval or other procedural step before assessment. Preserve those objections without overstating them.
• Appeals conference practice: A taxpayer who has not had a meaningful chance to present the dispute to IRS Appeals may request an Appeals conference in the response letter, subject to timing and procedural posture.
• Correspondence protocol: Address the letter to the recipients named in the notice or related instructions, and maintain copies suitable to document transmission and receipt.
• Authority-driven drafting: Every legal position should be tied to a controlling statute, regulation, or recognized doctrine; where a precise citation is unavailable from the materials, cite the authority category and the governing principle.

4. Analytical scaffolds

• Begin by identifying the notice, the asserted deficiency, and the deadline that governs the taxpayer’s next step.
• Enumerate each proposed adjustment in the notice before analyzing it; then address them one by one without collapsing distinct items into a single generalized objection.
• For each adjustment, state:
  • the IRS’s position;
  • the taxpayer’s position;
  • the source of the factual or computational dispute;
  • the legal authority supporting the taxpayer’s position;
  • the practical effect on the proposed deficiency.
• For partnership items, trace the IRS’s math back to the relevant return line, allocation input, or underlying assumption, and test whether the adjustment is being applied at the correct level.
• For character, timing, basis, or holding-period issues, identify the operative rule and apply it to the correct facts and measurement period.
• For any penalty adjustment, identify the procedural safeguard or approval requirement that may be implicated and preserve the objection if the record suggests noncompliance.
• When the notice involves more than one taxpayer, year, item, or recipient, keep the analysis separate and explicit for each.
• If the notice is ambiguous on a point, state the ambiguity, identify the competing readings, and request supporting documentation or clarification.
• End with an express request for an Appeals conference and, if appropriate, a request that collection and assessment action be held in abeyance consistent with procedure.

5. Vertical / structural / temporal relationships

• Track the relationship between partnership-level determinations and partner-level consequences so the letter reflects where the dispute is legally decided and where the tax effect lands.
• Preserve the sequence of events: notice issuance, petition deadline, Appeals request, and any pending documentation request or procedural objection.
• Where a penalty or adjustment depends on a prior approval, notice, or computational step, state the dependency and challenge the downstream effect if the upstream step is defective.
• If multiple recipients are identified, mirror the notice hierarchy in the correspondence so the record shows who was notified and when.

6. Output structure conventions

• Draft as a formal IRS response letter in professional correspondence format.
• Address the letter to the individuals or office identified in the notice, and include copies to any additional recipients the notice directs.
• Opening paragraph:
  • identify the notice of deficiency;
  • state the asserted deficiency and the relevant tax year or period;
  • state the applicable deadline;
  • state that the taxpayer disputes the proposed adjustments.
• Body:
  • organize by adjustment or issue, one section per proposed adjustment;
  • for each issue, identify the IRS’s position, the taxpayer’s response, the legal authority, and the computational correction or factual clarification;
  • preserve any procedural objections separately and clearly;
  • request any supporting information needed to evaluate the IRS’s position.
• Appeals request:
  • state expressly that the taxpayer requests an Appeals conference;
  • make the request in a way that preserves the taxpayer’s procedural rights before the deadline.
• Closing:
  • provide contact information for counsel or authorized representative;
  • request confirmation of receipt if appropriate;
  • keep the tone formal, concise, and litigation-aware.
• Use only authority that supports the proposition stated; do not present legal conclusions without naming the rule, statute, regulation, or doctrine that supports them.