We work best when there is a specific challenge to solve — or a gap in expertise to fill. Here are the most common situations that bring banks to Onirem, with detail on how we approach each one as your Core Banking consultant.
Your bank runs OLYMPIC Banking System — it has been the Core for years. But the internal team doesn't have a dedicated OLYMPIC specialist. When something breaks, or when the business wants a change, the IT team is out of their depth. The bank either accepts delays or pays a consultant every time for an expensive intervention.
We become your bank's external OLYMPIC Banking System support team on a retainer basis. This means a predictable monthly engagement with a defined scope of coverage — incident response, change requests, parametrisation updates, user queries and small-scale module work.
We agree a scope and a monthly retainer fee. Your team contacts us directly — email or phone — and we respond within the agreed SLA. There are no intermediaries and no account managers to route around. You speak to the OLYMPIC Banking System specialist who actually knows the system.
Items outside the retainer scope are handled as small fixed-fee additions. Nothing is left ambiguous — we document what is and isn't included at the outset.
Typical client: a regional bank with 3–15 branches, 5–50 staff using OLYMPIC daily, no dedicated internal Core Banking specialist. Often in a market where local OLYMPIC expertise is scarce.
Your bank has decided to move to OLYMPIC Banking System from a legacy Core — an ageing in-house system, an end-of-life platform or a system the bank has outgrown. The OLYMPIC vendor has been selected. Now the real work begins: data migration, configuration, testing and cutover. Most banks underestimate this phase significantly.
We manage the functional and technical complexity of the OLYMPIC Banking migration, working alongside your internal team and the OLYMPIC vendor. Our role is to bridge the gap between the vendor's standard implementation approach and your bank's specific operational requirements.
Data migration to a new Core Banking system is where most projects run into trouble. Legacy systems often have data quality issues that were invisible before migration. OLYMPIC's data model has specific requirements. The reconciliation between old and new must be exhaustive before cutover.
We have seen migrations fail — or go significantly over budget — when these phases are underestimated. We don't underestimate them.
Typical timeline: 6–18 months depending on the size of the bank and complexity of the product portfolio. We work alongside your IT team and the OLYMPIC vendor throughout.
Your bank is running a T24 version that is several releases behind — R14, R15 or R17 in environments that are now on R22 or Transact. Temenos is withdrawing support for old versions. The bank needs to upgrade, but nobody internally has managed a major T24 upgrade before. The environment has years of custom code and local modifications.
We plan and execute the Temenos T24 upgrade, with specific attention to the customisations that are the primary upgrade risk. Our approach is methodical:
T24 upgrades fail when custom code is treated as an afterthought. Banks accumulate hundreds of local routines, TAFC modifications and bespoke enquiries over years of operation. In a version upgrade, any of these can break — silently or noisily. Our first step in any T24 upgrade engagement is a full customisation audit, because you cannot manage a risk you have not identified.
Typical challenge: a T24 environment with 200–500 custom routines, an upgrade spanning 4–8 major versions, and a bank that has never done this before. We have.
Your bank wants to launch a new product or activate a new OLYMPIC module — trade finance, loans with complex structures, multicurrency accounts, or a new e-banking feature. The business has signed off. The vendor has confirmed it is possible. But your internal team doesn't have the OLYMPIC Banking System expertise to configure and test it safely.
We scope, configure, test and hand over the new module — working within your OLYMPIC environment and alongside your team. The process is defined up front so there are no surprises on timeline or cost:
OLYMPIC's modules are interconnected. A new loan module affects the general ledger, interest accrual, reporting and potentially the e-banking front-end. Activating it without understanding those dependencies creates inconsistencies that are expensive to unpick later. We understand the dependencies.
Typical timeline: 4–12 weeks depending on module complexity. Fixed-fee engagement with a defined scope agreed before we start.
Your bank is about to go live on a new Core Banking system — or a major new version — and the implementation vendor's testing report says everything is fine. But you have seen enough to know that vendor-supplied testing is not always independent. You want a second set of eyes on the system before it goes live.
We design and execute an independent functional and regression test programme, focused on the banking processes that matter most to your institution. We don't just follow the vendor's test scripts — we design scenarios based on how your bank actually operates:
The implementation vendor should not be the primary tester of their own work. This is not a criticism of vendors — it is a structural conflict of interest. Their incentive is to declare the system ready. Our incentive is to find what would break in production before it gets there.
Ideal for: any Core Banking go-live where independent QA has not been built into the project. Also used for major releases into production in live environments.
Your bank's operations team uses OLYMPIC Banking System or T24 every day — but institutional knowledge is concentrated in one or two people, or has been lost through staff turnover. New staff receive no structured training. The team is using the system inefficiently, making errors they don't know are errors, or afraid to use functions they don't fully understand.
We design and deliver practical training programmes built around your bank's actual OLYMPIC or T24 configuration — not generic vendor slides that don't match what users see on their screens. Training is hands-on, in your environment, with scenarios drawn from real banking operations:
Training is available in English, French and Spanish — remotely via video conference or on-site at your premises. We have delivered OLYMPIC Banking System and T24 training in both formats across multiple regions.
Available for OLYMPIC Banking System, Temenos T24 / Transact and Triple'A Plus TAP. Can be delivered as a standalone engagement or as part of a broader support or implementation project.
If your situation resembles one of these — or is something we haven't listed — get in touch. We respond within one business day.