From legacy T24 environments to modern Transact deployments, we provide support, upgrades and project delivery for banks running the world's most widely deployed Core Banking platform — without the consulting firm overhead.
Temenos T24, now branded Temenos Transact, is the world's most widely deployed Core Banking system — used by over 3,000 financial institutions across retail, private, commercial and microfinance banking. Its power is in its breadth: thousands of pre-built components covering every aspect of banking operations.
That breadth creates complexity. T24 implementations are rarely vanilla: banks accumulate custom routines, bespoke interfaces, local component modifications and non-standard configurations over years. Managing that complexity — safely, through upgrades and operational changes — requires specialists who have actually done it before.
Onirem's Temenos T24 consultants have worked inside real T24 environments, not just in training labs. We understand the difference between what the documentation says and what actually happens in production.
Retail and private banks using T24 or Transact as their Core, often running a version that is several releases behind. They need a reliable partner for day-to-day Temenos T24 support, planned upgrades or specific project delivery — without committing to a large consulting firm.
The biggest challenge in most T24 environments is not the platform itself — it's the years of customisation that have accumulated and which nobody has fully documented. We work with what you have, not with a clean-sheet assumption.
Practical delivery from T24 consultants who have worked with Temenos T24 in live banking environments — across retail, private and microfinance institutions.
Ongoing support for T24 environments — incident resolution, change requests, parameter queries and first-line triage. Available as a retainer for banks that need reliable external T24 coverage without a full internal team.
T24 upgrades are high-risk because of accumulated custom code. We assess your current environment, identify customisations at risk, plan the upgrade path and execute it — including regression testing and post-upgrade stabilisation.
Migration of account, customer and transaction data between T24 environments or from legacy systems to T24/Transact. Includes data mapping, cleansing routines, reconciliation and parallel-run validation.
TAFC, TAFJ and Java-based customisation for T24/Transact. We develop or review custom routines, local components and enquiry definitions — with proper documentation so your team understands what was built.
Independent functional and regression testing for T24 environments. We design test plans, execute test cycles and document outcomes — particularly valuable before go-live or after a major upgrade where vendor-supplied testing is insufficient.
Practical T24 training for operations and IT staff, built around your bank's actual environment. We don't run generic Temenos courses — we train your people on your system, your products and your workflows.
Temenos rebranded T24 as Transact as part of its cloud-first strategy. Functionally, Transact is an evolution of T24 — but the transition involves a different deployment model, a shift toward SaaS and a different upgrade cadence.
Many banks still run legacy T24 environments — R14, R15, R17 or R19 — on on-premise infrastructure. These environments require different support skills than a modern Transact cloud deployment. Our Temenos T24 consultants work across both.
We review your T24 environment: version, customisations, integrations, deployment model and outstanding issues. This gives us an honest picture of complexity before we commit to a scope or timeline.
We produce a written proposal with a defined scope, timeline and fee. For T24 upgrade projects in particular, we flag the known risk areas upfront — not as justification for scope creep later.
We work alongside your internal IT and operations staff — not instead of them. Knowledge transfer is built into every engagement, so your team understands what changed and how to manage it going forward.
Every engagement ends with a documented handover. Parametrisation changes, custom code modifications, test results and known limitations — all recorded and explained to your team.
Tell us about your environment — a 30-minute call is usually enough to understand whether we can help and how.