What your bank account was doing that your wallet is not

The case for wallet consolidation is straightforward. A company with hundreds of bank accounts also has hundreds of KYC files, mandates, signatory structures and reconciliation jobs to maintain.

Moving toward one wallet per legal entity reduces that operational sprawl. But reducing the number of containers does not reduce the number of financial relationships inside them.

A single wallet holds tokenized deposits from several banks, stablecoins from several issuers and tokenized money market funds from several managers across multiple chains. The banks, issuers, asset managers and instruments are all still there. Only the number of places holding them has changed.

The market is already moving in this direction.

In January 2026, Lloyds issued tokenized sterling deposits, describing it as the UK's first tokenized deposit issuance on a public blockchain and a global debut for sterling deposits. In July, Lloyds completed three live tokenized deposit transactions under the Real-Value Testing phase of Project Agorá, including a cross-currency transaction.

J.P. Morgan's JPM Coin USD deposit token, JPMD, has been available to institutional clients on Base since November 2025. Citi Token Services for Cash is live in the US, UK, Singapore and Hong Kong.

The issuer side is expanding too. Societe Generale's digital asset arm issued euro and dollar stablecoins, AllUnity launched a euro stablecoin under a BaFin license and a coalition of major banks announced work on G7-currency stablecoins. Franklin Templeton's BENJI gives investors blockchain-based access to shares of its tokenized money market fund.

The end state is fewer wallets, with more instruments and more financial relationships inside each one.

What you were buying with a bank account was more than a place to hold money. You received an institution-issued statement. Payments passed through compliance controls. The account belonged to a known legal entity. Payment schemes provided defined procedures for some errors. Transfers carried structured information about the parties involved.

Strictly speaking, the account did not perform all of these functions itself. Some sat with the bank and others with the payment scheme. Operationally, they arrived together as part of the banking relationship.

That matters for how much of the bundle survives the move. A deposit token is a bank deposit in token form, so a regulated institution stays the obligor, and Citi runs its service on a permissioned chain, so the institution stays in the payment path. Screening and entity identity can travel with a bank-issued leg. A statement never does, a stablecoin or a fund token brings none of it, and nothing produces one record across all three. Your own obligations do not vary by leg.

Move the money into wallets and those functions do not automatically follow it. That is the part you have to rebuild.

That lands hardest on the companies that never made the journey the consolidation case describes. Not the multinational being introduced to wallets, but the finance lead who is already there: wallets across several chains, one or two custodians, an exchange account and a couple of bank accounts. You did not consolidate down into wallets, you started in them, and the account layer is the part you never had.

Range is the platform for companies operating across stablecoins and fiat. It connects the accounts and rails you already use and orchestrates the risk and compliance providers you already pay for rather than replacing them, so the ledger, controls, counterparties and reporting sit on the same record.

The regulatory environment is also becoming clearer. The GENIUS Act established a US federal framework for payment stablecoin issuers, while MiCA has applied in full in the EU since December 2024.

What has not changed is the operating question: who performs the functions that used to arrive with the account?

Your wallet does not produce a financial statement

A bank account gave you a record you did not have to build.

Balances, movements, dates and payment information arrived from the institution holding the account in a format your accounting systems could ingest and your auditor could inspect. You reconciled against that record rather than assembling it.

A self-custody wallet does not issue the equivalent.

A block explorer can prove that a transaction happened on one chain. It does not tell you what the payment was for, which of your legal entities owned it, how the counterparty appears in another system or what your position was across banks, custodians, exchanges and chains at period close.

Enterprise software has already started rebuilding this layer. SAP's Digital Currency Hub manufactures a bank-format account statement, CAMT-53, for every stablecoin transaction so it can be imported and reconciled like a bank feed. Standard delivery reaches two stablecoins, USDC and PYUSD, on two chains, Ethereum and Polygon. Further ERC-20 stablecoins can be added on request.

The ERP vendor's answer to "where is the statement?" was to create one in software.

