CorphedgeVisit Website →
← Back to blog

Fix FX Segregation of Duties in 30–90 Days for Treasury Teams

October 7, 2026
Fix FX Segregation of Duties in 30–90 Days for Treasury Teams

Segregation of duties in FX exists to stop one person from being able to execute, confirm, and settle the same trade. The immediate priority for any treasury team is simple: separate trade capture from confirmation and settlement, assign a reconciler who never touches trade entry, and update your delegated authority matrix so limits and sign-off rights are current. Everything else builds on those three moves.

TL;DR:

  • Proper segregation of duties in FX controls trade capture, confirmation, settlement, and reconciliation to prevent one person from executing, confirming, and settling the same trade.
  • Controls should span the entire trade lifecycle, with separate ownership for each stage, including trading, confirmation, settlement, and risk oversight.
  • System access and entitlements must restrict trade entry from approval and settlement, with dual sign-offs and independent reconciliation.
  • Small treasury teams should implement compensating controls like mandatory second-person approval, daily exception reviews, and detailed audit trails due to staffing limitations.
  • Daily monitoring of settlement fails, limit breaches, and reconciliation gaps, along with periodic independent audits, is essential to ensure controls are effective.
Corphedge
corphedge.com
Strengthen Your FX Risk Controls
CorpHedge helps treasury teams monitor currency positions and apply risk management strategies across their FX operations.
Visit CorpHedge

Table of Contents

Core principles of segregation of duties for FX

Segregation of duties in FX controls three distinct exposures: principal risk, where you pay out before confirming receipt; replacement cost risk, the loss if a counterparty defaults before settlement; and settlement or operational risk, where a timing mismatch, a fat finger, or a missed fail causes a direct loss. No single control catches all three. Basel's consolidated guidance states that the board carries ultimate responsibility for FX settlement-related risk governance, while management operates the internal controls, formal policies, and timely reporting that make that governance real.

That is why SoD cannot stop at the trading desk. It has to span the full lifecycle, from pre-trade limit checks through execution, confirmation, settlement, and the reconciliation that follows.

  • Execution sits with traders operating inside board-approved limits.
  • Pre-settlement checks (confirmation, exposure monitoring) sit with an independent back or middle office.
  • Settlement and post-settlement reconciliation sit with operations or finance, never with the trader.

Even well-designed desk-level separation fails quietly if exceptions never reach senior management for challenge, which is why reporting lines matter as much as task separation itself.

Roles, responsibilities and a practical SoD matrix for FX teams

Illustration of separated FX treasury duties

A workable SoD matrix starts with naming who owns each task, then drawing hard lines around who may never hold two of them at once. Basel guidance frames this as assigning separate ownership across capture, confirmation, exposure monitoring, valuation, settlement, reconciliation, accounting, and independent assurance, which cuts both fraud risk and the chance a loss stays hidden.

A practical split looks like this:

  • Trading: executes deals within approved limits and counterparty lists, never confirms or settles.
  • Confirmation: an independent back office, or a matching service, verifies trade economics against the counterparty's version.
  • Settlement: operations releases payment instructions under dual sign-off, separate from the trader and the confirmer.
  • Reconciliation and accounting: a different individual again matches cash and position breaks and books the entries.
  • Risk oversight: a risk function sets and monitors limits independently of the desk that uses them.

Limits and exceptions should sit with risk management or treasury leadership, never with the trader requesting the exception. Escalation points need a named owner and a deadline, not just a policy statement.

Concrete controls across the FX trade lifecycle

Controls earn their value only when they are embedded at each stage of the trade, not bolted on afterward.

  1. Pre-trade: enforce counterparty limits, an approved counterparty list, and a delegated authority matrix that states who can commit the organization to what size and tenor of trade.
  2. Execution and capture: keep trade entry separate from execution authority, use pre-agreed standard settlement instructions (SSIs), and route every deal through independent confirmation rather than letting the trader confirm their own ticket.
  3. Settlement: use a payment-versus-payment (PVP) settlement mechanism through a financial market infrastructure wherever it is practicable, since BCBS supervisory guidance notes PVP eliminates principal risk outright. Where PVP is not available for a currency pair, set binding principal-risk limits and monitor exposure intraday, with dual sign-off on outgoing payments and a defined fail-management process.
  4. Post-settlement: reconcile nostro and position breaks on a fixed daily cadence, route exceptions to an independent owner, and hand off clean, matched data to accounting rather than letting operations self-certify.
  5. System entitlements: restrict system access so the person who can enter a trade cannot also approve its settlement, and use automated matching or confirmation services to remove manual steps where volumes justify it.

