A SimCorp go-live issue may have warning signs that surface during UAT but are deferred or assessed as low priority. The problem is that in a multi-fund environment, what looks like a minor discrepancy in testing is often the surface expression of a structural data issue that affects every fund sharing the same instrument master or accounting rule. Building SimCorp test cases that expose these structural issues before cutover is what separates implementations that go live cleanly from those that require weeks of emergency remediation.
What Makes Multi-Fund Migration Testing Different
Multi-fund migrations require detailed testing because shared data, instruments, and settlement instructions can affect multiple funds. The SimCorp migration checklist should test these elements explicitly. A 2026 ResearchGate-published paper on a SimCorp Dimensions migration describes the use of phased migration, validation, go-live checklists, and User Acceptance Testing before cutover, alongside subsequent performance and analytics considerations.
Structuring Your UAT Programme for Multi-Fund Complexity
Test Environment Setup and Data Staging
UAT must run against a data set that reflects the full complexity of your production environment. Using overly simplified or synthetic data can limit the effectiveness of UAT because it may not reproduce the complexity and edge cases present in production data.
SimCorp migration risk analysis from Ascenteum notes that synthetic data rarely mirrors real production patterns, and that organisations should conduct early stress tests against full-volume datasets rather than representative samples. For a multi-fund environment, this means loading complete instrument master data, full position histories, all active counterparty records, and all fund accounting configurations before UAT begins.
Reference Data Validation Test Cases
The first tier of SimCorp data validation test cases covers the instrument master, counterparty records, fund setup, and static data that underpin every subsequent calculation. Test cases in this tier should verify that every instrument identifier maps correctly between the source system and SimCorp, that ISIN, CUSIP, and SEDOL identifiers are correctly assigned, that day count conventions and settlement conventions match source system records, and that coupon schedules for fixed income instruments produce the correct accrual amounts for a known historical period.
Position and Transaction Validation
Position validation test cases compare opening position quantities in SimCorp against the legacy system as at the migration date. For each fund, every security position should be reconciled by ISIN, quantity, and base currency equivalent value. Transaction history validation checks that historical trades loaded into SimCorp reproduce the correct position build-up over a defined look-back period. These tests often surface instrument static data errors that only become apparent when transaction history is applied to current positions.
NAV and Accounting Calculation Validation
NAV validation is the most consequential test category in a multi-fund migration because it confirms that the entire accounting configuration is producing correct outputs. For each fund, the SimCorp UAT checklist should include a full NAV calculation covering the migration date and selected historical calculation dates where reliable legacy outputs are available. Discrepancies must be investigated to the root cause rather than adjusted to make the numbers balance, because an adjustment that forces agreement without understanding the cause simply defers the problem to the first production run.
Compliance Rule Validation
Compliance test cases verify that the investment restriction rules configured in SimCorp for each fund correctly reflect the fund’s investment mandate as documented in the IMA. Test cases should cover at least three types of restriction: a concentration limit that would be breached by a specific hypothetical trade, a currency exposure limit that approaches the threshold under a defined scenario, and a derivative usage restriction that applies to specific instrument types.
For US registered investment companies and Canadian investment funds subject to applicable requirements such as NI 81-102, accurate configuration of relevant compliance rules is an important regulatory consideration.
Settlement and Collateral Test Cases
Settlement test cases verify that trade-generated settlement instructions carry the correct counterparty SSIs, settlement amounts, and settlement dates for a sample of historical transactions across each asset class. For funds with active derivatives portfolios, collateral calculation test cases should confirm that the margin call amounts generated by SimCorp match legacy system outputs for a set of historical calculation dates. A discrepancy in margin calculations should trigger investigation into valuation inputs, market data, collateral terms, configuration, and relevant netting-set mappings.
Strengthen your business transformation with Ascenteum’s expertise in asset management implementations. Our experienced consultants build robust testing frameworks that uncover structural data issues early, helping investment managers reduce migration risks and achieve more reliable implementation outcomes.
Who Should Own UAT in a SimCorp Migration Project
UAT Responsibility | Primary Owner | Role in UAT |
Operational validation | Operations Managers | Confirm that SimCorp workflows support day-to-day operational requirements. |
Accounting validation | Portfolio Accountants | Verify migrated data, calculations, accounting outputs, and NAV-related results. |
Risk validation | Risk Officers | Confirm that risk calculations, controls, and reporting produce appropriate results. |
Compliance validation | Compliance Professionals | Check that applicable compliance rules and controls operate as intended. |
Technical validation | IT / Technology Teams | Confirm successful data loads, integrations, interfaces, and technical processes. |
Business sign-off | Business SMEs | Confirm that migrated data produces correct outputs and that workflows align with the target operating model. |
Defect investigation | Business SMEs + IT | Business users validate the impact and expected outcome, while IT supports technical investigation and resolution. |
UAT availability | Business SMEs / Project Leadership | Allocate sufficient specialist time for testing, defect review, retesting, and final sign-off. |
Frequently Asked Questions
User Acceptance Testing (UAT) validates real operational scenarios using migrated data before go-live. It confirms that data, configuration, and calculations produce the expected results.
A complex multi-fund migration may require several hundred test cases across reference data, NAV, compliance, settlement, and collateral. Prioritise coverage of high-risk areas rather than exhaustive testing.
Portfolio accounting, risk, compliance, operations, data management, project management, and IT should have defined roles. Business teams should own validation and sign-off, while IT supports the testing environment.
Validate instrument data, opening positions, NAV calculations, compliance configurations, counterparty SSIs, and settlement data. Dimensional Community guidance also highlights reference data, historical NAVs, portfolio structures, security master data, and pending transactions.
Test shared reference data first, followed by fund-specific configuration and cross-fund calculations. Prioritise scenarios that test interactions between multiple modules.
Final Thoughts
Building UAT test cases that reflect the real complexity of a multi-fund SimCorp environment requires a structured approach that covers shared data elements, fund-specific configurations, and cross-module calculation logic. When UAT is conducted with the right data, the right people, and the right scope of test cases, it catches the structural issues that would otherwise surface in production under the worst possible conditions. For investment managers in the US, Canada, and the UK preparing for a SimCorp migration, a rigorous UAT programme is one of the most effective risk-mitigation measures available before cutover.
Build confidence in your SimCorp implementation with Ascenteum. Our team develops comprehensive test frameworks designed to identify complex data issues that conventional testing can overlook, supporting a smoother transition and more dependable platform performance.
