Banking & Capital Markets Systems · Chapter 1 of 13
How a bank's stack actually decomposes
Seven layers, and why 'core banking' means three different things depending on who is saying it.
Banking technology is unusually legible once you see the layering, and unusually confusing before that — mostly because one term, core banking, gets used for three different things in the same conversation.
The three meanings, because you will hear all of them
- The ledger. Accounts, balances, posting, the general ledger, interest accrual, end-of-day. This is what a core banking system is, strictly.
- The vendor suite sold around it. Finacle, BaNCS and FLEXCUBE are all sold as families — core, plus payments, trade finance, wealth, treasury, digital engagement as separately licensable modules on a shared customer and account master. A bank can run one vendor's core and a different vendor's wealth module, and several do.
- The whole stack, colloquially. “We're replacing core banking” often means a programme touching channels, origination and reporting as well.
The distinction matters in an interview because the three have completely different job shapes. Ledger work is COBOL-adjacent conservatism, batch windows and reconciliation. Suite-module work is configuration and integration. Programme work is migration and coexistence, which is where most of the actual difficulty lives.
The two layers people conflate at the bottom
Risk and AML is a detection problem. Regulatory reporting is a lineage problem. They sit next to each other on the diagram and get merged in job titles, but transaction monitoring is about finding anomalies in behaviour, while reporting to the regulator is about extracting the same number the same way every time, with a defensible trail back to the ledger. Different skills, different tools, different failure modes — and the second one is much larger than outsiders assume.
A note on how this book is sourced, because it is different from the rest of the site
Every other book here is written from a job-posting corpus. This one is not, and it cannot be — the corpus contains 184 employers and not one of them is a bank. Searching all 4,556 full job descriptions in it returns zero mentions of Finacle, BaNCS, FLEXCUBE, Temenos, Murex, Calypso, OFSAA, Aladdin, SimCorp, UPI, RTGS (Real Time Gross Settlement) or SEBI.
So this book is written from regulator and exchange publications, bank annual reports and disclosures, and dated vendor announcements — and it says out loud, chapter by chapter, which claims are sourced and which are not.
That is not a disclaimer. It is the single most useful thing this book can teach you about the field: a very large amount of what circulates as fact about who runs what is unsourced, and the confident lists online are citing each other rather than a bank.
Check yourself