What should an advisory firm preserve before transferring a client's cost-basis records?

Keep source records and received records distinct. Compare identifiable securities acquisitions and preserve unresolved basis questions with a next-step owner.

Bhavya Barot

15 Oct 2026 — 9 min read

Conceptual record-continuity illustration, not client records or a completed transfer.

Preserve an identified source packet and a lot-level inventory before a transfer, then compare them with the records actually received. Keep missing fields, inconsistent values and unanswered questions in a separate exception record with an owner. A position appearing in the receiving account does not, by itself, establish that its cost-basis evidence is complete or correct. This proposed workflow organizes records for review; it does not calculate tax basis, authorize a transfer or certify a tax return.

Key takeaways

Keep the original source records and their dates. A rewritten summary should not become the only evidence.
Compare securities and identifiable acquisitions, not only an account balance or total position.
Preserve a reported covered or noncovered label without treating it as proof that every needed record is present.
Keep a blank or uncertain basis field unresolved. Do not turn it into zero or choose a value because it looks plausible.
Assign the next evidence request and review step within the actual engagement. Organizing records is different from deciding their tax treatment.

What does this review decide?

The narrow question is whether the supplied records support a particular comparison: what was held before the transfer, what information arrived and what remains unexplained. Define that question before collecting a packet. Otherwise, a reviewer can drift from checking records into deciding which institution to use or which shares to sell.

A holding and the records describing its acquisitions are different things to inspect. Several purchases of the same security may appear as one position in a summary. A matching position total is useful evidence about that total; it does not show that each acquisition date or reported basis field was preserved.

The CRM-export guide covers reconstructing synthetic objects and their relationships from a sample file. The connected-account-dashboard guide covers what an account view displays and leaves unconfirmed. This article has a different job: retaining and comparing the source evidence behind securities tax-lot and basis records. It does not assess either a CRM or an account-aggregation service.

Which records should be preserved first?

Start with the records available through the firm's approved process and within the agreed scope. Identify the account and securities being reviewed internally, without putting client identifiers into public examples. Record which source supplied each document, what period it covers and when it was obtained. Keep the original alongside any working inventory.

FINRA's Cost Basis Basics describes trade confirmations, reinvested dividends and distributions as relevant records. It also recommends comparing a firm's reported basis with the investor's own records and consulting a tax professional when computing and reporting gains or losses. [1] Those points support preserving evidence; they do not make a spreadsheet an authoritative basis calculation.

For each identifiable acquisition, retain the security identifier used in the source, quantity, acquisition date as reported, reported basis and any stated coverage or adjustment information. Preserve the source's units and labels. If a document gives only a position total, record that limit rather than manufacturing the underlying lots.

Keep supporting confirmations, relevant transaction history and any available explanation of a correction or adjustment connected to the inventory entry. A statement can help locate a question without answering it. Do not assume that the most recent-looking document contains every earlier transaction or that a source without an acquisition date can supply one by inference.

Conceptual folder with separate transaction slips, source sheet and a magnifying lens. — Conceptual illustration: preserve the source packet before comparing received records.

How should covered and noncovered labels be handled?

The IRS distinguishes covered securities, for which brokers provide specified basis information on Form 1099-B, from noncovered securities, for which the taxpayer may need to determine acquisition date and basis from available records. Its stock FAQ describes different starting dates for stock and certain mutual-fund or dividend-reinvestment-plan acquisitions. [2] That is not a single date test for every kind of security or situation.

For this workflow, preserve the label shown in each source and identify where it came from. Do not independently classify a security from a convenient cutoff date or treat an absent label as a determination. If two records show different statuses, put the difference in the exception record for the appropriate review.

Transfer-statement rules also have scope limits and exceptions. [3] The existence of a transfer process does not establish that every field in the firm's working inventory will arrive or that all client-held supporting documents travel with it. This article does not set out those rules or impose a transfer-statement duty on every advisory firm. Have the qualified reviewer check the rules and circumstances relevant to the actual transfer.

Inherited-property basis is a separate subject. The inheritance guide introduces those questions; this workflow does not explain valuation or inherited-basis treatment.

A covered label does not remove the need to preserve the sources being compared. A noncovered label does not mean that useful records do not exist. Both labels belong beside the evidence and its limits, not in place of them.

What should the pre-transfer inventory contain?

Use a record small enough to review but detailed enough to point back to the evidence. These are proposed organizing fields, not a prescribed regulatory form or a complete checklist for every security.

Source reference

Identify the document or supplied file, its date or period and the entry being inspected. Keep a route to the original through the approved internal process. A working note should distinguish a source record from a client recollection or a question still awaiting documentation.

Security and acquisition reference

Preserve the identifier, reported quantity and identifiable acquisition reference. If the source does not separate acquisitions, say so. Do not create apparent lot precision from an aggregate position.

