RWA Infrastructure10 min read
MB
Editorial Team
·November 3, 2026

How Should a Tokenized Bond Use ICMA's Bond Data Taxonomy?

The ICMA Bond Data Taxonomy (BDT) is a standardised, machine-readable language for the key terms in a bond term sheet, from issue amount and coupon to governing law, selling restrictions and DLT details. Version 2.0, published on 27 April 2026, grew it from over 100 to over 300 fields. For a tokenized bond, the practical answer is a BDT record the smart contract points to, not a contract that is the only copy of the terms.

TL;DR — Key Takeaways

  • ✓What it is: ICMA's Bond Data Taxonomy is an XML vocabulary for the terms in a bond term sheet. It is free, voluntary and technology agnostic, built for both traditional and tokenised bonds.
  • ✓Version 2.0: Published 27 April 2026. Over 300 fields, up from over 100, with support for programmes, multiple tranches, taps and global notes. ICMA's download pack is now labelled 2.1, last updated 20 August 2026.
  • ✓DLT fields: A DLT Bond Indicator, platform identifiers such as LEI or DTI, smart contract name, description, type and public key, token type, and on-chain or off-chain custody.
  • ✓Our recommendation: Keep the full term set in a BDT record, mirror only what the contract computes on, and enforce only what must block a transfer. The legal documents prevail over both, as ICMA states.

Ready to get started?

Join others who are already using our platform.

How Should a Tokenized Bond Use ICMA's Bond Data Taxonomy?

Why do tokenized bonds still get re-keyed?

Because most token contracts encode the economics a contract needs, such as balances and coupon logic, while the full term sheet stays a PDF. Every custodian, agent and depository then types those terms into its own systems again.

A token standard defines how a balance moves and who may hold it. It does not define how a bond's governing law, selling restrictions, denominations or tranche structure are described. Those terms live in the offering documents. A tokenized bond can settle on-chain and still need the same manual set-up of static data that a paper bond needs, at each firm that touches it. Our guide to RWA token standards covers what ERC-3643, ERC-1400 and similar standards control; this article covers the layer underneath them, the bond's terms as data.

ICMA's Bond Data Taxonomy (BDT) is the market's attempt to make that layer shared. The question for a tokenization team is not whether to adopt it in the abstract. It is which terms belong in the BDT record, which belong in contract state, and which must be enforced by the contract.

“The BDT is a standardised, machine-readable language for key bond information typically contained in a bond term sheet.”

ICMA, Bond Data Taxonomy FAQs, April 2026, question 1.1

What does the ICMA Bond Data Taxonomy contain?

Seven documents: three XSD schema files, example XML files, a reference spreadsheet, a user guide and an introductory presentation. It is built on the 2001 W3C XML Schema standard, uses ISO definitions where they exist, and is also available in JSON.

ICMA's April 2026 FAQs list the components:

  • BDT XSD: the overall structure of a bond issuance and its key fields.
  • Enumerations XSD: the allowed values for coded fields.
  • Type Restrictions XSD: ISO and other data type rules.
  • Example files: term-sheet or final-terms data in XML. The current pack includes a DLT-based issuance example and a multi-class issuance example.
  • Reference Sheet: a spreadsheet of fields with XML and ISO definitions, an enumeration list and a tab of changes from version 1.2 to 2.0.
  • User Guide and an Introduction to BDT 2.0 presentation.

The taxonomy is free to members and non-members. ICMA grants a worldwide, royalty-free licence to use and implement it in internal systems, documentation, products and services. Two limits matter to vendors: the BDT cannot be sold as a standalone product, and a modified version cannot be presented as an official ICMA taxonomy. ICMA provides it “as is”, with no warranty on accuracy or completeness.

Governance sits with ICMA's Bond Data Taxonomy Working Group, which is open to all ICMA members. Its published participant list includes Clearstream, Euroclear, DTCC, SIX Group, Swift, SG Forge and the World Bank, alongside banks, law firms and data vendors. There is no fixed release schedule. Changes follow working-group feedback and market implementations.

