Brawlers Guide
Contents

Tokenisation: The €150m Loan Lifecycle Test

Tokenisation faces a lifecycle test in Iberdrola's €150m loan. Shared records matter if amendments, lender transfers and costs hold up after disbursement.

Heath Donald Tokenisation @heathdonald /post/tokenisation-150m-loan-lifecycle-test

Tokenisation has a harder job than putting a loan on a ledger. It has to keep the borrower and lenders working from the same account of what happens afterwards. Interest changes. A lender transfers its share. The borrower asks for consent to change a condition. Those events are a better test of useful infrastructure than a successful launch announcement.

On 15 October, Iberdrola, BBVA and Santander announced a €150 million corporate syndicated financing facility administered using distributed ledger technology. The platform, developed by ioBuilders with the two banks, is intended to manage the loan from execution and disbursement through interest, amendments, repayments and maturity.[2]

That makes this a useful transaction to watch. The interesting claim concerns the years of administration after the money moves. A live facility gives that claim somewhere to be tested. It does not mean every future event has already passed the test.

A shared loan record is a specific claim

Santander's announcement says participating institutions share a synchronised record rather than reconcile separate databases. Authorised participants can see contractual events recorded on the infrastructure, while the appointed agent bank retains operational control.[2] That description gives a buyer something to examine: a shared administrative record, with an institution still accountable for running it.

The agent-bank detail deserves attention. A shared ledger does not imply that every participant has equal authority to change the record. Ask which institution may submit an event, whose approval makes it effective and how another lender disputes it. The system should make those responsibilities easier to inspect, rather than obscure them behind a claim that the record is immutable.

Keep the label precise, too. The release describes DLT-based loan administration. It does not establish that investors received freely transferable tokens, that the disbursement used tokenised money or that the facility can trade on a public exchange.[2] Treat those as separate claims requiring separate evidence. Otherwise a useful operational development gets dressed up as a different financial product.

This is a narrower story than the industry's issuance headlines. AFME reported on 19 October that global DLT fixed-income issuance had reached €8.1 billion in 2026 to date, 86% above full-year 2025.[1] That measures issuance in the category AFME tracks. It cannot tell a borrower whether administering its particular loan will cost less.

The difficult work arrives after disbursement

The announced platform covers interest calculations and notifications, principal and fee payments, early repayments, covenant monitoring, certain contractual consents and transfers between lenders.[2] These are the functions to examine when assessing the lifecycle claim. A checklist of supported functions is the beginning of that assessment, not the results.

Consider a hypothetical borrower requesting a waiver. The request needs to reach the relevant lenders. Their decisions need to be recorded against the correct version of the request. Someone must determine when the required consent has been obtained. The resulting change then has to appear correctly in later administration. Recording each message is useful only if the participants agree on what those messages authorise.

A lending-share transfer raises another test. Ask the operator to show the outgoing lender's position, the incoming lender's admission and the effective date used for subsequent payments. Then ask what happens if a submitted instruction contains an error. An audit trail should explain the correction without leaving participants unsure which position governs the next payment.

These are proposed acceptance tests, not reports of defects in this facility. The announcement does not provide event-by-event operating results or a measured comparison with conventional administration.[2] Until those results exist, the defensible conclusion is that a live transaction has been put onto a platform with broad administrative scope. Savings and reliability still need evidence.

That extends the argument in Tokenisation's real bottleneck is settlement. Getting value transferred with legal certainty matters. For a loan intended to remain outstanding, the operating record also has to survive everything the contract permits after that transfer. Settling the opening transaction cannot answer every later question about the obligation.

More participants will test the operating model

The banks say they plan to add participants progressively and expand functionality following the first transaction.[2] That next stage matters because a platform designed with its initial institutions has yet to demonstrate what a new lender must do to join. The cost of admission belongs in the commercial assessment.

For a treasury team evaluating a similar proposal, start with the prospective lending group. Identify who can use the platform now and what an additional lender would need to change. Ask whether that institution can keep its existing systems, how it receives notices and whether it must duplicate any work outside the shared record. Get those answers before treating broader participation as an automatic benefit.

Apply the same scrutiny to the borrower. If its finance team still has to prepare a second set of instructions for internal accounting, include that work in the cost comparison. A cleaner view for the agent bank would be useful, but it would not by itself establish a lower total administrative burden across the transaction.

None of this requires every bank to replace its internal systems. A credible design can connect different systems to a shared record. The procurement question is which work that connection removes and which work it adds. Require a diagram showing where an approved contractual event enters, who validates it and how it reaches each participant's books.

Measure administration before claiming liquidity

The release says the technology may improve market liquidity and help medium-sized companies access syndicated financing.[2] Those are possibilities, not published outcomes of this transaction. Faster administration could make participation easier. It would not, on its own, establish that a willing buyer exists for a lender's share or that a borrower qualifies for credit.

A useful comparison would measure staff time and correction work against a suitable conventional facility. Include integration, support and onboarding costs. For a transfer, measure the elapsed time from an agreed transaction to an effective change in the lending record. For access, look for actual additional lenders or borrowers admitted on workable terms.

Avoid using the facility's €150 million size as a proxy for any of those benefits. That figure describes the announced financing, not the platform's revenue, the borrower's savings or the value available for immediate resale.[2] Keep the unit attached to the claim. A large transaction can be a meaningful operational test without proving a large addressable market.

The reason to take this development seriously is its attention to ordinary contractual work. My test for tokenisation would be whether a borrower and its lenders can handle a difficult amendment with fewer conflicting records and less manual repair. That is an outcome worth buying. Watch the next participants joining and the administrative results before treating the launch as proof of it.

Subscribe to the Brawlers Guide weekly digest for clear-eyed writing on AI, tokenisation and capital raising. A field guide to the brawl of life, delivered to your inbox.

One post a week

Subscribe to the Brawlers Guide weekly digest for clear-eyed writing on AI, tokenisation and capital raising. A field guide to the brawl of life, delivered to your inbox.

Weekly. Unsubscribe from any post.

Also in this edition