Share Purchase Transactions

How to verify share ownership and transfer restrictions for Share Purchase Transactions

Buyer-side share ownership diligence: reconcile stock records, assess transfer restrictions and liens, and document evidence gaps and required actions.

October 18, 2026  ·  10 min read
Book a Demo →

Verify the buyer’s proposed acquisition by reconciling the target’s stock ledger with its capitalization table, issuance records, certificates or uncertificated-share records, and prior transfers. Then trace restrictions, liens, and required holder actions to the shares being purchased. The deliverable is a source-linked share ownership checklist identifying each seller’s proposed holding, unresolved discrepancies, applicable restrictions, and evidence needed before accepting the transfer. Keep factual verification, legal analysis, and commercial risk acceptance separate: a seller’s assurance does not resolve a missing ownership record.

When to use this workflow

Buyer’s counsel and in-house deal teams should begin when the proposed sellers and acquisition perimeter become identifiable. Use the review to inform ownership representations, seller schedules, and transfer requirements. Refresh affected entries when capitalization or transaction documents change.

The scope is the shares being acquired, including instruments and historical events that could change the selling holders, share count, or transferability. This is a US-oriented professional workflow, not a complete securities-law, regulatory, or tax review. Delaware statutory points apply to Delaware corporations; other entities require their own governing-law analysis. The practical checks below are recommendations, not statutory mandates.

What you need

Request a dated evidence set:

  • Ownership records: current and historical stock ledgers, capitalization tables, certificate registers, certificates, cancellation records, and uncertificated-share notices.
  • Issuance and transfer evidence: subscriptions, issuance approvals, relevant payment records, transfer instruments, and predecessor-holder records.
  • Restrictions: charter and bylaws with amendments, shareholder agreements, voting agreements, side letters, joinders, consents, and waivers.
  • Competing interests: equity plans, options, warrants, conversion instruments, pledges, and evidence addressing identified liens.
  • Transaction documents: draft purchase agreement, seller and purchased-share schedules, ownership disclosures, proposed releases, and transfer deliverables.

Ask the target to distinguish nonexistent documents, documents not supplied, and categories considered inapplicable. Record the respondent and response date. Give each file a stable document ID and retain its version, execution status, and data-room location in a supporting index.

Use the template

Use the Share Purchase Transactions — Share ownership checklist below. Copy this table into your working document or spreadsheet. Create separate rows for distinct share blocks or issues; one seller may require several rows where acquisition history or restrictions differ.

ID / holder Shares / class Source / pinpoint Reconciliation Restriction / evidence Gap / risk Action / owner Status / proof

“Shares / class” identifies the precise block proposed for purchase. “Source / pinpoint” contains document IDs and page, clause, or spreadsheet-cell references—not a folder name. “Reconciliation” records the amounts in each source and any variance.

Use “Restriction / evidence” for operative wording and compliance evidence. Keep uncertainty in “Gap / risk,” distinguishing missing facts from legal questions. “Action / owner” identifies the response, accountable person, and follow-up date. “Status / proof” distinguishes pending requests, agreed drafts, executed documents, and effective resolution; include the verification date. Link supporting records rather than compressing the entire ownership history into one cell.

Step by step

1. Fix the share population and evidence date

Start with the draft purchased-share schedule. Identify the target’s legal name and jurisdiction, every selling holder, each class, and the number being acquired. Specify the ownership evidence date and whether the buyer expects all outstanding shares or a defined subset. Do not confuse this working date with a statutory voting record date.

Track options and convertible instruments separately from issued shares unless exercise or conversion is contemplated. Identify that dependency rather than silently substituting a fully diluted number for purchased shares.

Template output: one row per proposed seller block, with the schedule reference and evidence date. Flag unidentified holders, undefined classes, and outstanding instruments affecting the perimeter.

2. Reconcile the ledger against the capitalization table

Compare holder names, amounts, classes, certificate identifiers, and transfers. Investigate cancellations, duplicate entries, omitted issuances, name changes, and differing evidence dates. Do not overwrite a source to force agreement. For an all-shares acquisition, reconcile the aggregate outstanding count as well as individual seller blocks.

For Delaware corporations, DGCL § 219(c) defines the stock ledger to include record holders, addresses, registered share amounts, and issuances and transfers recorded under § 224. Its separate rule about evidence for voting and list-inspection rights should not be treated as a general clean-title determination. See DGCL § 219(c). (delcode.delaware.gov)

