CAIIB – BFM

CAIIB BFM – December 2026

Article

122/174

Treasury Supervision, Control and Segregation of Duties - Article

Treasury deals expose a bank to market, credit, liquidity, settlement, operational, and conduct risks. Effective supervision therefore requires **clear segregation of Front Office, Mid Office, and Back Office functions**, Board-approved limits, independent risk monitoring, confirmation, reconciliation, valuation, exception reporting, and audit. This article uses practical cases to explain how treasury controls prevent unauthorised dealing, concealed losses, settlement failures, and manipulation.

Free preview 18 min read 5 views English
Published
In this article

Introduction

Treasury handles some of the bank's largest and fastest-moving transactions.

A dealer may execute:

  • Government securities;

  • money-market instruments;

  • foreign exchange;

  • repos;

  • derivatives; and

  • other authorised treasury products

within seconds.

This speed creates opportunity, but it also creates risk.

A weak treasury-control structure can allow:

  • unauthorised positions;

  • excess limits;

  • incorrect valuations;

  • unrecorded deals;

  • settlement failures;

  • concealed losses;

  • incorrect accounting; or

  • fraud.

Therefore, the central principle of treasury supervision is:

The person who takes the risk should not independently control, confirm, settle, value, and account for that same risk.

The current 2026 IIBF CAIIB BFM syllabus specifically includes “Supervision and Control of Treasury” under Module C – Treasury Risk Management.

RBI's current investment directions require a robust internal-control framework and clear functional separation among trading, settlement, monitoring/control, and accounting. RBI guidance for treasury and Primary Dealer operations similarly recognises the familiar Front Office–Mid Office–Back Office segregation.

Learning Objectives

After studying this topic, you should be able to:

  • explain why treasury requires strong segregation of duties;

  • distinguish Front Office, Mid Office, and Back Office responsibilities;

  • understand the role of senior management and the Board;

  • identify important dealing, limit, confirmation, valuation, and reconciliation controls;

  • recognise conflicts of interest in treasury operations;

  • analyse dealing-limit and settlement-control cases;

  • identify weaknesses in new-product and exception-management processes; and

  • solve CAIIB case studies involving treasury supervision.

Why Treasury Requires Stronger Controls

Treasury differs from many traditional banking activities because:

  • transaction values can be very large;

  • market prices move continuously;

  • dealers can create positions quickly;

  • exposures can change intraday;

  • complex instruments may be difficult to value;

  • settlement occurs through specialised systems; and

  • losses can grow rapidly if a breach remains undetected.

Controls must therefore operate before, during, and after a deal.

A good framework is:

Authorise → Execute → Capture → Monitor → Confirm → Settle → Reconcile → Review

No single individual should control this complete cycle.

Three-Layer Treasury Structure

The classic control structure consists of:

  1. Front Office

  2. Mid Office

  3. Back Office

Each has a different responsibility.

Front Office

The Front Office is the dealing and trading function.

It may undertake authorised activities such as:

  • buying and selling securities;

  • money-market borrowing and lending;

  • foreign-exchange dealing;

  • repo transactions;

  • derivative transactions;

  • customer pricing; and

  • managing authorised market positions.

The Front Office therefore creates market and counterparty exposure.

Typical dealer responsibilities include:

  • dealing only in approved products;

  • remaining within delegated limits;

  • executing at appropriate market rates;

  • promptly recording deals;

  • identifying the correct counterparty; and

  • following authorised dealing procedures.

The dealer should not independently perform the final control over the risks created by the dealer.

Mid Office

The Mid Office provides independent risk monitoring and control.

Typical responsibilities include:

  • monitoring dealer and desk limits;

  • measuring market risk;

  • monitoring counterparty exposure;

  • independent price/valuation checks;

  • monitoring open positions;

  • VaR, duration, sensitivity, or other risk measures;

  • stress testing;

  • monitoring stop-loss limits;

  • exception reporting;

  • regulatory monitoring; and

  • management information.

