Top 10 Best Asset Liability Management Software of 2026

GITNUXSOFTWARE ADVICE

Finance Financial Services

Top 10 Best Asset Liability Management Software of 2026

Top 10 asset liability management software tools ranked side by side for banks, with Abrigo ALM, OneSumX for Risk, and Oracle Financial Services ALM.

33 min readUpdated AI-verified · Expert reviewed
How we ranked these tools
01Feature Verification

Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.

02Multimedia Review Aggregation

Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.

03Synthetic User Modeling

AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.

04Human Editorial Review

Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.

Read our full methodology →

Score: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy

Asset liability management software supports interest-rate and liquidity risk modeling, balance-sheet simulation, and regulatory reporting using defined data models, scenario engines, and auditable outputs. This ranked list helps analysts and technical evaluators compare platforms by model depth, integration and automation options, and governance features like RBAC and audit logs.

Abrigo ALM suits risk teams that want repeatable IRRBB and liquidity stress runs with controlled assumptions, while OneSumX for Risk is the enterprise pick for traceable, scenario-driven workflows, and if you need analytics-grade governance for simulations, SAS Asset and Liability Management is the stronger fit.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Abrigo ALM

Run traceability ties model inputs and configuration versions to each scenario result set for review and audit.

Built for fits when risk teams need repeatable IRRBB and liquidity stress runs with controlled assumptions..

2

OneSumX for Risk

Editor pick

Assumption and model-input workflow controls are integrated with scenario execution so approvals travel with the run setup.

Built for fits when banks need ALM run traceability with controlled assumption workflows and repeatable scenario execution..

3

SAS Asset and Liability Management

Editor pick

Model and scenario execution built around SAS analytics workflows for controlled NII and EVE simulation runs.

Built for fits when ALM teams need analytics-grade scenario simulation with tight assumption governance..

Comparison Table

1
Abrigo ALMBest overall
vertical specialist
9.5/10
Overall
2
9.1/10
Overall
3
8.8/10
Overall
4
8.5/10
Overall
5
8.2/10
Overall
6
7.9/10
Overall
7
enterprise
7.5/10
Overall
8
vertical specialist
7.2/10
Overall
9
enterprise
6.9/10
Overall
10
enterprise
6.6/10
Overall
#1

Abrigo ALM

vertical specialist

Provides community and regional banks with interest-rate risk, liquidity, and balance-sheet analysis.

9.5/10
Overall
Features9.6/10
Ease of Use9.4/10
Value9.5/10
Standout feature

Run traceability ties model inputs and configuration versions to each scenario result set for review and audit.

Abrigo ALM is built around configurable ALM workflows that map inputs into scenario runs, including repricing schedules, rate shock scenarios, and behavioral assumptions for deposits and prepayments. Outputs can be produced in scenario sets for earnings-at-risk and economic value style measures, then packaged for management reporting and review cycles.

A key tradeoff is that advanced modeling accuracy depends on disciplined input mapping from banking system feeds, because runtime results reflect the quality of cash flow and behavior datasets. Abrigo ALM fits best when a risk team needs repeatable scenario runs with controlled assumptions and a consistent audit trail for committee reporting.

Pros
  • +Scenario run configurations enforce consistent NII and EVE input-to-output mapping
  • +Behavioral modeling inputs improve realism for deposits and prepayment assumptions
  • +Role-based access and run traceability support committee-ready governance
  • +Export-ready reporting outputs fit iterative stress testing workflows
Cons
  • Core feed mapping effort can dominate time for first deployment
  • Some advanced assumption variants require careful configuration governance
Use scenarios
  • IRRBB risk analysts

    Monthly scenario runs and committee decks

    Consistent, reviewable scenario outputs

  • ALM governance teams

    Approval workflow for assumptions and runs

    Reduced audit friction

Show 2 more scenarios
  • Treasury and finance

    Balance sheet risk reporting from simulations

    Timelier risk reporting

    Scenario outputs are packaged into reporting cycles for monitoring and stress decisioning.

  • Model validation staff

    Traceability for model inputs and assumptions

    Faster validation evidence assembly

    Scenario results remain linked to configuration versions and the input datasets used.

