Precise treasury management that optimizes risk, liquidity, and settlements is an asset that transforms back-office operations into a growth driver.
.webp)
1. Introduction
2. Managing FX Exposure
3. Settlement and Liquidity Management
4. Safeguarding: The Regulatory Dimension
5. Building the Right Foundation
For Money Service Businesses - whether a payments firm, a foreign exchange specialist, a remittance provider, or an e-money institution - treasury management is not a back-office function. It sits at the very heart of how the business operates. Unlike a corporate treasury, which exists primarily to manage cash and funding for operational purposes, an MSB's treasury is directly tied to the revenue model. Every client FX transaction and every international payment depends on a treasury function that has priced the trade correctly, hedged it appropriately, and stands ready to settle it without disruption.
Two pillars above all others determine whether an MSB's treasury function is genuinely fit for purpose: how well it manages FX exposure, and how effectively it controls settlement liquidity. Get these right, and the firm has the operational foundation to scale with confidence. Get them wrong, and the consequences range from unplanned P&L volatility through to regulatory breaches and, in the most serious cases, an inability to meet client obligations on time.
The Accumulation Problem
Every MSB that facilitates FX transactions accumulates exposure between the moment a trade is confirmed with a client and the moment it is covered in the market. For a firm transacting a handful of trades each day, this risk is manageable through manual oversight. As volume grows across multiple currency pairs, trading channels, and client segments, the aggregate open position can build quickly, and even modest adverse rate movements can translate into material P&L impact.
The starting point for managing this is real-time visibility. Treasury teams need a single, consolidated view of net and gross exposures across every currency pair the firm operates in, updated continuously as new trades flow in. In practice, many MSBs rely on a fragmented set of systems - a trading platform here, a payments system there, a spreadsheet to tie it all together - that make it difficult to see the true aggregate position at any given moment. The distinction between net and gross matters in its own right: a desk that is flat net but holds large offsetting client and cover positions still carries operational and counterparty risk on each leg.
The risk of operating without real-time visibility is not theoretical. A treasury team that cannot see its position cannot manage it, and intraday market moves do not pause to allow end-of-day reconciliation to catch up.
Setting and Enforcing Limits
Visibility on its own is not sufficient. MSBs need a structured limit framework that defines, in advance, the maximum exposure the firm is prepared to tolerate in each currency, in each tenor bucket, and in aggregate. These limits should be calibrated to the firm's risk appetite, its hedging capacity, and the liquidity characteristics of the currencies it trades. A major pair such as EUR/USD, where market depth is substantial and spreads are tight, can generally support a higher limit than a thinly traded pair such as USD/KES or EUR/PHP, where the cost of covering a position at short notice can be significant.
Limits should operate at two levels: a soft threshold - commonly set at 70–80% of the hard limit - that generates an alert and prompts a review, and a hard threshold that triggers immediate action and, where appropriate, an automatic block on further exposure-increasing activity. The distinction matters. Soft limits give the treasury team situational awareness and the opportunity to intervene before a breach occurs. Hard limits represent the firm's absolute risk tolerance and should escalate to a defined owner with a documented response procedure.
Often neglected is the governance around limit-setting itself. Markets evolve, volatility regimes shift, and client flow patterns change. A limit that was appropriate twelve months ago may be materially too loose or too tight today. MSBs should build a formal review cadence into their treasury governance framework, ensuring limits are stress-tested against historical volatility events and reviewed at an appropriate level of seniority - at least annually, and immediately on any material change in product mix, client base, or market regime.
Auto-Cover and Hedging Logic
For most MSBs, FX exposure is managed through a combination of periodic manual hedging and rule-based automatic hedging, commonly referred to as auto-cover. The principle is simple: when a trade, or an aggregate position, causes exposure in a given currency to reach a defined threshold, the system automatically executes a corresponding hedge in the wholesale market.
Well-designed auto-cover logic addresses several practical questions. What is the threshold that triggers an automatic hedge - is it based purely on notional size, or does it also take account of current market volatility and time of day? Should the system cover each large trade individually, or net multiple trades before going to market to reduce transaction costs? How should auto-cover behave during illiquid sessions, when even normal-sized trades carry elevated gap risk? And how are auto-cover trades reconciled back to the underlying client trades that generated them, both for P&L attribution and for audit purposes?
The right answers will differ by firm and by currency corridor, but the discipline of documenting, testing, and regularly reviewing this logic is non-negotiable. Auto-cover is only as good as its configuration, and a rule set calibrated for one volume profile and currency mix can quickly become inappropriate as the business grows. Transparency matters as well: dealers and Risk should be able to see why a particular trade was auto-covered and reconstruct the decision chain after the fact.
Spread Configuration as a Risk Tool
Treasury spreads - the margin applied between the mid-market rate and the rate offered to clients - serve a dual purpose. They are a source of revenue, but they are also a primary tool for managing risk. A spread that is too tight may not adequately cover the cost of hedging, particularly in volatile conditions or in pairs where the wholesale bid-offer spread is wide. A spread that is too generous damages competitiveness and pushes clients towards alternative providers.
Effective spread management requires the treasury function to understand the true cost of hedging each currency pair - including the interbank bid-offer, settlement costs, and an allowance for market impact on larger trades - and to configure client spreads accordingly. Many MSBs apply a single spread across a pair regardless of trade size, but a more refined approach uses tiered spreads that widen for smaller transactions (which carry a higher fixed cost relative to notional) and for exotic or illiquid pairs (which carry a higher hedging cost). Dynamic spread adjustment, driven by real-time measures of market volatility, represents the next level of sophistication for firms with the systems capability to support it.
Spreads also need to be monitored after the fact. Persistent slippage between expected and realised spreads in a particular pair is typically a signal that either the spread calibration is off or that value is being lost somewhere in the cover process - through a slow LP, a delayed booking, or a routing inefficiency - and warrants investigation.
How Kooltra Helps
The Invisible Risk
If FX exposure is the most visible risk in an MSB's treasury function, settlement liquidity risk is often the least visible - right up until the moment it becomes a crisis. Settlement risk arises whenever the firm has insufficient funds in a given currency account to meet its payment obligations on a given value date. In a worst-case scenario, the consequences are failed payments, frustrated clients, regulatory scrutiny, and reputational damage that is difficult to recover from.
The difficulty is that settlement obligations are not always perfectly predictable. Client flow can be lumpy, correspondent bank cut-off times are unforgiving, and the timing of inbound receipts does not always align neatly with outbound payment requirements. Managing this effectively demands both forward visibility and operational discipline.
Building the Settlement Ladder
The most important tool in managing settlement liquidity is a multi-day settlement ladder: a currency-by-currency, date-by-date view of all confirmed payables and receivables for at least the next three to five business days. This gives the treasury team advance sight of where shortfalls may arise, allowing them to act pre-emptively - drawing on a credit line, accelerating an inbound payment, or adjusting pre-funding levels - before a problem materialises.
The ladder needs to distinguish between value dates (T+0, T+1, and T+2 being the most common) and should incorporate cut-off time data for each currency corridor. USD payments through CHIPS and Fedwire, GBP payments through CHAPS, and EUR payments through T2 (the ECB platform that replaced TARGET2) each have specific intraday windows that determine whether a payment will settle on the intended value date. Missing a cut-off effectively pushes a payment to the following business day, with knock-on implications for client expectations and the firm's own liquidity planning.
Scenario capability is also valuable. What would the liquidity picture look like if today's volume came in fifty percent above forecast? What if a large inbound payment was delayed twenty-four hours? What if a major correspondent bank experienced an outage? Running these scenarios regularly builds a culture of proactive liquidity management rather than reactive firefighting.
Nostro Management and Pre-Funding
For most MSBs, settlement obligations are met through a network of nostro accounts held with correspondent banks in the currencies the firm operates in. Managing these accounts well is both an art and a science. Pre-fund too heavily and the firm ties up capital in idle balances earning little or no return. Pre-fund too lightly and it risks settlement shortfalls or becomes dependent on expensive intraday credit from correspondent banks.
The optimal approach involves setting minimum balance thresholds for each nostro based on expected daily settlement needs, with a buffer to absorb intraday volatility, and establishing a clear process for sweeping surplus balances back to a central treasury currency on a regular basis. Firms with strong correspondent bank relationships can also negotiate intraday credit facilities that provide a safety valve in periods of unexpectedly high settlement demand, although these should be treated as backstop arrangements rather than a substitute for sound pre-funding discipline.
Counterparty diversification is worth attention too. Concentrating settlement activity through a single correspondent in a given currency may be operationally convenient, but it creates a single point of failure. The withdrawal or sudden constraint of a correspondent banking relationship - whether for commercial, regulatory, or risk-management reasons - is a well-known stress event for MSBs, and the firms that weather it best are those that have already built relationships with alternatives.
How Kooltra Helps
For most MSBs, settlement liquidity management carries an additional regulatory dimension in the form of client fund safeguarding obligations. The specifics vary by jurisdiction, but the underlying principle is consistent across major regimes: a firm holding client money in connection with payment or e-money services must keep those funds separate from its own working capital, and must be able to demonstrate at all times that safeguarded balances are sufficient to meet outstanding client obligations.
The UK's CASS 15 regime, introduced by the FCA as part of its broader Safeguarding Review, sets out detailed requirements around designated safeguarding accounts, qualifying liquid asset investments, daily reconciliations, and resolution-pack documentation to support the orderly return of client funds in an insolvency scenario. Canada's Retail Payment Activities Act (RPAA), administered by the Bank of Canada, imposes comparable obligations on payment service providers, including end-user fund safeguarding requirements and ongoing operational risk and incident response standards. In the European Union, the second Payment Services Directive (PSD2) and the Electronic Money Directive establish equivalent safeguarding principles, with implementation details varying across member-state competent authorities. In the United States, money transmitter regulation operates primarily at the state level, with permissible investment and net worth requirements that effectively serve a similar function, alongside emerging federal-level scrutiny. Singapore's Payment Services Act, Australia's stored value facility framework, and frameworks in Hong Kong, the UAE, and other major jurisdictions follow broadly the same pattern, even where the detailed mechanics differ.
The common operational requirement across all of these regimes is structural. Regulated MSBs must segregate client funds from their own money, hold them in designated accounts or qualifying liquid investments, and perform regular - typically daily - reconciliations to confirm that the safeguarded amount matches outstanding client obligations. This places a structural constraint on how an MSB can use client balances. Unlike a bank, which can deploy customer deposits as part of its own balance sheet, an MSB must ring-fence client funds and maintain clear documentation of the safeguarding calculation at all times. Errors here - even administrative oversights rather than deliberate misuse - can constitute regulatory breaches with material consequences.
For firms operating across multiple jurisdictions, the challenge is multiplied. A global MSB may be subject to overlapping but non-identical safeguarding requirements in each market it serves, with differing definitions of what constitutes client money, what counts as a qualifying safeguarding arrangement, and how reconciliation evidence must be documented. The operational model needs to be designed to satisfy the strictest applicable requirement in each currency and entity, not the most convenient.
In practice, effective safeguarding requires close coordination between treasury, finance, and compliance. Treasury needs to know which balances are safeguarded and therefore unavailable for general operational use. Finance needs accurate, timely data on outstanding client obligations to support the daily reconciliation. Compliance needs assurance that the framework is operating as intended and that any breaches are identified and remediated promptly. Firms that treat safeguarding as a compliance exercise rather than an operational discipline tend to accumulate timing gaps, rounding errors, and undocumented edge cases that become significant issues under regulatory scrutiny.
How Kooltra Helps
Across both FX exposure management and settlement liquidity, the common thread is that effective treasury management in an MSB is only as good as the systems, processes, and governance structures that support it. Real-time exposure visibility requires technology that aggregates data from multiple sources without latency. Sound limit management requires governance that is genuinely owned by senior management, not just documented in a policy file. Settlement planning requires operational processes that are executed consistently, not just designed soundly on paper.
For growing MSBs, the temptation is often to defer investment in treasury infrastructure until the business is larger. The risk of that approach is that, by the time the volume is there to justify the investment, the operational and regulatory exposure from inadequate controls has already accumulated. The firms that manage treasury most effectively tend to be those that build the framework early, scale it deliberately, and treat it as a source of competitive advantage rather than a cost centre.
Equally important is the choice of technology partner. The right platform can transform treasury from a reactive function into a strategic capability - surfacing exposures in real time, enforcing limits consistently, and converting settlement data into actionable intelligence that supports both day-to-day operations and longer-term commercial decisions. The wrong one creates exactly the opposite: brittle workflows, manual workarounds, and blind spots that compound as the business grows. Selecting a partner with deep domain expertise in FX and payments operations, a proven track record at scale, and a roadmap aligned with the firm's own growth trajectory is one of the most consequential decisions a treasury function will make.
In an industry where margins are under continuous pressure and regulatory expectations are rising, a treasury function that operates with precision - managing risk tightly, deploying liquidity efficiently, and meeting settlement obligations without fail - is not merely a risk management asset. It is a commercial one.
.png)
