Cecabank and Crédit Mutuel Join RL1 at Launch: What CFOs and Accounting Firms Must Track Now

The Regulated Layer One (RL1) blockchain cooperative officially launched on 28 July 2026, with ten founding institutions spanning five European jurisdictions. Spanish wholesale bank Cecabank and French umbrella cooperative Crédit Mutuel were named as new founding members at launch. The timing is not incidental: the Eurosystem's wholesale central bank money settlement mechanism is due to go live in September 2026, making a regulated, bank-grade DLT network directly relevant to how tokenized assets will be settled, reported, and accounted for across the EU and UK.

What RL1 Is and How It Is Structured

RL1 is a cooperative incorporated in Luxembourg. Its founding technology partner is SWIAT, which transferred its DLT platform to the cooperative as part of the launch. SWIAT continues to serve as the technical operator, but the governance and ownership structure now sits with the member banks rather than a single fintech entity. That distinction matters from a financial reporting and counterparty risk perspective: institutions dealing with RL1 are dealing with a member-governed entity, not a proprietary vendor platform.

The Founding Member Roster

Ten institutions make up the founding membership. Five are German: DekaBank, DZ Bank, LBBW, Chartered Investment, and Seturion (the digital subsidiary of Boerse Stuttgart). The remaining five represent four other jurisdictions: ABN Amro (Netherlands), Crédit Mutuel and Natixis CIB (France), Cecabank (Spain), and SC Ventures, the venture arm of Standard Chartered (UK). Two German development banks, L-BANK and KfW, are now listed as supporters rather than full members. KfW is among the most active bond issuers globally, so its presence even as a supporter signals the network's ambition in the debt capital markets. NatWest and V-Bank, both previously announced as members, are no longer part of the group at launch.

Luxembourg as the Legal Home

Incorporating the cooperative in Luxembourg is a deliberate regulatory choice. Luxembourg sits within the EU's MiCA perimeter and has an established DLT regime under the CSSF. For accounting firms advising clients on cross-border tokenized transactions, the Luxembourg domicile means RL1 falls under CSSF supervision and that member institutions' interactions with the platform will be governed by EU law, including MiCAR and the EU DLT Pilot Regime where applicable. The CSSF's MiCAR Title II notification process is already active, and any asset-referenced tokens or e-money tokens issued or settled through RL1-connected infrastructure will need to satisfy those requirements.

The Eurosystem Settlement Link: Why September 2026 Changes the Calculus

The Eurosystem is scheduled to activate its wholesale central bank money settlement capability for tokenized assets in September 2026. This is not a pilot or a sandbox experiment; it is the live infrastructure that will allow tokenized securities to settle against wholesale CBDC on a delivery-versus-payment basis. RL1 is explicitly positioning itself to interoperate with that mechanism.

Wholesale CBDC Is Not a Retail Stablecoin

Accounting teams need to hold this distinction clearly. Wholesale CBDC issued by the Eurosystem for interbank settlement is a central bank liability, not a commercial bank deposit and not a privately issued stablecoin or e-money token. Its accounting treatment under both IFRS and national GAAP frameworks will differ from the treatment of, say, a euro-denominated e-money token issued by a payment institution. For firms already wrestling with IFRS versus FASB crypto asset classification, the arrival of wholesale CBDC as a settlement asset adds another category that needs its own ledger treatment and disclosure policy.

Implications for Stablecoin and Tokenized Asset Accounting

The RL1 network is designed for tokenized financial assets, including bonds, funds, and potentially other capital market instruments. When those assets settle against wholesale CBDC, the accounting entries on both legs of the trade need to be captured with precision. Several questions immediately arise for CFOs and their advisers:

• How is the tokenized bond recognised on the balance sheet at trade date versus settlement date when settlement is on-chain and near-instantaneous?
• Does delivery-versus-payment on a DLT network change the derecognition timing under IFRS 9 or IAS 39 compared with traditional CSD settlement?
• How are transaction costs, including network fees paid to the RL1 cooperative, capitalised or expensed?
• What disclosure is required in the notes to the financial statements when an entity holds tokenized securities settled through a CBDC mechanism?

None of these questions has a universally settled answer yet. Standard-setters including the IASB have been consulting on digital asset accounting, but no final standard specifically addresses tokenized capital market instruments settled via wholesale CBDC. CFOs and their auditors will need to apply existing principles by analogy and document their judgements carefully.

Stablecoin Accounting in the RL1 Context

While RL1's initial focus is on tokenized capital market instruments rather than retail stablecoins, the broader infrastructure question is relevant to any firm already holding or transacting in euro-denominated digital assets. Stablecoin accounting and broader digital asset accounting software will need to handle an expanding set of instrument types as platforms like RL1 mature.

Classification Challenges

Under IAS 32 and IFRS 9, the classification of a financial instrument as a financial asset, financial liability, or equity instrument depends on the contractual terms, not the technology used to represent it. A tokenized bond traded through RL1 is still a debt instrument and should be classified accordingly. The token wrapper does not change the underlying economics. Where firms can go wrong is treating the token as a separate asset class requiring a separate accounting policy, when the correct approach is to look through the token to the underlying instrument and apply the relevant financial instrument standard.

Valuation and Fair Value Measurement