Best for: Fits when risk teams need repeatable IRRBB and liquidity stress runs with controlled assumptions.

#2

OneSumX for Risk

enterprise

Supports asset liability management, liquidity risk, interest-rate risk, and regulatory reporting.

9.1/10
Overall
Features9.2/10
Ease of Use9.2/10
Value9.0/10
Standout feature

Assumption and model-input workflow controls are integrated with scenario execution so approvals travel with the run setup.

OneSumX for Risk supports ALM processes that feed both earnings and economic perspectives, including scenario execution and multi-dimensional analysis runs. Assumption handling is a first-class workflow element, with versioning and review steps that help keep behavioral inputs aligned to approvals. The configuration approach centers on mapping and controlling what data streams drive runs, which fits banks that need repeatable stress testing cycles.

A tradeoff is that the strongest outcomes depend on clean upstream mapping for behavioral and market inputs, since incorrect input granularity makes gap and scenario outputs harder to reconcile. The best fit is a bank risk team that already has defined IRRBB and liquidity governance steps and needs ALM run traceability across model changes and scenario libraries.

Pros
  • +Assumption versioning supports controlled IRRBB and ALM scenario iterations
  • +Scenario libraries speed repeated shock and multi-curve sensitivity runs
  • +Workflow orchestration links approvals to model input changes
  • +Connector-based ingestion reduces manual data wrangling for runs
Cons
  • Behavioral input mapping granularity can limit reconciliation when upstream is coarse
  • Deep configuration requires governance discipline to keep mappings consistent
  • Advanced scenario design needs structured input management to avoid run sprawl
  • User workflows may feel heavier than report-only ALM tools
Use scenarios
  • IRRBB model risk teams

    Run controlled scenario iterations

    Fewer audit-cycle reworks

  • ALM risk managers

    Standardize shock and sensitivity reporting

    Consistent exposure views

Show 2 more scenarios
  • Balance sheet analytics teams

    Integrate core and market inputs

    Less manual preparation

    Ingest mapped account and market data into ALM runs with repeatable orchestration steps.

  • Finance and risk controllers

    Coordinate approvals and releases

    Tighter change management

    Track governance steps for behavioral assumptions and ensure outputs correspond to approved inputs.

Best for: Fits when banks need ALM run traceability with controlled assumption workflows and repeatable scenario execution.

#3

SAS Asset and Liability Management

enterprise

Analyzes interest-rate risk, liquidity, capital, and balance-sheet scenarios.

8.8/10
Overall
Features9.2/10
Ease of Use8.5/10
Value8.6/10
Standout feature

Model and scenario execution built around SAS analytics workflows for controlled NII and EVE simulation runs.

SAS Asset and Liability Management covers the core ALM loop from balance-sheet data preparation to repricing gap views, scenario generation, and output reporting for earnings and economic measures. It supports behavioral modeling inputs for deposit dynamics and optionality handling through model parameters that can be versioned alongside the scenario run. Automation comes through repeatable runs for yield curve scenarios, shocks, and internal stress sets, which reduces manual rework between cycles.

A practical tradeoff is that deep configuration is required to operationalize behavioral and optionality assumptions, which can slow initial rollout compared with tools that ship more prebuilt templates. SAS Asset and Liability Management fits situations where asset managers or ALM teams need strong control over model parameters, then re-run the same scenario libraries on a schedule with consistent audit trails.

Pros
  • +Scenario-run automation supports repeatable earnings and economic metrics
  • +Behavioral parameter control helps keep deposit and prepayment assumptions consistent
  • +Analytics-grade modeling supports detailed cash flow and assumption calibration
  • +Versioned assumptions improve traceability from inputs to scenario outputs
Cons
  • Configuration depth can extend setup time for behavioral and optionality logic
  • Core ALM workflows depend on well-structured upstream data feeds
  • User experience can feel analytics-centric for non-modeling teams
  • Integration projects may require SAS and surrounding stack alignment
Use scenarios
  • ALM model risk teams

    Track assumption versions across scenario runs

    Fewer disputes over model inputs

  • Treasury and risk managers

    Run IRRBB shock scenarios on schedules

    Faster cycle turnaround

