Treasury dealing mandates: define who may trade, with whom and within what limits

A dealing mandate sets the boundaries within which named treasury staff may enter deposits, FX trades, derivatives or other permitted transactions. This guide explains the mechanics, evidence, risks and controls a UK business should understand before relying on the process.

What treasury dealing mandates means in practice

A dealing mandate sets the boundaries within which named treasury staff may enter deposits, FX trades, derivatives or other permitted transactions. The commercial effect often appears before accounting catches up, so treasury should identify the exact event that changes the position.

Authority should be specific enough to identify products, counterparties, value limits and tenor limits rather than relying on a broad statement that someone may 'manage treasury'. A practical procedure should say exactly who checks the condition, when it is tested and where the supporting record is retained.

How treasury dealing mandates works from start to finish

The operating file should contain authorised dealers, permitted instruments, per-deal limits, tenor limits, counterparty limits, escalation thresholds, confirmation addresses and mandate expiry dates. Bringing those facts together prevents legal, treasury and accounting teams from reaching different conclusions about the same event.

Operational ownership should follow the transaction through to its final state. The person who initiates an action does not need to perform every later step, but the business must know who owns unresolved exceptions.

The data and evidence that matter

Evidence also needs a retention location that survives staff turnover. A material treasury dealing mandates decision should be understandable from the treasury or finance record without depending on a private mailbox or one employee's memory.

An effective record should also make the exception path visible. If the normal rule cannot be met, the team should capture who approved the deviation, how long it applies and what evidence will close it. For treasury dealing mandates, that distinction prevents a temporary workaround from becoming an undocumented permanent practice. For treasury dealing mandates, the specific checkpoint is this: Link dealer authority to the same live limit data used for counterparty and liquidity monitoring, and block rather than merely report prohibited trades where systems allow.

Where the process can fail

A trader may stay within a personal transaction limit while causing the company to exceed a counterparty or tenor limit that sits elsewhere in the treasury policy. The financial exposure can grow quickly when the issue is discovered close to settlement, drawdown or payment day.

Deadline pressure can also weaken controls. If the process depends on an emergency override every month, the underlying timetable is wrong and should be redesigned rather than normalising exceptions.

Worked example: test the mechanics

An authorised dealer can place deposits up to £2 million per trade. A bank counterparty has only £1.2 million of remaining approved capacity. The dealing mandate does not justify a £2 million deposit because the counterparty limit is the tighter control.

This example is a method rather than a universal rule. The business should replace every illustrative figure with its own contractual terms, bank data and dates, then test the result before assuming that cash or authority is available.

Governance and controls for treasury dealing mandates

Link dealer authority to the same live limit data used for counterparty and liquidity monitoring, and block rather than merely report prohibited trades where systems allow. A reviewer should be able to see the rule, the data used and the final status in one case file without rebuilding the chronology from emails.

Monitoring should focus on unresolved items and ageing. For treasury dealing mandates, management gains more from seeing exceptions that are approaching a deadline than from a report showing only how many transactions completed successfully.

Senior review is most valuable where judgement remains. Automated controls can check limits and formats, but unusual legal, liquidity or counterparty issues still need an accountable person to decide whether the business should proceed.

Decision records should separate three layers: what the governing document or payment scheme allows, what the bank or counterparty operationally supports, and what internal policy permits. Those layers can produce different answers, and treasury dealing mandates is safest when the difference is explicit before the transaction proceeds. In this workflow, the supporting record should cover authorised dealers, permitted instruments, per-deal limits, tenor limits, counterparty limits, escalation thresholds, confirmation addresses and mandate expiry dates.

The review should use authorised dealers, permitted instruments, per-deal limits, tenor limits, counterparty limits, escalation thresholds, confirmation addresses and mandate expiry dates and should identify which item would force the team to pause, obtain consent or change the planned date. A useful challenge question is whether the transaction would still be safe if a trader may stay within a personal transaction limit while causing the company to exceed a counterparty or tenor limit that sits elsewhere in the treasury policy. Where that answer is uncertain, link dealer authority to the same live limit data used for counterparty and liquidity monitoring, and block rather than merely report prohibited trades where systems allow.