T24Connect A certified morning 15-day pilot Services About Start a pilot
Released 8 October 2026 — T24Connect V3.0.3

Your T24 data.
Readable, complete,
and certified — every morning.

A read-only service that turns your Temenos T24 database copy into a SQL database your own teams can use, and hands you a signed Data Certificate each morning stating exactly what arrived — and what did not, and why.

See a certified morning →
9,620
applications, live and history, in one morning · certificates 27/28, 5 Oct 2026
22 min
for that morning (live 13 + history 9) — 675,620 records reconciled, remainder zero
0
T24 write code in the installed program
15 days
free pilot on your own T24, one success criterion
T24Connect Morning Status, 4 October 2026: Your T24 data is ready. CERTIFIED · PASS.
Morning Status, 4 October 2026. Temenos model bank · 9,620 applications · Data Certificate 25 and 26 · CERTIFIED · PASS. A real morning, not a mock-up.
T24Connect V3.0.3 — the certified extraction and assurance layer for Temenos T24
Read-only, proven at build time Real field names from your own dictionary Change history, version by version Signed Data Certificate every morning
The product

The data is yours.
Reading it is the problem.

T24 stores every record in a form only T24 can read. Field names are hidden behind generic tags; repeating values are packed together; the layout differs by release, by company and by every local field your bank has added over the years.

So when finance, risk or audit need T24 data outside T24, nobody can prove the extract is complete. A missing table, a truncated value, a record that vanished — all look like "nothing there".

T24Connect reads your bank's own T24 dictionary, lands every application you choose into SQL Server with real names and full change history, moves only what changed each night, reconciles source to landing to the record, and signs a Data Certificate every morning.

Oracle (TAFJ) SQL Server (TAFJ on SQL Server) Landing: SQL Server One Windows host beside your copy
How it works
6,944
applications learned from the dictionary
about 198,000 fields · 96 seconds · 8 Oct 2026
13 + 9
minutes, live + history, 9,620 applications · 917,140 source rows read
Certificates 27/28 · 5 Oct 2026
3 of 10M
changed records found by content alone
10,000,000 compared in 23 m 28 s
15 min
a night with no changes on ten million records
fingerprint computed inside Oracle · ten-million fixture
🏛️
Your T24 database copy
SELECT-only login
→
🛡️
T24Connect V3.0.3
read-only, reconciled, signed
→
🗄️
SQL Server landing
Power BI · Excel · your reports

All figures measured on a Temenos model bank on an ordinary business laptop that also hosts Oracle and SQL Server; your hardware will differ. Each figure names its record.

📖

Learns your T24 in minutes

Reads your bank's own T24 dictionary — every application, every field, every local field — from your copy. No mapping spreadsheet, no developer. A dictionary that reads back short is refused, never silently accepted.

Real field names
🗄️

Lands it where your tools are

Every application you select arrives in SQL Server with T24's real field names as columns, repeating values in child tables, and change history kept version by version. Power BI, Excel and your reporting tools connect directly.

Live and history
🔍

Moves only what changed

After the first load, each morning moves only the records that changed — detected by comparing record content, not by trusting a counter. Records removed in T24 are flagged, never deleted from your copy.

Content, not counters
📜

Proves it, every morning

Every run ends with a reconciliation of source against landing, application by application, and a signed Data Certificate stating what was counted, what was verified, and what was not included and why.

Data Certificate
🛡️

Never writes to T24

The installed program contains no T24 write code — proven at build time and shown on a page inside the product, computed from the running binary. The T24 login it asks for is SELECT-only; your DBA grants it.

Read-only proof
⏰

Runs itself

Scheduled, unattended, from trigger to certificate. A late start after a server restart is logged once and runs once; two schedules never overlap. The Morning Status page shows the night in one glance.

Unattended
A certified morning

The screens a banker actually reads

Real pages from T24Connect V3.0 running on a Temenos model bank, captured between 4 and 10 October 2026. Nothing below is a mock-up.

T24Connect — Morning Status
CERTIFIED · PASS
Morning Status page

One verdict. "Your T24 data is ready." — or "not ready" with the applications named, the reason and the action. Four numbers a sponsor can repeat in a meeting. Ten business days, one verdict each.

T24Connect — Data Certificate DC-20261010-001
Signed
Data Certificate DC-20261010-001: CERTIFIED · PASS, 7,795 of 7,795 tables match

Numbered, signed, dated — this one is DC-20261010-001, 10 October 2026: 7,795 of 7,795 tables match, 659,323 records read on this run’s scope, signature valid — bound to your T24 dictionary's fingerprint. Source count = landing count, per application, remainder zero. What was not included is named, with the reason. Evidence you can hand an auditor.

T24Connect — Browse Data · ACCOUNT
Real field names
Browse Data page showing real T24 field names as columns

Columns named the way T24 names them — read from your bank's own dictionary, every local field included. No c1, c2, c3; no mapping spreadsheet. Repeating values sit in child tables keyed to the parent.

T24Connect — Read-only proof
none-compiled
Read-only proof page

Computed from the running program, not from a slide. No T24 write code in the installed binary; the T24 login in use is SELECT-only; program starts are under administrator control and listed on the same page.

How it works

Beside your T24, never inside it

T24Connect sits between the database copy your bank already refreshes and the SQL Server landing database your teams read from. Nothing changes in your production environment, and nothing is ever written to T24.

🏛️

Your T24 database copy

Oracle (TAFJ) or SQL Server (TAFJ on SQL Server)
Live files and $HIS history
Read with a SELECT-only login

→
Read-only
V3.0.3
🛡️

