Close of Business (COB) is run daily by banks to consolidate the transactions that happened and make the systems available for next-day transactions. Monitoring the COB requires in-depth knowledge of T24 services, jobs, and COB setup. This also involves executing a few manual steps to run and check the COB progress.

Open Financial Services (OFS) is the language T24 uses to communicate with itself and the outside world. You can send a transaction in the OFS format to T24 and receive the response in the same standardized OFS format. In this blog, we will explore how to create an OFS string and test the posting of a transaction.

The Application Test Framework (ATF) uses OFS to run bulk testing for T24 applications. It is designed for Release Validation Tests (RVTs) that cover high-value functional tests across the core banking system. It supports automated testing of key business processes and modules relevant to the release being validated. Test scripts are created using Apache Karate feature files, which can be tailored to various modules and functionalities. The framework is integrated into the re

Temenos provides an Operational Data Store (ODS) to retrieve data from the Transact environment and expose it as services through an IRIS Runtime. The ODS is typically provided as part of the Data Lake solution, which separates read operations from the Transact core.

Arrangement Architecture (AA) is the agreement between the customer and the bank with predefined, customized conditions to maintain Loans, Deposits, or Accounts in a core banking platform. Before learning AA, you need to understand the basic concepts of Customer, Account, Interest, Charges, Limits, and coding concepts.

Coding in the T24 Globus release started with the INFOBASIC programming language. Almost all core routines/applications are developed using this language. T24 later evolved from GLOBUS to TAFC and TAFJ. During this transition, the coding changed from INFOBASIC to Componentized, and then to Java. The extensibility framework also uses Python coding now. Depending on the T24 release and framework, banks can choose the required programming language.

To grasp the fundamental concepts of T24 core banking, it is essential to connect them with our everyday banking practices. A straightforward example is a balance inquiry, which involves retrieving the balance stored in the database. Another example is the transfer of funds, which functions as both a debit and credit update, representing a write operation to the database. In this blog, we will share the basic concepts of T24 core banking.

The Close of Business (COB) is a daily operation and a vital component for any banking institution. Many common issues can be swiftly assessed if we have an appropriate monitoring system established on our dashboard. With our fastpack services, we provide you with the majority of the details related to COB. In this blog, we will explore how these details can assist in the analysis of COB-related issues.

Numerous banks continue to operate with older iterations of Temenos T24, which have been reliable for many years. Nevertheless, as business requirements change, these systems become increasingly challenging to manage due to the rising demands of digital transformation.

Learn how to effectively debug TSA services in your T24 Transact environment using native commands. This step-by-step guide explains how to run services in debug mode, track real-time execution details, and gain deeper insights into your code’s behavior.

Understanding the structure and behavior of our T24 database is essential for maintaining healthy performance as data volumes grow. Efficient communication between the database and the application layer ensures that queries, COB operations, and daily transactions run smoothly.

Temenos Payment Hub (TPH) is a sophisticated payment module designed to streamline the posting and processing of transactions. TPH is made up of two modules: PP, or payment processing, which is an end-to-end payment process from start to finish, and PI, or payment instruction, which is used to set instructions for executing the payment. The banks must choose both modules to fully deploy TPH. We must perform functional testing and related regression testing to test the TPH

Managing services in T24 isn’t just a technical task—it actually shapes how well the system runs. Services are basically collections of jobs scheduled to run in a specific order. You decide when they start, set schedules, run them automatically, and shut them down when they’re no longer needed.

La gestión eficiente de las tablas JOB.LIST es fundamental para una ejecución fluida de COB en T24. Aprende las mejores prácticas para reducir el tamaño de las tablas, ajustar las exportaciones DW, monitorear los registros y evitar cuellos de botella de rendimiento para mantener tu sistema de core banking ágil y confiable.

Optimizar el rendimiento y reforzar la seguridad del core bancario es fundamental para cualquier institución financiera que utilice T24 Transact

Learn how SEAT automates testing in T24 covering script creation, execution, result validation, and error tracking.

This blog explains the bulk payment workflow in T24, outlining how payment data usually uploaded via a CSV file—is processed through the FILE.UPLOAD application. Once uploaded, a MAIN bulk payment record and related ITEM records are created for each transaction.

Effective COB monitoring is essential for ensuring smooth overnight processing and timely service at the start of each banking day. Temenos Transact provides several enquiries and tools that give real-time visibility into COB operations.

Temenos lanza una nueva versión de T24 cada año, y en 2025 presenta R25, centrada en el rendimiento y la eficiencia. Temenos launches a new T24 release every year, and in 2025 introduces R25, focused on performance and efficiency. Key improvements include Data Lifecycle Management (DLM) optimizations, such as excluding ReadOnly data from batch jobs and online searches

Build better T24 APIs with this best practice guide covering everything from input validation to performance and documentation.