Managing Liquidity: From Blockchain Balances to Corporate Accounts

Corporate liquidity no longer fits neatly inside a bank account. A growing number of businesses now hold assets across two separate financial layers (traditional accounts and blockchain wallets), and the gap between them creates real operational friction. What managing cash looks like when a balance sheet spans both worlds is what this piece covers.

The Split Balance Sheet Problem

There’s a situation that’s become quietly common among mid-size international companies: part of their working capital sits in a Deutsche Bank account in euros, and another chunk lives in USDT on a custodial wallet. Both are real money. Moving between them is not simple.

Traditional banking infrastructure runs on SWIFT, settles T+1 or T+2, and comes with layers of compliance checks. Blockchain-based assets confirm in seconds but exist in a legal grey zone that shifts depending on which country you’re operating in. These two systems weren’t designed to talk to each other — and yet many treasury teams now have to manage both, often simultaneously.

The practical answer, increasingly, is a dedicated conversion layer. Services built around a crypto-to-fiat gateway (Inqud being one of the more focused providers in this space, alongside names like Mercuryo, Transak, and Ramp Network) exist precisely to handle this handoff. The operational value isn’t technical novelty; it’s that a payment arriving in crypto can land on a corporate bank account as fiat without requiring the finance team to manually manage an exchange, AML checks, and settlement separately. For companies serving clients across markets where correspondent banking is patchy or slow, that matters more than it might sound.

What Actually Changed After 2020

The vulnerability that nobody planned for

The pandemic did something useful for treasury professionals, grimly. It demonstrated that routing all liquidity through a single channel — conventional banking — carries real operational risk. When banks moved to skeleton crews and SWIFT processing slowed, companies with backup payment rails absorbed the disruption better.

At roughly the same time, stablecoin adoption started reaching past the crypto-native world:

• PayPal launched PYUSD, its own stablecoin, targeting mainstream business use
• Visa and Mastercard ran live settlement pilots on Ethereum — not experiments, actual transaction settlements
• MicroStrategy and Tesla both moved portions of corporate reserves into Bitcoin, framing it as a treasury allocation rather than speculation
• SWIFT accelerated the GPI rollout partly because its institutional clients were genuinely asking about crypto alternatives

None of this killed traditional banking. What it did was create a parallel layer that, after enough serious institutions started using that ignoring it became harder to justify.

New instruments, same old objectives

The underlying treasury goals haven’t shifted: keep enough liquid assets available, don’t pay more than necessary to move money, don’t let conversion costs eat into margins on international transactions. What’s changed is the toolkit available to meet those goals. Automated stablecoin-to-fiat conversion, multi-wallet management, and real-time on-chain balance visibility are now part of the picture alongside overnight deposits and revolving credit facilities.

The Accounting Question That’s Still Unresolved

Holding USDC or USDT on a corporate wallet creates accounting headaches that current standards don’t fully address. The IASB only started developing dedicated guidance for crypto assets in 2024, which means most companies are currently working around the problem with imperfect solutions.

The two most common approaches:

• IAS 38 (intangible assets) — technically applicable, but built for things like patents and software licenses, not dollar-denominated digital instruments
• IAS 2 (inventories) — used by some companies, particularly exchanges, but awkward for assets held as near-cash equivalents

Both approaches miss something. A stablecoin pegged to the US dollar doesn’t behave like an intangible asset — it behaves like cash. But until standards catch up, companies have to pick the least bad option and document their reasoning carefully.

A lot of smaller companies sidestep the whole issue by converting to fiat as fast as possible after receipt. Keep digital assets on the books for the minimum time, and reduce the complexity. Platforms like Inqud are partly built around this workflow — instant conversion means the accounting entry becomes a fiat receipt rather than a crypto holding. It’s not elegant, but it works.

Regulation: Still Fragmented, Still Moving

The compliance picture looks different depending on where a business operates.

The EU’s MiCA regulation — Markets in Crypto-Assets — came into force in 2024 and represents the first comprehensive framework for stablecoin issuers and crypto service providers operating across member states. It brings predictability, which most businesses actually welcome, even if the compliance burden increases.