Franklin Templeton comes closest to an exception. One share of FOBXX equals one BENJI token, and the fund's transfer agent "maintains the official record of share ownership" on a proprietary system that uses public blockchain networks for transaction activity. The chain carries the transactions, the transfer agent keeps the book, so holding the token does not produce the fund's books.

It also does not give you one accounting record across BENJI, a JPMD position, USDC in another wallet, a custodian balance and three bank accounts.

You need a ledger above them.

Range Treasury gives you a consolidated position across wallets, custodians, exchanges and bank accounts. Transaction Reconciliation normalizes and classifies activity across those sources. Reporting and Intelligence produces financial reporting from labeled transactions and feeds enriched onchain data into Xero, QuickBooks, NetSuite and SAP.

Range covers 200+ networks and 100+ stablecoins. That is the scope the record has to reach once your positions are spread across multiple instruments and rails.

You should be reconciling from a unified record rather than reconstructing one at close.

Onchain settlement removes the recovery window

Bank payments are not universally reversible, but major payment schemes define procedures for specific mistakes.

The SEPA Credit Transfer Scheme Rulebook allows recalls for duplicate transfers, technical errors and fraudulently originated instructions. Your provider has 10 banking days for a duplicate or technical error and 13 months for fraud, while the beneficiary's provider must respond within 15 banking days.

A recall still "does not guarantee that the Originator will effectively receive back the Funds" because recovery can depend on the beneficiary's consent. Fifteen banking days of asking is still a different category from having nobody to ask.

In the US, Nacha's rules guidance names an "incorrect receiver" as one of the permitted reasons for an ACH reversal, provided the reversal reaches the receiving institution within five banking days after settlement. Sending money to the wrong party is a defined error with a remedy and a clock.

Public blockchain settlement works differently.

ethereum.org states that once a block is finalized, the transaction it contains "will never be altered". Changing it would require a network-level attack that "would cost many billions of dollars".

A bank payment has a conditional recovery procedure and a counterparty to ask. An onchain transfer has to be correct before it settles.

The cut-off window is disappearing too. Citi says Token Services for Cash is "designed to help eliminate traditional cut-off times and geographical restrictions". That is valuable when you operate across time zones, but the old window was also an interval in which a payment could sometimes still be stopped before final settlement.

Remove the window and the undo, and the remaining controls have to run before the money moves.

Range Transaction Screening exists for that constraint. Onchain transactions can be screened and blocked before execution, while fiat bank-account activity can be monitored against the same policy framework. Policy-Aware Controls can also turn your governing documents and internal policies into transaction-level rules.

The bank was screening your payments and never invoiced you for it

Banks also brought regulated compliance infrastructure into the payment path.

Under 31 CFR 1020.320, banks must report certain suspicious transactions conducted or attempted by, at or through the institution. That monitoring was part of the banking relationship rather than a separate control your finance team had to operate.

Take the institution out of the payment path and your own obligations do not disappear.

OFAC FAQ 560 asks whether sanctions compliance obligations are the same whether a transaction is denominated in digital currency or traditional fiat. Its answer begins: "Yes, the obligations are the same."

OFAC's guidance for the virtual currency industry makes the same point, saying sanctions compliance obligations apply equally to transactions involving virtual currencies and fiat currencies.

In Europe, Regulation (EU) 2023/1113 places transfer-information obligations on crypto-asset service providers. Article 14 covers the information that must accompany transfers of crypto-assets.

If you move your own assets through self-hosted wallets, there is no bank or payment service provider in the middle creating the counterparty and business-purpose record for you. That record becomes your job.

This is also where custody controls and payment controls separate.

A multisig, hardware security module or institutional custodian can answer whether the right people authorized a transfer. It does not answer whether this approved payment should go to this address.

Address poisoning is the case where that gap gets expensive. A two-year academic study of Ethereum and BNB Smart Chain published at USENIX Security 2025 identified over 270 million address-poisoning attempts against over 17 million victims, and 6,633 successful incidents causing at least $83.8 million in losses.