What changed between BDT 1.2 and 2.0?

Version 2.0 expanded the field count from over 100 to over 300 and moved from the plain vanilla bond to issuance programmes, multiple tranches, taps and global notes. Version 1.2, released in February 2024, had already added a DLT extension.

ReleaseDateWhat it added (per ICMA)
First releaseMarch 2023A composite list of over 100 fields for key term-sheet data
Version 1.2February 2024DLT extension for DLT-based or tokenised debt instruments
Version 2.027 April 2026Over 300 fields; programmes, standalone issues, multiple tranches, taps, global notes; more registration, safekeeping and asset-servicing detail; more DLT features; SeriesTrancheClass group
Download pack 2.1Last updated 20 August 2026Listed on ICMA's BDT page, which does not summarise its changes

The SeriesTrancheClass group is the change with the most direct effect on token design. ICMA's FAQs describe it as the place to define the details of each note “while inheriting many common elements from the parent issuance.” A bond with two tranches has one parent record and two child records. A token design that issues one token contract for the whole programme has nowhere to put that distinction.

“The launch of the Bond Data Taxonomy version 2.0 marks an important step forward in the market's ability to communicate bond terms in a consistent, open and machine-readable way.”

Bryan Pascoe, ICMA Chief Executive, ICMA release of 27 April 2026

Which DLT fields does BDT define for a tokenized bond?

Seven items plus custody: a DLT Bond Indicator, platform identifiers such as an LEI or DTI, the smart contract's name, description, contract type and public key, the token type, and whether custody sits on an on-chain or off-chain platform.

These fields, listed in question 7.1 of ICMA's FAQs, answer one narrow question: where does this bond live on a ledger, and what is the contract? An LEI (Legal Entity Identifier) identifies a legal entity such as a platform operator. A DTI (Digital Token Identifier) identifies a digital token. With both, a custodian or depository can link the bond's static data to a specific ledger and contract without asking the arranger by email.

ICMA is careful about how far this goes. Question 7.2 says that “in some market implementations” the BDT is used to communicate the issuance conditions of the security to a smart contract, and that “conceptually” it could define the legal terms in digital form from the outset. That is a statement of possibility, not a requirement. One public example listed on ICMA's BDT page is DZ Bank's Smart Bond Contract concept: a May 2025 white paper describing a standardised data format based on the BDT, followed in March 2026 by a crypto security issued under Germany's Electronic Securities Act (eWpG), with KfW as investor.

“Custody arrangements can also be defined through indicating on-chain or off-chain platforms.”

ICMA, Bond Data Taxonomy FAQs, April 2026, question 7.1

Which terms belong in the BDT record, the contract state, or the contract's rules?

Our rule: every term goes in the BDT record; only terms the contract computes on are mirrored in contract state; only terms that must stop a transfer are enforced by the contract. This mapping is our editorial guidance, not ICMA guidance.

The BDT describes terms. It does not say how a smart contract should use them. The table below sorts the term groups ICMA names in its FAQs into three treatments.

Term groupBDT recordMirror in contract stateEnforce in contract
Issue amount, currency, denominationsYesYes: supply cap and unit sizeMint cap; minimum transfer unit
Interest and payment datesYesYes, if the contract pays couponsPayment logic only; day-count disputes stay off-chain
Maturity dateYesYesRedemption trigger; block transfers after final record date
Selling restrictionsYesAs eligibility rules, not textYes: transfer rules for investor type and jurisdiction
Governing lawYesNoNo: a legal fact, not a computable rule
Series, tranche, class (SeriesTrancheClass)YesOne identifier per trancheKeep tranches in separate balances or contracts
DLT fields (platform, contract, token type, custody)YesContract stores a pointer and hash of the recordNo; checked off-chain at onboarding

