Industry: Retail & Commercial Banking
Region: Europe / Middle East
Business Driver: Core banking modernization and T24 sunset
Overview
A mid-sized retail and commercial bank operating across multiple markets ran Temenos T24 as its core banking system of record for over a decade, managing product definitions, transaction processing, and customer account data across its retail, corporate, and private wealth divisions.
Following a strategic decision to migrate to a next-generation core banking platform, the bank faced a decommissioning challenge that most T24 customers encounter too late: T24’s proprietary data structure makes historical data effectively inaccessible without the live application running. Retiring the system without a compliant, searchable archive in place would have meant either maintaining an expensive parallel instance indefinitely or accepting a regulatory gap across years of transaction and account history.
The bank required a T24-native archive solution capable of preserving full data fidelity, regenerating original reports on demand, and replicating end-user access controls, without T24 itself.
Challenges
- Proprietary data structure: T24 does not store data in conventional relational tables. Records are held in two columns as multi-valued fields using internal references, making data unreadable by standard RDBMS tools or generic archive platforms without native parsing capability.
- Report and statement regeneration: Historical statements of account, loan schedules, transaction histories, and regulatory reports were generated dynamically by T24. Without the live application, reproducing them accurately from archived data was a significant technical barrier.
- Access model continuity: The bank’s existing T24 environment enforced role-based application groups controlling which users could access which data. Replicating that access model in a decommissioned archive, rather than rebuilding it from scratch, was a compliance and operational requirement.
- Dual-stack support: The bank’s environment included both TAFJ and TAFC T24 deployments, requiring a solution with native support for both technology stacks.
- Retention and holds: Regulatory obligations across multiple jurisdictions required the archive to enforce configurable retention schedules, legal holds, and defensible disposition, not just passive storage.
Business Requirements
- Decommission the T24 application while preserving full historical data fidelity.
- Enable on-demand search, retrieval, and regeneration of T24 reports and statements post-sunset.
- Replicate existing T24 application group structures and user access controls in the archive.
- Support both TAFJ and TAFC deployments within a single archival workflow.
- Convert multi-valued field structures to clean, auditable XML without data loss.
- Enforce jurisdiction-specific retention policies, legal holds, and purge workflows in the archive.
- Eliminate ongoing T24 licensing and infrastructure costs after decommissioning.
Solution
The bank implemented Archon Data Store to archive and decommission its Temenos T24 environment.
Archon’s in-house T24 connector, built specifically for the platform’s proprietary data architecture, extracted records directly from the T24 database without requiring custom middleware or third-party ETL tooling. The extraction engine natively parsed multi-valued fields and internal T24 references, converting them into clean, structured XML that is both human-readable and machine-queryable.
Archon provided:
- Native T24 data extraction across both TAFJ and TAFC environments, with no custom code required on the client side.
- Multi-valued field conversion to structured XML, preserving the full fidelity of T24 records in a format accessible to audit, legal, and compliance teams.
- On-demand report and statement regeneration including Statements of Account, Loan Details, and transaction histories, reproduced accurately from archived data without the T24 application.
- Access model replication, migrating existing T24 application group structures into Archon to maintain user-level access restrictions and functional continuity for end users post-decommission.
- Compliance controls including configurable retention schedules, legal hold orchestration, and defensible purge workflows aligned to the bank’s multi-jurisdictional regulatory obligations.
- Full T24 sunset, eliminating the need to maintain a parallel T24 instance for historical access.
Business Outcomes
Ready to sunset your T24 environment without losing access to your data? Request a Consultation
