MASTIX

For treasury and ALM teams

ALM Studio

Balance-sheet analytics that trace every valuation, projection, and risk metric back to its drivers.

ALM Studio combines scenario analysis, attribution, and reporting in one analytical model across the full balance sheet, working alongside existing source systems.

What teams can do

  • Attribute changes in EVE and NII to rate moves, new business, portfolio runoff, and model effects.
  • Run interest-rate and balance-sheet scenarios interactively instead of waiting for overnight batches.
  • Produce risk metrics, audit trails, and reports from the same model used for scenarios and sensitivities — no separate reporting layer.

How it works

ALM Studio starts from contract-level cash flows and keeps the same analytical foundation through sensitivities, scenarios, and attribution.

  1. 1

    Model loans, deposits, securities, and derivatives in one cash flow framework on top of existing source systems.

  2. 2

    Compute valuations, risk metrics, and sensitivities from one engine instead of stitching separate tools together.

  3. 3

    Carry the link from contract-level inputs up to portfolio and balance-sheet results so every number stays explainable.

What changes operationally

Move from fragmented spreadsheets to one repeatable workflow across treasury, ALM, and reporting.

Answer ALCO and governance questions with traceable explanations instead of manual reconciliation.

Test alternatives in minutes instead of requesting overnight batch runs.

Work through Excel, Python, and connected reporting workflows instead of being locked into one vendor interface.

In practice

EVE moved overnight. What drove it?

Decompose the move into rate changes, new business, runoff, model updates, and assumption changes — automatically, not by reconciling reports.

The board wants to see the impact of a 200bp rise.

Run the scenario interactively, compare it against alternatives, and present results with full attribution in the same session.

Audit wants to trace an IRRBB figure back to its source.

Follow the reported number from the balance-sheet result through the calculation back to the contracts and assumptions that produced it.

Why it holds up under scrutiny

Built for institutions where risk numbers face questions from management, model governance, regulators, and auditors.

Scenario workflow

Test rate and balance-sheet alternatives during the working session

Interactive scenarios in seconds. Broader balance-sheet scenarios in minutes.

Instead of waiting for another overnight ALM batch.

Consistency

EVE, NII, sensitivities, and attribution from one analytical foundation

The same projected cash flows support the core balance-sheet metrics.

Instead of reconciling separate model chains for risk, reporting, and explanation.

Governance

Explain reported movements without manual reconciliation

Trace balance-sheet results back to contracts, assumptions, and model effects.

Instead of assembling the answer from multiple reports after the committee meeting.

  • Every result traceable from balance-sheet aggregates down to individual contracts and inputs.
  • Scenarios, sensitivities, and reported metrics all come from the same model — no reconciliation between analytical layers.
  • Designed for repeatable, auditable workflows — not one-off analysis that cannot be reproduced.

Benchmarks based on internal test environments and client implementations.

See ALM Studio on a realistic portfolio

Run a scenario, inspect the result, and explain exactly what changed — on a portfolio that looks like yours.