The last row is the design choice that matters. The BDT record already names the contract. If the contract also stores a reference to the record and a hash of it, the link runs both ways, and any party can check that the record it received is the one the issuer published. The record stays the readable source for agents and custodians; the contract holds only the parameters it executes.

Selling restrictions are the row where data becomes control. In the BDT they are descriptive terms. On a permissioned token they become eligibility rules that a compliance layer checks before each transfer. How those rules are enforced, and who holds the keys that change them, is covered in our guide to smart contract compliance and Layer-0 governance. Blockmaze enforces transfer rules on-chain; it does not publish or validate BDT records.

Which wins if the BDT record and the bond documents disagree?

The bond documents. ICMA's FAQs state that the BDT is not a substitute for the issuance documents, that those documents need no amendment, and that in any discrepancy the legal documentation prevails.

This sets a three-level hierarchy for a tokenized bond: the legal documents first, the BDT record second, the contract parameters third. ICMA recommends that parties using the BDT add their own disclaimers to address liability, and notes that the BDT messages contain a section for this. A token contract that executes coupon or redemption logic from mirrored parameters inherits the same position. If the parameters drift from the documents, the documents decide what is owed, and the contract's output becomes an error to correct.

“The BDT is not a substitute for the issuance documents that form the legal basis of an offering, nor do the issuance documents need to be amended to reflect the BDT.”

ICMA, Bond Data Taxonomy FAQs, April 2026, question 6.3

Where is BDT already used in digital bond issuance?

ICMA says the HKSAR Government's digital green bond of 29 September 2026, priced at around HK$20 billion, was the third issuance to adopt the BDT and aligned with version 2.0. The earlier issue of around HK$10 billion in November 2025 also used it.

ICMA's BDT page and its 27 April 2026 release list the main public references:

  • Hong Kong: ICMA welcomed the HKSAR Government digital green bonds' alignment with the BDT in February 2024, the November 2025 issue of around HK$10 billion adopted it, and the September 2026 issue of around HK$20 billion aligned with version 2.0.
  • Swift: a Digital Asset Standards platform proof of concept, announced at Sibos in October 2025, uses the BDT. ICMA and Swift are also working to integrate the BDT into ISO 20022.
  • Clearstream and Euroclear: their joint Issuance and Processing Taxonomy (IPT), part of an effort to digitise the Eurobond market, is aligned with the BDT.
  • Project Guardian: the BDT is applied in its Global Fixed Income Framework.
  • Eurosystem: a September 2025 report from the ECB's Advisory Group on Market Infrastructures for Securities and Collateral (AMI-SeCo) recommends existing market standards such as the BDT for data exchange from issuer to CSD.
  • World Bank Treasury: its SHASTRA tool, launched in August 2025, uses the BDT to create digital copies of securities terms.

The pattern is infrastructure, not individual tokens. Swift, the two ICSDs and a central bank advisory group are the adopters that make the taxonomy hard to ignore, because they are the parties that receive the static data. For an issuer weighing a digital bond, that matters more than any one deal. Our analysis of Africa Finance Corporation's CHF 350 million digital bond on SDX makes a related point: the gains from a digital bond come from register and settlement plumbing, and term data is part of that plumbing.

“The issuance aligns with Version 2.0 of the Bond Data Taxonomy (BDT), the latest major release of the standard.”

ICMA, statement on the HKSAR Government digital green bond, 29 September 2026

When does a BDT-referenced token break?

In three places: after a tap or amendment, when several tranches share one token, and when the custody field disagrees with where tokens sit. Each is a drift between the record and the chain, and none is caught by the BDT itself.

Taps and amendments

Version 2.0 can describe a tap. The contract does not update itself. Illustrative example, not a real issue: a bond launches at 500 million with a mint cap of 500 million in the contract. The issuer taps it for another 200 million and publishes an updated BDT record showing 700 million. If the cap is not raised in the same controlled change, the tap cannot be minted; if it is raised without the record, custodians see 700 million on-chain against 500 million in their static data. The fix is procedural: the record update, the contract change and the new record hash go through one approval.

