Loading
Loading
The platform, stage by stage
A Calypso configuration is not eight separate systems. It is one trade moving through seven stages, each inheriting what the stage before it decided.
A product modelled wrong here is inherited by every number downstream
Trade booked against product, book, counterparty, and static data
The product model, legal entity, and book hierarchy already being right
Every valuation, risk, and accounting number the trade goes on to produce
What the work produces
The problems these engagements address, and the products they are applied across.
Earnings and audit
Where accounting treatment decides what the numbers say.
Designation, effectiveness testing, and the documentation that has to hold when a reviewer pulls the file. The framework decides which period a gain lands in, so a design that is merely defensible on paper still moves earnings if the system implements it differently.
Discuss this programWhere accounting treatment decides what the numbers say.
Where the platform changes hands or changes shape.
Where a booking decision becomes a reported one.
Earnings and audit
Designation, effectiveness testing, and the documentation that has to hold when a reviewer pulls the file. The framework decides which period a gain lands in, so a design that is merely defensible on paper still moves earnings if the system implements it differently.
Applied acrossSix product domains
Swaps, caps, floors, and swaptions, and the curves behind them.
Spot, forwards, swaps, and options across currency pairs.
Bonds and repo, with the accrual and settlement behaviour they carry.
Short-dated funding, deposits, and liquidity instruments.
Physical and financial exposure, and the delivery terms attached to it.
Options, futures, and total return structures on single names and indices.
How the work is scoped
Most Calypso engagements arrive as one of four shapes. What separates them is not the technology involved but where the risk concentrates, and which office ends up carrying it when a date moves.
Implementation risk concentrates where a decision taken for the front office quietly changes the ledger. The design has to hold all three offices at once.
Migration risk concentrates at the first close after cutover. A migration that reconciles on day one can still fail at month end.
Testing risk concentrates in the events nobody scripted. Happy-path coverage passes, and the exception breaks the close.
Readiness risk concentrates in the handover. A system that works is not the same as an organization ready to run it.
Start a conversation
Share the platform change, current constraint, and decision that needs senior attention. Ulysses will respond directly.