Use when intaking crypto and digital-asset activity and organizing wallet, exchange, and transaction records into a source-cited intake matrix for tax professional review.
When to use
A taxpayer's digital-asset activity must be organized into an auditable record before a tax professional evaluates it.
A team needs wallet, exchange, and transaction records categorized with sources and gaps flagged.
Crypto activity must be scoped — business vs. personal, entity-involved or not — before substantive tax review.
Required inputs
Wallet and exchange accounts, referenced by masked identifier.
Taxpayer/entity type, jurisdictions, and the user's role.
Tax year(s) or period(s) of interest, or not provided.
Transaction types present: purchases, sales, swaps and trades, staking, mining, airdrops, NFTs, DeFi activity, and token grants.
Whether activity is business or personal, and any entity involvement.
Cost-basis records and Forms 1099, if provided, with citations.
Any foreign-account facts the user raises.
Source documents — wallet/exchange exports, statements — with citations to rows, pages, or fields.
If the accounts, the taxpayer/entity type, jurisdictions, or the tax period are missing, record them as not provided and return the missing-information list first.
Use when intaking worker, engagement, and payroll facts into a source-cited facts-to-verify table for employment-tax and worker-classification review by qualified counsel.
When to use
A worker or worker population's employment-tax facts must be organized before counsel evaluates classification.
A team needs engagement, payment, and document facts captured with sources and gaps flagged.
An employment-tax question must be coordinated between tax and employment counsel.
Required inputs
Workers or worker groups and their roles, referenced without full personal identifiers.
Taxpayer/entity type, jurisdictions, and the user's role.
Tax period(s) of interest, or not provided.
Engagement facts: degree of control, supervision, who provides tools and equipment, hours, exclusivity, and work location.
Payment facts: payment method, benefits, reimbursements, and expense treatment.
Contracts, and Forms W-2 / 1099 if provided, with citations.
Payroll practices and any state or local payroll-tax facts the user reports.
Source documents with citations to sections, form lines, or pages.
If workers/roles, taxpayer/entity type, or jurisdictions are missing, record them as not provided and return the missing-information list first.
Use when organizing entity formation, ownership, and election facts into a source-cited facts table so qualified tax counsel can evaluate tax classification.
When to use
A new or existing entity's tax classification facts must be organized for review by tax counsel.
An ownership change, a new owner, or a contemplated election makes classification a live question.
A transaction or diligence workstream needs the classification facts mapped before a professional evaluates them.
Required inputs
Entity type and jurisdiction of formation, or not provided.
Formation date and structure, and the user's role.
Ownership facts: members, shareholders, or partners; ownership percentages; and any ownership changes with dates as the documents state them.
Single-member vs. multi-member, and any disregarded-entity question raised.
Partnership, corporation, S-corporation, C-corporation, or LLC facts relevant to classification.
Elections made or contemplated, if provided, and the documents evidencing them (echo any election dates as [deadline verification required]).
Use when issue-spotting cross-border tax questions into a source-cited issue map and missing-facts list for tax counsel, without concluding treaty, withholding, PE, or CFC/PFIC treatment.
When to use
A cross-border structure or transaction needs its tax issues spotted and organized before tax counsel evaluates them.
A team needs the jurisdictions, issue areas, and missing facts mapped for an international tax review.
A matter touches foreign entities, persons, payments, or operations and the questions must be scoped.
Required inputs
The cross-border structure: foreign entities and persons, the jurisdictions implicated, and the user's role, or [verify jurisdiction].
Cross-border activity facts the user provides: withholding situations; permanent-establishment concepts, if raised; transfer pricing; intercompany services; royalties and IP; cross-border employment.
VAT/GST facts, if relevant.
Tax treaties, if provided.
Foreign bank accounts, if mentioned, and any CFC or PFIC questions, if raised.
Tax year(s) or period(s) and the review purpose.
Source documents with citations to sections, schedules, or pages.
If the structure, the jurisdictions, or the activity facts are missing, record them as not provided and return the missing-information list first.
Use when intake-mapping sales and use tax nexus facts by jurisdiction into a source-cited fact map and open-question tracker for tax professional review.
When to use
A taxpayer's sales/use tax footprint must be mapped across multiple jurisdictions before a professional evaluates it.
A team needs physical-presence, economic-activity, and marketplace facts organized per jurisdiction with sources.
A transaction or registration project needs the nexus facts triaged first.
Required inputs
Jurisdictions in scope (states and localities), or not provided.
Taxpayer/entity type and the user's role.
Tax period(s) of interest, or not provided.
Customers and revenue streams, and product/service type — including digital goods, software, and SaaS where relevant.
Physical-presence facts: offices, inventory locations, remote employees, and property.
Marketplace-facilitator facts: sales made through marketplaces.
Exemption certificates and resale certificates on file.
Economic-nexus facts the user supplies (sales volume, transaction counts) — recorded as user-stated facts, never measured against an invented threshold.
Historical registrations and filings.
Source documents with citations to reports, ledgers, or pages.
If jurisdictions, taxpayer/entity type, or the product/service type are missing, record them as not provided and return the missing-information list first.
Use when reviewing the tax covenants and indemnities of a transaction agreement and mapping their architecture and negotiation issues for tax counsel verification.
When to use
A transaction agreement's tax covenants and indemnities must be mapped and organized for tax counsel.
A negotiating team needs the tax-risk-allocation architecture and its gaps surfaced from one side's perspective.
Tax indemnity mechanics must be checked for completeness before signing.
Required inputs
The transaction agreement and its tax covenant and indemnity provisions.
The user's role and perspective (buyer, seller, or other).
Transaction type, jurisdictions, and the review purpose, or not provided / [verify jurisdiction].
Source references to sections, clauses, schedules, or pages.
Any Straddle Period, pre-closing, or post-closing facts the user provides.
Whether the review should cover: pre-closing and post-closing taxes, Straddle Period allocation, transfer taxes, tax refunds, tax contests, cooperation, filing control, indemnity scope, survival, caps, baskets, exclusions, exclusive remedy, and procedures.
If the agreement text, the user's role, or the transaction type is missing, record it as not provided and return the missing-information list first.
Use when organizing a tax-related document set into a source-cited inventory with masked identifiers, missing-document list, and reviewer notes for supervised tax review.
When to use
A tax document set must be ordered into an auditable inventory before review.
A team needs to see what documents exist, what is missing, and what is unclear, with sensitive identifiers protected.
A diligence, intake, or controversy workstream needs its document record organized.
Required inputs
The tax document set, which may include: tax returns, Schedule K-1s, Forms W-2 and 1099, tax notices, audit correspondence, entity documents, capitalization records, payroll records, sales-tax filings, exemption certificates, transaction documents, invoices, ledgers, and supporting schedules.
Taxpayer/entity type, jurisdictions, and the tax years or periods covered, or not provided.
The review purpose the inventory supports.
Whether sensitive identifiers (SSN, EIN, TIN, account numbers) appear, and the masking convention to apply.
If the document set, the taxpayer/entity type, or the periods covered are missing, record them as not provided and return the missing-information list first.
Use when capturing and structuring the facts of a tax-sensitive matter or transaction into a source-cited working paper and tax issue map for qualified tax professional review.
When to use
A new tax-sensitive matter, transaction, or activity needs structured intake before substantive tax analysis by a professional.
A team needs an auditable working paper that separates facts, sources, and open questions and flags every gap.
A matter must be routed to the right specialist tax skill and the issues scoped first.
Required inputs
Taxpayer/entity identity and type (individual, C corp, S corp, partnership, LLC, trust, estate, nonprofit, other), and the user's role.
Jurisdiction(s) implicated (federal, state, local, foreign), or [verify jurisdiction].
Tax year(s) or period(s) at issue, or not provided.
Transaction or activity type and the review purpose.
Activity facts, each as available or marked missing: revenue streams, ownership and cap structure, employees and contractors, assets, intellectual property, real estate, digital assets, and any foreign persons or entities.
Filings already made and notices received, as the user describes them.
Source document set, with citations to form lines, schedules, sections, or pages.
Any user-supplied deadlines, echoed and marked [deadline verification required].
Whether sensitive identifiers (SSN, EIN, TIN, account numbers) appear, so they can be masked.
If any gate (taxpayer/entity type, jurisdiction, tax period, activity type, review purpose) is missing, record it as not provided and return the missing-information list before substantive intake.
Use when reviewing the tax provisions of a contract and producing a source-cited issue checklist and negotiation-point list for tax professional review.
When to use
A contract's tax provisions — gross-up, withholding, indemnity, allocation, and related terms — must be reviewed and organized for a tax professional.
A negotiating team needs the tax terms mapped, with gaps and negotiation points, from one side's perspective.
Tax terms must be checked for completeness before signing.
Required inputs
The contract or agreement text, and the specific tax provisions to review.
The user's role and perspective (which side the review supports).
Transaction type, jurisdictions, and the review purpose, or not provided / [verify jurisdiction].
Source references to tax sections, clauses, schedules, or pages.
Any related schedules or ancillary documents provided.
Whether the review should cover: tax gross-up, withholding, tax indemnity, tax cooperation, allocation, purchase-price allocation, transfer taxes, sales/use taxes, VAT/GST (where relevant), information reporting, audit cooperation, survival, caps and baskets (where applicable), and post-closing tax covenants.
If the agreement text, the user's role, or the transaction type is missing, record it as not provided and return the missing-information list first.
Use when building a transaction tax diligence request list and follow-up tracker organized by tax workstream for attorney-supervised diligence.
When to use
A transaction — M&A, asset purchase, stock purchase, reorganization, real estate deal, financing, or restructuring — needs a tax diligence request list.
A diligence team needs requests organized by workstream with priority, rationale, and ownership.
Tax diligence follow-ups must be tracked against documents produced.
Required inputs
Transaction type and stage, and the user's role (buyer, seller, lender, borrower, or other).
Target/counterparty profile and the jurisdictions implicated, or [verify jurisdiction].
Tax workstreams in scope: income tax, sales/use tax, payroll/employment tax, property tax, transfer tax (where relevant), tax returns, audits and notices, NOLs and credits if provided, tax sharing agreements, intercompany arrangements, foreign tax issues, and withholding.
Documents already provided, with citations to sections or pages.
Any transaction-specific tax representations the user wants tracked.
Any user-supplied deadlines, echoed and marked [deadline verification required].
If transaction type, jurisdictions, or the workstreams in scope are missing, record them as not provided and return the missing-information list first.