One Economic Right, Multiple Records

The quantity that must remain singular

An economic right can refer to an issued share, debt principal amount, Article 8 security entitlement, collateral allocation, corporate-action allocation, or another defined financial interest. The relevant unit may be fractional or denominated differently across systems. A token unit can represent a fraction of a share, a bond denomination, or a unitized interest. Parity concerns the defined relationship between quantities, rather than an assumption that one token always equals one share.

A useful operational expression is:

outstanding represented quantity ≤ eligible underlying quantity

The precise calculation follows the model. In a direct issuer structure, operations may compare the master securityholder file, the token contract state, and linked offchain records. In a custodial entitlement structure, they may compare the eligible or immobilized underlying position, the intermediary entitlement record, and outstanding tokenized entitlements. In a conversion workflow, the comparison can include traditional-form balance, reserved or pending conversion quantity, active tokenized quantity, and retired quantity.

The word “eligible” matters. A gross custody position may include quantity pledged elsewhere, restricted from transfer, pending settlement, or allocated to another purpose. The backing quantity must be the pool designated for tokenized representation. Class, series, restriction, record-date status, and associated rights can make superficially similar units operationally distinct.

Record hierarchy and fact ownership

A robust design does not rely on a universal master ledger. Different records can govern different facts. The issuer or transfer agent may govern registered holder and issued-capital facts. A securities intermediary can govern the customer entitlement credited to a securities account. A depository can govern participant-level positions. A token contract records the network's token state. A payment record establishes completion of a cash movement. A corporate-action record may govern eligibility, election, and allocation for a specific event.

Article 07, Authoritative Record, addresses this fact-by-fact hierarchy. An operating model should document it before launch. The institution needs to identify which record controls if a token balance differs from a custody account, which party may correct a failed conversion, and how a wallet mapping is updated after a key rotation, merger, court order, or account closure.

Reconciliation compares records; it does not independently establish legal title. It detects whether defined quantities, statuses, and relationships align. The governing documents and designated record hierarchy determine the legal effect of a divergence. This distinction keeps an operational control from being mistaken for a legal conclusion.

Four controls that preserve parity

Allocation control establishes the source position before representation begins. The workflow identifies the instrument, class, quantity, source account, restriction status, and responsible provider. Only quantity that is issued, eligible, and assigned to the programme can enter the tokenization or representation process.

Supply control governs minting, burning, reissuance, and conversion. The programme assigns authority for those functions, applies separation of duties and approval procedures appropriate to the risk, and compares outstanding supply with the relevant backing quantity. The source position is reserved or immobilized while the corresponding representation is active, so it cannot be made independently available for an incompatible transfer, pledge, or settlement process.

Lifecycle control connects transfers, restrictions, conversions, redemptions, and corporate actions across records. Each material state needs a defined meaning. A position can be reserved, pending mint, active, restricted, frozen, pending burn, or re-credited. Clear state labels let teams distinguish a temporary in-flight difference from an unresolved break.

Reconciliation and exception control compares quantity, status, instrument identity, account or wallet mapping, and lifecycle events. The process needs materiality thresholds, aging rules, evidence requirements, a responsible owner, and an authorised correction path. A break is not resolved simply because one system has been changed; the responsible team must confirm that all linked records now support the permitted state.

Conversion is a controlled state change

Tokenization and de-tokenization can be understood as controlled changes in representation or record rail. They are not automatically secondary trades, and the tax, legal, accounting, and regulatory treatment of any particular process depends on the governing facts and applicable rules. The operational requirement is that the source position and the represented quantity move through a controlled sequence.

DTC's December 2025 no-action letter provides a fact-specific illustration. In the preliminary service described to SEC staff, a DTC participant instructs DTC to tokenize an eligible entitlement held in the participant's account. DTC debits that position, credits the corresponding amount to a Digital Omnibus Account, and mints a tokenized entitlement to the participant's registered wallet. For de-tokenization, the token is burned and the related amount is re-credited to the participant's account.

The letter also describes controls intended to avoid a double use of the represented position. The Digital Omnibus Account quantity is not available for conventional DTC transfer until the related token is burned. DTC's LedgerScan records the tokenized entitlements for the stated service. The underlying securities remain registered to Cede & Co. This is a defined DTC arrangement, not a universal blueprint for tokenized securities.

Issuer-sponsored structures can apply a different sequence. Distributed ledger technology can form part of the master securityholder file, while identity, contact, and compliance information remains in linked offchain systems. The programme still needs an explicit rule for issue, transfer, correction, conversion, and the quantity recognised in each state.

Managing asynchronous timing differences

Onchain and offchain systems do not always update at the same moment. A network event may be confirmed before a transfer-agent or custody posting is complete. A position may be reserved while mint approval is pending. A token may be burned while book-entry re-credit awaits an operating window. A restriction review may remain open after a token event has been observed.

These timing differences can be managed when the status is explicit. The institution should identify the owner of each pending event, the maximum aging period, permitted actions, and escalation path. The lifecycle status must show whether the difference is expected, contained, or unresolved.

Timing parity differs from economic parity. Temporary state differences can exist during a controlled workflow. The total economic claim must remain within the defined eligible quantity throughout that workflow. The programme should prevent a pending or active representation from being treated as freely available in another rail unless the terms expressly support that use.

Corporate actions are the ultimate parity test

Corporate actions bring every layer into one event. A dividend, split, merger, tender, conversion, rights offering, or vote requires the institution to determine eligibility, quantity, authority, allocation, and evidence at a specific point in time. A weak cross-rail design can pay a dividend twice, accept conflicting votes, miss a split adjustment, or allocate new consideration to an ineligible wallet.

A controlled corporate-action sequence begins with the event terms and record-date hierarchy. Operations freeze or snapshot the relevant records, compare eligible quantities, validate account and instruction authority, process the event through its designated channels, update token and offchain positions, and reconcile the completed outcome. Residual breaks are investigated before final accounting and reporting are treated as complete.

Raw wallet balances do not answer every event question. The process may need to determine whether the wallet is mapped to an eligible account, whether the position is subject to a restriction, whether a transfer was pending at the cut-off, and whether a custodian holds the address on behalf of multiple downstream customers. Article 10, Tokenized Security Rights Entitlements, sets out the related rights and servicing framework.

What reconciliation must prove

Institutional reconciliation goes beyond comparing two totals. It should be able to connect the instrument and class to the token contract and network, identify the quantity permitted for representation, map wallets to approved accounts or holders, and compare restriction, collateral, and lifecycle status across each relevant record. It should also trace every conversion, distribution, split, redemption, and correction through a retained evidence trail.

The expected service level varies by product and provider. Not every system needs to update at the same millisecond, and not every fact belongs on a shared ledger. The standard is a controlled process: the institution can identify the source and effect of a difference, contain it where necessary, assign it to a responsible party, and demonstrate resolution.

Devancore can map a financial instrument across issuer, depository, custody, broker, token, wallet, cash, and corporate-action records. One hybrid core helps teams monitor position parity, conversion status, restriction alignment, and lifecycle evidence across traditional, tokenized, and onchain rails. It can route exceptions to the provider responsible for the governing record without forcing institutions to replace their established systems.

Devancore does not issue securities, create legal rights, act as a transfer agent, custodian, broker-dealer, clearing agency, depository, or paying agent, determine an authoritative record, or establish legal ownership. Those responsibilities remain with the designated parties and the governing documentation.