RBI guidance for Primary Dealers specifically requires an independent risk-control unit responsible for analysing risk-measurement output, monitoring the relationship between exposures and trading limits, back-testing, and reporting to sufficiently senior management.

The key word is:

Independent

A Mid Office controlled by the traders whose risk it monitors would weaken the entire control structure.

Back Office

The Back Office processes and settles transactions created by the Front Office.

Typical responsibilities include:

  • independent deal confirmation;

  • settlement instructions;

  • payment and receipt of funds;

  • delivery and receipt of securities;

  • transaction accounting;

  • reconciliation;

  • monitoring failed settlements;

  • maintaining settlement records; and

  • resolving operational exceptions.

RBI's investment directions require controls over deal documentation, receipt of counterparty confirmations, verification, reconciliation, valuation, prudential limits, risk limits, and cancelled deals.

Front, Mid and Back Office Comparison

Function

Front Office

Mid Office

Back Office

Main role

Deal and take authorised positions

Independently monitor risk

Process and settle transactions

Creates market exposure

Yes

No

No

Executes trades

Yes

No

No

Monitors limits

Should know limits

Independently monitors

Operational checks where relevant

Risk measurement

Uses for dealing

Primary independent role

Not primary role

Independent valuation/check

No final control

Yes

Supporting/accounting role

Confirmation

Deal information initiated

Exception oversight

Independent confirmation

Settlement

No

No

Yes

Accounting

No

No / oversight only

Yes or independent accounting function

Reconciliation

Not controlled by dealer

Reviews exceptions

Performs/coordinates

Main control principle

Take authorised risk

Challenge and monitor

Complete transaction correctly

Process diagram showing segregation between treasury Front Office dealing, Mid Office risk control, and Back Office settlement and reconciliation.
Effective treasury control separates risk-taking from independent risk monitoring and transaction settlement.

Functional Segregation Is More Important Than Job Titles

Calling three employees:

  • Dealer;

  • Risk Officer; and

  • Settlement Officer

does not create genuine segregation if one individual can override the others.

The control must operate in practice.

For example, a dealer should not be able to:

  • alter risk limits;

  • independently approve a limit excess;

  • modify settlement instructions after execution without control;

  • confirm the transaction on behalf of the counterparty;

  • authorise payment;

  • reconcile the settlement account; and

  • erase evidence of an exception.

RBI's internal-control framework emphasises actual functional separation. For derivative activities, RBI expressly requires clear functional and physical separation between Front Office and Back Office.

Role of the Board and Senior Management

Treasury control does not begin in the dealing room.

It begins with governance.

The Board or appropriate Board-level authority should establish the broad framework covering areas such as:

  • authorised activities;

  • risk appetite;

  • dealing authority;

  • exposure limits;

  • counterparty limits;

  • product approval;

  • valuation principles;

  • reporting;

  • escalation; and

  • internal controls.

Senior management converts this framework into operational limits and procedures.

RBI's supervisory framework recognises written delegation-of-power policies covering investments, money-market operations, foreign exchange, and other major activities.

Treasury Limits

A treasury dealer is not authorised to take unlimited risk.

Important limits may include:

  • individual dealer limit;

  • desk limit;

  • counterparty limit;

  • position limit;

  • currency open-position limit;

  • stop-loss limit;

  • tenor limit;

  • product limit;

  • concentration limit;

  • sensitivity or duration limit; and

  • VaR limit.

The exact limits depend on the bank's approved policy and regulatory requirements.

RBI requires appropriate exposure/dealing limits and ongoing monitoring of market risks and intraday exposures.

Case 1: Profitable Limit Breach

A dealer has authority to hold a Government-security position up to ₹200 crore.

The dealer expects yields to fall sharply and increases the position to ₹275 crore without approval.

The prediction proves correct and the bank earns a large profit.

Management argues that no control issue exists because the bank made money.

Analysis

The conclusion is wrong.

The dealer exceeded delegated authority.

The correct question is not:

Did the deal make a profit?

It is:

