The same bond, a different delivery route: preparing a collateral assessment

Tokenizace.cz Editorial Team · Planned publication: 2026-11-10 · Sources checked as of: 2026-11-01

Basis of the article: This article draws on the primary material below, checked as of 1 November 2026. Sources 1–3 provide the initial subject basis; further references add professional and comparative context. The practical approach and illustrative situations are editorial analysis, not test results reported by the named institutions.

Reader summary

• Separate the asset’s characteristics from its new delivery method.
• Prepare a comparison of risks and responsibilities for the changed route.
• The output is an assessment pack, not an assumed permission.

A different delivery method needs assessment

A tokenised form of an accepted asset may require the relevant approval process where risks differ. The proposal does not automatically expand eligible asset types. [1]

We therefore suggest two separate descriptions. The first identifies the asset and the holder’s claim. The second shows its new delivery, recording and control arrangements. The bond name may remain identical in both columns, while each changed dependency still needs explanation. This is an editorial working method, not a supervisory application form.

Prepare a record of the differences

In a purely hypothetical example, an operator wants to use the same bond through a different recording and transfer service. The comparison maps the original and proposed routes: where the decisive record sits, who has disposal authority and how completion of delivery is evidenced. Each unverified feature receives an owner and a verification task. This example describes no actual application or approval.

Next comes evidence for each change. A contract explains responsibility, a technical test shows system behaviour, and an operational exercise covers exceptions. One item should not automatically substitute for all the others. The reviewer can then see both the proposed technology and the precise scope of completed verification.

A price needs an accessible market

The comparison should also cover available buyers, achievable prices and time until usable funds arrive. General risk frameworks address liquidity and operational dependencies. [3, 5] Our example therefore does not assume that an identical asset name produces the same outcome in both environments.

A comparison should include custody charges, operating restrictions and dependence on a single conversion point alongside transfer fees. The same bond name should not be taken to imply identical liquidation costs across different arrangements.

A lesson for a business borrower

An ordinary SME does not automatically become a clearing member or gain access to these services. A company discussing finance against digitally recorded assets can nevertheless ask similar questions. Who has which claim? Who can transfer the asset, where can it be sold, and who handles an operational exception? Contracts and provider permissions must establish the actual service scope.

The decision pack can use three states: evidenced, open and requiring assessment. Each retains a specific item of evidence and its date. Implementation follows conditions actually resolved; completing a technical test is not presented as supervisory permission.

Implications for Czech and Slovak companies

A Czech or Slovak company cannot treat the British proposal as a local rule for its own assets. In discussions with its bank, it should establish eligibility, valuation, haircuts and enforcement for the specific contract. The European legislation in the further reading provides a comparison of frameworks.

Sources

1. Bank of England — Tokenised collateral consultation, 29 October 2026 — subject basis
2. Bank of England — Approach to tokenised collateral in central clearing — subject basis
3. CPMI–IOSCO — Principles for Financial Market Infrastructures — subject basis
4. BIS–CPMI — Tokenisation in the context of money and other assets (2024) — further context
5. FSB — The Financial Stability Implications of Tokenisation (2024) — further context
6. ESMA — Report on the functioning and review of the DLT Pilot Regime (2025) — further context
7. EU — Regulation (EU) 2022/858: DLT Pilot Regime — further context
8. EU — Regulation (EU) No 909/2014: central securities depositories — further context
9. EU — Regulation (EU) No 648/2012: derivatives, central counterparties and trade repositories — further context
10. EU — Regulation (EU) 2022/2554: digital operational resilience — further context

Methodological note: The article distinguishes documented institutional information from editorial analysis. Numbered references identify direct evidence and professional or legal context. A contextual source does not document this particular transaction. Hypothetical examples are editorial illustrations, not findings about an actual client. A later planned publication date does not advance the verification cutoff.

Notice: For information and education. This is not investment, legal, tax or accounting advice, or an offer of a financial service. Any application requires individual assessment. The institutions mentioned are not partners or guarantors of Tokenizace.cz.