Pro Tip: Build your entitlements model before you build your policy document, since a policy that contradicts what the system actually permits will not survive its first audit.

Adapting SoD for small treasury teams: compensating controls

A two- or three-person treasury function often cannot staff full separation, and internal controls for small businesses treat this as a documentation and testing problem rather than a staffing one. Compensating controls close the gap without pretending it does not exist.

  • Require second-person approval on every payment release, with no exceptions for seniority.
  • Review exceptions daily, performed by someone outside the trade-to-settlement chain, even if that person sits in finance rather than treasury.
  • Restrict entitlements to the minimum needed for each role and turn on automated notifications for limit breaches and unusual settlement activity.
  • Keep an audit trail for every override, with a reason code and the approver's name.
  • Document each compensating control in writing and schedule independent testing on a fixed interval rather than leaving it to chance.

Monitoring, reporting and independent assurance

SoD only holds up if someone outside the trading chain is watching it work. Daily operational metrics should flag settlement fails, unresolved reconciliation breaks, and limit breaches the moment they occur, with an escalation trigger attached to each one.

  • Daily: fails, exceptions, and limit utilization reported to a risk owner independent of the desk.
  • Periodic: management and risk committee reporting that covers trends, not just point-in-time snapshots.
  • Independent: internal audit testing of the SoD matrix itself, with remediation tracked to a close date.

BCBS guidance expects monitoring of unusual settlement activity and counterparty exposure limits proportionate to the size and complexity of the operation, meaning a small corporate treasury needs a lighter process than a bank dealing desk, but it still needs one.

Operational 30–90 day checklist to implement or strengthen SoD for FX

  1. Update the FX policy and delegated authority matrix to reflect current roles and limits.
  2. Lock down system entitlements so trade entry, confirmation, and settlement sit with separate logins.
  3. Assign a named, independent confirmer and reconciler who hold no trading authority.
  4. Introduce standard settlement instructions and, where volumes support it, a matching service.
  5. Schedule the first independent test of the SoD matrix and set a recurring interval for future tests.

A practitioner report on multinational FX risk treats this kind of separation as the single most important internal control requirement in FX, and it stresses that responsibility for it runs across treasury, accounting, IT access administration, compliance, and internal audit rather than sitting with treasury alone.

Practitioner perspective: common pitfalls and how to avoid them

The recurring failure is not a missing policy; it is a policy nobody updated after a resignation or a system migration left old entitlements active. Review the matrix every time a role changes, not just annually, and test a small sample of trades each quarter rather than waiting for a full audit cycle to find the gap.

— Bartas

CorpHedge: how a platform plus advisory helps enforce SoD and reporting

We built the CorpHedge platform to give treasury teams one place to see exposure, limits, and entitlements together, which makes gaps in segregation of duties visible before an auditor finds them instead of after. For teams without the headcount to staff full separation, our operational expert advice and Risk Safari Tours walk through compensating controls and documentation that hold up to scrutiny, and our FX hedging course runs 220 EUR one-off for teams who want their staff trained on the controls themselves. We are extending our platform and advisory support to treasury teams in additional markets.

Corphedge

  • Centralize exposure tracking so limit breaches surface automatically rather than at month-end.
  • Use role-based entitlements inside the platform to enforce the separation your policy already requires.
  • Request a walkthrough of the product tour to see how reporting maps to your SoD matrix.

Review our use-cases page to see how the setup fits a treasury team your size.

FAQ

What does segregation of duties mean in finance?

Segregation of duties means splitting a process, such as authorizing, recording, and reconciling a transaction, across different people so no single individual controls it end to end. In FX, that means the person who trades is never the person who confirms or settles that same trade.

What is an example of segregation of duties?

A common example is requiring that the employee who requests goods cannot also approve the invoice for them, a rule university finance policy applies explicitly when staff work across departments. In FX, the equivalent is a trader who executes a deal having no ability to confirm it or release the settlement payment.

What does "segregation of duties" mean?

It is a control principle that assigns incompatible tasks, like initiating, approving, and recording a transaction, to different people so errors or fraud are more likely to be caught. The goal is not to slow work down but to make sure no single point of failure can move money unchecked.

How does separation of duties work?

It works by mapping each stage of a process to a distinct role, then restricting system access and sign-off rights so those roles cannot overlap for the same transaction. In FX operations, that typically means separate owners for trade capture, confirmation, settlement, reconciliation, and accounting, with an independent risk function monitoring limits across all of them.

Sources