The UK has been expanding FCA registration requirements for crypto businesses incrementally. No single sweeping framework yet, but the direction is clear.

The US remains the most complicated picture. The SEC and CFTC have been fighting over jurisdiction on digital assets for years without a full resolution. New York’s BitLicense sits on top of federal requirements for anyone touching that market. Companies operating across multiple US states need jurisdiction-specific legal advice — there’s no clean general answer.

The practical implication for any treasury team: before building a multi-channel payment infrastructure that includes digital assets, the regulatory map for each operating jurisdiction needs to be drawn first. AML and KYC requirements don’t relax because a transaction runs on a blockchain rather than through a bank.

How Multi-Channel Liquidity Actually Works in Practice

Segmenting by time horizon

The logic of separating operational from strategic liquidity hasn’t changed, but the instruments available for each layer have expanded.

Operational liquidity, the funds needed to cover obligations within the next 30 to 90 days, should stay in the most accessible, most conservative instruments. Bank accounts, short-term deposits, and dollar stablecoins with instant conversion capability all fit here. The moment conversion takes longer than a few hours, it stops functioning as operational liquidity.

Longer-horizon reserves have more flexibility. Some companies are experimenting with yield-bearing stablecoin instruments for this portion, though the risk and accounting implications need to be understood clearly before going that route.

Building in redundancy

Dependence on a single bank or payment provider is a risk that reveals itself only when something breaks. A bank holiday in a key market, a compliance hold, a correspondent banking relationship severed due to sanctions pressure. Companies that have discovered this problem tend to fix it quickly. Companies that haven’t discovered it yet tend to underestimate it.

Having parallel channels, including the ability to send and receive via digital asset rails, isn’t about crypto enthusiasm. It’s about not having a single point of failure in payment infrastructure.

Real-time visibility

Treasury management platforms like Kyriba, Finastra, and SAP Treasury have started integrating on-chain data alongside traditional bank feeds. The difference this makes is practical: a real-time consolidated view of cash positions, across bank accounts and blockchain wallets, lets treasury teams respond to liquidity gaps the same day rather than the following morning when reconciliation reports appear.

The Wider Picture: Payments Infrastructure Is Changing Everywhere

It would be a mistake to read the blockchain element of this as the only story. Parallel shifts are happening across the payment infrastructure that affect corporate liquidity just as directly:

• Instant payment networks: SEPA Instant, India’s UPI, Brazil’s PIX are handling enormous volumes at near-zero marginal cost, and the companies already routing payments through these networks are paying measurably less for cross-border settlement
• Central bank digital currencies: the digital euro and digital yuan are the most watched, but dozens of countries are in various stages of pilot or development; when these arrive at scale, they change the settlement layer for a significant portion of global trade
• Open banking under PSD2/PSD3: creating the technical infrastructure for third-party cash management tools to access bank account data and initiate payments directly
• Embedded finance: payment rails built into non-financial software, changing how businesses interface with their own treasury operations

McKinsey’s cross-border payments data puts the global market above $150 trillion annually. SWIFT gpi has improved tracking and speed, but average costs remain high relative to domestic payment costs. The combination of alternative rails — crypto gateways from providers like Inqud, Mercuryo, or Banxa, plus instant payment networks — is chipping away at that gap from multiple directions.

The Underlying Logic Hasn’t Changed

What does change is the range of instruments available to execute against it. A treasury team that can move competently across both traditional and digital infrastructure — that understands when to use a SWIFT transfer and when a crypto-to-fiat conversion via a gateway is faster and cheaper — holds a practical operational advantage. Not a theoretical one. It shows up in settlement costs, in the speed of cross-border supplier payments, and in the ability to keep operating when one payment channel develops a problem.

The balance sheets may have gotten more complicated. The objective ( keep money moving, keep costs manageable, keep risk bounded) remains exactly what it always was.

Disclaimer

The content shared by Meyka AI PTY LTD is solely for research and informational purposes. Meyka is not a financial advisory service, and the information provided should not be considered investment or trading advice.