OFS Response Parser & Error Explainer

Why you need to parse OFS responses

When an external system sends an OFS message to T24, the response tells you everything that happened — but only if you can read it. Raw OFS responses are comma-separated strings that pack the application, options, record ID, returned data fields, error codes, and override messages into a single hard-to-read line.

This parser takes that raw response and breaks it into clear, labelled sections: the overall status (success, error, override, or malformed), the parsed components, any error codes with their human-readable explanations, override messages, returned data fields, and step-by-step guidance on what to do next. It is designed for incident investigation, interface debugging, and learning how T24 responds to different OFS operations.

OFS response parsing example

Try pasting this synthetic OFS response into the parser to see how it decomposes:

FUNDS.TRANSFER,FT.V1/I/PROCESS,INPUTT/123456/GB0010001,FT20260708001,
DEBIT.ACCT.NO=100234,CREDIT.ACCT.NO=100567,
DEBIT.AMOUNT=5000.00,CREDIT.AMOUNT=5000.00,
ORDERING.CUST=100100,BENEFICIARY=Acme Corp

The parser will show you the overall success status, the record ID (FT20260708001), every returned field, and a confirmation that no errors or overrides were detected. If the response contains an error code like FIELD.NAME.UNKNOWN=DEBIT.AMOUNTX, the parser flags it as a validation error, explains what the code means, and suggests the most likely cause and next steps.

Common use cases

• Debugging failed integrations: When an external system gets an error from T24, paste the response to instantly see which error code was returned and what to check next.
• Verifying successful operations: After creating or updating a record via OFS, confirm the response includes the expected record ID and returned fields.
• Analysing override conditions: Some operations succeed but with override messages — parse the response to see what conditions were triggered and whether manual authorisation is needed.
• Learning OFS response patterns: Use the example responses to understand how T24 formats success, error, and override responses for different scenarios.

Frequently asked questions

What is an OFS response and why do I need to parse it?

An OFS response is what T24 sends back after processing an OFS message. It contains the record ID, returned data fields, error codes, override messages, and status information. Parsing the response helps you quickly understand whether the operation succeeded, what fields were returned, and what went wrong if it failed.

What OFS response statuses does this tool recognise?

The tool recognises six statuses: Success (record created/updated with returned data), Validation Error (field-level or data validation failures), Error (connection, security, or system-level errors), Override (conditions triggered that need attention), Partial Success (record saved but with override conditions), and Malformed (response does not match expected OFS structure).

Does this tool send my OFS response data anywhere?

No. All processing happens entirely in your browser with zero server calls. Your OFS response data, including any log content, credentials, or account information, never leaves your machine. There is no API, no server-side processing, and no data storage.

How do I read a T24 OFS response?

A T24 OFS response is a comma-separated string with five main segments: the application being called, the options (version/function/flag), the user credentials, the record ID, and the data/body section. The data section contains returned fields as field=value pairs, error codes, and override messages. This tool breaks each part into its own section for easy reading.

What OFS error codes are recognised?

The parser recognises 25+ common OFS error codes including OFS_CONN_ERR, OFS_TIMEOUT, FIELD.NAME.UNKNOWN, OFS.INVALID.FIELD, OFS.MISSING.MANDATORY, OFS.RECORD.NOT.FOUND, OFS.RECORD.ALREADY.EXISTS, OFS.SECURITY.ERR, ROUTINE.FAILURE, and TRANSACTION.ABORTED. Each error code comes with a plain-English explanation, common causes, and practical next steps.

Related articles