Show 2 more scenarios
  • Quantification analysts

    Calibrate behavioral deposit assumptions

    More realistic cash flows

    Behavioral parameters support deposit dynamics so cash flow projections reflect modeled decay.

  • Finance and reporting operations

    Reconcile ALM outputs to reporting views

    Consistent management reporting

    Execution outputs feed earnings and economic reporting views for governance-ready review.

Best for: Fits when ALM teams need analytics-grade scenario simulation with tight assumption governance.

#4

Moody's Analytics Asset Liability Management

enterprise

Supports balance-sheet simulation, interest-rate risk, liquidity analysis, and stress testing.

8.5/10
Overall
Features8.6/10
Ease of Use8.6/10
Value8.3/10
Standout feature

Run traceability across assumption versions tied to scenario results used for audit-ready ALM reporting workflows.

Moody's Analytics Asset Liability Management targets bank balance-sheet risk work with an analytics-first workflow for interest rate and liquidity scenarios. It supports NII simulation and related ALM outputs such as EVE and repricing-gap driven risk views built from banking book cash flow assumptions.

The solution is distinct in how it operationalizes economic risk into repeatable scenario runs and reporting artifacts used by risk and finance teams. It also fits governance-heavy ALM cycles that require audit trails around assumption changes and model runs.

Pros
  • +Strong NII and economic value reporting for scenario-based ALM cycles
  • +Operational assumption management that supports repeatable model runs
  • +Workflow supports end to end batch processing of cash flow and risk outputs
  • +Designed for risk governance with traceable run and assumption history
Cons
  • Higher setup effort than lighter ALM tools for data prep and mappings
  • Scenario configuration can feel technical for teams without quantitative support
  • Core ALM outputs require disciplined model validation to stay decision-ready
  • Depth in banking book modeling can widen integration scope to upstream sources

Best for: Fits when ALM teams need scenario-driven NII and economic risk outputs with strong run governance and traceability.

#5

FIS Asset Liability Management

enterprise

Supports balance-sheet risk measurement, liquidity management, and interest-rate scenario analysis.

8.2/10
Overall
Features8.3/10
Ease of Use8.2/10
Value8.0/10
Standout feature

Behavioral deposit and prepayment optionality handling integrated into scenario simulations for balance sheet risk analytics.

FIS Asset Liability Management runs balance sheet risk analytics that feed ALM decisions for IRRBB and liquidity planning. It supports scenario-based NII and value metrics across repricing, maturity, and cash flow assumptions, including behavioral components used for deposits and prepayment optionality.

Configuration centers on ingesting model inputs, mapping product and account structures to simulation drivers, and producing audit-ready outputs for reporting cycles. Integration depth depends on how FIS connects to core banking, data feeds, and downstream reporting controls in the buyer environment.

Pros
  • +Scenario-driven NII and value calculations that support frequent recalculation cycles
  • +Behavioral assumptions for deposits and optionality risk improve realism versus static schedules
  • +Model mapping supports product and account structure alignment for simulation drivers
  • +Outputs are designed for audit trail needs during ALM reporting workflows
Cons
  • Complex configuration and model parameterization increase time-to-first-stable results
  • Documentation and operational knowledge depend on implementation scope and governance rigor
  • Throughput can be constrained by large portfolio sizes and granular cash flow assumptions
  • Automation coverage relies on provided integration connectors and workflow setup

Best for: Fits when banks need tightly governed ALM scenario runs tied to account and product mappings.

#6

Fiserv Asset Liability Management

enterprise

Provides financial institutions with interest-rate risk, liquidity, and balance-sheet analysis.

7.9/10
Overall
Features7.7/10
Ease of Use8.0/10
Value8.0/10
Standout feature

Run-level audit trail and assumption control for ALM scenario executions, tied to approval and change history for governance.

Fiserv Asset Liability Management targets banks that need balance sheet analytics for IRRBB and liquidity decisions inside a controlled enterprise workflow. It supports scenario-based NII and economic value measurement with cash flow inputs and behavioral assumptions, which helps teams run repeatable shock and stress analyses.

Integration and automation tend to matter most for feeds from core banking and general ledger systems, plus operational controls for model governance and audit trails. Fiserv Asset Liability Management is most practical when data provisioning, approvals, and recalculation runs are treated as governed processes rather than ad hoc spreadsheet work.