Was the exposure authorised when it was taken?

A limit breach remains a control breach even when profitable.

Otherwise, dealers may learn that limits can be ignored whenever they believe strongly in a market view.

Required Response

The Mid Office should:

  • identify the breach promptly;

  • report it;

  • escalate according to policy;

  • require appropriate corrective action; and

  • investigate why preventive or detective controls failed.

Case 2: Loss Hidden by Delayed Deal Entry

A foreign-exchange dealer enters into a transaction that immediately moves into loss.

Instead of entering the transaction into the treasury system, the dealer waits until the next day hoping the market will reverse.

Analysis

This is a serious control failure.

Delayed deal capture can:

  • understate the bank's true position;

  • distort limit utilisation;

  • distort profit and loss;

  • produce incorrect risk measures;

  • affect settlement;

  • conceal unauthorised dealing.

RBI requires deal records to contain core transaction details and expects transactions to be promptly captured and processed. Current investment directions also require deal slips and monitoring of cancelled deals and confirmations.

CAIIB Learning

Every deal must enter the official system promptly.

A dealer must not decide whether to record a transaction based on whether it becomes profitable.

Case 3: Dealer Also Controls Settlement

A small treasury allows the same employee to:

  • execute a bond trade;

  • enter settlement instructions;

  • authorise the payment; and

  • reconcile the settlement account.

Management says this is efficient because the employee is experienced.

Analysis

This creates excessive concentration of control.

The employee can both:

create the transaction

and

complete and verify the transaction.

That makes independent detection of:

  • fictitious trades;

  • altered settlement instructions;

  • unauthorised payments;

  • incorrect counterparties; and

  • concealed errors

much more difficult.

RBI requires clear separation of trading from settlement, monitoring/control, and accounting functions.

CAIIB Learning

Operational convenience does not justify incompatible duties.

Case 4: Counterparty Confirmation Differs from Dealer's Record

Front Office reports that it purchased a security at a particular price.

The counterparty confirmation received by Back Office shows a different price.

Settlement is due shortly.

Analysis

Back Office should not simply use whichever figure the dealer prefers.

The mismatch is an exception.

It should be:

  • investigated immediately;

  • independently checked against available transaction records;

  • escalated where required; and

  • resolved before incorrect settlement.

RBI specifically requires Back Office to monitor timely receipt of counterparty confirmations.

CAIIB Learning

Confirmation is not a clerical formality.

It is an important independent control over trade accuracy.

Case 5: Market Price Falls Below Stop-Loss Level

Treasury policy contains a stop-loss trigger.

A dealer's position crosses the approved level.

The dealer asks Mid Office not to report the breach because the market is expected to recover tomorrow.

Analysis

Mid Office must remain independent.

Its responsibility is not to support the dealer's market view.

It must:

  • report the exception;

  • follow the approved escalation procedure; and

  • ensure that any decision to retain the position is made only by the appropriately authorised authority.

RBI's supervisory approach specifically considers adherence to stop-loss/take-profit limits and the effectiveness of treasury risk-control architecture.

CAIIB Learning

Mid Office monitors the rule; authorised management decides the permitted exception.

The dealer cannot suppress risk reporting.

Case 6: Dealer Marks an Illiquid Bond at an Optimistic Price

A dealer holds an illiquid corporate bond.

Using an optimistic price makes the trading book show a profit and keeps the position within a loss limit.

The dealer asks that this price be used for valuation.

Analysis

Valuation cannot be controlled solely by the person whose performance is affected by that valuation.

There should be an independent valuation/control process using:

  • approved methodologies;

  • reliable market inputs;

  • validated models where required; and

  • documented valuation procedures.

RBI's internal-control framework explicitly includes portfolio valuation and monitoring of risk limits among required controls.

CAIIB Learning

Dealer price is information—not automatically the independent control price.

Case 7: Cancelled Deal without Independent Review

A dealer books a losing transaction.

Later the deal is cancelled in the system and replaced with a new transaction at a different price.

