calseda

Credit risk

Check every deal against the exposure as it is now.

Counterparty exposure changes with every new trade and every market move. Calseda keeps each counterparty's exposure and limit use current all day, so a deal can be checked against that figure before it is done. If a limit is crossed, the right people are told at once.

What you can't see today

Most credit teams see exposure as it was at the last batch.

This morning's trades

Exposure is calculated overnight, so deals booked since 7am are missing from the figure the desk checks against.

Today's market

A sharp move in rates or currencies changes exposure at once. The report shows it tomorrow.

A rating change

A downgrade should shrink the room left under a limit straight away. Often it waits for the next run.

Who is close to the edge

Without a current figure, a breach turns up in a report after the fact, and someone then has to chase the desk.

What you'd see instead

At 10:13 a rating agency cuts Counterparty C.

Today

  1. 07:00

    The overnight run finishes. Counterparty C is at 82% of its limit.

  2. 10:13

    A rating agency cuts Counterparty C from A to BBB+. Nothing changes on screen.

  3. 10:14

    The desk books a large swap with Counterparty C, checked against the 07:00 figure. It passes.

  4. Next day

    The morning report shows Counterparty C over its limit. Credit asks the desk what happened.

With Calseda

  1. 10:13

    The rating change arrives. Counterparty C's limit use goes from 82% to 91% at once, and turns amber.

  2. 10:14

    Before booking, the desk checks the swap against the current figure. It would take Counterparty C to 104%.

  3. 10:14

    The desk can resize the deal, or ask credit for an exception, with the same current figures in front of both.

  4. Any time

    If a limit is crossed, credit is told at once, with the trade or rating change that caused it.

An example with simulated data.

Exposure, current all day

Each counterparty's exposure and limit use, recalculated when its trades or market data change, and only then.

A check before the deal

A proposed deal is tested privately against the current figure. Nobody else sees it, and nothing is booked.

Breaches told at once

An alert reaches credit in Teams or Slack once per crossing, with what caused it.

The same figures in Excel

Analysts keep their spreadsheets, with live figures in the cells instead of pasted copies.

See it in a demo

Six counterparties, each against a limit that follows its rating.

In a demo, a simulated bank's exposure to six counterparties moves as trades arrive. Cut a rating and the limit shrinks with it. Open any row to see the trades and rates behind the figure, each with its source and age.

A demo's limit board with one counterparty's row opened to its inputs A demo's limit board with one counterparty's row opened to its inputs
From a demo running on public data: a counterparty's exposure, opened to the inputs behind it. Everything about the bank is simulated, and exchange rates move around the ECB's real daily rates.
A demo's what-if page with the answer for a trade against a counterparty's limit A demo's what-if page with the answer for a trade against a counterparty's limit
From a demo running on public data: a trade tried against a counterparty's limit before it is made. The answer goes only to the page that asked. The same simulated bank.

What changes for your team

Fewer surprises, and conversations that start from facts.

No morning-after breaches

Breaches are seen when they happen, while something can still be done. The alert says what moved the figure, so the call with the desk starts from what happened.

Questions without a project

"What if this counterparty is downgraded two notches?" is a private question on the live data, from a browser or Excel.

What your regulator or auditor gets

An answer to "how was this figure produced?" that nobody has to rebuild.

  • For each exposure figure as it stands, the exact trades and market data it was calculated from, with where each came from and how fresh it was.
  • A flag on any figure that rests on data older than its source should allow.
  • For every breach: what caused it, and where the alert went.
  • Every limit change or override logged with who posted it, and when.

How it starts

With one figure, next to what you run today.

  1. Pick one figure

    For example, exposure for one desk, or for one group of counterparties.

  2. Connect the data you already have

    Trades and market data, read from the systems that already produce them. Nothing is replaced.

  3. Write the calculation

    Your developers, or ours, write the exposure calculation. Calseda does the rest.

  4. Run it side by side

    It runs alongside today's process, so your team can compare the two before relying on it.

See your own exposure live

Become a design partner: a pilot on generous terms, in exchange for a case study published only with your approval.