Tool

OFS Message Builder

Build OFS messages interactively. Select an application, set options, add fields with values, and get a correctly formatted OFS string — every comma in the right place.

What is an OFS message in T24?

OFS (Open Financial Services) is the real-time messaging protocol used by Temenos T24 (Transact) to process transactions, create records, and run enquiries. Every time an external system sends data to T24 — whether it is a payment instruction, a customer update, or an account creation — it does so through an OFS message.

An OFS message has five parts: the application name, processing options, user credentials, a record ID, and the data fields. Getting the format wrong means the message is rejected with an OFS error, which is one of the most common integration issues T24 teams face.

This tool helps you build correctly formatted OFS messages without memorising the comma positions, multi-value notation, or field ordering rules.

OFS message example

A typical OFS message to create an account in T24 looks like this:

ACCOUNT,OFS/I/PROCESS,INPUTTER/12345/,,
CATEGORY=1001,
CURRENCY=GBP,
CUSTOMER=100100,
ACCOUNT.TITLE.1=John Smith,
ACCOUNT.OFFICER=CO01,
ONLINE.ACTUAL.BALANCE=0

Each part is separated by a comma: the application (ACCOUNT), the options (OFS/I/PROCESS), the user (INPUTTER/12345/), the record ID (blank for new), and the data fields. Multi-value fields use:1, :2 notation. This tool handles all of that for you.

Frequently asked questions

What is an OFS message in T24?

OFS (Open Financial Services) is the real-time messaging protocol used by Temenos T24 to process transactions, enquiries, and record updates. It is the primary way external systems — such as payment engines, online banking platforms, and middleware — communicate with T24.

How do I format an OFS message?

An OFS message follows a five-part structure: APPLICATION,OPTIONS,USER,,DATA. The options control how T24 processes the message (e.g. OFS/I/PROCESS for input processing). Data fields are comma-separated with multi-value positions using:1 notation. Use this builder to generate correctly formatted messages without memorising the syntax.

What is the difference between OFS and API in T24?

OFS is the legacy real-time protocol that has been part of T24 since the beginning. APIs (REST/SOAP) are a newer integration layer, often provided through the Temenos Integration Framework (IRIS). OFS is still widely used because it is simpler, faster for high-volume transactions, and does not require additional middleware. Many production T24 environments process millions of OFS messages daily.

How do I validate an OFS message before sending it?

You can use the VALIDATE mode in the OFS options to check the message without committing it. This tool also provides field-level validation — required fields are marked, and the generated output can be reviewed before use. For more detail, read the OFS in T24 article.

Read about OFS in T24Try the OFS ParserAA Activity Builder

Click any example to pre-fill the form with realistic data. Then tweak the values.

FUNDS.TRANSFER,/I/PROCESS,//,//

This updates as you type. Colour-coded: Application · Options · Credentials · Record ID · Data

The T24 application this message will act on — e.g. FUNDS.TRANSFER for payments, CUSTOMER for customer data.

Version
Function
Flag

I = Input (create/modify) · R = Read (display) · D = Delete.
PROCESS commits to the database. VALIDATE tests without saving.

User
Password
Company

The T24 sign-on that will own this transaction. Format: USER/PASSWORD/COMPANY. Company is optional.

The 4th segment of the OFS message. This is the record key or transaction reference for the application. For R (read) operations, this is the record you want to retrieve. For I (input) operations, this can be a specific ID or left blank for T24 to auto-generate.

FIELD.NAMEGroupItem= VALUE

Format: FIELD.NAME : Group : Item = value. Group and Item are optional — leave blank for simple single-value fields.