Temenos upgrades that start with your local developments.
We upgrade Temenos Core Banking, the product long known as Transact and before that T24. That means reviewing local developments, planning moves to Temenos SaaS on Azure or AWS, building integrations and staffing Temenos developers when the bank's bench is thin.
Copilot for Workbench, Copilot for Core, FCM AI Agent
release watch
Embedded AI capabilities07 May 2026
New CEO03 Dec 2025
connects with
in short·15-second read
We work on Temenos Core Banking, which Temenos now markets as Temenos Core and many banks still call Transact or T24.
We plan upgrades, inventory local developments and cut them back, prepare moves to Temenos SaaS on Microsoft Azure or AWS, and build integrations to payments, digital channels and data platforms. We also supply Temenos developers and analysts on contract or permanent terms.
you probably need this if
The upgrade is overdue and nobody has counted the local developments.
Every release breaks an interface to payments or digital banking.
The board wants a view on Temenos SaaS by next quarter.
We pieced these together from Temenos Core Banking situations that come up a lot. They're patterns. You won't find a specific client in them.
case file 01
Hundreds of local developments and an upgrade years overdue
composite · not a client story
Beforethe situation
A bank runs an old Temenos release with hundreds of local developments, several duplicating features now in the base product. The upgrade has been deferred twice and support costs keep rising.
What we dothe work
We inventory the local developments and hold each one up against what the target release already does. Duplicates get marked for retirement, everything else for rework. A regression pack built from close-of-business runs is the baseline.
Afterwhere you end up
Fewer local developments go into the upgrade, and the ones that remain are documented.
case file 02
Screening alert backlog and the FCM AI Agent on the table
composite · not a client story
Beforethe situation
Watchlist screening throws up more alerts than compliance can clear, and the team is evaluating Temenos's FCM AI Agent. Before relying on it, compliance wants evidence.
What we dothe work
We take a sample of past alerts that already have analyst decisions, run them through the agent in a test environment and compare. Senior analysts look at every disagreement, and review rules get written from what they find.
Afterwhere you end up
When compliance decides on the agent, it has a comparison with its own past decisions to go on.
We don't start a step until the last one has produced something you can check.
step 01
Local development inventory
Every local development, interface and report goes on a list, marked keep, replace with base product, or retire against the target release.
step 02
Regression baseline
We build a regression pack out of your products, accounts and close-of-business runs. Run it on the current release and you have a baseline.
step 03
Upgrade or SaaS plan
The inventory and baseline become an upgrade or SaaS plan with code changes, interface work and testing durations.
step 04
Cut-over and handover
We stay for cut-over and the close-of-business checks that follow. You keep the runbooks, the regression pack and documentation for every piece of local code.
ai on temenos core banking
Where AI fits on Temenos Core Banking, and where it needs guardrails.
Temenos lists four AI products. FCM AI Agent handles watchlist screening, Copilot for Core is for product teams, Copilot for Workbench is for developers and AI Studio covers governed models. Copilot for Workbench is the one that affects how a Transact development team works, because it generates code extensions and experts approve every change.
AI agentasks for data or an action
Scoped identityonly the access it needs
MCP serverthe one door into the platform
Logged, approveda person signs off on writes
Temenos Core Bankingdoes the work
Temenos doesn't currently publish an official MCP server, so agents call Transact through Temenos APIs. Give them a dedicated service user, read-only by default, and log every call. Account, payment and customer record changes need a human to approve.
Temenos FCM AI Agent
It's an AI compliance engine. It reviews watchlist screening alerts to cut false positives and explains how it reached each decision. Before a compliance team relies on it, we help them compare its results with what analysts decided on past alerts.
Copilot for Workbench
Temenos Core gets a conversational assistant. It answers questions and surfaces insights, and it generates code extensions that experts review before they go in. Our work is fitting it into the code review and testing you already run, and into your release process.
Copilot for Core and AI Studio
Copilot for Core is for product teams designing banking products and looking for customer insights. AI Studio is where you build and explain AI models, and where you govern and deploy them. For each, we confirm licensing and plan the data access.
AI around Transact upgrades
AI can document local developments, map each one to the target release and draft regression tests. No code changes until an engineer has checked every mapping.
architecture
Where Temenos Core sits in a retail bank
Digital channels and branch systems are the way in. Temenos Core holds the accounts and runs close of business, and its outputs go to payments, the ledger and reporting.
use cases
Typical Temenos Core Banking projects
The work teams usually bring us, and the platforms Temenos Core Banking has to talk to while we do it.
TEM-01An upgrade is overdue and local developments block it
common request
TEM-02You're weighing a move from on-premises Temenos to Temenos SaaS
common request
TEM-03Interfaces to payments and digital channels break on each release
common request
TEM-04Your Temenos knowledge sits with a few long-serving developers
common request
TEM-05Compliance wants to test the FCM AI Agent on screening alerts
common request
What a Temenos Core Banking engagement leaves behind
These are working documents, written against your configuration, so your team can run them without us.
inventory01
Local development inventory marked keep, replace or retire
yours to keep
tests02
Regression pack from your products, accounts and close-of-business runs
yours to keep
tests03
Upgrade or SaaS plan with code, interface and testing effort
yours to keep
inventory04
Interface catalogue with owner and failure handling per feed
yours to keep
tests05
Review rules and test plan for Temenos AI features you license
yours to keep
talent and delivery · temenos core banking
Certified engineers, wherever you need them.
Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.
Onsite
Engineers at your sites in the US
Nearshore
Overlapping hours with US teams
Offshore
Overnight progress on your backlog
All time zones
Coverage handed over across time zones
24-hour coverage · US Central time
OnsiteUS business hours
Nearshoreoverlapping US hours
Offshoreovernight progress
Combinedhandover, not hand-off
00:0006:0012:0018:0000:00
roles we staff
Temenos Core (Transact) developer
Temenos business analyst (retail or lending)
Temenos integration developer
Temenos upgrade and environment lead
Temenos regression test analyst
due diligence · temenos core banking
Questions to ask any partner, including us.
Put these to anyone bidding on your Temenos Core Banking work. The ones who've done it answer differently from the ones who've read about it.
Q1
How many local developments do we carry, and which duplicate the base product?
Local developments set the cost of every Temenos upgrade. Retiring duplicates shortens this one and the next.
Q2
What does the bank still own on Temenos SaaS?
Temenos runs the platform on Azure or AWS. Configuration, testing and interfaces are still the bank's job.
Q3
How will close-of-business be tested after the upgrade?
COB failures are what customers notice first. A regression baseline on today's COB runs catches them in test.
Q4
How do you vet Temenos developers when certification names aren't public?
Temenos trains people through its Learning Community, but there are no named certificates a buyer can check. Screening has to test which modules and releases someone has really worked on.
Q5
How will you prove the FCM AI Agent agrees with our analysts?
Compliance won't lean on AI for screening without evidence. Comparing the agent with past decisions is that evidence.
01Is Temenos Transact still the product name?
Temenos's core banking page now uses the name Temenos Core, under a Core Banking heading. T24 was renamed Transact earlier, and many banks still use both older names. We use whichever name your contracts and documents use.
02How long does a Temenos upgrade take?
It depends on how far apart the releases are, how many local developments you carry and how long a full regression run takes. We count local developments first, because they usually set the timeline.
03What changes on Temenos SaaS?
Temenos runs the platform on Azure or AWS and handles updates. The bank still owns product configuration, testing, interfaces and data access decisions, and those have to fit Temenos's release rhythm.
04Do your people hold Temenos certifications?
Temenos trains clients, partners and independents through the Temenos Learning Community, but it doesn't publish its certification names. So we screen people by the modules and releases they've actually worked on.
05Can you help us use Temenos AI features?
Yes. The licence comes first, so we confirm what it includes. Then data access and review rules, like comparing FCM AI Agent results with past analyst decisions before anyone relies on it.
services
Related services
Projects on Temenos Core Banking usually end up touching one of these, so they're worth a look.