No independent explanation or authorisation is recorded.

Analysis

Cancelled and amended deals deserve special scrutiny because they can be used to:

  • conceal losses;

  • shift profit between periods;

  • hide unauthorised trades; or

  • manipulate dealer performance.

RBI's investment-control directions specifically require monitoring of cancelled deals.

Appropriate Control

The bank should have procedures governing:

  • who may cancel/amend deals;

  • permitted reasons;

  • independent approval;

  • audit trail;

  • reporting of unusual frequency; and

  • subsequent review.

Case 8: Counterparty Limit Is Exhausted

A dealer sees an attractive repo rate from a counterparty.

The bank's approved counterparty exposure limit is already fully utilised.

The dealer argues that the new transaction should still be entered because it is profitable and secured.

Analysis

The dealer cannot independently ignore the approved limit.

Counterparty limits reflect the bank's approved risk tolerance.

Even collateralised transactions can involve:

  • settlement risk;

  • collateral risk;

  • operational risk; and

  • residual counterparty exposure.

RBI guidance requires Board-approved dealing/exposure limits for counterparties covering relevant money-market, repo, and securities transactions.

CAIIB Learning

Pricing cannot override counterparty risk limits.

Case 9: New Derivative Product without Approval

A trader discovers a derivative structure used by another bank.

The trader believes it will be profitable and executes the first transaction before the bank has formally approved:

  • the product;

  • valuation method;

  • risk measurement;

  • accounting treatment;

  • legal documentation; or

  • settlement process.

Analysis

This is poor treasury governance.

Before launching a new product, the bank should understand and control:

  • market risk;

  • credit risk;

  • liquidity risk;

  • legal risk;

  • model risk;

  • operational risk;

  • accounting;

  • documentation; and

  • settlement.

RBI's derivative directions require identification of risks, risk-tolerance levels, comprehensive limits, stress testing, controls over model risk, legal documentation, counterparty assessment, and internal audit.

CAIIB Learning

New product approval must precede dealing.

Commercial opportunity does not replace governance.

Case 10: Unreconciled Nostro Difference

Back Office observes a large unexplained debit in a foreign-currency Nostro account.

The dealer says reconciliation can wait because the total treasury profit is positive.

Analysis

Profitability is irrelevant to reconciliation.

An unexplained Nostro difference may represent:

  • incorrect settlement;

  • duplicate payment;

  • missing receipt;

  • wrong value date;

  • fraud;

  • incorrect charges; or

  • accounting error.

RBI guidance emphasises verification and reconciliation of Nostro/Vostro transactions and balances.

The item should be promptly:

  • identified;

  • investigated;

  • aged;

  • escalated; and

  • resolved.

Case 11: Same-Day Settlement but No Reconciliation

A Government-security trade settles successfully.

Because settlement completed without failure, Back Office postpones reconciliation until month-end.

Analysis

Settlement success does not eliminate reconciliation risk.

RBI's G-Sec guidance advises that funds and investment accounts should be reconciled on the same day before close of business.

Timely reconciliation can detect:

  • wrong quantities;

  • incorrect cash consideration;

  • duplicated entries;

  • missing transactions; and

  • accounting differences.

CAIIB Learning

Settlement confirms movement; reconciliation confirms records agree.

Case 12: Broker Changes Counterparty after Deal

A dealer concludes a securities transaction through a broker.

After the deal is agreed, the broker asks the bank to replace the original counterparty with another institution.

Analysis

This should not be treated as a harmless operational adjustment.

RBI's treasury-control guidance has specifically prohibited post-deal substitution of the agreed counterparty or security through a broker in such investment transactions.

CAIIB Learning

The broker's proper role does not include changing the fundamental economic parties after a deal has been concluded.

Case 13: Mid Office Reports to Head Dealer

A bank creates a Mid Office, but the Mid Office head reports directly to the Chief Dealer whose positions it monitors.

Analysis

The structure exists in name but independence is weakened.

