A large deal is estimated against its limit first
The Basel Committee asks banks to “estimate in a timely fashion whether a new transaction could potentially lead to a breach of the applicable limit”. Your pre-deal check does that on the live book.
Calseda reruns your exposure calculation for a counterparty when anything behind it changes: a new trade, a rating, an interest rate, an exchange rate. A deal is checked against the result before it is booked.
The overnight run finishes. Counterparty C is at 51% of its limit.
A rating agency cuts Counterparty C from A to BBB+. Nothing changes on screen.
The desk books a large swap, checked against the 07:00 figure. It passes.
The morning report shows Counterparty C over its limit, too late to stop.
The rating change arrives. Counterparty C's limit falls with its rating, and utilisation jumps from 51% to 82%.
Before booking, the desk runs the swap through your exposure calculation on the live book. It would take Counterparty C to 104%. Only the desk sees the answer, and nothing is booked.
The desk resizes the deal, or asks credit for an exception, with the same figures in front of both.
If a limit is crossed, one alert goes to credit in Teams or your ticketing tool, opening on the trade or rating change behind it.
A heavy model, such as a PFE simulation, can run at a minimum interval you set.
The demo follows six counterparties' exposure as trades arrive. Open any row to see the trades and rates it used, each with its source and age. Exposure recalculates at most once a second, a pace you choose per calculation; each change then reaches the limit board in milliseconds.
Neither page needs a sign-in: The live limit board ↗ · Try a trade against a limit ↗
The rating cut, filmed in the product: Why did this figure change? (1 min 18 s)
The Basel Committee asks banks to “estimate in a timely fashion whether a new transaction could potentially lead to a breach of the applicable limit”. Your pre-deal check does that on the live book.
Open it and see its full lineage, the trades and rating behind it down to the raw data, and export it for credit committee or your regulator.
Your credit quants write the exposure calculation, or Calseda calls the exposure engine you already run. Either way it runs in your own environment, and your limits system stays as it is.
Nothing upstream changes.
Credit compares the two until it relies on the live exposure.
Become a design partner: your exposure figure live in about six weeks, for a fixed fee. At the end you keep the framework, licensed to run what you built on one server.
To pass on to credit colleagues: Credit risk, one page (PDF).