Role of Treasury in Financial Risk Management

Why Treasury Risk Management Is Harder in Practice Than on Paper

Every treasury function operates with a documented risk mandate. Currency exposure stays within defined bands. Liquidity is monitored against covenant thresholds. Counterparty concentrations are capped. The policies exist, the frameworks are signed off, and the responsibilities are assigned. On paper, the risk management infrastructure looks complete. 

The gap appears somewhere between the policy and the exposure picture. 

A Group Treasury Director monitoring exposure across eight operating entities is rarely working from a consolidated, current picture of what the group actually holds. Regional entities report at different times. Systems do not share a common data layer. By the time positions are aggregated and a consolidated figure emerges, market conditions have shifted and the consolidation already describes something that no longer exists. The mandate has not failed. The information infrastructure behind it has. 

This is not unusual. The PwC 2025 Global Treasury Survey found that 36% of organizations still incorporate manual processes in exposure capture, and 16% rely on offline or homegrown systems for financial risk management specifically. Those numbers reflect something most treasury professionals already recognize from experience. The gap between having a risk framework and having real-time visibility into the exposures that framework is supposed to monitor is where the operational problems in treasury risk management actually live. 

Where Exposure Visibility Breaks Down in Treasury Operations

The structural problem with treasury exposure visibility is not that data is unavailable. Most organizations have it somewhere. It lives in multiple places, arrives at different times, and requires manual assembly before anyone can act on it. 

In a multi-entity environment, this becomes a compounding issue. A regional subsidiary closes its books at local end of day and sends an exposure report. Another entity, operating in a different time zone, has not closed yet. A third is mid-settlement on a transaction that will materially affect the group’s net currency exposure once it clears. The consolidation that reaches group treasury reflects all three entities, but not at the same moment. What looks like a group exposure picture is actually a composite of several different points in time stitched together into a single figure. 

The gaps this creates are specific and recurring: 

• Delayed exposure reporting: entities report on their own schedules and consolidation runs after the fact, meaning group treasury is routinely working from figures that are hours behind current market conditions 

• No shared data layer: when treasury management systems across entities do not integrate directly, exposure data has to be extracted, reformatted, and manually consolidated, introducing lag and the possibility of error at each transfer point 

• Incomplete intraday visibility: transactions, facility draws, and intercompany settlements that occur between reporting cycles are invisible to group treasury until the next consolidation run 

• Currency translation timing: in multi-currency environments, the rate applied to translate a subsidiary’s local exposure into the group’s reporting currency may not reflect current market rates at the time of review 

These are not edge cases. They are the routine conditions under which most treasury teams consolidate exposure data. By the time the data is assembled and reviewed, it is already a partial picture of an exposure that has continued shifting. 

The consolidation mechanics and data infrastructure conditions that create this lag are examined in how centralized data improves treasury efficiency. 

How Risk Identification Lags Behind Market Movement

Treasury risk reporting is structurally retrospective. Not because teams are slow or processes are poorly designed, but because data moves through a sequence of collection, aggregation, and consolidation before it reaches the person who needs to act on it. By the time that sequence completes, the report describes a risk picture that existed at some point earlier in the day, or earlier in the week. 

Markets do not observe that sequence. A currency pair can move two percent in a session. A sovereign credit event can reprice an entire asset class before a consolidation run completes. An interest rate decision can shift the cost of an unhedged exposure materially between the moment it was last measured and the moment a decision about it needs to be made. The reporting cycle and the market cycle operate on different timescales, and the gap between them is where risk accumulates without registering. 

Hedging decisions illustrate the consequence most clearly from a data visibility perspective. A treasury team reviewing an overnight consolidation is assessing an exposure figure that was accurate at close of business yesterday. If the underlying exposures have shifted since then through intraday transactions, settlements, or market rate changes, the assessment is based on a figure that no longer reflects current conditions. It may still be within policy tolerance. The decision is still being made with less visibility than the mandate requires.Responsiveness suffers for the same reason. When conditions shift and a review is needed, the quality of that review depends entirely on how current the underlying exposure data is. A team relying on end-of-day reporting cannot assess intraday exposure changes, regardless of how well-designed their risk framework is. 

How this reporting lag translates into decision quality problems at the CFO and finance director level is covered in how real-time visibility helps leadership make better financial decisions. 

What Happens When Liquidity Risk Sits Outside the Reporting Cycle

Liquidity risk occupies a different part of the treasury risk picture than market or counterparty exposure. Currency sensitivity and interest rate risk live in exposures that update as markets move. Liquidity risk lives in the relationship between what the organization expects to happen in cash flows, facility availability, and working capital, and what actually happens. That relationship is only visible when the forecast, the facility position, and the current cash picture are all current at the same time. When any one of them lags, the liquidity picture becomes unreliable in a way that is harder to detect than a stale FX exposure reading. 

Cash flow forecasts are built on assumptions, receivables timing, payables schedules, intercompany settlement dates, that were reasonable when the model was last updated. Counterparties do not always behave according to those assumptions. A key customer delays a significant receivable. A supplier draws on an intercompany facility earlier than modeled. Neither event triggers an automatic update to the liquidity forecast. Treasury finds out when the picture is already different from what the model predicted. 

