Legacy App Modernization in Amsterdam, Netherlands

Pension Administration / Financial Services / Legacy Modernization / Amsterdam

A Dutch pension administration organisation (managing EUR 320B in pension assets across 4 pension funds, administering pensions for 2.4 million active members, 1.2 million deferred members, and 800,000 pensioners, 1,800 employees) needed to modernize their core pension administration system to support the Wet toekomst pensioenen (WTP) transition — the most significant change to Dutch pensions in 80 years. The WTP required every Dutch pension fund to transition from a defined benefit (DB) system to a defined contribution (DC) system by January 1, 2028. The administration organisation's legacy system could not support this transition. Core challenges: (1) Legacy pension calculation engine — the core administration system (built 1994 on IBM AS/400, written in RPG/ILE and CL, with DB2/400 database) managed the full pension lifecycle: contribution collection, benefit accrual, benefit calculation, payment processing, and regulatory reporting. The system contained 2.6 million lines of RPG code implementing: 48 pension scheme variations (each pension fund having multiple schemes with different rules accumulated over decades — early retirement provisions from the 1990s, VPL transitional arrangements, crisis levy adjustments from 2013, and various employer-specific supplements), benefit calculations that differed by: entry date (members joining before/after specific dates having different accrual rates), retirement date (early retirement penalties/bonuses varying by scheme and era), marital status (partner pensions calculated differently for married, registered partner, and cohabiting couples — each with different Dutch legal provisions), and disability (WIA, WAO, WGA, IVA — each Dutch disability regime creating different pension calculation variants). The calculation engine processed monthly: pension payments (800,000 payments totalling EUR 1.2B monthly), contribution calculations (2.4 million active members with varying contribution rates), and benefit statements (annual Uniform Pension Overview — UPO — for all participants). (2) WTP transition requirements — the WTP fundamentally changed Dutch pensions from DB to DC, requiring: invaren (transfer) — converting accumulated DB pension rights into DC capital accounts. This required calculating, for every participant, the actuarial value of their accumulated DB rights and converting this to a personal capital account. For 4.4 million participants with varying entry dates, schemes, and personal circumstances, this was a calculation of unprecedented complexity. The legacy RPG system could not perform invaren calculations — it was designed for DB administration, not DC conversion. New DC administration — after invaren, the system needed to manage personal capital accounts: tracking individual investments, processing variable pension payments (DC pensions fluctuating with investment returns), and providing participants with real-time capital account visibility. The legacy system had no concept of individual capital accounts — it tracked accrued pension rights, not investment portfolios. Transition period management — during the transition (2025-2028), the system needed to simultaneously: administer existing DB pensions (for current pensioners and deferred members not yet transitioned), process invaren calculations (converting rights to capital), and manage new DC accounts (for transitioned members and new entrants). The legacy system could not handle this dual administration. (3) Regulatory timeline — the WTP implementation deadline (January 1, 2028) created a hard constraint. Pension funds needed to submit their transition plans (implementatieplan) to DNB by mid-2025. The administration organisation needed to demonstrate to DNB that their technology could support the transition — the legacy system could not. DNB was actively assessing pension administration organisations' WTP readiness as part of its supervisory programme. (4) Participant communication — WTP required extensive participant communication: transition impact statements (showing each participant how their pension changed from DB to DC), real-time capital account access (participants able to see their personal pension capital online), and choice architecture (some WTP transitions offering participants choices about risk profiles and investment allocations). The legacy system's batch-processing architecture could not support real-time participant portals — UPO statements were generated annually through a month-long batch process, and participants had no online self-service access to their pension data. (5) Integration complexity — the administration organisation interfaced with: 4 pension fund boards (each with different governance requirements and scheme rules), 12,000 participating employers (submitting payroll data for contribution calculations), DNB and AFM (regulatory reporting), investment managers (5 asset managers managing the pension funds' investments), and the Pensioenregister (national pension registry — providing participants with a consolidated view of all their pensions). These interfaces ran through a mix of SFTP file transfers, legacy EDI formats, and manual processes — none through modern APIs.

