Compare Proposed Settlement Against Original Assessment

Skill: Compare Proposed Settlement Against Original Assessment

2. Failure modes the skill is correcting

• Describing the settlement in narrative form without reconciling each issue to the original assessment, the taxpayer’s submissions, and the proposed resolution, which hides mismatches and omitted items.
• Accepting stated reductions, percentages, or penalty computations without independently verifying the arithmetic against the source figures.
• Treating a broad waiver, release, or finality clause as boilerplate without testing whether its scope exceeds the specific years and issues actually resolved.
• Missing how the settlement instrument chosen changes later procedural rights, including refund posture and the ability to contest the settled amount.
• Overlooking a forward-looking methodology commitment or similar undertaking that could constrain positions in related or future tax proceedings.
• Failing to separate a negotiated concession from an automatic mechanical consequence, such as interest recomputation on a lower principal base.
• Ending each issue with description only, rather than tying it to size, related source provisions, and client consequence.
• Stating a tax conclusion without naming the governing authority, regulation, or procedural rule that supports it.

3. Legal frameworks / domain conventions that apply

• Assessment and settlement reconciliation: Compare the original notice, examination position, and proposed Appeals resolution issue by issue, using the dollar amounts and issue descriptions as the organizing frame. Where a stated percentage or penalty tier appears, verify the implied amount against the stated base and flag any inconsistency.
• Penalty and interest mechanics: Penalties are ordinarily computed from the relevant underpayment or adjustment base, and interest mechanically follows the reduced principal once the tax amount changes. Distinguish negotiated reductions from arithmetic effects so the memo does not misstate what was bargained for.
• Scope of waiver and release: A waiver or release should be read against the specific controversies resolved. Under federal tax procedure, overbroad language can reach beyond the intended matters if not narrowed to the assessed years and issues actually at stake. Cite the governing settlement document language and the applicable procedural rule or form structure reflected in the source set.
• Settlement instrument consequences: A waiver of restrictions on assessment is not the same as a closing agreement. The former generally permits assessment consistent with the resolved terms but does not necessarily foreclose later refund procedures in the same way a closing agreement does. Identify the instrument used and explain the practical refund and finality consequences under the controlling tax procedure authority or document form.
• Cross-border or methodology coordination: If the settlement embeds a transfer-pricing method, allocation approach, or similar methodology commitment, test that commitment against any related foreign, treaty, or administrative proceedings in the source set. Flag potential inconsistency with positions the taxpayer is defending elsewhere and, if needed, suggest limiting language.
• Authorities: Every legal point should be anchored in the applicable statute, regulation, revenue procedure, form instruction, treaty article, or other authority named in the source materials or, if not named there, the generally recognized authority for the issue.

4. Analytical scaffolds

• Start by enumerating the issues, years, or adjustment buckets actually in scope; if there is only one, say so expressly and explain why.
• Build a reconciliation table with one row per issue: original assessment; taxpayer position; proposed settlement; delta; and a short note on what changed.
• For each row, verify the arithmetic from the source figures and compare the stated settlement mechanics to the implied amount.
• For each issue, analyze scope, waiver, and finality: what is being resolved, what is not, and whether the language is broader than the controversy.
• If the settlement includes a methodology or conduct commitment, test it against any related proceeding, filing position, or future-year exposure identified in the materials.
• For interest or penalty items, distinguish negotiated reductions from recalculated consequences of a lower base.
• Close each issue with: size of impact, source interaction, and client consequence.
• End with a clear recommendation on whether to accept as-is, seek narrowing edits, or continue negotiating.

5. Vertical / structural / temporal relationships (only if applicable)

• Track relationships among original assessment, protest/submission, Appeals proposal, and any revised draft terms; later text may supersede earlier positions, but only for the issues it actually covers.
• Distinguish current-year resolution from carryforward or future-year effects, especially where the settlement language reaches beyond the settled period.
• Identify whether a term is retrospective (tax, penalty, interest on the assessed period) or prospective (future methodology, reporting, or conduct covenant), because the risk profile differs.
• Where a provision references other proceedings or jurisdictions, map the interaction before recommending acceptance.

6. Output structure conventions

• Write a settlement reconciliation and issues memorandum organized by issue, not by document chronology.
• Open with a concise reconciliation table showing original assessment, proposed settlement, and net change by issue, plus an aggregate summary.
• Define a simple ordinal severity scale at the outset and apply it uniformly to every issue entry.
• For each issue, use the same internal sequence: issue summary; arithmetic verification; governing authority; scope/finality analysis; downstream consequence; severity; recommendation.
• State the specific source authority or procedural rule for each legal proposition; do not give naked conclusions.
• End with a separate Recommended Actions block that names the action, the responsible role, and the timing anchor tied to the engagement or filing deadline.
• Use conventional memorandum headings and keep the prose tight enough for partner review, but include enough detail to support sign-off decisions.