Facility headroom carries a similar visibility problem. A revolving credit facility provides a buffer, but available headroom at any point depends on what has been drawn, what covenants are in effect, and whether draws earlier in the day have been reflected in the current balance. Covenant calculations tend to run on reporting cycles rather than continuously. A treasury team monitoring headroom against an end-of-day covenant figure may not have a current picture of where the covenant sits intraday, which matters most precisely when conditions are moving quickly and the buffer is being tested. 

Three visibility gaps appear consistently in multi-entity liquidity management: 

• Offshore cash translation: cash held in subsidiaries in restricted or illiquid currencies may appear available in a consolidated view but cannot be repatriated or redeployed without friction the headline figure does not reflect 

• Intercompany loan accessibility: funds lent between entities within the group may be visible on paper but practically inaccessible within the timeframe a liquidity need requires 

• Intraday facility draws: drawdowns made during the business day by regional entities are often not visible to group treasury until the next consolidation cycle, meaning the available liquidity picture at any given moment may differ materially from the last reported figure 

Liquidity risk in a multi-entity environment is not always where the consolidated report suggests it is. The report shows a snapshot of a position at a point in time. What it cannot always show is whether that snapshot reflects liquidity that is accessible, accurate, or consistent with the covenant obligations it is supposed to support. 

When Risk Data Gaps Reach the Decision Table

Exposure visibility problems, reporting lag, and liquidity blind spots do not stay contained within treasury operations. They travel upward. The decisions that depend on current, consolidated, accurate risk data are made at a level where the people making them have no direct line of sight into whether the underlying data reflects current market conditions. 

Hedging decisions illustrate this most clearly from a data visibility perspective. A treasury team reviews the consolidated exposure picture from the most recent reporting cycle. That picture was accurate when it was produced. Between then and now, a subsidiary has settled a transaction that reduced the underlying exposure, and a counterparty has delayed a receivable that increased it. The net effect may be modest. It may also be material. The assessment is based on an exposure picture that nobody in the room can verify still reflects current conditions. 

Liquidity approvals carry the same structural uncertainty. A CFO approving a capital allocation or a facility draw is working from a cash availability figure that reflects the last consolidated position. If intraday draws by regional entities have reduced available headroom since that consolidation ran, the approval is based on a liquidity picture that may no longer reflect the current state. The decision is not wrong in intent. It is made in a gap between what the data showed and what the current exposure picture actually is. 

This is where the problem becomes a governance issue rather than just an operational one. A finance director signing off on a treasury risk summary is making a judgment about whether the summary reflects current market conditions, not just whether the numbers add up. When the data infrastructure cannot support real-time treasury risk reporting, that sign-off becomes an act of reasonable assumption rather than informed oversight. Most CFOs who have operated in this environment recognize the feeling. The report looks complete. The question they cannot fully answer is whether it is current. 

The rate-driven market dynamics that compound liquidity and exposure visibility gaps are examined in [the relationship between interest rates and commodities. 

What Real-Time Visibility Changes in Treasury Risk Management

Improving the data infrastructure behind treasury risk management does not change the mandate. The risk categories stay the same. What changes is whether the information available to support that mandate reflects what is actually happening in the market at the moment a decision needs to be made. 

When consolidated exposure data updates continuously, decisions about hedging coverage are based on an exposure picture that reflects current market conditions rather than where things stood several hours ago. That does not eliminate basis risk. It removes the layer of structural uncertainty that sits between a policy limit and the actual exposure picture it is supposed to govern. 

Liquidity monitoring shifts in a similar way. When facility headroom, covenant calculations, and cash positions across entities are visible as they change rather than as they were reported, the question treasury is answering changes. Whether the current liquidity picture requires review now is a more useful question than whether it falls within the range suggested by the last report. That distinction matters most when conditions are moving. 

For CFOs and finance directors, the shift is less about operational efficiency and more about oversight quality. Signing off on a risk summary described by data you can verify is current is a different act from signing off on a summary described by data you have reason to trust but cannot confirm. The gap between those two conditions is where governance risk quietly lives in treasury operations that have not modernized their data infrastructure. 

Real-time treasury market intelligence changes four things at the visibility level: 

• Consolidated exposure monitoring: group treasury sees the full exposure picture across all entities at the same moment, measured against current market rates rather than yesterday’s close 

• Intraday liquidity tracking: facility draws, settlements, and intercompany movements update the cash picture as they occur, so the available liquidity figure reflects current conditions rather than a prior consolidation snapshot 

• Current covenant monitoring: covenant calculations are tracked against live data rather than end-of-day snapshots, giving treasury and finance leadership an accurate headroom picture when conditions are moving 

• CFO-level reporting confidence: risk summaries presented to leadership describe the exposure picture as it exists at the moment of review, not a picture reconstructed from a reporting cycle that closed hours earlier 

Treasury teams operating with this level of visibility are not monitoring risk differently in principle. They are monitoring it with the market intelligence the mandate always assumed they had. 

Tresmark’s treasury market data and visibility platform consolidates real-time exposure data, liquidity positions, and market rates across entities, giving treasury and finance teams the market intelligence to monitor risk at the moment conditions exist rather than at the interval their reporting cycle allows. 

How the same data visibility gap affects procurement decisions and cross-functional cost alignment is covered in improving procurement decisions using commodity insights.