In an address-poisoning loss, the authorization layer can work exactly as designed. The signer approves the transaction and the custody policy is satisfied. The problem is that the approved address belongs to the wrong party.

That requires a control on the destination before execution.

Range screens onchain transactions against sanctions, fraud and illicit-activity signals before execution. Threat and Fraud Prevention checks for risks including address poisoning, scams and exploit exposure. Counterparty Risk keeps those signals attached to the entity you are actually transacting with, while Range can orchestrate the compliance providers you already use rather than forcing a second screening stack.

The account carried its legal entity in its identity

A bank account also had a legal entity attached to it by construction.

Statements, mandates, signatories and audit evidence belonged to a specific company. If several subsidiaries held separate accounts, much of the entity separation already existed in the account structure.

A wallet address contains none of that corporate context by itself. "One wallet per legal entity" can recreate the boundary, but the relationship between the address and the company still has to be maintained somewhere. So does the approval evidence around every transaction leaving it.

Consider an intercompany transfer. With two bank accounts, both companies receive separate institution-issued records. With wallets, the blockchain gives you the transfer. Your systems still have to preserve which entities were involved, who approved it, what policy applied and why the movement occurred.

For that record to survive an audit, four things need to exist when the transaction happens:

• Approval evidence linked to the transaction.
• Legal entity attribution linked to the account and movement.
• The policy and rule under which the payment was approved.
• Records that survive changes in signers, wallets and custody providers.

An auditor asking about one transfer eleven months later should retrieve those records rather than force you to reconstruct them from signer addresses, chat logs and spreadsheets.

An address is not a counterparty

The same problem exists on the recipient side.

When you paid a supplier through a bank account, the payment moved through institutions that maintained structured identity information about the parties. For covered funds transmittals of $3,000 or more, 31 CFR 1010.410(f) requires financial institutions to transmit specified information through the payment chain.

A wallet gives you an address, so the same supplier might appear internally as a wallet address, a bank account and an exchange deposit address, and without an entity layer those look like three separate counterparties.

A per-counterparty exposure cap is not a control if the same company appears three times and the records are never connected. A screening result on an address is harder to use if you cannot tie it back to the vendor record you already know. If a supplier changes banks, custodians or wallet addresses, that should appear as a change to an existing relationship rather than as a new anonymous recipient.

Risk, limits and compliance obligations attach to the entity, while the payment rails expose identifiers.

You therefore need an entity layer underneath those identifiers.

Range Counterparty Management resolves wallets, bank accounts and exchange identifiers to a single counterparty record. Risk, approvals and compliance context can then sit on the company rather than being scattered across each address or account it uses.

Wallet-native teams need the control layer

The usual wallet-consolidation model starts with a traditional finance function at zero wallets. It introduces digital assets gradually, pilots a few transfers and eventually integrates those rails into an existing treasury stack.

You may have started from the other direction. You already have the wallets, custodians, exchanges and bank accounts. The digital asset infrastructure came first. The account-level control layer did not.

For you, the sequence runs backwards:

• Build one ledger across every financial source so the record exists before you need to reconcile it.
• Resolve accounts and payment identifiers to legal entities and counterparties.
• Put controls in front of every transaction because the settlement rail offers no recovery path.
• Feed classified transactions and approval evidence into the systems you use to close the month.

Nothing in that sequence argues against consolidation. Fewer accounts is a real prize. The services bundled into those accounts still need somewhere to live once the containers disappear.

Range is the platform for companies operating across stablecoins and fiat. It connects wallets, custodians, exchanges and bank accounts into one real-time ledger, orchestrates the risk and compliance providers you already use, applies controls before onchain payments execute and keeps counterparty, approval and reporting context attached to the transaction.

Range protects over $30B in assets under management for our customers, across 10,000+ integrations with banks, custodians and wallets.

If you already operate across stablecoins and bank accounts, get in touch and we will show you the unified ledger, counterparty layer and pre-execution controls against the accounts you use today.