
A steering committee approves "replace the corporate banking platform" and asks for a shortlist. Nobody in the room can say which of the seven layers is broken. That is the decision that goes wrong most often: a platform bought to fix a channel problem, or a channel built to hide a trade back-office problem. The question is not which vendor, but which layer you are missing, and whether it should be bought, rented or built.
What changed
2 February 2026 — the counterparty changed legal entity. Apax completed its purchase of Finastra's Treasury & Capital Markets business; Teciem launched with 1,300 specialists and the Kondor, Summit, Opics, Sophis and Arc products. For a bank running Kondor, vendor, roadmap and support now sit in a different company. Procurement should list Finastra and Teciem separately.
2017 — the widest portfolio is a portfolio, not a suite. Finastra, formed from the Misys and D+H merger, sells four separately deployable components — Trade Innovation, Corporate Channels, Loan IQ, Global PAYplus — linked by APIs and a common data model. Buying "Finastra" is four purchases.
September 2026 — the largest local footprint is a core footprint. Temenos states that around 30 domestic banks run its software, against more than 3,000 globally, and the named references are core-banking references. Running the core is not running corporate banking on it.
30 August 2022 — one announced trade reference, four years later. The only announced Surecomp implementation in Vietnam went live on the bank's own infrastructure in Hanoi with a local integrator. A pure-play with 40 years and customers in 80-plus countries still had a single domestic reference after four years.
30 April 2019 — the global standard, not the domestic one. CGI Trade360 was chosen by a global banking group as its worldwide trade platform; no domestic bank has been announced since. That absence reflects commercial model, not quality: it is sold as a multi-year group-wide transformation.
31 July 2026 — the channel moved in-house. A large joint-stock bank launched a corporate digital channel with an integrator under a technology-transfer model in which the bank owns the IP, phased accounts and payments first, then credit, trade finance, collections, FX and investment.
A mature bank runs four to six systems across seven layers, and no platform here is best at all seven. Forcing one product to cover everything raises customisation cost and hands the roadmap to the vendor.
The decision framework
Score seven criteria before any demonstration. The weights assume an existing core the bank is not replacing this year.
| # | Criterion | Weight | What "high" looks like |
|---|---|---|---|
| 1 | Depth in the layer you are missing | 20% | Import L/C with amendment, conditional guarantee, collection and one SCF deal end to end, unmodified |
| 2 | Integration surface to core and payments | 20% | Tested against the real core and payment rails, not mock-ups |
| 3 | Local delivery capacity | 15% | Two reference customers of similar size and region, plus a named partner with trade operations skills |
| 4 | Ownership and roadmap risk | 10% | No ownership change in 24 months; ISO 20022, CBPR+ and MT798 roadmap in writing |
| 5 | Operating model and control | 10% | Multi-level approval, branch authorisation and limits work as configured, not patched |
| 6 | Three-year cost including change requests | 15% | Cost tracks the layers you use; change request rate bounded in the contract |
| 7 | Exit and data | 10% | Data transfer, customisation ownership and termination terms agreed before signature |
Criterion 3 is the one committees discount and regret: a vendor with one local implementation has one delivery model, and it may not be yours.
Options and trade-offs
| Option | Strength | Risk | Three-year cost shape |
|---|---|---|---|
| Buy a suite — one vendor across several layers | Single contract, one data model | Widest coverage lands on layers you may already own; customisation grows where depth is thin | Highest licence, lowest integration; rises with every module |
| Extend — keep the core, add a channel and trade workflow layer | Preserves the core; pairs a core platform with a documentary trade pure-play | Two vendors, two roadmaps, and the integration becomes yours | Moderate licence, higher integration and testing; most predictable if scope is fixed |
| Build — technology transfer, bank owns the IP, phased by product | Roadmap control where the channel is the product | Needs internal product and engineering capacity plus a conversion budget | Low licence, highest people cost in years one and two, lowest later |
The pairing that recurs here is a core platform plus a documentary trade specialist. Not elegant, but it matches where each product is deep.
The numbers
The research carries no price for any of the four, and its one comparative statement is uncomfortable: cost is not proportional to coverage. The most expensive model covers only part of the portfolio, because you buy a multi-country operating model, not feature count.
What can be quantified is scope:
- Seven layers, four to six systems in a mature bank. Below four, ask which layer is improvised.
- Around 30 domestic banks on the dominant core platform, against 3,000-plus globally. Installed base buys skills, not depth.
- One announced domestic trade reference after four years for the pure-play; one global group reference for the SaaS platform, with no domestic bank announced.
- Three to five real transactions across four product types is the proof-of-concept scope that separates products; two reference interviews is the cheapest due diligence available.
A three-year range built on licence alone misleads. My estimate: integration, data mapping and retraining outweigh licence in every option except the suite, where licence and customisation compete.
What I would do in 30 / 60 / 90 days
First 30 days — name the missing layer. Map every corporate banking capability to the seven layers and mark the system serving it today. Interview the trade operations head, not only the CIO. Collect the public lifecycle and ownership facts on every incumbent, including the February 2026 spin-off. Write down the decision you are actually making.
Next 30 days — test transactions, not features. Run three to five real deals: an import L/C with an amendment, a conditional guarantee, a documentary collection and one supply chain finance transaction. Test multi-level approval, branch authorisation and limits. Test integration against the live core. Require the business demo in Vietnamese, for the business team.
Final 30 days — structure the deal. Separate the Finastra and Teciem lots. Put data transfer, customisation IP and termination on the table before pricing. Phase the channel with accounts and payments first. Take two reference calls and write the architecture decision record, including what you deliberately did not replace.
What I would not do
- I would not buy a suite to fix a layer I already own. That is how a bank pays twice for the same capability and customises the second one.
- I would not put Finastra and Teciem into one tender. Different companies, different roadmaps, different support commitments since February 2026.
- I would not accept a demonstration as integration evidence. A mock-up proves the vendor's demo environment works.
- I would not sign a multi-year programme without data transfer, customisation ownership and termination terms. Those three clauses set the price of leaving.
For the non-technical sponsor
Corporate banking is seven capabilities, not one product. Before approving a replacement, ask which capability is failing, which systems serve it today, and whether the fix is a purchase, an extension of what you own, or a build. In my experience the cheapest answer is the narrowest one, and the licence is rarely the largest line.
Sources
- Finastra — lending and corporate banking
- Finastra — trade and supply chain finance
- Finastra — Trade Innovation
- Teciem — launch announcement (2 February 2026)
- Temenos — corporate and commercial banking
- Temenos — core for corporate and commercial
- Surecomp — back-office trade finance
- CGI — CGI Trade360
- VTV — core banking in Vietnam, around 30 banks (9 September 2026)
Personal views. Client and employer details are anonymised. Figures are third-party estimates, not vendor quotes, and are dated November 2026.
Comments
Join the discussionNo comments yet. Be the first to comment.




