Guides preparation of a tax due diligence issue memo for an acquisition where multi-year tax returns, foreign subsidiary filings, net operating loss schedules, transfer pricing, and employee benefit plan compliance must be systematically reviewed.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill identify-tax-issues-in-target-company-pre --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Identify Tax Issues In Target Company Pre?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-identify-tax-issues-in-target-company-pre)More formats (shields.io, HTML) on the badges page.
---
name: identify-tax-issues-in-target-company-pre
task_id: corporate-ma/identify-tax-issues-in-target-company-pre
description: Guides preparation of a tax due diligence issue memo for an acquisition where multi-year tax returns, foreign subsidiary filings, net operating loss schedules, transfer pricing, and employee benefit plan compliance must be systematically reviewed.
activates_for: [planner, solver, checker]
---
# Skill: Pre-Acquisition Tax Due Diligence Issue Identification
## 1. Subject-matter triage
- Treat the assignment as a pre-acquisition tax diligence review, not a return-preparation exercise.
- Start by mapping the document set by tax type, jurisdiction, and period so each filing stream is reviewed against the correct compliance regime.
- If the source set contains multiple entities, jurisdictions, or taxable periods, enumerate them first and analyze each one separately rather than relying on a single representative pass.
- Where the record is incomplete, distinguish between confirmed issues, probable exposure, and information gaps that require follow-up.
## 2. Failure modes the skill is correcting
- The review summarizes each year in isolation and misses trends, recurring adjustments, or changes in tax posture that indicate deferred liabilities or inconsistent positions.
- Foreign filing obligations are identified but not checked against controlled foreign corporation reporting, inclusion rules, earnings-and-profits tracking, and information-return compliance.
- Net operating losses are noted without assessing pre-existing limitations, post-transaction limitations, or practical utility after closing.
- Related-party transactions are listed without testing arm’s-length support, contemporaneous documentation, or consistency across return positions.
- State and local filings are reviewed as a checklist, but nexus, apportionment, and sales/use tax exposure are not tied back to operations or filing history.
- Employee benefit plan materials are mentioned without evaluating qualification risk, discrimination testing, contribution timing, or excise exposure.
- Findings are described without closing the loop to scale, cross-document interaction, and transaction consequence.
- Recommendations are omitted or stated abstractly, leaving the client without a clear diligence path.
## 3. Legal frameworks / domain conventions that apply
- Pre-acquisition tax diligence normally covers federal, state, and local income taxes; payroll and employment taxes; sales and use taxes; foreign reporting; transfer pricing; employee benefit plans; and audits, assessments, or disputes.
- Federal return review should track book-to-tax adjustments, credits, deferred tax positions, uncertain positions, and changing effective tax rates across the lookback period.
- Foreign subsidiary analysis should test reporting and inclusion obligations under the applicable controlled foreign corporation regime and related information-reporting rules.
- Loss carryforward analysis should address ownership-change limitations, built-in gains or losses where relevant, and any pre-existing restrictions that affect post-closing value.
- Transfer pricing analysis should assess whether related-party pricing is supported by applicable arm’s-length standards and contemporaneous documentation requirements.
- State and local analysis should evaluate nexus, sourcing, apportionment, filing footprint, and indirect tax collection exposure under the relevant state and local regimes.
- Employee benefit review should assess qualification, nondiscrimination, funding or contribution timing, and any excise or disqualification consequences under the applicable tax and benefits rules.
- Cross-reference diligence inputs with quality-of-earnings findings when non-recurring items or normalization adjustments may have tax consequences.
- Cite the controlling authority for each legal proposition relied on, using the applicable statute, regulation, rule, or other recognized authority rather than conclusory labels alone.
## 4. Analytical scaffolds
- Build a return-by-return matrix for the review period and note, for each year, the filing posture, major adjustments, credits, reserves, and any items requiring explanation.
- Test year-over-year changes in effective tax rate, deferred tax balances, and uncertain positions to identify trends that suggest shifting risk.
- For each foreign filing, confirm the entity, the reporting trigger, the associated inclusion or earnings analysis, and whether the required returns or statements were filed.
- For losses, identify the pool of carryforwards, any pre-closing limitations, any historic ownership changes that matter, and whether the contemplated acquisition will further restrict use.
- For related-party items, identify counterparties, transaction types, pricing method or support, and whether documentation exists to defend the reported result.
- For state and local items, identify where the business has operations, customers, employees, inventory, or other nexus-creating facts, then compare those facts to filed returns and collected taxes.
- For employee benefit plans, identify the plan type, compliance checks performed, contribution timing, and any corrective actions or exposure.
- For each issue, close with: the scale of the item as reflected in the documents, the cross-reference that makes it material, and the consequence for the buyer or transaction.
- Assign a uniform severity level to every issue using an ordinal scale defined once at the outset, and keep the label consistent throughout.
- End each identified issue with a concrete recommendation that names the responsible role and ties timing to a transactional or regulatory milestone.
- If a point turns on a legal rule, state the rule or authority that governs it before stating the conclusion.
## 5. Vertical / structural / temporal relationships
- Compare periods across the lookback window to distinguish a one-off filing anomaly from a recurring exposure.
- Compare federal positions against state, local, payroll, and foreign positions where the same underlying transaction can create multiple tax consequences.
- Compare return positions against supporting schedules, financial statement data, and diligence materials to catch mismatches in classification or timing.
- Compare pre-closing limitations against post-closing transaction effects to determine whether value is already impaired before signing.
- Where a filing position depends on another document, note the dependency explicitly and state whether the cross-document support is present, inconsistent, or missing.
## 6. Output structure conventions
- Produce a single tax due diligence issue memorandum.
- Open with a short executive summary that ranks the most material risks and states the overall diligence view.
- Follow with organized sections for federal income tax, foreign reporting and controlled foreign corporation matters, loss carryforwards and limitation analysis, transfer pricing, state and local taxes, employee benefit plans, and known audits or controversies.
- Within each section, organize findings by issue, not by document, and keep each issue tied to the relevant year, entity, or jurisdiction.
- For each issue, include the severity label, a brief statement of the issue, the governing authority or rule, the relevant document cross-reference, the quantified or scaled significance drawn from the record, the buyer consequence, and the recommended action.
- Use conventional legal-diligence prose; do not reproduce the rubric’s internal checklist language.
- End with a Recommended Actions block listing imperative next steps, the responsible role, and the timing anchor for each item.
- If the source set supports no issue in a category, say so expressly and note the basis for that conclusion rather than omitting the category.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!