Pros
  • +Scenario runs support repeatable NII and value metrics across defined interest rate shocks
  • +Behavioral assumptions help represent deposit and prepayment dynamics beyond contractual cash flows
  • +Governed workflows improve consistency of assumptions, runs, and approvals for ALM committees
  • +Designed for enterprise integration with upstream balance, product, and ledger data pipelines
Cons
  • Model setup and assumption tuning require governance discipline to avoid inconsistent results
  • User workflows can feel heavy when teams need quick one-off what-if sensitivity checks
  • Advanced scenario orchestration and validations typically need specialized ALM configuration effort
  • Full workflow visibility depends on configuring audit and reporting outputs for each run type

Best for: Fits when mid-market or enterprise banks need governed ALM scenario processing with repeatable outputs and integration-driven data feeds.

#7

QRM

enterprise

Provides integrated modeling for market risk, liquidity risk, capital, and asset liability management.

7.5/10
Overall
Features7.3/10
Ease of Use7.7/10
Value7.7/10
Standout feature

Assumption versioning with traceable change history ties parameter updates to each simulation output cycle.

QRM is an ALM-focused application that centers on balance sheet and risk scenario modeling with workflows tailored to IRRBB and liquidity management reporting. The solution connects forecast data into scenario engines for NII and EVE-style outputs, then supports managed assumptions for behavioral and optionality-driven cash flows.

QRM emphasizes audit trail controls around model inputs and results so changes remain traceable across cycles. It also provides integration-oriented configuration for general ledger and core banking feeds to keep simulation runs aligned with upstream accounting and market data.

Pros
  • +Scenario runs are built around ALM-specific cash flow and repricing logic
  • +Managed assumption library supports behavioral and optionality parameter updates
  • +Change traceability supports audit log needs for model inputs and outputs
  • +Integration configuration is geared toward GL and core banking aligned datasets
Cons
  • Scenario configuration can require specialist setup to avoid modeling inconsistencies
  • Behavioral modeling depth may lag suites that offer broader deposit and prepay toolkits
  • Complex scenario governance can feel heavy without clear role separation
  • API extensibility is limited compared with tools that expose deeper automation hooks

Best for: Fits when mid-sized banks need repeatable ALM scenario workflows with controlled model inputs.

#8

Baker Hill ALM

vertical specialist

Supports interest-rate risk measurement, liquidity analysis, and asset liability reporting.

7.2/10
Overall
Features7.2/10
Ease of Use7.3/10
Value7.2/10
Standout feature

Behavioral modeling workflows that tie deposit, prepayment, and early withdrawal assumptions to scenario runs with traceable inputs.

Baker Hill ALM is an asset liability management system built for balance sheet risk modeling across interest rate, liquidity, and earnings perspectives. It supports scenario-based NII simulation and stress testing workflows that feed IRRBB and liquidity risk use cases.

The product is centered on governance for assumptions such as deposit behavior, prepayment, and early withdrawal, with model and run traceability tied to each scenario. Baker Hill ALM also emphasizes integration with banking data sources for repeatable repricing gap and cash flow gap analysis.

Pros
  • +Scenario-driven NII simulation designed for repeatable stress testing
  • +Behavioral assumption management for deposits, prepayments, and early withdrawals
  • +Supports repricing gap and cash flow gap analysis from modeled cash flows
  • +Audit-friendly run traceability for assumptions and scenario inputs
Cons
  • Complex assumption configuration can slow first-cycle model validation
  • Advanced outputs depend on complete upstream data integration coverage
  • Workspace navigation can feel heavy for small ALM teams
  • Automation depth is stronger for structured runs than ad hoc analysis

Best for: Fits when mid-size to large banks need scenario governance for behavioral assumptions across NII and liquidity analytics.

#9

Murex MX.3

enterprise

Covers treasury, market risk, liquidity, capital, and balance-sheet management.

6.9/10
Overall
Features6.6/10
Ease of Use7.0/10
Value7.1/10
Standout feature

End-to-end scenario simulation that reuses Murex valuation and market data so ALM measures align with trading risk outputs.