Template output: source amounts, the precise variance, and the owner of the follow-up. Mark agreement only for fields actually compared.

3. Trace each seller’s acquisition and signing authority

Work backward from the current entry to the issuance or transfer through which the seller acquired the block. Match approvals, subscriptions, transfer instruments, certificate cancellations and replacements, and ledger entries. Check execution and share identifiers, not just document titles.

For nominee, trust, estate, or entity holdings, identify the recorded holder, disclosed beneficial interest, proposed signatory, and supporting authority documents. Do not assume the beneficial owner is the proper transferor.

A historical entry establishes what the company recorded without necessarily explaining the underlying transaction. Request missing links and assess their significance under applicable law; neither infer invalidity nor certify title solely because records are incomplete.

Template output: a source-linked acquisition chain, authority evidence, missing links, and the proposed response. Separate authority questions from numerical discrepancies.

4. Map restrictions to the affected shares

Read operative corporate documents, shareholder agreements, amendments, joinders, and side letters. Extract any first-refusal rights, consent requirements, permitted-transfer provisions, lockups, and participation rights. Identify covered holders, shares, triggers, exceptions, notice recipients, response periods, and consequences. A permitted-transfer exception may still require notice or a transferee joinder.

For Delaware corporations, § 202(b) permits restrictions through the certificate of incorporation, bylaws, and specified security-holder agreements. Restrictions adopted after issuance do not bind those securities unless their holders are parties to an agreement or voted in favor of the restriction. Review chronology and participation rather than assuming the newest document governs every block. See DGCL § 202(b). (delcode.delaware.gov)

Template output: clause references, covered shares, adoption dates, participation evidence, and required notice, consent, waiver, or joinder analysis.

5. Test restriction notices and investigate liens

Compare operative restrictions with certificate legends and uncertificated-share notices. Under Delaware § 202(a), a restriction permitted by that section is ineffective against a person without actual knowledge unless conspicuously noted on the certificate or included in the prescribed uncertificated-share notice. A missing legend therefore does not establish unrestricted transferability. See DGCL § 202(a). (delcode.delaware.gov)

Separately, investigate disclosed pledges and other potential liens. Obtain underlying documents and determine what additional searches or evidence the facts and governing law warrant. Define the scope and limitations of any search; do not treat a search result alone as comprehensive ownership verification. Examine the release’s covered collateral and effectiveness dependencies.

Template output: notice evidence, identified liens, open knowledge questions, search scope, and release dependencies. A draft release remains a draft.

6. Translate findings into buyer requirements

Link unresolved issues to purchase-agreement provisions or proposed deliverables. Responses may include corrected schedules, supporting records, seller joinders, consents, waivers, or releases. Confirm that every intended selling holder is covered by effective transaction documentation.

Keep factual cure separate from contractual protection. A representation or negotiated loss allocation does not supply missing transfer evidence. Record the authorized buyer’s acceptance of residual uncertainty separately from verified resolution.

As a negotiated example, AMD–ZT § 8.2(e) specifies share-transfer documents and a CEO certificate addressing designated closing conditions. These are contractual deliverables, not universal requirements or independent proof of underlying facts. See the filed agreement, § 8.2(e). (sec.gov)

Template output: requested response, affected draft clause, decision-maker, and evidence needed to close the issue.

7. Refresh and complete the verification record

Compare the latest seller schedule with the reviewed population. Request updates for intervening issuances, exercises, transfers, pledges, amendments, and waivers. Identify any period not covered by evidence.

For each proposed resolution, verify execution, parties, covered shares, and effectiveness conditions. A waiver limited to another transaction does not address this sale. Where payment and release occur at closing, record the dependency and required contemporaneous evidence rather than prematurely marking completion.

Template output: final status, resolution references, reviewer, and verification date. Deliver the reconciled seller schedule with exceptions separating missing evidence, legal questions, closing-dependent actions, and accepted commercial risks.

Worked example

Fictional scenario: Birch Quay Holdings proposes to acquire all outstanding shares of Larkspur Sensors, a fictional Delaware corporation. Schedule S01 and capitalization table C01 show Mara Chen with 600 common shares and Alder Ridge Ventures with 400. Ledger L01 instead shows Mara with 550, Alder Ridge with 400, and former employee Theo Ames with 50. All parties, documents, quantities, and clauses in this example are fictional.

