Technology
Why fast attribution and traceable risk results require a different engine
Fast attribution, scenario analysis, and traceable risk analytics depend on sensitivities that come from the valuation itself, not estimated afterward. That technical foundation is Adjoint Algorithmic Differentiation (AAD).
Tracking every driver of every number means calculating thousands of sensitivities. For a portfolio of 100,000 instruments with 1,000 risk factors, that means 100 million individual calculations just to get a full sensitivity set.
Traditional bump-and-revalue methods require a separate run for each sensitivity: change one input, recalculate everything, measure the difference. At portfolio scale, that rules out anything faster than an overnight batch.
Adjoint Algorithmic Differentiation (AAD) computes sensitivities to all inputs in a single structured pass through the calculation. Instead of asking 'what happens if I change this input?' over and over, it answers all of those questions simultaneously.
The cost is roughly a small multiple of a single valuation — regardless of how many sensitivities you need. Whether you need 10 or 10,000, the computational cost is essentially the same.
Comparison
Traditional approach
One full recalculation per factor. For 1,000 factors, that is 1,000 runs.
AAD approach
A small multiple of one portfolio calculation, not one run per factor.
AAD is not a reporting add-on. The calculation engine itself has to track dependencies through every operation, so sensitivities are produced as part of the valuation rather than estimated afterward.
That architectural choice matters downstream. If valuations, sensitivities, scenarios, and attribution share one foundation, the numbers stay aligned and the explanations stay connected to the calculation that produced them.
Architectural consequence
When sensitivities come from the valuation itself, attribution and scenario analysis stop being separate reconciliation problems.
Because scenarios reuse the same analytical foundation, teams can test assumptions during the working session instead of turning every follow-up into an overnight request. Broader balance-sheet scenarios can still run as controlled portfolio-scale analyses when needed.
Because sensitivities come from the valuation itself, attribution stays connected to the calculation that produced the result. Movements can be decomposed into rates, volumes, model changes, and new deals without rebuilding the explanation afterward.
Because outputs, drivers, and assumptions share one engine, the path from result back to input remains visible. That gives ALCO, model governance, and audit teams something they can review and challenge directly, rather than a black-box report that has to be defended after the fact.
Because the same engine is available across interfaces, teams can work through Excel, Python, C#, or API workflows without switching models between exploration, reporting, and review.
For readers who want more technical detail, these are the best next steps.
12 min read
How the computational foundation of ALM is changing, and what an architecture built for interactive, auditable analysis looks like in practice.
Read more6 min read
How MASTIX Derivatives Studio uses Adjoint Algorithmic Differentiation to produce fast, sensitivity-based P&L explain across portfolio, time, and market-data effects.
Read moreWe can walk through interactive attribution on a portfolio that looks like yours and show how the same analytical foundation supports scenario analysis and review.