Murex MX.3 manages market risk and ALM analytics through an end-to-end workflow that spans cash flow planning, scenario simulation, and balance-sheet and regulatory reporting.

The system’s strength is tight integration across pricing, valuation, and risk engines so ALM measures reflect consistent market assumptions and deal behavior.

Liquidity and interest rate risk use case coverage includes scenario-based stress testing and comprehensive balance sheet risk views.

Governance controls focus on controlled model and parameterization workflows that support audit trails for risk and reporting changes.

Pros
  • +Shared valuation and risk engines keep ALM outputs consistent with market assumptions
  • +Scenario simulation workflows support interest rate shocks and multi-scenario comparisons
  • +Strong integration path from trade and pricing data into risk and reporting pipelines
  • +Governance around model and parameter changes supports traceable ALM results
Cons
  • Configuration depth is high for organizations without in-house Murex specialists
  • Operational tooling for day-to-day ALM analysts can feel less streamlined than specialist tools

Best for: Fits when a bank needs IRRBB and liquidity management driven by consistent valuation and scenario engines.

#10

Numerix Oneview

enterprise

Provides risk analytics for market risk, liquidity, valuation, and balance-sheet exposure.

6.6/10
Overall
Features6.8/10
Ease of Use6.4/10
Value6.5/10
Standout feature

Scenario and assumption lifecycle management that keeps NII and EVE inputs consistent across automated runs and dependent reports.

Numerix Oneview targets asset liability management workflows where ALM calculations, scenario runs, and reporting must connect to enterprise market, banking, and risk data. It supports end-to-end IRRBB and liquidity risk processes including NII simulation, EVE calculations, and cash flow gap style views for balance sheet management.

Administration features focus on controlling model inputs and scenario libraries so governance teams can manage assumptions across runs and downstream reporting. Automation and extensibility center on integrating with external systems via documented interfaces and repeatable job runs that support scheduled stress testing and audit trail needs.

Pros
  • +Supports ALM simulation workflows for NII and EVE under scenario frameworks
  • +Scenario library management helps keep assumption sets consistent across runs
  • +Automation-friendly execution supports scheduled stress testing cycles
  • +Designed to integrate ALM outputs into enterprise risk and reporting processes
Cons
  • Requires model input and data mapping discipline to avoid run-to-run drift
  • Behavioral modeling coverage and configuration depth vary by use case scope
  • Complex governance controls can increase onboarding time for new teams
  • Advanced workflow customization depends on integration effort with source systems

Best for: Fits when ALM teams need controlled scenario libraries, repeatable execution, and enterprise integration for regulatory-ready runs.

Conclusion

After evaluating 10 finance financial services, Abrigo ALM stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
Abrigo ALM

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

How to Choose the Right asset liability management software

This buyer’s guide covers Abrigo ALM, OneSumX for Risk, SAS Asset and Liability Management, Moody's Analytics Asset Liability Management, FIS Asset Liability Management, Fiserv Asset Liability Management, QRM, Baker Hill ALM, Murex MX.3, and Numerix Oneview for banks managing interest rate risk in the banking book and liquidity risk with repeatable balance sheet simulations. Each tool review focuses on scenario execution governance, assumption controls, and the mechanics that connect model inputs to NII and economic value outputs for audit-ready ALM cycles.

The evaluation emphasis centers on integration depth, API and automation surface where documented, and admin controls that keep assumption workflows consistent across runs. The sections also compare how each platform handles behavioral modeling for deposits and optionality and how traceability ties scenario result sets back to configuration versions for review and audit.

Asset liability management software for governed NII and economic value scenario execution

Asset liability management software supports structured simulation of cash flow and repricing behavior across scenario libraries so NII and economic value outputs stay consistent run to run. These platforms operationalize ALM workflows for scenario execution, assumption governance, and traceable reporting to support interest rate shock and multi-curve sensitivity cycles.

Abrigo ALM ties model inputs and configuration versions to each scenario result set for review and audit so ALM runs keep a controlled assumption-to-output mapping. OneSumX for Risk integrates assumption and model-input workflow controls with scenario execution so approvals travel with the run setup and scenario libraries speed repeated shock and sensitivity runs.