Risk monitoring should have sufficient organisational independence and escalation authority to challenge:

  • dealer positions;

  • limit breaches;

  • pricing;

  • risk-model output; and

  • exceptions.

RBI's market-risk guidance requires the independent risk-control unit to be separate from trading desks and to report to senior management with sufficient authority to enforce reductions in exposures where necessary.

CAIIB Learning

Independence must be organisational as well as procedural.

Case 14: Back Office Receives Dealer's Password

A dealer is absent.

To avoid delayed settlement, the dealer gives login credentials to Back Office so that staff can access the dealer's screen and modify the transaction.

Analysis

This destroys access segregation and audit accountability.

Proper control should use:

  • individual user IDs;

  • role-based access;

  • authorised backup procedures;

  • maker-checker controls; and

  • traceable approvals.

Shared credentials make it difficult to establish:

who actually performed the action.

CAIIB Learning

Segregation of duties must be supported by system-access segregation.

Case 15: Large Unusual Profit

A dealer consistently reports profits far above the rest of the treasury.

Management praises the dealer and reduces scrutiny because performance is excellent.

Analysis

Unusually high profit should not automatically imply misconduct, but it should also not reduce supervision.

Management should understand:

  • which positions created the return;

  • whether the risk taken was within limits;

  • whether prices are independently verified;

  • whether profits are realised or mark-to-market;

  • whether cancelled/amended deals are unusual; and

  • whether settlement and reconciliation records agree.

Strong performance and strong control should coexist.

Treasury Control Cycle

A robust control cycle can be understood as follows:

Before the Deal

Check:

  • product approval;

  • dealer authority;

  • counterparty eligibility;

  • available limit;

  • market conditions; and

  • documentation requirements.

At Execution

Ensure:

  • correct price/rate;

  • authorised counterparty;

  • immediate deal capture;

  • complete transaction data; and

  • audit trail.

After Execution

Independently perform:

  • confirmation;

  • position updating;

  • risk measurement;

  • limit monitoring;

  • settlement;

  • accounting; and

  • reconciliation.

After Settlement

Review:

  • exceptions;

  • failed trades;

  • cancelled/amended deals;

  • unresolved reconciliation items;

  • limit breaches; and

  • unusual profit/loss.

Treasury control cycle showing pre-trade approval, dealing, independent risk monitoring, confirmation, settlement, reconciliation and exception escalation.
Treasury supervision begins before trade execution and continues until settlement, reconciliation, and exception review are complete.

Importance of Deal Slips and Audit Trail

Every transaction should create a reliable record.

RBI's current investment directions require deal slips to capture information such as:

  • counterparty;

  • security;

  • amount;

  • price;

  • date and time;

  • confirmation method;

  • broker details where applicable; and

  • relevant investment classification.

An effective audit trail helps answer:

  • Who executed the deal?

  • When was it executed?

  • At what price?

  • With whom?

  • Was it modified?

  • Who approved the modification?

  • When was it confirmed?

  • When was it settled?

Without this record, independent supervision becomes difficult.

Maker-Checker Principle

The maker-checker principle means that one person initiates an action and another authorised person independently verifies or approves it where required.

Examples include:

  • settlement instructions;

  • payment release;

  • static-data changes;

  • counterparty-account changes; and

  • manual accounting adjustments.

Its purpose is to prevent one person from having complete control over a sensitive transaction.

Exception Reporting

A good control system does not only produce normal reports.

It highlights what is abnormal.

Important exceptions can include:

  • limit breaches;

  • off-market prices;

  • unconfirmed deals;

  • cancelled deals;

  • unusual amendments;

  • failed settlements;

  • stale valuations;

  • unreconciled balances;

  • unusual dealer profits/losses;

  • excessive counterparty concentration; and

  • repeated manual interventions.

Exception reports should reach personnel with enough authority to act.

Internal Audit

Internal audit provides another independent layer.

It should assess whether:

  • policies are adequate;

  • controls operate as designed;

  • transactions comply with authority;

  • systems accurately capture positions;

  • risk measures are reliable;

  • exceptions are resolved;

  • reconciliations are timely; and

  • segregation actually exists.