T24Connect

Reads your dictionary · lands with real names
Compares record content each night
Reconciles source to landing
Signs the Data Certificate

→
Structured SQL
🗄️

SQL Server landing

Relational tables, real field names
Child tables for repeating values
Change history, version by version
Power BI · Excel · your reports

9,620
applications checked, live and history; 675,620 landed records reconciled to the record, remainder zero, in one morning
Certificates 27/28 · 5 Oct 2026
3 h 05m
first load of a ten-million-record table; afterwards a night moves only what changed
Ten-million fixture · 25 Sep 2026
23min
content check over ten million records, landing the three that changed
Ten-million fixture · 26 Sep 2026
<1hour
from the release package to a running install with the first login screen
V3.0.3 package verified 8 Oct 2026
Never writes to T24

No T24 write code in the installed program — proven at build time, shown on a page.

Never touches production

It reads the database copy your bank already refreshes, with a login your DBA grants.

Never drops a table, never deletes a record

What you have landed stays yours — including after the licence ends.

Runs after your close of business, never during it

You set the schedule; COB stays entirely with your operations team.

Never guesses

An application it could not verify is named, with the cause. A certificate is withheld rather than issued on a doubt.

All figures measured on a Temenos model bank on an ordinary business laptop that also hosts Oracle and SQL Server; your hardware will differ. Flat-format T24 files are counted and reported but not landed in this release; the certificate names them.

The pilot

Fifteen days, no charge,
one success criterion

A morning Data Certificate that reads CERTIFIED · PASS on your T24, on your companies, with your DBA holding every credential. If it does not, you keep the certificate that says why. The pilot edition covers ten applications live and ten history, two sync groups, one company — enough to prove the morning.

1

Before day one

The DBA questionnaire and the reader-login grant list. Oracle: CREATE SESSION, SELECT on T24 tables, EXECUTE on DBMS_CRYPTO — no FLASHBACK, no system views. SQL Server: db_datareader.

2

Day one

Install on your host in under an hour: wizard, learn the dictionary, choose scope, first load — on your database copy, never on production.

3

Days two to fifteen

The nightly schedule runs on your chosen applications, live and history. Each morning: one verdict, the reconciliation, the signed certificate.

4

After

An annual licence per host, all-inclusive, price fixed for the first three renewals. The landing database and every certificate stay yours either way. At the end of the pilot, data disposal if you choose it.

Stated plainly

Oracle (TAFJ): proven in nightly certified runs on a Temenos model bank. SQL Server (TAFJ on SQL Server): supported; validated on your instance during the pilot.

Flat-format T24 files are counted and reported but not landed in this release; the certificate names them. The decoder is the first item on the roadmap.

The program is not yet code-signed: its SHA-256 is published in the release notes and the signing certificate is in progress. No independent penetration test has been run yet; one is available at cost.

Building the reports is your team's work, with your tools. T24Connect delivers the data and the proof.

It is not a streaming platform, not an API layer and not an analytics pack. It is the certified extraction and assurance layer — and it runs beside whatever else you have.

Included: the security pack, the installation guide, the operations runbook, the user guide, and the release notes with the build's SHA-256.

Services

Temenos T24 consulting and delivery

Beyond T24Connect, iGen Services and Solutions delivers Temenos T24 consulting, implementation and support — backed by more than a decade of field experience.

01

T24 Implementation

End-to-end implementation following a structured implementation method: process workshops and gap analysis through BRD, FSD, design, development and UAT — Agile or Waterfall.

BRD & FSDSIT & UAT
02

T24 Upgrade

A field-tested upgrade process from G10 to the latest release, preserving local customisations and interfaces.

G10 to latestCustomisation retention
03

T24 Data Migration

Structured migration with validation, reconciliation and rollback safeguards, across legacy migration and fresh implementation scenarios in retail, corporate and Islamic banking.

Legacy migrationData validation
04

Local Development & Interfaces

T24 local developments, interface builds and channel integration, delivered by T24 technical consultants with jBase and AA expertise.

jBaseAAInterfaces
05

Application Support & Offshore

Ongoing T24 application support including COB management, first-level incident response, DevOps and release management and flexible offshore engagement models.

COB supportDevOpsOffshore
06

GL & Consulting

GL setup, analysis, reconciliation and correction, alongside technical and business consulting and structured T24 training programmes.

GL setupTrainingConsulting
About

Banking technology since 2018

iGen Services and Solutions is a specialist IT company serving the banking and financial services industry, registered in Singapore since 2018, whose T24 consulting work has taken it to banks in the Middle East, Africa, Asia and Europe.

Our consultants bring more than a decade of hands-on Temenos T24 experience. T24Connect, first released in 2024 and now in its third release, is the product that experience produced: a read-only, certified way to get T24 data into the hands of the people who need it.

T24Connect — certified extraction and assurance
Temenos T24 implementations and upgrades
T24 data migration and local development
Application support and offshore services
GL setup, analysis and reconciliation
🏦Commercial banks
☪️Islamic banks
🏛️Investment banks
💳Retail and digital
🌐Regional MFIs
📊Central banks
GCC
and Africa — the first markets for T24Connect
Day 1
your T24 release read from your own dictionary and confirmed in the pilot
2
database providers: Oracle and SQL Server (TAFJ)
10+
years of Temenos T24 consulting experience

A certified morning
on your own T24.

A 25-minute demonstration on a Temenos model bank — this morning's certificate, what changed overnight, the read-only proof, a fresh install from the box — then a free 15-day pilot on your copy.

Email us
📧support@igenss.com
🌐t24connect.com
📍Singapore · India