1. Treasury Operations
  2. Features
  3. Treasury deals
Feature · Treasury deals

Treasury deals

Record FX, money market and ALM deals under their authorizing instruction and complete them only on approval and verified bank evidence.

OverviewDeals Awaiting Approval
Treasury Operations · Treasury deals

Deals Awaiting Approval

Approval conditions

New
ParentInstrumentTrade dateNotional USDCounterparty confirmationRevision
BI-69762INS-31608 Oct100CC-544640
BI-73473INS-41423 Oct870CC-411220
BI-47534INS-70010 Oct440CC-861840
BI-70913INS-42705 Oct290CC-602860
BI-91533INS-11122 Oct80CC-706480
6 of 6 records
INS-316Treasury deals · TD-75353
ParentBI-69762
Trade date08 Oct
Notional USD100
Counterparty confirmationCC-544
Revision640
Example screen with sample data

What you can do

Tie every deal to the money that settles it

A treasury deal records what the desk traded: an FX spot or forward, a money market deposit or loan, an ALM hedge. Each deal names its instrument, trade date, notional in US dollars and the counterparty’s confirmation reference, and sits under the bank instruction that authorizes its settlement. The deal carries its own revision and decision date.

Deals move through Draft, Submitted, Approved or Rejected, and Completed. The preparer submits the deal. An independent approver records a decision for the same instruction and revision. The deal completes only when the instruction’s source authority is confirmed and verified bank evidence is in.

How the work is organized

  • Under an authorized instruction. A deal is always recorded under its parent instruction, so the settlement and the trade are read together.
  • Independent approval. The approver who decides on the deal did not prepare it, and decides on the exact revision.
  • Complete on evidence. Approval alone does not complete a deal. Completion needs verified settlement or confirmation evidence from the bank.

What to agree during setup

Agree the instrument names the desk will use, such as FX Spot, FX Forward, MM Deposit and IRS Hedge. Agree how the counterparty’s confirmation reference is recorded. Agree whether deals are entered before or after the trade is struck, and the deadline for entering them. Decide who approves deals and whether that differs from instruction approval.

Check the handoff on an actual case

The dealer buys EUR 10,000,000 against USD for spot value at 1.0850, a notional of 10,850,000 USD. The preparer records the deal with instrument FX Spot, the trade date and the bank’s confirmation reference, under the instruction that pays the USD leg, and submits it. The approver checks the confirmation against the dealer’s ticket and approves the deal.

Two days later the bank’s settlement advice for the USD payment arrives and is verified. The instruction is confirmed and the deal moves to Completed. If the bank’s confirmation had shown a different rate, the approver would have rejected the deal and the preparer would have raised a corrected revision.

What your team sees

  • Deal Blotter — All deals by status with instrument, trade date, notional, confirmation and revision.
  • Deals Awaiting Approval — Submitted deals waiting for the approver.

Follow the work through

Review the data model before importing open deals.

What it keeps track of

Data model
Treasury deals
FX, money market and ALM deals executed against authorized instructions.
Bank instructions
Typed banking instructions raised by the treasury desk.
Review decisions
Independent reviewer decisions recorded against a specific instruction revision.
Bank evidence
Provider statements, confirmations and settlement evidence received per instruction.

Who uses it

Permissions
Treasury Preparer
Records and submits deals.
Treasury Approver
Approves or rejects them.
Treasury Manager
Reads the blotter.
Settlement Officer
Supplies the evidence that completes them.
Admin
Corrects access.

Set up Treasury Operations your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started