Understanding Applications in T24: A Practical Introduction

To start the new year 2026 on the right foot, we have decided to begin this new post to share basic knowledge about T24, where we will review concepts, main structures, and other topics. In this first post, we will explain the main data component in T24: Applications.

Application

An Application is a structure used for data storage in T24. Applications perform field-by-field validations of the entered information and also allow the execution of functions such as leaving data pending authorization, performing authorizations, deleting records, and generally maintaining the information within the application.

Example of the CUSTOMER application for customer data entry

Database-level categories

An application has four categories or types at the database level:

1. Live Table: Stores authorized records

2. Unauthorised Table: Stores unauthorized records

3. History Table: Stores historical records

4. Delete Table: Stores deleted unauthorized records

Functions to interact with applications

Certain functions allow us to maintain application records. These functions can be used either from the administrator command line in T24 or from within the application window. The main functions are:

• L → List authorized records

• E → List unauthorized records

• I → Enter or create a new record

• S → View a record in view-only mode

• A → Authorize a record

• D → Delete an unauthorized record

• R → Reverse an authorized record

The above functions are also available as buttons within the application window.

Business Classification

Applications in T24 are defined at the business level in three types:

• INT (Installation): Applications shared by all branches. These are typically system configuration applications, such as SPF.

• FIN (Financial): Applications related to financial operations, such as accounts and funds transfer.

• CUS (Customer): Applications used to manage and store customer data.

  
  

This type is defined in FILE.CONTROL, in the Classification field

VERSION

A version is basically a customized application. We can create different versions of T24 applications and, through them, provide better visibility. This allows us to define which fields we want to display, perform custom validations through programs, set default values, catalogs, and other validations.

Example of a Customized CUSTOMER Version

Company

It is one of the main T24 applications that helps us define our service branches. It also works to segment information within the core system, since, depending on how data is managed, it belongs to specific companies and can only be accessed through them. In T24, there must always be at least one company master.

To operate, companies require at a minimum a name, a mnemonic, and an ID, in addition to the definition of which applications will be associated with them.

Standard Selection

It is an application where the structure of other applications is defined. Here, field formats, data types, catalogs, and, in general, all the necessary information related to the structure of an application are defined.

There are many other applications of great importance in T24. If you need to know how to have them correctly configured, understand the functionality of each one, and be able to apply all types of banking operations, at Performetriks, our experts are at your disposal. We will be happy to work with you to help you get the most out of your core banking system.

Happy Performance Engineering!

#T24 #CoreBanking #SoftwareEngineering