Article map
Cash visibility answers where money is recorded. Cash mobility answers whether that money can be moved, when it can be moved, at what cost and under whose authority. The distinction is crucial. A group can report a large global balance and still face a funding shortfall because surplus cash is restricted by regulation, tax, minority interests, loan covenants, capital requirements, operational buffers or simple timing constraints.
Intercompany funding is one route for mobilising liquidity, but it is not a universal answer. Loans, deposits, capital movements, dividends, cash-pool transfers and netting each create different documentation, pricing, maturity, accounting and approval consequences. Treasury needs an entity-level decision model rather than a single “available cash” label.
This article explains how a TMS can convert cash mobility into a governed data and workflow capability that supports daily decisions and longer-term liquidity planning.
1. Classify cash by transferability and time horizon
Mobility should be assessed at the entity, account, currency and legal-route level. A balance may be available for local payments today but not transferable cross-border, or transferable only after tax, approval or notice. The classification should therefore combine legal ability, economic cost and operational readiness.
The operating boundary should define:
- freely transferable cash with no material legal or operational impediment
- transferable cash subject to notice, documentation, tax or approval lead time
- cash reserved for payroll, tax, debt service, regulation or minimum operating needs
- cash restricted by pledge, escrow, minority rights, exchange control or financing terms
- cash technically transferable but economically unattractive after FX, tax and funding costs
The TMS should store both the classification and the reason. A generic “trapped” flag does not tell management whether the constraint is permanent, temporary, curable or simply uneconomic.
2. Maintain a mobility rulebook with effective dates
Mobility conditions change. Regulations, tax rules, covenants, entity capital needs and bank arrangements can all alter the transferability of cash. Treasury should maintain a controlled rulebook rather than rely on institutional memory or a static annual survey.
The governed data record should capture:
- entity, country, currency and account to which the rule applies
- permitted transfer methods and required supporting documentation
- thresholds, withholding or transaction taxes, fees and FX implications
- minimum retained balance, liquidity buffer and forecast horizon
- rule owner, legal or tax reviewer, approval date and next review date
Rules should be linked to actual balances and forecasts. This allows treasury to calculate mobilisable value rather than maintain a separate narrative file that never influences daily decisions.
3. Choose the transfer route through a structured decision
When liquidity is needed elsewhere in the group, the decision should compare routes on timing, cost, capacity and reversibility. The cheapest nominal method may not be the best if it creates a long approval cycle or locks the receiving entity into an unsuitable maturity.
The end-to-end workflow should make visible:
- confirm the local entity’s projected surplus after committed and stressed outflows
- test legal, tax, covenant and minority-shareholder constraints
- compare intercompany loan, deposit, dividend, capital, pool and netting alternatives
- set amount, currency, value date, maturity, rate and repayment profile
- obtain approvals, execute, confirm and post both sides of the transaction
The TMS should retain alternatives considered and the reason for the selected route when the transfer is material. This makes later review more useful than a bare record of the final intercompany entry.
4. Protect entity solvency and bilateral consistency
Group optimisation must not weaken an entity’s ability to meet its own obligations. Central treasury should challenge surplus assumptions, especially where forecasts are volatile or local teams face information gaps. Internal funding also needs bilateral agreement so that lender and borrower do not record different terms.
The control architecture should address:
- minimum post-transfer liquidity and stress buffer by entity
- authorised internal lending and borrowing limits
- approved pricing methodology, currency and day-count terms
- electronic bilateral confirmation and mirror accounting
- maturity monitoring, rollover approval and overdue-interest escalation
Transfers should not be backdated to repair a period-end shortfall or documentation gap. Value date, approval and accounting should reflect the actual transaction and the policy in force at that time.
5. Create a mobility dashboard that leads to action
A useful dashboard should reconcile visible cash to mobilisable cash and then show the actions needed to unlock value. It should distinguish a structural restriction from a missing approval or a forecast uncertainty that can be resolved quickly.
The TMS configuration should support:
- cash by entity split into free, conditional, reserved, restricted and uneconomic categories
- forecast surplus after local buffer across relevant horizons
- approved internal funding capacity and current utilisation
- transfer route, expected lead time, cost and documentary requirements
- open actions such as tax opinion, covenant consent, board approval or bank setup
Drill-down should reach the source balance, mobility rule and decision evidence. Management should be able to understand why two similar balances have different mobility outcomes.
6. Measure liquidity unlocked and constraints resolved
Mobility management should produce more than a static trapped-cash total. The objective is to increase the proportion of cash that can support group decisions while avoiding unnecessary transfers and respecting entity needs.
Management reporting should measure:
- mobilisable cash as a percentage of visible cash by currency and region
- value of surplus transferred, invested locally or used to avoid external borrowing
- average lead time and all-in cost by transfer route
- expired rules, unresolved constraints and overdue approvals
- entity liquidity incidents or emergency reversals after internal transfers
The quality metric is not maximum centralisation. A local investment can be the right answer when transfer cost exceeds the benefit or local obligations require the cash to remain in place.
7. Start with material balances and repeatable routes
The initial programme should focus on entities and currencies that materially affect group funding. Treasury can then establish a repeatable mobility assessment, validate transfer mechanisms and expand to smaller populations once governance is working.
The implementation plan should sequence:
- rank entities by average surplus, volatility, external borrowing impact and constraint complexity
- complete legal, tax and covenant assessments for priority routes
- configure mobility classes and minimum buffers in the TMS
- pilot transfers with full bilateral confirmation and accounting reconciliation
- review outcomes and update rules before scaling to additional entities
Periodic reassessment is essential. A route that was attractive in a low-rate environment may become uneconomic, and a previously restricted market may become more accessible.
Management questions before approval
Before management approves cash mobility treasury, the discussion should test the boundary described by classify cash by transferability and time horizon, the reliability of entity, country, currency and account to which the rule applies, and whether minimum post-transfer liquidity and stress buffer by entity remains effective when an exception occurs. It should also ask how mobilisable cash as a percentage of visible cash by currency and region will reveal whether the decision delivered its intended treasury result.
- Is visible cash classified by transferability, timing and cost?
- Does each mobility rule identify its owner and review date?
- Are local operating and stress buffers reflected?
- Can treasury compare all permitted transfer routes?
- Are tax, legal and covenant conditions documented?
- Are internal limits and pricing rules configured?
The TMS record should connect those answers to choose the transfer route through a structured decision and to the action 'rank entities by average surplus, volatility, external borrowing impact and constraint complexity'. Where judgement changes the normal route for cash mobility treasury, the evidence, approver, effective date and next review should remain visible beside cash by entity split into free, conditional, reserved, restricted and uneconomic categories.
Evidence a controlled TMS should retain
The operating record for cash mobility and intercompany funding should show how entity, country, currency and account to which the rule applies became an approved action under protect entity solvency and bilateral consistency. It should retain source identity, calculation or transformation, workflow status, exception treatment and approval, together with the downstream result represented by cash by entity split into free, conditional, reserved, restricted and uneconomic categories.
- minimum post-transfer liquidity and stress buffer by entity
- authorised internal lending and borrowing limits
- approved pricing methodology, currency and day-count terms
- cash by entity split into free, conditional, reserved, restricted and uneconomic categories
- forecast surplus after local buffer across relevant horizons
- approved internal funding capacity and current utilisation
Version history for entity, country, currency and account to which the rule applies should preserve the information used when the decision was taken, even if later correction changes the current view. Comparing that history with mobilisable cash as a percentage of visible cash by currency and region and the practical outcome in 'a group surplus that could not fund tomorrow’s maturity' allows management to evaluate process discipline and decision quality without hindsight rewriting.
Practical illustration: a group surplus that could not fund tomorrow’s maturity
A group reports equivalent cash of ₹1,200 crore and a debt maturity of ₹300 crore due in two days. Initial management reporting suggests no funding action is required. The mobility dashboard shows that ₹420 crore is pledged or regulated, ₹260 crore supports local operating buffers, and ₹190 crore can be transferred only after tax clearance and a five-day approval process.
Only ₹330 crore is currently mobilisable. Treasury executes a documented short-term intercompany loan of ₹220 crore from two surplus entities and draws ₹80 crore under a committed facility to preserve a central buffer. It also begins the approval process for a longer-term dividend route rather than forcing an uneconomic emergency transfer.
The insight is that cash mobility converted a reassuring group total into an executable funding plan.
Implementation checklist
A treasury team preparing to operationalise this topic should be able to answer yes to the following questions:
- Is visible cash classified by transferability, timing and cost?
- Does each mobility rule identify its owner and review date?
- Are local operating and stress buffers reflected?
- Can treasury compare all permitted transfer routes?
- Are tax, legal and covenant conditions documented?
- Are internal limits and pricing rules configured?
- Do both entities receive one confirmed transaction record?
- Are maturities and rollovers monitored?
- Can management reconcile visible cash to mobilisable cash?
- Are constraints tracked to resolution rather than merely reported?
Common design failures
Mobility decisions become unreliable when treasury uses broad country labels or treats every intercompany transfer as operationally identical.
- classifying all cash in a jurisdiction as trapped without analysing specific routes
- ignoring local forecast uncertainty when declaring surplus
- using undocumented or inconsistent intercompany pricing
- recording only one side of the internal transaction
- allowing temporary approvals and legal opinions to remain valid indefinitely
- optimising central cash at the expense of entity solvency or payment continuity
A transparent mobility model allows the group to respect constraints and still improve liquidity. It replaces intuition with a governed sequence of evidence and action.
Closing perspective
Visible cash becomes strategically useful only when treasury understands its mobility. That requires more than country knowledge: it requires entity-level rules, forecasts, buffers, route economics, approvals and bilateral execution.
A TMS can connect those elements so that group liquidity decisions are based on what can actually be moved, not what happens to appear in a consolidated balance.
Frequently asked questions
What is cash mobility in treasury?
Cash mobility is the ability to transfer or otherwise deploy cash across entities, accounts, currencies or jurisdictions within an acceptable time, cost and risk framework.
Is trapped cash the same as restricted cash?
Not always. Restricted cash may be legally or contractually unavailable. Trapped cash is a broader management term that can include regulatory, tax, operational, economic or timing constraints.
How can a TMS support intercompany funding?
A TMS can identify surplus, apply mobility rules, compare routes, enforce limits and pricing, coordinate approvals, generate bilateral confirmations, post mirror entries and monitor maturity and settlement.