A token can appear in a wallet while other records still show a pending allocation. Conversely, an investor register can be updated before the intended digital representation has moved. A future servicing operation must decide which records establish entitlement and how the related systems remain reconciled, with the actual legal and product structure determining their respective roles.
Name the authoritative records
The instrument documents should explain the relationship among the issuer's register, platform records and any distributed ledger. Qualified advisers must establish the legal effect of those records for the actual product. BIS's analysis emphasises the arrangements behind tokenised representations. The operating implication is to define the hierarchy before processing begins. A hypothetical investor should not have to infer legal ownership from a transaction hash when the product uses a different authoritative register. Support staff need the same explanation, including how a discrepancy is investigated and which party can authorise a correction to a record relied on for servicing.
Control the issuance instruction
An issuance should connect to an accepted allocation, the required settlement conditions and a unique instruction. Approval, execution and confirmation need a clear record. The process should prevent a retry from producing a second allocation or additional tokens unintentionally. CPSS-IOSCO's principles concerning issue integrity and operational risk provide reference points. They do not establish regulatory status for a platform. The owner should commission tests of ordinary instructions and exceptions, including interrupted processing. A successful demonstration of a token transfer alone would leave the allocation, authority and register-reconciliation requirements of a complete issuance process unfinished.
Reconcile quantities and identities
The operation should compare the relevant totals and account-level information, with timing differences distinguished from errors. Opening balances, new issues, cancellations and transfers need to explain closing positions. A hypothetical batch whose aggregate total matches can still contain allocations assigned to the wrong investors. The review should therefore operate at a resolution suited to the product and risk. Owners need an exceptions process with responsible parties and controlled corrections. Investors should receive confirmations that use the same units and account identity as their ongoing statements, allowing an allocation to remain traceable after later transfers, distributions or other servicing events change the account.
Preserve evidence beyond the launch
The final record should identify the accepted instruction, authorisations, execution details and confirmed resulting position. Later amendments need history rather than silent replacement. The ALFA utility-token design does not grant automatic rights in instruments supported by the infrastructure programme. Any such product would need its own documents and servicing arrangements. The practical readiness test is a coherent investor record across the whole instruction lifecycle, including failure and correction. It allows the platform, issuer and investor to understand the same entitlement without relying on a single screen whose relationship to the governing records remains unspecified.