Governed scenario execution, assumption control, and ALM output traceability

Asset liability management software succeeds when scenario execution carries its configuration and approvals through to NII and economic value outputs. Buyers should focus on the mechanisms that prevent run-to-run drift in cash flow mappings, behavioral parameters, and scenario libraries.

Across Abrigo ALM, OneSumX for Risk, and Fiserv Asset Liability Management, traceability is not a report artifact. It is a run-level linkage between assumption versions and the scenario result set used for governance and audit-ready ALM cycles.

  • Run traceability from configuration to results

    Abrigo ALM ties model inputs and configuration versions to each scenario result set so review and audit workflows can trace assumption-to-output mapping. Fiserv Asset Liability Management keeps a run-level audit trail and assumption control tied to approval and change history for governed scenario executions.

  • Assumption and workflow controls embedded in scenario execution

    OneSumX for Risk integrates assumption and model-input workflow controls with scenario execution so approvals travel with the run setup. Moody's Analytics Asset Liability Management centers operational assumption management around repeatable model runs that support scenario-driven NII and economic value reporting workflows.

  • Behavioral modeling workflows tied to scenario inputs

    Baker Hill ALM ties deposit, prepayment, and early withdrawal assumptions to scenario runs with traceable inputs so behavioral governance stays aligned to simulation outputs. FIS Asset Liability Management integrates behavioral deposit and prepayment optionality handling into scenario simulations so results reflect optionality risk versus static schedules.

  • Scenario libraries for repeatable shock and sensitivity cycles

    OneSumX for Risk uses scenario libraries to speed repeated shock and multi-curve sensitivity runs with controlled assumption workflows. Numerix Oneview manages scenario libraries to keep assumption sets consistent across automated runs and dependent reports for NII and EVE frameworks.

  • Analytics-grade scenario execution built on analytics workflows

    SAS Asset and Liability Management builds model and scenario execution around SAS analytics workflows for controlled NII and EVE simulation runs. Moody's Analytics Asset Liability Management also emphasizes scenario-driven NII and economic value outputs with strong run governance and traceability for ALM cycles.

How to choose asset liability management software for governed ALM runs

The right ALM platform is chosen by how scenario configuration, approvals, and result generation are coupled. The decision hinges on whether the platform enforces consistency through run configuration controls or expects analysts to manage consistency through governance discipline.

Another decision hinge is how the system aligns ALM outputs with upstream systems and valuation engines. Murex MX.3 reuses Murex valuation and market data so ALM measures align with trading risk outputs, while Abrigo ALM emphasizes traceability tying inputs and configuration versions to scenario results used for review and audit.

  • Pick the platform that keeps assumption approvals attached to the run setup

    Choose OneSumX for Risk if approvals must travel with the run setup because assumption and model-input workflow controls are integrated with scenario execution. Choose Fiserv Asset Liability Management if run-level audit trails and assumption control tied to approval and change history are the governance priority for repeatable scenario processing.

  • Decide whether traceability is your primary control mechanism

    Select Abrigo ALM when traceability must link model inputs and configuration versions to each scenario result set for review and audit. Choose Moody's Analytics Asset Liability Management when operational assumption management must support repeatable model runs feeding scenario-driven NII and economic value reporting workflows.

  • Choose the behavioral modeling depth based on deposit and optionality requirements

    Select FIS Asset Liability Management if deposit and prepayment optionality handling must be integrated into scenario simulations for balance sheet risk analytics. Select Baker Hill ALM when deposit, prepayment, and early withdrawal behavioral assumptions must be tied to scenario runs with traceable inputs.

  • Match scenario library usage to the bank’s execution cadence

    Choose OneSumX for Risk when repeated shock and multi-curve sensitivity cycles must be accelerated through scenario libraries. Choose Numerix Oneview when automated runs and dependent reports must stay aligned to scenario library-managed assumption sets for NII and EVE under scenario frameworks.

  • Align ALM engines with existing valuation or analytics workflows

    Choose Murex MX.3 when ALM outcomes must align with trading risk because it reuses Murex valuation and market data inside scenario simulation workflows. Choose SAS Asset and Liability Management when analytics-grade scenario simulation should follow SAS analytics workflows with tight assumption governance.

