Devancore Inc.
Devancore Post-Trade Glossary
Glossary
Beneficial vs Direct Ownership
Direct owners are recorded on issuer-level books; beneficial owners hold their economic interest through an intermediary, custodian, or depository account.
Document source: https://devancore.com/glossary/beneficial-ownership-vs-direct-ownership/
Devancore Post-Trade Glossary
Beneficial vs Direct Ownership
Direct owners are recorded on issuer-level books; beneficial owners hold their economic interest through an intermediary, custodian, or depository account.
Definition
Beneficial ownership and direct ownership describe the legal and operational route through which an investor holds a security. The distinction begins with the issuer-level holder record. A direct owner, also called a registered owner or record holder, appears on that record in the investor's own name. A beneficial owner holds through one or more intermediaries, such as a broker-dealer, bank, custodian, clearing participant, or depository nominee.
The distinction remains relevant when the security is represented through distributed ledger technology. A token, wallet address, smart contract, or blockchain transaction records technical state. It does not, by itself, identify whether the holder is directly registered with the issuer, holds a security entitlement against an intermediary, controls an omnibus custody account, or has a contractual claim against a separate provider. The governing documents and designated records establish that relationship.
The holding relationship comes first
Issuer records, transfer-agent records, depository positions, custodian books, broker customer accounts, and wallet mappings can each carry important information. Their meaning depends on the role assigned to each record. An institution reviewing a tokenized product should therefore start with four questions:
- Who is recorded at the issuer level for the underlying security?
- Does the investor hold directly, through a securities account, or through another contractual arrangement?
- Which party maintains the record that establishes the investor's position?
- How are wallet authority, account authority, restrictions, and servicing instructions linked?
The SEC's January 2026 staff statement on tokenized securities uses a related distinction. An issuer-sponsored model can integrate distributed ledger technology into an issuer's master securityholder file or a connected process. A third-party custodial model can give the customer an entitlement through an intermediary. The staff statement is guidance rather than a Commission rule, and the implementation details remain specific to the product and applicable requirements.
Holding-chain map
| Holding arrangement | Issuer-level record | Investor-level record | Rights and servicing path |
|---|---|---|---|
| Direct registration | Investor recorded on issuer or transfer-agent holder file | Direct registration statement or account record | Issuer or transfer agent communicates and services the holder directly |
| Street-name holding | Nominee or intermediary appears on issuer-level record | Broker or bank securities account | Rights and payments pass through the intermediary chain |
| Depository-held position | Depository nominee, commonly Cede & Co. for DTC-eligible securities | Participant and downstream customer records | Issuer, depository, participant, and customer-account processes each perform a defined role |
| Issuer-sponsored tokenized security | Ledger, transfer-agent file, or linked arrangement designated by programme documents | Verified holder and wallet relationship | The programme defines how registration, transfer, distributions, and voting are serviced |
| Tokenized entitlement | Underlying security remains in a custody or depository chain | Intermediary account and tokenized-entitlement record | The intermediary and its providers administer rights under the entitlement arrangement |
Direct registration and the record holder
Direct registration means the investor is recorded in its own name on the issuer's official holder file, often maintained by a transfer agent. It can be certificated or uncertificated. The Direct Registration System, or DRS, supports book-entry direct registration without requiring a physical certificate. An investor can therefore be directly registered even though every relevant record is electronic.
The direct holder relationship gives the issuer or its agent a direct record for communications and servicing. Dividend payments, annual reports, proxy materials, and corporate-action notices can be delivered using that holder record, subject to the issuer's governing documents and the relevant procedures. Direct registration has its own operational path for transfers and trading. A holder may need to use a broker or other provider to access a particular trading venue or settlement arrangement.
Direct registration does not eliminate the need for controls. The holder file must still identify the instrument, class, quantity, legal name, address, authority, restrictions, and transaction history required for the arrangement. Where a wallet is used, the program also needs a process for linking the wallet to the registered holder, approving a wallet change, handling key loss or compromise, and preserving the evidence supporting a transfer.
Street name and beneficial ownership
Most actively traded U.S. securities are held through an intermediated chain. The issuer-level record may show a depository nominee or an intermediary rather than the investor's name. The investor's broker, bank, or custodian maintains the account record showing the customer's position. This arrangement is commonly described as holding securities in street name.
In the DTC environment, eligible securities are generally registered in the name of DTC's nominee, Cede & Co. DTC records positions for its participants, while those participants and other intermediaries maintain their own customer-level records. The issuer therefore does not ordinarily see every ultimate beneficial owner from the issuer-level register or DTC's participant position records. Other disclosure, proxy, and issuer-services processes may be used to communicate through the chain.
The intermediary model supports centralised clearing, settlement, custody, financing, and high-volume processing. It also distributes information and servicing responsibilities. The issuer, depository, participant, broker, custodian, and account holder may each have a role in a single corporate event. An operational team needs a complete map of those roles before assuming that a customer-facing balance is sufficient for voting, payment, tender, or transfer.
Beneficial owner and entitlement holder
Beneficial owner is a broad term. It commonly identifies the person who has the economic interest in a security even though another party appears as record holder. The expression can be relevant to securities operations, tax administration, disclosure, custody, and corporate communications.
Entitlement holder is more specific. Under UCC Article 8, it refers to a person identified in a securities intermediary's records as having a security entitlement against that intermediary. The securities account and related entitlement establish the customer's relationship with the intermediary. Article 8 also provides rules concerning the financial asset credited to the account and the intermediary's duties in relation to entitlement orders.
In a conventional broker account, the investor will often be both the practical beneficial owner and an Article 8 entitlement holder. The labels should nevertheless be used with care. Beneficial ownership may also arise through trusts, funds, nominee arrangements, or other structures whose legal analysis does not reduce to the same account relationship. A product design should identify the actual holder, account, intermediary, and right rather than relying on a general label.
Article 8 is particularly important to intermediated tokenization. A token that is issued or administered by a custodian can represent a position held through that custodian. The token may make the position easier to transfer or observe within a programme, but the customer relationship remains defined by the custody and entitlement arrangement. Article 04, Security Entitlement, explains this account-based framework in greater detail.
How rights move through the chain
A corporate action makes the distinction visible. For a directly registered position, the issuer, transfer agent, or paying agent can use the issuer-level holder record to determine notice, distribution, and voting processes. For an intermediated position, the issuer's instructions and cash or securities movements travel through the depository and participant structure. The intermediary then uses its customer records to allocate the event and collect any instructions.
Timing matters. Record dates, ex-dates, election deadlines, settlement status, and internal cut-off times can differ. An investor in street name may need to give instructions before the issuer's published deadline because the broker or custodian must process the instruction upstream. A tokenized system must make its snapshot rule and event hierarchy explicit, particularly where an onchain balance changes close to a record date.
Corporate actions across holding models
| Event | Direct registration | Intermediated holding | Tokenized design question |
|---|---|---|---|
| Dividend or coupon | Issuer or paying agent follows direct holder record | Funds move through depository, participant, and customer-account records | Which record identifies the eligible holder and payment instruction? |
| Proxy voting | Materials and voting process reach the registered holder | Voting instructions move through the intermediary chain | How does the system link a record-date token position to an eligible person or account? |
| Tender or election | Holder follows the issuer or exchange-agent process | Customer instructs intermediary before its operational deadline | Which instruction is valid when wallet authority and account authority differ? |
| Transfer | Designated holder record is updated under the programme process | Intermediary debits and credits securities accounts through its settlement process | Which event establishes completion: a network event, a book entry, or both? |
| Tax reporting | Transfer agent or other responsible party uses direct holder data | Broker or bank generally reports through the customer relationship | Where are tax status, withholding, and reporting evidence maintained? |
Three tokenized ownership patterns
In an issuer-sponsored direct model, the distributed ledger may form part of the issuer's master securityholder file or connect to it under a defined transfer-agent process. The investor can be directly registered, and an allowlisted wallet can be linked to that holder record. A programme should specify whether a validated ledger event updates the record immediately, requires a transfer-agent posting, or follows another sequence.
A second model retains an offchain issuer holder file while using the token as a transfer instruction, evidence source, or operational representation. The transfer agent or responsible party validates the event and updates the issuer-level record. The holder may still be directly registered, but the network confirmation and the issuer-record posting can be distinct events.
A third model tokenizes an entitlement held through a custodian, broker, or depository arrangement. DTC's 2025 no-action letter describes a particular tokenized-entitlement structure in which the underlying securities remain registered to Cede & Co. and DTC administers tokenization entitlements through its stated system. That fact pattern illustrates an indirect holding model; it does not define every tokenized product.
These structures can look similar at the wallet layer. Their rights, records, transfer conditions, insolvency analysis, corporate-action processes, and regulatory roles can differ substantially. Classification before implementation helps operations, legal, compliance, and technology teams apply the correct controls.
Wallet control is an authority layer
A private key enables a party to sign a transaction for a wallet address under the relevant network rules. In institutional securities operations, that authority must be connected to the account and holding relationship. The same wallet can be controlled by a natural person, a legal entity, an authorised agent, a qualified custodian, or an omnibus provider acting for many downstream customers.
A wallet map commonly needs supporting information: the legal entity or customer account, authorised signers, custody status, sanctions and eligibility controls, tax and jurisdictional information, instrument restrictions, and the process for changing or retiring an address. The appropriate evidence depends on the product. The core principle is consistent: a wallet address cannot independently answer who is entitled to receive a distribution, instruct a tender, vote a security, or transfer a restricted position.
Omnibus wallets require particular discipline. One address may contain positions for multiple downstream customers. The custodian's internal records then identify allocations, customer rights, and servicing outcomes. This is a tokenized version of a familiar market-infrastructure problem: the public or shared ledger layer must be reconciled with the controlled account records that identify the actual customer relationship.
Operating the holding topology
Institutions need a holding-model inventory for each instrument and programme. It should identify the issuer, transfer agent where applicable, depository or custodian, participant, customer account, token contract, wallet relationship, record hierarchy, and corporate-action workflow. The inventory should also state which party can approve an instruction, correct an error, freeze a transfer, replace a wallet, or resolve an unavailable or disputed position.
Reconciliation follows the topology. A direct model may compare the master securityholder file, related ledger state, verified holder mapping, and outstanding quantity. An indirect model may compare the underlying eligible or allocated position, intermediary entitlement record, wallet state, and downstream customer accounts. The team should preserve evidence for each comparison and assign ownership for breaks.
Devancore can classify direct and indirect holding structures within a security master, map issuer, intermediary, account, wallet, and provider relationships, and coordinate reconciliation and lifecycle workflows across rails. One hybrid core provides an operating view across traditional, tokenized, and onchain records while preserving the responsible parties and their authoritative systems.
Devancore does not act as a transfer agent, broker-dealer, custodian, depository, or issuer; maintain an official statutory holder record; establish legal title; or determine the legal effect of a transfer. Those responsibilities remain with the designated parties and records in the relevant structure.
Direct and intermediated holding
Devancore Glossary · devancore.com
How it works
Classify the holding relationship
The institution determines whether the investor is directly registered, holds through a securities intermediary, or has another contractual arrangement. It records the issuer-level holder, the customer-level account, and the legal and operational relationship between them.
Map rights, authority, and records
The operating model links the instrument, transfer-agent or intermediary records, customer account, wallet, authorised parties, restrictions, and corporate-action processes. It identifies the record used for each decision and the party responsible for each update.
Reconcile through the lifecycle
Operations compare the relevant issuer, custody, account, and token records through transfers, record dates, distributions, conversions, and exceptions. A break is routed to the party responsible for the designated record and resolved with an evidence trail.
Holding-model control
Devancore Glossary · devancore.com
In Devancore™
Devancore — holding topology
Devancore Glossary · devancore.com
Devancore can connect holding-model data across issuer, intermediary, custody, account, and wallet systems. It helps teams maintain a security-level view of direct registrations, security entitlements, controlled wallet relationships, lifecycle events, and reconciliation exceptions without forcing records into one ledger.
Devancore does not custody assets, act as a transfer agent, maintain an issuer's official holder file, determine beneficial ownership, or establish legal title. The responsible parties retain their records, controls, and legal responsibilities.
Related terms
- Tokenized Security Entitlement
https://devancore.com/glossary/tokenized-security-entitlement/
A tokenized security entitlement represents an indirect interest in a financial asset held through a securities intermediary. Its operating model connects custody positions, securities accounts, wallet controls, and authoritative records.
- Master Securityholder File
https://devancore.com/glossary/master-securityholder-file/
The master securityholder file is the official list of individual securityholder accounts in the transfer-agent recordkeeping framework.
- Authoritative Record Tokenized Securities
https://devancore.com/glossary/authoritative-record-tokenized-securities/
An authoritative record is the designated source that controls a specific legal or operational fact about a security or tokenized security.
- Onchain vs Offchain Records
https://devancore.com/glossary/onchain-records-vs-offchain-records/
Onchain records are maintained on a distributed ledger; offchain records are maintained in connected enterprise and market-infrastructure systems.
- Registered Wallet for Tokenized Securities
https://devancore.com/glossary/registered-wallet-tokenized-securities/
A registered wallet is an approved blockchain address linked to a verified participant or account for controlled holding and transfer of tokenized securities.
- Corporate Actions for Tokenized Securities
https://devancore.com/glossary/corporate-actions-tokenized-securities/
Corporate actions for tokenized securities coordinate issuer events, account entitlements, wallet records, instructions, and outcomes across conventional and onchain rails.
Contact
Request a briefing or platform walkthrough with the Devancore team.
Request access https://devancore.com/access/