1099-CAP Adviser Handoff: Documents and Review Questions

Begin with a short cover note identifying the transaction, reporting year, legal entities and current executed-document version. State which decisions you need: reporting obligation, corporation responsible, recipient population, consideration selection or a specific unresolved field.

The IRS CAP instructions connect the form with specified corporate transactions, Form 8806 and several exceptions or related reporting routes. A handoff should therefore identify the relevant questions rather than ask advisers to approve a final spreadsheet whose assumptions are hidden.

Separate an initial scope review from a later review of populated records. The first determines what should be prepared; the second checks whether the prepared records follow that decision. Record which stage this packet supports.

Include executed agreements and amendments, ownership records, closing schedules, valuation support and existing adviser memoranda. Link each document to the relevant review question and cite useful pages or exhibits. A folder containing hundreds of files is not a substitute for a navigable index.

Identify draft and superseded records, but retain them if they explain a change. Flag missing exhibits explicitly. Where two sources disagree, show the conflicting facts side by side rather than selecting one without explanation.

Include the shareholder and consideration workbooks with their control totals. Advisers should be able to see the complete source population, documented exceptions and unresolved amounts before evaluating a selected reporting output.

For a document that covers several entities or transactions, point to the applicable section and explain which party supplied it. If a reviewer needs a translation or clarification of an unfamiliar class label, record that request with the original document reference. This preserves the source meaning instead of silently rewriting a legal or ownership term in the workbook.

This matrix is an organizational example, not a statement that any named person has reviewed the transaction. Populate it with actual responsibilities and distinguish supplying a fact from approving its legal treatment.

Fictional 2026 example. The Orion team has a 600-share source population. Its workbook currently shows 450 shares included in proposed records, 100 with a documented recipient exception and 50 awaiting an intermediary review.

The team does not ask for blanket approval of 600 reportable shares. It supplies the source bridge and three focused questions, each linked to the affected records.

If the adviser resolves the 50-share issue as included, the proposed population becomes 500 included and 100 excepted, still totaling 600. The workbook records the decision reference and preserves the prior pending classification so the change is explainable.

For each response, capture the decision, supporting authority or memorandum reference, facts assumed and transaction version reviewed. Record unanswered portions separately. An answer about the reporting corporation may not also resolve shareholder exceptions or consideration timing.

When advisers request more facts, assign the document request to the custodian and track the specific missing item. Provide the response through the same indexed issue so the discussion does not become scattered across unrelated email threads and spreadsheets.

If a subsequent amendment changes ownership, consideration or another relied-on fact, identify which conclusions depend on it and request the appropriate renewed review. Do not assume an earlier response remains applicable to a materially different source version.

After the relevant conclusions are documented, provide operations with the approved scope, recipient treatment, calculation inputs and unresolved exclusions. Link those instructions to the source packet and actual review record.

Publication 1099 supplies the general filing, recipient-statement and correction framework, while CAP instructions supply the form-specific rules. The operational handoff should identify which applicable-year references the team will use without claiming that a spreadsheet review proves filing or delivery occurred.

Retain a final packet index and the preparation version that followed it. Record actual submission and furnishing evidence when available as separate events. This keeps transaction review, record preparation and filing completion distinct enough for a later reviewer to understand what was done.