ProcessAsset Tokenization Studio
The tokenised bond lifecycle, event by event, from term sheet to closed register
A tokenised bond goes through the same events as any other bond: issuance, transfers, coupons, exceptions and redemption. What changes is where each event is recorded and who checks it. This page follows a clearly hypothetical fixed-rate note through every stage, shows which Asset Tokenization Studio feature handles it, names the party that stays accountable, and marks the point where token and register must be reconciled.
On this page
- The hypothetical note followed on this page
- The parties a token does not replace
- Seven stages from term sheet to closed register
- Running each event on Asset Tokenization Studio
- Choosing how cash moves at issue and on coupon dates
- Which record wins at each lifecycle event
- Exception procedures to agree before the first investor buys
- Questions and answers
- Sources
The hypothetical note followed on this page
The parties a token does not replace
- Issuer
- Owes the coupons and principal, approves the token configuration and holds ultimate responsibility for every administrative action taken in its name.
- Arranger
- Structures the note, gathers investor demand and coordinates documentation; for a token, it also confirms investors can receive and hold it.
- Paying agent
- Calculates and pays coupons and principal. With a token it pays against a snapshot, or operates the on-chain distribution.
- Registrar or central securities depository
- Keeps the record of holders the law recognises. The token's balances must agree with that record, or replace it only where the law allows.
- Custodian
- Holds investors' or the issuer's keys and assets, runs signing ceremonies and handles recovery when a key is lost.
- KYC provider
- Verifies investors and keeps evidence; its approvals feed the token's on-chain KYC registry with an expiry date.
Seven stages from term sheet to closed register
- Term sheet
Commercial terms, restrictions and the legal form of the note are agreed.
- Token parameters
Terms become a bond configuration: nominal value, coupon schedule, maturity and eligibility rules.
- Issue and settle
Tokens are minted to verified investors against payment of the issue price.
- Holding period
Transfers are checked for eligibility, lock-ups and freezes until maturity.
- Coupon cycle
Each coupon date repeats a snapshot, an entitlement calculation and a payment.
- Maturity and redemption
Principal is paid and the tokens are taken out of circulation.
- Register closed
Final reconciliation, archived records and a security with no holders left.
Running each event on Asset Tokenization Studio
Feature names are those used in the Studio's capabilities overview1; the owner is the party accountable for the outcome, not the person pressing the button.
Turn the term sheet into a bond configuration
Enter nominal value, currency, coupon rate, payment dates and maturity using the Studio's coupon configuration, maturity management and nominal value tracking. Encode eligibility as KYC requirements and control lists, and record which clause of the term sheet each parameter comes from.
Issue against payment
Mint to each verified investor only when the issue price has arrived. A hold can escrow the tokens until the cash leg is confirmed, then be executed, or released if payment fails.
Police transfers during the holding period
Every transfer is checked against KYC validity, allowlists and freezes. A post-issue lock-up can be enforced with a partial freeze, and clearing workflows can require approval before a secondary transfer executes.
Fix entitlements at each record date
Take a balance snapshot at the record date, calculate each holder's coupon from it, and reconcile the snapshot against the register before any money moves.
Pay the coupon
Pay from the entitlement list, either off-chain by bank transfer or on-chain through Mass Payout, which can distribute HBAR or an HTS token such as a stablecoin2. Record failed or returned payments against the holder, not the token.
Handle exceptions under instruction
Use freeze account, forced transfer or forced redemption only against a documented instruction, such as a court order, a sanctions determination or a verified lost-key claim, and log the instruction alongside the transaction.
Redeem at maturity and close the register
Snapshot holders at the final record date, pay principal and the last coupon, then use maturity redemption to take the tokens out of circulation. Reconcile one last time and archive the records the law requires.
Choosing how cash moves at issue and on coupon dates
- If
Investors and the issuer bank conventionally and the pilot is about the security, not the payment.
ThenSettle and pay in fiat through the paying agent, using holds to release tokens once payment is confirmed.
It keeps payment risk where it already sits and limits the pilot to one new system.
- If
All parties can hold a regulated stablecoin on Hedera and accept its issuer risk.
ThenPay coupons with Mass Payout in that stablecoin and agree how a holder without a funded account is handled.
Both legs on one network make atomic settlement possible and simplify reconciliation.
- If
The investors are banks or large corporates that prefer bank money.
ThenExplore a tokenised deposit for the cash leg; our tokenised deposits guide compares the options.
It keeps the cash leg as a claim on a regulated bank rather than on a stablecoin issuer.
Which record wins at each lifecycle event
Decide this before launch. When the token and the register disagree, this table says which one is corrected.
| Event | Authoritative record | Token-side evidence | Reconciliation check |
|---|---|---|---|
| Issuance | Allocation agreed by issuer and arranger | Mint transactions per investor | Minted amounts equal allocations and cash received |
| Secondary transfer | Register of record, unless law makes the ledger authoritative | Transfer events and clearing approvals | Daily comparison of balances by holder |
| Record date | Register at the record date | Balance snapshot | Snapshot equals register before entitlements are calculated |
| Coupon payment | Paying agent's payment records | Mass Payout transactions, if paid on-chain | Each entitlement matched to a payment or an exception |
| Forced transfer or freeze | The instruction or order behind it | Controller transaction and event | Every controller action matched to a filed instruction |
| Redemption | Paying agent's principal payments | Redemption transactions and remaining supply | Outstanding supply reaches zero only after all principal is paid |
Exception procedures to agree before the first investor buys
Questions and answers
Can a tokenised bond pay its coupons in a stablecoin?
Technically yes: Asset Tokenization Studio's Mass Payout module can distribute an HTS token, which includes a stablecoin issued on Hedera. Whether you should depends on the bond documentation, which must name the payment currency and method, on every holder being able to receive that token, and on the parties' view of the stablecoin issuer's risk. Many pilots keep fiat payments first.
Who keeps the official register of a tokenised bond?
Usually the same party as for a conventional bond: a registrar, transfer agent or central securities depository, with the token reconciled to its record. Some regimes allow a distributed ledger to serve as the record, for example market infrastructures operating under the EU's DLT Pilot Regime, Regulation (EU) 2022/8583. Counsel must confirm which applies before you decide the token is authoritative.
What changes for a floating-rate note?
Each coupon depends on a reference rate observed shortly before the payment date, so the coupon amount cannot be fixed at issue. The Studio supports floating structures and rate adjustment, but someone must observe the rate, apply the margin and enter it, and a second person should check it. Document the rate source, fallback and approval for every coupon period.
What happens to a holder whose KYC lapses before a coupon date?
The answer is a policy choice to make before launch. An expired approval normally blocks transfers to and from the holder, but it does not end their legal right to interest. Most issuers will want to pay or escrow the coupon while prompting the holder to renew, so the procedure and the record of each case should be agreed with counsel.
Sources
- ATS capabilities overview — Hashgraph on GitHub · checked 10 October 2026
- Asset Tokenization Studio repository (Mass Payout) — Hashgraph on GitHub · checked 10 October 2026
- Regulation (EU) 2022/858 on a pilot regime for market infrastructures based on distributed ledger technology — EUR-Lex · checked 10 October 2026