What does the OFS Generator do?

The OFS Generator is a browser-based message builder for creating synthetic T24 OFS request strings. It helps place the operation, options, sign-on context, operation-specific ID information, and data fields in the expected sections without hand-counting separators.

How do I format an OFS message?

A common OFS request follows five sections: APPLICATION or OPERATION, OPTIONS, USER or sign-on context, ID INFORMATION, and DATA. The fourth section is operation-specific and may be a record key, transaction reference, enquiry context, or blank; it is not a universal SOURCE field. Verify the exact syntax for the target operation and release.

When should I use the OFS Parser instead?

Use the Generator when you are creating a new synthetic request. Use the Message Parser when you already have an OFS request string and want to inspect its sections and fields. Use the Error Decoder for a short error fragment and the Response Parser for a complete response.

How do I validate an OFS message before sending it?

Where the target operation and release support the expected VALIDATE behaviour, use VALIDATE in an approved non-production path before PROCESS. The generator can help you structure the request, but it does not connect to T24 or prove that a message is valid for your environment.

Tool

OFS Generator & Message Builder

Build a synthetic T24 OFS request without hand-counting commas. Choose the application/operation, set processing options, add fields, and copy the resulting OFS string for controlled testing or learning.

Quick start

Use this generator when you are creating a request

Start here when you have an operation and field values but not a finished OFS message. Use synthetic values while learning. The generator runs in your browser; it does not submit anything to T24 and it cannot confirm that a locally configured version, field, user, or source/channel is valid.

You have...	Use...	Why
Fields/options but no request string	Generator / Builder	Create a structured synthetic request.
An existing OFS request string	Message Parser	Inspect the sections and field positions.
A short returned error fragment	Error Decoder	Classify likely failure stage and next evidence.
A complete returned response	Response Parser	Separate status, fields, errors, and overrides.

Need the five-section shape beside you? Open the OFS message quick reference.

Quick start — load an example

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

Live preview

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

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

Application (Operation)

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

Options

Version

Function

Flag

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

User / Password / Company

User

Password

Company

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

ID information (operation-specific)

The 4th section is operation-specific ID information. It may be a record key, transaction reference, enquiry context, or blank. For R (read) operations it commonly identifies the record to retrieve; for I (input) operations it may be a specific ID or blank. Confirm the exact syntax for the target operation and release. It is not a universal OFS.SOURCE field.

Data Fields

FIELD.NAMEGroupItem= VALUE

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

How to use

Click a Quick start example to pre-fill the form
Tweak the values in each section
Watch the live preview update as you type
Click Generate to build the final message

OFS message structure

A common OFS request has 5 comma-separated sections:

1. Operation — T24 application name (e.g. CUSTOMER, FUNDS.TRANSFER)

2. Options — VERSION/FUNCTION/FLAG (e.g. MB.TEST/I/PROCESS)

3. User info — USER/PASSWORD/COMPANY (company optional)

4. ID information — An operation-specific record key, transaction reference, enquiry context, or blank

5. Data — FIELD=value pairs, comma-separated

About VALIDATE

VALIDATE mode runs all normal T24 processing without committing anything to the database. Use it to test messages before sending them for real — T24 returns the full record with defaults populated, without touching live data.

Function reference

I — Input. Create or modify a record.

R — Read. Display a record without changing it.

D — Delete. Remove a record.

Learn how OFS messages work in detail, or parse existing messages:

Read the OFS guide Use the OFS Parser

Privacy

All processing happens locally in your browser. Nothing is sent to any server. Your OFS messages, credentials, and data never leave your machine.

What the generated OFS string contains

A common OFS request can be read as five sections:

OPERATION, OPTIONS, USER/SIGN-ON CONTEXT, ID INFORMATION, DATA

The fourth section is operation-specific. It may be a record key, transaction reference, enquiry context, or blank. It is not a universal OFS.SOURCEfield. Source/channel configuration is a separate concept and must be verified for the target interface and release.

If you want the detailed explanation and transaction/enquiry examples, read OFS in T24: Message Format, Examples & How It Works.

Synthetic OFS message examples

Use examples to understand separator placement, not as production-ready messages. Application versions, fields, sign-on behaviour, and required values differ between environments.

Create-style request

ACCOUNT,OFS/I/PROCESS,TEST.USER/654321,,
CATEGORY=1001,
CURRENCY=GBP,
CUSTOMER=100100,
ACCOUNT.TITLE.1=Example Account

The blank fourth section is intentional for this synthetic example only. It does not mean every create operation leaves ID information blank.

Enquiry-style request

ENQUIRY.SELECT,,TEST.USER/654321,CURRENCY-LIST,@ID:LK=C...

Here the fourth section is enquiry-specific context. This is why a message builder must not label that position as a universal source field.

Before you use a generated message

Confirm the operation. Check that the application/action and request family are correct.
Confirm the options. Version, function, and processing semantics can vary by operation/release.
Use safe sign-on values. Never paste real passwords, customer data, tokens, or confidential identifiers into examples.
Check ID information. Interpret the fourth section for the specific operation rather than assuming it is a source.
Validate locally. Use an approved non-production path and local documentation before PROCESS or any production use.

Frequently asked questions

Is this an OFS generator, OFS builder, or OFS message generator?

Those terms describe the same task here: creating a structured OFS request string from operation/options and field values. The canonical tool remains this single Generator & Message Builder page; there are no duplicate generator routes.

Does the generator prove my message is valid in T24?

No. It helps with structure and output assembly. Only the target environment can prove that the operation, version, fields, security context, source/channel, and business rules are valid.

When should I use VALIDATE?

Where the target operation/release supports the expected VALIDATE semantics, it can be useful in an approved non-production path before PROCESS. Confirm local behaviour first; do not treat one example as universal.

Free OFS resource