Several tranches, one token

The SeriesTrancheClass group gives each tranche its own record under a parent issuance. If all tranches are minted as one fungible token, a holder's balance no longer says which tranche it holds. Coupons, maturities or selling restrictions that differ by tranche then cannot be applied from the balance alone. Separate contracts, or separate token identifiers within one contract, keep the mapping one to one.

Custody field versus reality

The BDT can record whether custody is on an on-chain or off-chain platform. That is a statement made at issuance. If the record says off-chain custody but investors can withdraw tokens to self-custodied wallets, the record misleads every downstream system that relies on it. Custody design for tokenized securities is covered in our guide to institutional RWA custody.

Who should adopt BDT, and who should not?

BDT is for bonds and notes: issuers, arrangers, paying and calculation agents, custodians and tokenization platforms that handle debt securities. In our view it is not a model for fund units or equities, which its term-sheet fields do not describe.

ICMA's FAQs describe four levels of adoption, from lightest to deepest:

  • Terminology: align internal and external terms with the BDT reference sheet.
  • Mapping: map internal data to the BDT when communicating with third parties.
  • Integration: generate BDT XML outputs from existing workflows for connected systems.
  • Golden source: use the BDT as a shared source of trade data for other market participants.

For a tokenization platform, we see the integration level as the realistic minimum: produce a BDT XML file for each issue, publish it to the parties that need it, and store its hash in the token contract. ICMA's FAQs set the technical bar low. Any platform that can create and process XML can implement it, and a JSON format is also available. The harder work is organisational: deciding who owns the record after issuance, and who approves changes to it.

Teams outside debt should not stretch the taxonomy. A tokenized money market fund or a private equity feeder has terms, such as dealing days, redemption gates and share classes, that the BDT was not built to describe. Forcing them into bond fields produces records that look standard and mean nothing to the receiving system.

Frequently Asked Questions

What is the ICMA Bond Data Taxonomy?

It is a standardised, machine-readable language for key bond information typically found in a term sheet, published by the International Capital Market Association. It covers terms such as issue amount, currency, maturity date, interest, governing law, selling restrictions and, where relevant, DLT details. It ships as XSD schema files, example XML files, a reference spreadsheet, a user guide and a presentation, and is free to download.

What changed in version 2.0 of the Bond Data Taxonomy?

Version 2.0, released in April 2026, expanded the taxonomy from over 100 fields to over 300. ICMA's FAQs say it moves beyond the plain vanilla bond of version 1 to issuance programmes, standalone issues, multiple tranches, taps and global notes, with more detail for registration, safekeeping and asset servicing and additional DLT-related features. A new SeriesTrancheClass group handles multi-tranche, series and class structures.

Which DLT fields does the Bond Data Taxonomy include?

ICMA's FAQs list a DLT Bond Indicator, identifiers assigned to the platform such as an LEI or DTI, the smart contract name, description, contract type and public key, and the token type. Custody arrangements can be recorded by indicating on-chain or off-chain platforms. The download pack also contains an example XML file for a DLT-based bond issuance.

If the BDT record and the bond documentation disagree, which one wins?

The legal documentation. ICMA's FAQs state that the BDT is not a substitute for the issuance documents, that the documents do not need amending to reflect it, and that in any discrepancy the legal documentation prevails. ICMA recommends that parties using the BDT include their own disclaimers, and the BDT messages contain a section for this.

Is the Bond Data Taxonomy mandatory for tokenized bonds?

No. ICMA states that use and adoption of the BDT is voluntary. It is technology agnostic and built for both traditional debt securities and tokenised bonds. Adoption is spreading through market infrastructure instead: Clearstream and Euroclear aligned their Issuance and Processing Taxonomy with it, and ICMA is working with Swift to integrate it into ISO 20022.

Ready to get started?

Join others who are already using our platform.