Market scan guide · Core banking

How to run a core banking market scan

A core banking scan is the longest and most consequential a deposit-taking institution runs: the system holds every account and ledger, the migration takes years and the contract a decade. The scan has to settle, before any RFP, which vendors run institutions of your size under your regulator, and which of them you could actually get to.

Figures from the Vederca registry as of 2026-10-24: 75 core banking vendors, 215 products, 27 countries.

The core banking landscape in numbers

Core banking software for financial institutions: the Vederca market map
The core banking market map: every vendor's own mark, by named customers then name, drawn from the registry. Download the map (PNG, or as SVG).

The registry lists 75 core banking vendors with 215 products, headquartered in 27 countries. 55 name at least one financial institution as a customer. 0 of the products mention an AI capability in their own text (0%). 11 mention a cloud native or SaaS delivery.

Core banking vendors by headquarters country
United States: 20United States20Australia: 8Australia8India: 8India8United Kingdom: 6United Kingdom6Switzerland: 4Switzerland4Brazil: 3Brazil3Netherlands: 3Netherlands3Finland: 2Finland2France: 2France2Japan: 2Japan2
Core banking vendors by headquarters country: the figures as a table
ItemValue
United States20
Australia8
India8
United Kingdom6
Switzerland4
Brazil3
Netherlands3
Finland2
France2
Japan2
Capabilities most often mentioned by core banking products
Cloud native: 11, 0 confirmedCloud native11Deposits: 7, 0 confirmedDeposits7Cards: 3, 0 confirmedCards3Product config: 3, 0 confirmedProduct config3Term deposits: 3, 0 confirmedTerm deposits3Business: 2, 0 confirmedBusiness2General ledger: 2, 0 confirmedGeneral ledger2Migration: 2, 0 confirmedMigration2Becs bpay: 1, 0 confirmedBecs bpay1Cdr: 1, 0 confirmedCdr1Lending: 1, 0 confirmedLending1Real time: 1, 0 confirmedReal time1
Capabilities most often mentioned by core banking products: the figures as a table
ItemValue
Cloud native 0 confirmed11
Deposits 0 confirmed7
Cards 0 confirmed3
Product config 0 confirmed3
Term deposits 0 confirmed3
Business 0 confirmed2
General ledger 0 confirmed2
Migration 0 confirmed2
Becs bpay 0 confirmed1
Cdr 0 confirmed1
Lending 0 confirmed1
Real time 0 confirmed1
Core banking vendors founded, by year
2017: 3320172018: 1120182019: 1120192020: 020202021: 1120212022: 2220222023: 020232024: 020242025: 020252026: 02026
Core banking vendors founded, by year: the figures as a table
YearCount
20173
20181
20191
20200
20211
20222
20230
20240
20250
20260

The largest by named customers

VendorHQ countryNamed customers
DXC TechnologyUnited States20
ERISwitzerland20
TopazBrazil18
DigizooAustralia17
AzentioSingapore14
Netcompany Banking ServicesDenmark14
IBMUnited States13
Treasury PrimeUnited States12

The newest entrants

VendorHQ countryFounded
ConstantinopleAustralia2022
Engine by StarlingUnited Kingdom2022
SAP FioneerGermany2021
TuumEstonia2019
Netcompany Banking ServicesDenmark2018
DXC TechnologyUnited States2017

The full list, with every vendor's flagship product and named customers: Core banking software vendors.

How to evaluate core banking vendors

  1. Fix the scope firstDeposits, lending, payments, cards and the general ledger are one platform at some vendors and four at others. Decide what the core must own and what stays beside it before reading a vendor.
  2. Read deployed customers, not roadmapsA core that runs at an institution of your size, in your country, under your regulator, is evidence; a planned region or a reference abroad is a question for the RFI.
  3. Test configuration against your productsAsk each vendor to configure two of your real products (an offset home loan, a tiered savings account) in a scripted demonstration, with the fee and interest rules.
  4. Price the migration, not the licenceThe subscription is the smaller number. Ask for the implementation plan, the data conversion approach and two comparable migrations with their elapsed time.
  5. Check the operating modelWho runs it: the vendor as a managed service, the institution, or a partner. Each changes the operational resilience evidence your regulator will ask for.

The method for the scan as a whole, longlist to shortlist, is on the market scan page; the report template gives the headings.

The requirements that separate them

Must-haves in most scans of this category: the register's gates. Each needs evidence named beside it.

  • Product configuration by the institution without vendor code changes
  • Real-time transaction processing and a real-time ledger
  • Local payments rails and open banking obligations built in, not integrated later
  • Hosting in the institution's country, with the sub-contractors disclosed
  • A documented migration method with named prior conversions
  • Business continuity and exit terms that meet the prudential outsourcing standard

The rules procurement teams ask vendors about

By country, the rules specific to core banking procurements. Vederca certifies nobody against these: they say what evidence to ask for.

Australia

  • AML/CTF Act (AUSTRAC): Reporting entities keep customer identification, monitoring and AUSTRAC reporting in step with the Act and Rules.
  • APRA reporting (APRA Connect): Returns are prepared to APRA's reporting standards and lodged through APRA Connect.

United Kingdom

Canada

  • PCMLTFA (FINTRAC): Reporting entities verify identity, keep records and report to FINTRAC under the Act and Regulations.
  • OSFI and Bank of Canada reporting: Returns are prepared to the reporting instructions and lodged through the Regulatory Reporting System.

United States

Go further