We delivered a comprehensive pension administration modernization over 48 weeks — replacing the 30-year-old AS/400 system with a WTP-ready platform while maintaining continuous administration for 4.4 million participants. (1) Pension rule extraction: decoding 30 years of Dutch pension law. Automated RPG analysis: parsing 2.6 million lines of RPG/ILE code to extract: 12,400 pension calculation rules across 48 scheme variations, contribution calculation logic for 12,000 employer relationships, benefit payment processing rules (tax withholding, social insurance deductions, partner pension calculations), and regulatory reporting calculations (DNB reports, UPO generation, Pensioenregister submissions). Actuarial validation: every extracted rule validated against: scheme regulations (pensioenreglement) for each of the 4 pension funds, actuarial assumptions and methodologies, and historical calculations (comparing extracted rule outputs against actual pension payments and UPO statements from the past 5 years — 4.4 million statement comparisons). This validation uncovering 34 discrepancies between implemented rules and scheme regulations — errors that had existed in the legacy system for years (small calculation differences affecting specific participant categories that manual checks had never caught). These were corrected in the modern system with actuarial sign-off. (2) WTP-ready modern platform. Architecture: Kubernetes (AWS EKS, eu-west-1 Ireland region with data residency controls for Dutch-resident data) with: Java/Kotlin microservices for pension calculation engine (BigDecimal precision for actuarial calculations), PostgreSQL for participant and scheme data, event-driven architecture replacing batch processing, React participant portal with real-time capital account visibility, and API gateway enabling modern integration with employers, investment managers, and regulatory systems. Dual calculation engine: the key innovation — the modern platform containing both DB and DC calculation capabilities: DB engine (for ongoing administration of existing pensions and historical calculations), DC engine (for new WTP administration — capital accounts, variable pensions, investment allocation), and invaren engine (the transition calculator — converting DB rights to DC capital for each participant based on their specific scheme, entry date, and personal circumstances). The invaren engine implementing the WTP's transition methodology: determining each participant's accrued DB pension rights, calculating the actuarial value using prescribed parameters (interest rate, mortality table, indexation assumptions), converting to personal capital using the fund's chosen transition methodology (standard, vba — verdeelmethode bij aanpassing — or collectief), and applying solidarity and compensation mechanisms as defined in each fund's transition plan. Product configuration: all pension scheme rules parameterised — each scheme variation defined through configuration rather than code. The 48 legacy scheme variations modelled as configurations, with new WTP DC schemes configurable by pension fund boards without code changes. (3) Migration with zero participant impact. Parallel running: both AS/400 and modern systems processing all pension administration functions simultaneously: monthly pension payments calculated by both systems — automated reconciliation comparing 800,000 payments monthly (any discrepancy exceeding EUR 0.01 investigated and resolved), contribution calculations for 2.4 million active members compared monthly, and UPO statement generation compared for accuracy. Initial parallel running discrepancies: 0.8 percent of participants showing differences (primarily due to legacy system calculation errors discovered through comparison — the modern system actually calculating more accurately). After 12 weeks: 0.001 percent discrepancy rate (4 participants out of 4.4 million — each attributable to legacy data quality issues). Migration sequence: Phase A — pensioner payments (weeks 10-20): migrating 800,000 pensioner payment processing. Pensioner payments were the highest-risk migration (retirees depending on monthly pension income) — extensive parallel running before cutover. Phase B — active member administration (weeks 16-28): migrating contribution processing and accrual calculations for 2.4 million active members. Employer interfaces migrated from file-based to API-based (with legacy file format supported for employers not yet API-ready). Phase C — deferred member administration (weeks 24-34): migrating 1.2 million deferred member records. Phase D — participant portal launch (weeks 30-38): launching self-service portal providing participants real-time pension data access — a capability the legacy system could not provide. Phase E — WTP invaren capability (weeks 34-44): deploying invaren calculation engine, testing with actuarial teams using simulated transition scenarios. Phase F — legacy decommission (weeks 44-48): AS/400 decommissioned after 4 weeks of modern-only operation. (4) Participant communication platform. Self-service portal: participants accessing real-time pension data for the first time — current pension rights, projected retirement income (scenario-based), contribution history, and employer details. WTP transition tools: personalised transition impact statements showing each participant how WTP conversion would affect their pension — comparing DB projection with DC capital account projection under various market scenarios. The portal enabling participants to model different scenarios (retirement age, part-time working, additional contributions) — previously impossible with the batch-processing legacy system. Communication automation: automated participant communication for life events (marriage, divorce, job change, disability) — previously manual processes requiring 15 working days, now automated to 2 working days. (5) Regulatory compliance. DNB reporting: automated regulatory reporting replacing manual data extraction and manipulation. DNB quarterly returns generated in 4 hours (previously 3 weeks). DNB supervisory assessment: conducted during the modernization — DNB examiner commenting positively on the parallel-running validation approach and WTP readiness timeline. DORA compliance: the modern platform meeting DORA requirements for ICT risk management, incident reporting, and operational resilience testing — capabilities the legacy AS/400 could not support. Pensioenregister: automated submission replacing manual file generation — real-time data accuracy improving participant pension overview quality.

Results over 12 months post-modernization. WTP readiness: invaren calculation engine operational — capable of processing 4.4 million participant transitions. Actuarial validation of invaren calculations completed for all 4 pension funds. Pension fund boards submitting implementatieplannen to DNB with technology readiness confirmed. The administration organisation recognised by DNB as "WTP transition ready" — one of the first in the Netherlands. Administration efficiency: monthly pension payment processing: from 5-day batch cycle to real-time processing. Payment accuracy: maintained at 99.999 percent through parallel-running validation. UPO statement generation: from 30-day annual batch to on-demand real-time. Employer contribution processing: from 10-day file-based cycle to 2-day API-based processing. Participant communication: life event processing from 15 working days to 2 working days. Self-service portal: 680,000 participants registered in first year (from zero). Regulatory compliance: DNB reporting: from 3 weeks manual to 4 hours automated. DORA compliance: operational resilience requirements met. DNB examination: zero modernization-related findings — examiner noting "significantly improved technology governance." Cost: AS/400 infrastructure: EUR 3.8M annually — eliminated. Modern platform: EUR 1.4M annually. Annual infrastructure saving: EUR 2.4M. Development velocity: regulatory change implementation from 4-6 months (RPG modification) to 3-4 weeks (configuration). Total modernization investment: EUR 6.8M over 48 weeks. Annual savings: EUR 3.6M (infrastructure + processing efficiency + regulatory reporting). Payback period: 23 months. 5-year TCO reduction: EUR 11.2M.