Who needs asset liability management software with governed scenario execution

Asset liability management software is most suitable for banks that run repeatable IRRBB and liquidity stress cycles and need governed scenario execution rather than one-off calculations. These teams need traceability from assumption versions to scenario result sets and they need behavioral modeling to match deposit and prepayment dynamics.

Abrigo ALM is a strong fit when risk teams require controlled assumption-to-output mapping across NII and economic value scenario runs. QRM and OneSumX for Risk fit teams that prioritize controlled model inputs and assumption workflows tied to scenario execution.

  • IRRBB and liquidity risk teams running recurring scenario cycles

    Abrigo ALM provides scenario run traceability that ties configuration versions to scenario result sets for review and audit. Moody's Analytics Asset Liability Management supports scenario-driven NII and economic value reporting workflows with operational assumption management that supports repeatable model runs.

  • Model governance teams that require approval-linked assumption workflows

    OneSumX for Risk integrates assumption and model-input workflow controls with scenario execution so approvals travel with the run setup. Fiserv Asset Liability Management ties scenario audit trails and assumption control to approval and change history for governance.

  • Banks with behavioral deposit, prepayment, and early withdrawal modeling needs

    Baker Hill ALM provides behavioral modeling workflows that tie deposit, prepayment, and early withdrawal assumptions to scenario runs with traceable inputs. FIS Asset Liability Management integrates behavioral deposit and prepayment optionality handling into scenario simulations for realistic balance sheet risk analytics.

  • Banks with existing Murex trading valuation and market data alignment requirements

    Murex MX.3 reuses Murex valuation and market data so ALM measures align with trading risk outputs. This design supports scenario simulation workflows for interest rate shocks and multi-scenario comparisons grounded in shared valuation assumptions.

  • ALM teams automating regulated-ready reporting from scenario libraries

    Numerix Oneview keeps scenario and assumption lifecycle management aligned across automated runs and dependent reports using scenario libraries. It supports ALM simulation workflows for NII and EVE under scenario frameworks while keeping assumption sets consistent across runs.

Common mistakes in ALM platform selection

ALM selection fails when the platform’s run governance and data mapping workflow does not match the bank’s execution reality. Several tools in this category trade setup effort for stricter governance, so buyers should treat first-cycle configuration complexity as a deciding variable.

A second failure mode occurs when behavioral modeling depth or mapping granularity does not match upstream data quality. Buyers should align the platform’s behavioral and optionality capabilities with the granularity of upstream account and product feeds before committing to an implementation plan.

  • Choosing an ALM tool without validating core feed mapping effort for first deployment

    Abrigo ALM can require core feed mapping effort that dominates time for first deployment, so mapping scope needs a fit check against available upstream formats. Murex MX.3 configuration depth can also be high without in-house Murex specialists, so internal capability matters.

  • Assuming behavioral modeling will reconcile cleanly when upstream data is coarse

    OneSumX for Risk can face behavioral input mapping granularity limits when upstream is coarse, which can reduce reconciliation. Numerix Oneview also requires model input and data mapping discipline to prevent run-to-run drift.

  • Treating scenario governance as purely administrative instead of configuration-coupled

    SAS Asset and Liability Management provides strong scenario-run automation, but configuration depth can extend setup time for behavioral and optionality logic. FIS Asset Liability Management can increase time-to-first-stable results due to complex configuration and model parameterization.

  • Underestimating workflow friction for teams that need quick what-if sensitivity checks

    Fiserv Asset Liability Management user workflows can feel heavy when teams need quick one-off sensitivity checks, so workflow fit should be validated against typical analyst behavior. Murex MX.3 operational tooling can feel less streamlined for day-to-day ALM analysts compared with specialist tools, so role-based workflow fit matters.

How We Selected and Ranked These Tools

We evaluated Abrigo ALM, OneSumX for Risk, SAS Asset and Liability Management, Moody's Analytics Asset Liability Management, FIS Asset Liability Management, Fiserv Asset Liability Management, QRM, Baker Hill ALM, Murex MX.3, And Numerix Oneview based on features, ease, and value. We weighted features at 40%, ease at 30%, and value at 30% using the scored totals shown for each tool.

