Liquidity Isn't What You Think It Is

Liquidity Isn't What You Think It Is

Santhosh "Sonny" Koritala· Treasury & Finance Transformation LeaderApril 29, 20264 min read
Back to True North

Most organizations believe they know exactly how much liquidity they have. They can see it on the balance sheet. They can point to the credit facilities. What they often cannot explain is how much of that liquidity is genuinely accessible — under the conditions when it would actually be needed.

Part of a Series

Treasury Clarity Series

Article 3 of 6 by Santhosh "Sonny" Koritala

Part 3 of 3Treasury Clarity Series by Santhosh Koritala
Executive Summary

Most organizations believe they know exactly how much liquidity they have.

They can see it on the balance sheet. They can point to the credit facilities. The cash positions are in the system. On paper, liquidity appears managed.

What they often cannot explain is how much of that liquidity is genuinely accessible — under the conditions when it would actually be needed.

💧 Nominal vs. accessible liquidity
🔒 Encumbrance and conditionality
🌐 Cross-border access barriers
⚡ Stress-tested liquidity architecture

Liquidity is not a number. It is a condition — and that condition changes when pressure arrives. The organizations that understand this build for access, not just abundance.

The Number on the Screen Is Not Liquidity

There is a moment in every liquidity crisis — large or small — when a treasury team discovers the same uncomfortable truth.

The cash is there. The facilities are in place. The system shows sufficient coverage.

And yet — when they actually need to move it, draw on it, or deploy it — friction appears that wasn't visible in the calm.

Nominal liquidity is what you have. Accessible liquidity is what you can actually use — quickly, under stress, without destroying value in the process.

The difference between those two numbers is the gap most treasury organizations have not measured. And it is a gap that is invisible — until it matters.

The Five Sources of the Liquidity Gap

Liquidity appears encumbered or inaccessible for predictable reasons. Understanding them in advance is how you design around them.

01
Trapped Cash
Balances held in entities or jurisdictions where repatriation is slow, expensive, or blocked by regulatory or tax constraints.
02
Conditional Facilities
Credit lines that carry covenant conditions, MAC clauses, or lender-consent requirements that become relevant precisely when the organization is under pressure.
03
Operational Float
Working capital tied up in settlement cycles, intercompany positions, and in-flight transactions that cannot be mobilized on demand.
04
Collateral Encumbrance
Cash posted as margin or collateral against derivative programs — which increases precisely when markets move against the organization.
05
Concentration Risk
Excess reliance on a single bank, currency, or funding source — creating fragility that only becomes visible when that concentration is stressed.
⚠
The Correlation Problem
These five sources are not independent. In a stress event, they often materialize simultaneously — amplifying the gap precisely when it is least affordable.

Why This Gap Is Consistently Underestimated

The liquidity gap is underestimated for the same reason most treasury risks are underestimated: it is invisible during calm conditions.

What liquidity looks like in calm markets
  • → Facilities are available and undrawn
  • → Cash balances look healthy
  • → Reporting shows comfortable coverage ratios
  • → The system shows no alerts
What liquidity reveals under stress
  • ! Covenant conditions restrict facility access
  • ! Cash is trapped in the wrong jurisdictions
  • ! Collateral calls absorb available cash
  • ! Banking counterparties tighten terms

The gap is not created by the stress event.

It is revealed by it. The conditions were always there.

What a Stress-Tested Liquidity Architecture Looks Like

Resilient organizations don't just measure liquidity — they architect it. The distinction is significant.

Tiered liquidity buffers
Distinguish between immediately deployable cash, next-day accessible facilities, and strategic reserves — and maintain each tier deliberately.
Cross-border mobility design
Understand — in advance — which cash pools can move across borders, under what conditions, and at what cost and speed.
Stress scenario modeling
Run liquidity models against specific scenarios — not just generic shocks. Model the correlation between your risk factors, not just each one in isolation.
Counterparty diversification
Structure banking relationships and facility arrangements to eliminate single points of failure in the liquidity architecture.

The defining question for liquidity architecture:

"If we needed to mobilize $X in 72 hours — across which entities, through which banks, under which market conditions — could we actually do it?"

Closing Thought

Liquidity is not a balance. It is a capability. And like all capabilities, it must be built, tested, and maintained — not assumed.

The organizations with the highest nominal liquidity are not always the ones with the strongest liquidity position. The ones with the strongest position are the ones who have tested it — and know, with precision, exactly what they can access and when.

The series so far

Three dimensions of the same truth.

Part 1 ·What breaks — structural resilience under persistent volatility
Part 2 ·Why it breaks — valuation integrity and the illusion of control
Part 3 ·Where it breaks — liquidity access under stress
Connect

Bring these insights to your treasury

Want to go deeper with Santhosh "Sonny" Koritala, or need hands-on help with your SAP TRM or treasury implementation? Share where you are and the right person will reach out.

We'll only use your details to respond to this request.

About the Author

Santhosh "Sonny" Koritala
Santhosh "Sonny" Koritala

Treasury & Finance Transformation Leader

Santhosh Koritala is a treasury and finance transformation leader with deep expertise in derivatives, hedge accounting, and technology-enabled treasury design. He advises CFOs and treasury teams navigating complexity with clarity.

Discussion

Leave a comment

Sign in to join the discussion.

No comments yet. Be the first to start the conversation!

We value your privacy

We use privacy-friendly analytics to understand which content and tools are useful, and to measure performance. This includes a persistent anonymous identifier, approximate location (derived from your IP), and — when you share it — your email. No advertising cookies. See our Privacy Policy for what we collect, why, your rights, and our 13-month retention limit. You can opt out anytime.