Tokenized bonds traded on a regulated platform like RL1 should, in principle, have observable market prices, which supports Level 1 or Level 2 fair value measurement under IFRS 13. That is actually an improvement over some legacy OTC instruments. Accounting teams should ensure their digital asset accounting software can ingest prices from regulated DLT trading venues and map them correctly to the relevant fair value hierarchy level. Firms that lack this capability today need to assess whether their current systems are fit for purpose as RL1 and similar platforms scale up.

AML and Compliance Considerations for Accounting Firms

The RL1 network is designed to operate within the regulated perimeter. All ten founding members are supervised financial institutions in their home jurisdictions. That reduces but does not eliminate the AML considerations for accounting firms advising clients who transact through the platform.

Travel Rule and Transaction Monitoring

The EU's Transfer of Funds Regulation, which extends Travel Rule requirements to crypto-assets under MiCA, applies to transfers of crypto-assets between CASPs. Where tokenized assets move between member institutions on RL1, the institutions involved will need to satisfy themselves that their Travel Rule obligations are met, even on a bank-to-bank basis. Accounting firms that provide AML compliance advisory services should ensure their clients have documented how Travel Rule data flows are handled for on-chain settlement transactions. The growing MiCA licensing register is the reference point for identifying which counterparties are authorised.

Sanctions Screening

Settlement finality on a DLT network can be faster than on traditional systems. That speed creates a window-of-risk for sanctions screening: if a transaction reaches finality before a screen is completed, unwinding it may be technically complex or impossible. Firms advising clients active on tokenized asset platforms need to confirm that pre-settlement sanctions screening is embedded in their clients' workflows, not applied only post-trade.

What UK-Based Firms Need to Consider

SC Ventures, the Standard Chartered entity in the founding membership, is UK-based. UK firms advising SC Ventures or other UK entities that interact with RL1 should note that the platform itself is Luxembourg-domiciled and EU-regulated. Post-Brexit, UK firms cannot assume that EU regulatory approvals carry automatic equivalence for UK purposes. The FCA's own digital securities sandbox and the UK's approach to DLT settlement are still evolving. UK entities transacting through RL1 will need to assess whether their activities require separate FCA authorisation or notification, in addition to whatever approvals apply on the EU side.

Practical Steps for Accounting Firms and CFOs

The RL1 launch is a signal that institutional tokenization infrastructure in Europe is moving from pilot to production. Accounting firms and CFOs serving financial sector clients should take a few concrete steps now rather than waiting for the September Eurosystem activation.

Assess Your Chart of Accounts

Review whether your current chart of accounts can accommodate tokenized financial instruments as a sub-category of existing asset classes, rather than as a new top-level category. The goal is to preserve comparability with legacy instrument accounting while capturing the on-chain-specific data points needed for disclosure.

Review Software Capabilities

Crypto bookkeeping software and broader digital asset accounting software used by your firm or clients should be assessed for the ability to handle tokenized capital market instruments, not just cryptocurrencies or stablecoins. The data requirements differ: you need ISIN or equivalent identifier, on-chain transaction hash, settlement date, counterparty identifier, and fair value source, all in a single record. If your current tooling cannot capture all of these, that is a gap that needs addressing before clients begin transacting at scale on platforms like RL1.

Update Accounting Policies

Entities that anticipate using RL1 or similar platforms should update their digital asset accounting policies before their first transaction, not after. An accounting policy that is silent on DLT-settled instruments will create audit risk. The policy should address classification, measurement, derecognition, transaction cost treatment, and disclosure, all with explicit reference to the applicable IFRS or national GAAP standards being applied by analogy.

Frequently Asked Questions

What is the Regulated Layer One (RL1) cooperative?

RL1 is a Luxembourg-incorporated blockchain cooperative launched on 28 July 2026. It is governed by its ten founding member banks and uses the SWIAT DLT platform as its technical backbone. Its purpose is to provide a regulated, bank-grade infrastructure for issuing and settling tokenized financial assets within the European regulatory perimeter.

How does wholesale CBDC settlement affect accounting entries?

When a tokenized bond settles against wholesale CBDC, both the securities leg and the cash leg of the trade need to be recorded. The wholesale CBDC received is a central bank liability and should be accounted for as cash or a cash equivalent under IAS 7, depending on its maturity and liquidity profile. The derecognition of the tokenized bond follows IFRS 9 criteria applied to the underlying instrument, not to the token itself.

Does RL1 fall under MiCA?

The cooperative is domiciled in Luxembourg and subject to CSSF oversight. Whether specific activities conducted on the RL1 platform fall under MiCAR depends on the instrument type. Tokenized traditional financial instruments covered by MiFID II may fall under the EU DLT Pilot Regime rather than MiCA. Asset-referenced tokens or e-money tokens would fall under MiCA Titles III and IV respectively. Firms should assess each instrument category separately.

What changed in the RL1 membership between announcement and launch?

Two previously announced members, NatWest and V-Bank, are no longer part of the cooperative at launch. Two German development banks, L-BANK and KfW, moved from member to supporter status. Cecabank and Crédit Mutuel were added as new founding members, bringing the total founding membership to ten institutions across five jurisdictions.

What should CFOs do now to prepare for tokenized asset settlement?

CFOs should review their chart of accounts and accounting policies to ensure they cover tokenized financial instruments settled on DLT networks. They should assess whether their digital asset accounting software can capture on-chain transaction data alongside traditional instrument identifiers. They should also confirm that pre-settlement sanctions screening and Travel Rule compliance workflows are in place for any planned activity on platforms like RL1.

Source: Ledger Insights