RBI requires derivative business to be subjected to internal audit to test the effectiveness of risk management and internal controls, and its investment framework also requires robust control and audit arrangements.

Segregation Does Not Eliminate Management Responsibility

Management cannot say:

“The Mid Office is responsible for all risk.”

The Front Office must remain responsible for taking authorised positions.

Mid Office independently monitors and challenges.

Back Office independently processes and settles.

Senior management remains responsible for the overall control environment.

Therefore:

Segregation distributes responsibilities—it does not remove accountability.

CAIIB Exam Focus

Front Office = dealing and risk-taking.

Mid Office = independent risk measurement, monitoring, limits, and control.

Back Office = confirmation, settlement, accounting, and reconciliation.

Trading must be functionally separate from settlement and accounting.

The person creating an exposure should not independently approve and settle the same exposure.

A profitable limit breach is still a limit breach.

Risk limits should be approved, monitored, and escalated when breached.

Mid Office independence is essential.

Counterparty confirmation is an important control.

Cancelled and amended deals require monitoring.

Independent valuation reduces the risk of traders marking their own books favourably.

Nostro and other settlement-account reconciliations should be timely.

New products require risk and control assessment before dealing.

System-access controls should support organisational segregation.

Internal audit tests whether the control system actually works.

Common Exam Traps

Trap 1: Front Office Should Also Confirm and Settle Its Own Deals

Incorrect.

That defeats independent segregation.

Trap 2: Mid Office Is Another Name for Back Office

Incorrect.

Mid Office monitors risk; Back Office processes and settles transactions.

Trap 3: A Limit Breach Is Acceptable if It Makes Profit

Incorrect.

Delegated limits apply when risk is taken.

Trap 4: Only Loss-Making Deals Need Investigation

Incorrect.

Unusual profits, prices, amendments, and patterns may also warrant review.

Trap 5: Dealer's Valuation Should Automatically Be Used

Incorrect.

Valuation should be subject to independent control.

Trap 6: Deal Confirmation Is Only an Administrative Formality

Incorrect.

Confirmation independently verifies the economic terms of the transaction.

Trap 7: Successful Settlement Means Reconciliation Is Unnecessary

Incorrect.

Accounting and settlement records can still disagree.

Trap 8: Mid Office Can Be Fully Controlled by the Trading Desk

Incorrect.

Risk control must have sufficient independence.

Trap 9: New Products Can Be Approved After the First Trade

Incorrect.

Product approval and control design should precede dealing.

Trap 10: A Broker Can Freely Substitute the Counterparty after a Deal

Incorrect.

Post-deal substitution undermines transaction integrity and is restricted under RBI's control framework.

Trap 11: Segregation of Duties Is Only a Physical Seating Arrangement

Incorrect.

The critical requirement is functional independence supported by proper access rights, authority, reporting lines, and controls.

Trap 12: Back Office Should Ignore Small Reconciliation Differences

Incorrect.

Unexplained differences require investigation according to the bank's procedures.

Trap 13: Automated Systems Eliminate the Need for Control

Incorrect.

Automation reduces some operational risks but creates dependence on:

  • system configuration;

  • access security;

  • data quality; and

  • exception handling.

Trap 14: Treasury Supervision Ends Once the Deal Is Executed

Incorrect.

Control continues through:

risk monitoring → confirmation → settlement → accounting → reconciliation → review.

Memory Technique

Remember:

F-M-B

  • F – Front Office = Finds and Executes the Deal

  • M – Mid Office = Measures and Monitors Risk

  • B – Back Office = Books, Confirms and Settles

Then remember the control chain:

A-E-M-S-R

  • A – Authorise

  • E – Execute

  • M – Monitor

  • S – Settle

  • R – Reconcile

The central CAIIB principle is:

The person who takes the risk must not independently control the complete life cycle of that risk.

Back to Treasury Supervision, Control and Segregation of Duties