Issuing a token is a discrete event. Servicing the security is an ongoing obligation. Dividends, coupons, redemptions and investor elections require reliable information about the event and about who is entitled to receive what. A ledger can improve coordination, but a token balance does not automatically answer every question about ownership, eligibility or payment. Institutional diligence should follow a corporate action from the issuer’s announcement to the investor’s final receipt.
The announcement must become trusted data
Corporate actions begin with information, often supplied through several intermediaries. The terms need to identify the security, event, dates, calculation method and any investor choices. A mistake in one field can affect a large population of holders. Automating distribution is useful only after the event data has been validated and the responsibility for correcting it is clear.
Swift’s corporate-actions work describes the difficulty of harmonising data across the investment chain and explores shared technology to reduce friction. This is evidence of the coordination problem and an approach to it, not proof that every tokenised security has automated servicing. Our piece on token identifiers and reference data explains why consistent asset identification belongs at the beginning of that process.
Define the entitlement record
The relevant holding may be established by an issuer register, a central securities depository, a custodian account or a ledger specified in the instrument’s terms. Identify which record prevails and how holdings are captured at the required time. A current wallet balance is not necessarily the balance that determines entitlement for a past record date. Transfers in progress also need a defined treatment.
Our article on what a tokenised stock holder owns sets out why the legal claim matters. Servicing depends on the same distinction. A holder of a contractual instrument linked to a share may have different rights and a different payment intermediary from the registered shareholder. The servicing model must follow the actual instrument rather than assume that all tokens representing the same company share identical rights.
Cash dividends and elections are different workflows
For a mandatory payment, the system calculates an entitlement and delivers cash or another asset. For an elective event, it must also communicate options, collect instructions and apply deadlines. A token moving continuously on a network does not remove the need for a cutoff. Explain how late instructions, incomplete information and holders represented through intermediaries are handled.
Swift’s corporate-actions application criteria distinguish mandatory and elective workflows and include notifications, entitlement calculation and account activity confirmation. Applied to tokenised instruments, this is a useful process map. The ledger should support those business steps, rather than compressing them into a single token transfer labelled completed.
Corrections need a governed path
Announcements can be corrected, payment amounts disputed and historical ownership records reconciled. Decide whether the system recalculates automatically, issues a compensating payment or pauses for review. Retain the original event and its replacement so investors and auditors can reconstruct the decision. A permanent transaction record is valuable, but permanence does not make a mistaken entitlement correct.
The final payment also has its own dependencies: the chosen currency or token, the receiving account, restrictions on transfer and any withholding calculation. Test a full event with a rejected payment, a holder change near the record time and a corrected announcement. The Jorgen Ouaknine speaker profile connects to the wider securities-infrastructure discussion. Production readiness means showing that an investor receives the correct entitlement with a usable explanation, even when the records require correction.
Keep the investor explanation consistent
The issuer, servicer, custodian and client-facing platform should use the same event identifier and explain the same entitlement. If one system reports a dividend paid while another shows it pending, establish which milestone each label represents and align the customer explanation. Capture the record-date holding, applied calculation and payment identifier in an accessible record. That also makes an investor query actionable: the team can distinguish a disputed holding from a failed delivery or an incorrect rate. Servicing quality becomes visible in resolved exceptions, not merely in the number of token payments sent.