Abrigo ALM earned the top rank by combining scenario run configurations that enforce consistent NII and EVE input-to-output mapping with traceability that ties model inputs and configuration versions to each scenario result set. We selected the category emphasis around governed scenario execution because Abrigo ALM and OneSumX for Risk both connect assumption control to scenario execution for repeatable shock and sensitivity cycles.

Frequently Asked Questions About asset liability management software

How do Abrigo ALM and OneSumX for Risk differ in managing assumptions through an ALM run?
Abrigo ALM links scenario results to model inputs and configuration versions so the trace ties back to what was actually used. OneSumX for Risk integrates approval and model-input workflow controls with scenario execution, so the approval path travels with the run setup.
Which tools provide deeper ALM integration via APIs or connector-based ingestion for core and downstream systems?
OneSumX for Risk uses connector-based ingestion and workflow orchestration to pull inputs into ALM calculations. Abrigo ALM centers on importing feeds from core and subledger sources and exporting outputs into downstream reporting and governance processes. Numerix Oneview targets ALM calculation and reporting connections across enterprise market, banking, and risk data through documented interfaces and repeatable job runs.
When should a bank consider SAS Asset and Liability Management instead of a non-SAS analytics stack for IRRBB and EVE workflows?
SAS Asset and Liability Management fits when existing ALM teams already rely on SAS analytics engines and need ALM scenario simulation aligned with that stack. SAS-driven scenario simulation supports controlled NII and EVE workflows, while also running standard stress testing and governance artifacts tied to assumptions.
What tradeoff appears when Moody's Analytics ALM or QRM is selected for governance-heavy ALM cycles?
Moody's Analytics ALM operationalizes economic risk into repeatable scenario runs and reporting artifacts with audit trails around assumption changes. QRM focuses on assumption versioning and traceable change history that ties parameter updates to each simulation output cycle, which can increase governance workflow steps compared with simpler run engines.
How do FIS Asset Liability Management and Baker Hill ALM handle behavioral optionality for deposits and prepayments?
FIS Asset Liability Management includes behavioral components used for deposits and prepayment optionality as part of scenario simulations. Baker Hill ALM provides governance-centered behavioral modeling workflows that tie deposit, prepayment, and early withdrawal assumptions to scenario runs with traceable inputs.
Where does Murex MX.3 fall short if an organization needs ALM measures to reuse a single valuation workflow already used for trading risk?
Murex MX.3 is built to reuse valuation and market data so ALM measures align with trading-risk outputs. If the ALM program needs an approach that does not share market-data valuation assumptions with other risk engines, Murex MX.3's end-to-end reuse model may not match the required separation.
How do OneSumX for Risk and Fiserv Asset Liability Management differ in admin controls and audit trail coverage across ALM runs?
OneSumX for Risk emphasizes assumption and model-input workflow controls tied to scenario execution approvals. Fiserv Asset Liability Management focuses on run-level audit trail and assumption control tied to approval and change history, which prioritizes traceability at the execution record.
What common onboarding step for data migration and mapping causes delays across ALM tools like QRM and FIS Asset Liability Management?
Mapping product and account structures into simulation drivers is a recurring migration work item in FIS Asset Liability Management, because scenario outputs depend on those mappings. QRM similarly depends on integrating forecast data into scenario engines, so missing or mismapped upstream fields can block scenario execution until data structures align.
Which tool is more appropriate when ALM teams must align simulation inputs with general ledger and core banking feeds through repeatable configuration?
QRM provides integration-oriented configuration for general ledger and core banking feeds to keep simulation runs aligned with upstream accounting and market data. Fiserv Asset Liability Management also depends on governed data provisioning from core and general ledger systems, where approvals and recalculation runs are treated as governed processes rather than ad hoc work.
What breaks if an ALM implementation ignores run traceability and version control, as seen in tools like Abrigo ALM and Moody's Analytics ALM?
Abrigo ALM and Moody's Analytics ALM both tie results to assumption versions so review teams can reproduce what generated each scenario output. If traceability and version control are not enforced, scenario outputs cannot be reliably explained, and audit trail review becomes a manual reconciliation task that slows risk committee reporting.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

Logos provided by Logo.dev

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.