Reported fields and limits

Record acquisition date, basis, status and adjustment labels exactly as the source supplies them. Mark a missing field as missing. Note whether a date is the acquisition date, statement date or receipt date; they answer different questions.

Evidence still needed

Write the question narrowly: which field cannot be compared, which records disagree or which acquisition cannot be identified? "Basis problem" is less useful than a reference to the two entries and the unresolved difference.

The inventory describes the supplied material. It should not claim that the client's complete transaction history has been recovered merely because every row in that inventory has a value.

How should received records be compared?

Retain an identified copy of the received material before editing the working comparison. Record its source, receipt date and version where available. Keep the pre-transfer packet separately identifiable so that a later correction does not erase what the reviewer originally saw.

First check whether the security and reported quantity can be matched. Then compare identifiable acquisitions and the fields relevant to the defined review. A missing acquisition row, a changed date and a different reported basis are separate findings. Do not collapse them into one "transfer complete" flag.

Record a specific match narrowly. For example, "The supplied acquisition reference and date agree in these two records" does not establish that an adjustment was correct or that a tax return can use the value without further review. If the received file uses a different identifier or groups entries differently, document the relationship that supports a match or leave it unclear.

When a corrected record arrives, retain it with its source and date, identify which earlier observation it changes and have the assigned reviewer assess the difference. Replacing a file is not the same as resolving every question connected to it.

What belongs in the exception record?

Keep the original observations visible beside the follow-up. A useful exception entry identifies the security or acquisition, the two source references, the type of gap or inconsistency, the evidence still needed and the person responsible for the next step.

Separate the request from its result. "Asked for a missing acquisition record" is not "record received." "Record received" is not "review completed." A response can answer one question while leaving another open.

Use a status that reflects the defined review. A reviewer may resolve a source mismatch while a tax-treatment question remains with a tax professional. Describe that boundary rather than applying one broad closed status to the entire holding. Do not supply an assumed response deadline or mark work complete because a reminder was sent.

Conceptual mismatched record slips kept apart beside a question tab and follow-up envelope. — Conceptual illustration: keep a mismatch open until reviewed evidence supports the next status.

A fictional comparison with an unresolved lot

A supplied source packet identifies two acquisitions of the same fictional security, SAMPLE-S. The received summary shows a position for SAMPLE-S, but its supplied detail identifies only one of those acquisitions. No client facts, quantities or tax values are used in this example.

The reviewer can record that the security appears in the received summary. The reviewer cannot conclude from that appearance that both acquisition records arrived. The exception entry points to the pre-transfer evidence for the second acquisition, identifies what is absent from the supplied received detail and assigns a request for further records.

If another document later identifies the second acquisition, the reviewer compares that evidence and records what it resolves. Its arrival does not automatically settle a conflicting basis field. The point of the example is to preserve the difference between an observed position, identifiable acquisition records and an unanswered question.

Who owns the handoff?

Assign roles from the real engagement and permissions. The adviser may organize the agreed review and explain its boundaries. Operations may obtain or identify received records through approved channels. The client may supply older records they hold. A qualified tax professional may need to assess an adjustment or determine tax treatment. These are possible roles, not authority granted by this article.

For each open item, name the next evidence request, who can make it and who reviews the response. Explain any work outside the engagement before presenting it as included. The service-calendar guide covers that broader scope-and-responsibility task; a cost-basis inventory should not silently change it.

Use the firm's approved handling process for private records. A public worksheet or example needs no account numbers, tax identifiers, portal credentials or client transaction files. Do not ask a client to expose sensitive material in an ordinary marketing form to resolve a record mismatch.

The bottom line

Preserve the source packet, compare the received records at the level the evidence supports and keep unresolved items with a named next-step owner. A matching holding is not a complete basis record, and a completed comparison is not a tax calculation, transfer authorization or assurance that every record moved correctly. The useful result is a bounded account of what agrees, what differs and what still needs qualified review.

Frequently asked questions

Does a holding appearing in the new account prove its basis records arrived?

No. Compare the supplied acquisition and basis records separately. A visible position does not establish that every underlying record is present or correct.

Should a blank basis field be entered as zero?

Not as a way to finish this comparison. Record the field as missing or unresolved and route the question for appropriate review. This workflow does not determine the value to use for tax reporting.

Does a covered label mean the client's own records are unnecessary?

No. Preserve the available source evidence and compare the actual fields. A label alone does not resolve a missing record or conflicting value.

Which value should be chosen when two sources disagree?

Do not choose within this organizing exercise. Preserve both sources, identify the difference and assign the evidence request and qualified review needed to resolve it.

Can this workflow replace a tax professional or the transfer process?

No. It organizes records and open questions. It does not calculate basis, choose investments, submit a transfer or determine anyone's legal or tax responsibilities.