Instrument T03 describes Theo’s transfer of 50 shares to Mara, but its signature page is missing. Agreement A02 gives Alder Ridge a consent right over Mara’s proposed sale. The supplied records show Mara executed A02 after the relevant issuance. Alder Ridge’s pledge P04 identifies its 400 shares as collateral. Consent W01 and release R01 are unsigned drafts. R01 also conditions release effectiveness on payment; no payment evidence has been supplied.

ID / holder Shares / class Source / pinpoint Reconciliation Restriction / evidence Gap / risk Action / owner Status / proof
O-01 / Mara 600 common proposed L01 p. 2; C01 B4:C6; S01 B4:C6; T03 pp. 1–2 Ledger 550; cap table and schedule 600; Theo recorded for 50 T03 describes the prior transfer Signature page absent; acquisition chain unresolved Seller counsel: obtain complete instrument and explain ledger treatment Open; no complete executed instrument supplied
O-02 / Mara Proposed 600 common A02 § 4.2 and signature page; W01 p. 1 Covered block depends on O-01 A02 requires Alder Ridge consent; Mara signed A02 W01 unsigned; scope requires verification after O-01 Buyer counsel: confirm block and obtain transaction-specific consent Pending; draft only
O-03 / Alder Ridge 400 common L01 p. 2; S01 B5:C5; P04 schedule A; R01 § 2 Ledger and schedule agree P04 identifies pledged shares Release unsigned; payment dependency unverified Finance lead and counsel: confirm execution and release mechanics Open; no effective release established

The aggregate sources each show 1,000 shares, but that agreement conceals a seller-level discrepancy. O-01 affects who should sell 50 shares and the scope of O-02. Counsel must investigate the incomplete transfer before choosing corrected records or revised seller documentation. O-03 shows why matching numbers do not establish transferability. No supplied evidence establishes an effective release, and the example does not assume that one will occur.

Common mistakes

  • Treating the cap table as sufficient ownership proof. Compare seller-level and aggregate amounts with the ledger and underlying transactions.
  • Assuming recorded and beneficial holders are interchangeable. Identify the proper transferor and verify signing authority separately.
  • Reviewing restrictions only at company level. Map coverage, chronology, exceptions, and holder participation to each block.
  • Equating no legend with no restriction. Investigate notices, actual knowledge, agreements, and applicable law.
  • Closing an issue when a draft arrives. Check transaction scope, execution, and effectiveness; preserve closing-dependent actions as open.

Final quality check

  • Every purchased block identifies seller, class, amount, and evidence date.
  • Individual and aggregate discrepancies are resolved or assigned explicitly.
  • Acquisition-chain and authority references point to verified source documents.
  • Restriction analysis covers amendments, participation, notices, and applicable exceptions.
  • Consents, waivers, and releases cover the intended parties, shares, and transaction.
  • Execution and effectiveness dependencies are verified or assigned for closing.
  • Open issues identify an owner, next action, follow-up date, and buyer decision-maker; accepted risks remain visible.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its due diligence capabilities support bulk document classification and tabular review across documents to organize evidence and prioritize human review. In contract review in Word, provide buyer-specific instructions and examine findings that quote and locate clauses, rank severity, and identify missing language. Lawyers retain ownership analysis and decide which suggestions to insert as tracked changes. To assess this workflow against your document set, book a demo. (decover.ai)

Frequently asked questions

Is the stock ledger enough to verify ownership?

For this diligence workflow, use it with issuance and transfer evidence, certificate records, and seller schedules. Identify what each source establishes. Do not turn an unexplained ledger entry into an unqualified ownership conclusion.

What if a certificate is missing?

Record the affected block and request certificate-register, issuance, transfer, and cancellation records. Determine the appropriate replacement or transfer response under governing documents and law. Do not treat a generic affidavit as sufficient without that analysis.

Should options appear in the purchased-share checklist?

Track them separately unless exercise or conversion creates purchased shares. Link any contemplated exercise to the resulting holder, class, count, evidence, and schedule update; avoid counting the instrument and resulting shares twice.

Can the buyer accept an unresolved ownership issue?

Record the uncertainty, proposed protection, and authorized decision. Obtain legal analysis of whether the transaction can proceed. Commercial acceptance is not factual cure and should never be presented as verified ownership or removal of a restriction.

Sources

Source scope: the assignment’s research cutoff is October 13, 2026; live statutory pages are not certified historical snapshots.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.

Run this workflow in DecoverAI

Clause-quoted findings, missing-language flags, and tracked changes in your name — with your team deciding every call. Plans from $299 per seat per month, SOC 2 Type II certified.

Book a demo
to learn more.
Book a Demo