Quick answer
A core banking system is the back-end software that processes a bank's daily transactions and updates its accounts and records: deposits, withdrawals, loans, customer details and the accounting ledger[1]. The app you see is only a window onto it; the core is the bank's official record of who owns what.
Key points
- The core is the bank's system of record: it holds the official balances for every account and loan.
- Many banks run cores up to 40 years old on mainframe hardware written in outdated programming languages.
- Most smaller US banks outsource their core to a few large providers rather than building it themselves.
- Instant payments need cores that can post transactions in real time, 24 hours a day, every day.
- Replacing a core is risky and expensive; a failed migration can disrupt banking for a large share of a bank's customers, as at TSB in 2018.
On this page
#What does a core banking system actually do?
The Federal Reserve Bank of Kansas City defines the core banking system as the back-end information technology system that processes daily banking transactions and updates financial accounts and records[1]. Its main jobs are account management, customer management, deposit and withdrawal processing, loan processing and finance and accounting[1]. Think of it as the bank's master spreadsheet, except it must be correct to the penny, never lose data and handle millions of updates.
| Function | What it means in plain words |
|---|---|
| Account management | Opening and closing accounts, keeping balances and account settings |
| Customer management | Storing who each customer is and which accounts they hold |
| Deposits and withdrawals | Posting money in and out of accounts |
| Loan processing | Recording loans, repayments and interest owed |
| Finance and accounting | Keeping the general ledger that the bank's financial statements are built from |
Functions as listed by the Federal Reserve Bank of Kansas City[1].
Everything else, such as the mobile app, the card system or the link to a payment network, has to talk to the core to find out a balance or to record a transaction. When a bank lets other companies plug into it through banking APIs, those APIs are ultimately reading from or writing to the core.
Worked example
Worked example: two jobs a core does every day
First, a transfer of £50 from customer A to customer B at the same bank is recorded as two equal and opposite entries, so the bank's books still balance. Second, the core calculates interest daily. Here a savings balance of £10,000 earns a hypothetical 3% a year, calculated on a 365-day basis. Figures were computed with code.
- Customer A's account
- −£50.00
- Customer B's account
- +£50.00
- Net change in the bank's total deposits
- £0.00
- Daily interest: £10,000 × 3% ÷ 365
- £0.82
- Interest over 30 days at that rate (before rounding each day)
- £24.66
#Why do so many banks still run old cores?
Because the core works, holds decades of data and is connected to everything. The Kansas City Fed notes that many institutions operate systems up to 40 years old that run on mainframe hardware coded in outdated programming languages, with a monolithic design in which the parts are tightly intertwined[1]. Changing one part can break another, so banks are cautious.
Supervisors see the risk. An ECB Supervisory Board member said in July 2025 that many banks continue to use legacy systems that, while functional, can pose inherent risks to operational resilience[2]. In the EU, the Digital Operational Resilience Act (DORA) aims to achieve a high common level of digital operational resilience across European financial firms[2]; see DORA explained.
#Who builds core banking systems?
Some banks build their own core. Most smaller US banks and credit unions outsource to core service providers, according to the Kansas City Fed[1]. The market is concentrated: survey data cited by the Kansas City Fed show that the three biggest providers served more than 70 percent of banks surveyed in 2022 and nearly half of credit unions surveyed in 2020[3]. Concentration matters because a problem at one provider can affect many banks at once, which is one reason supervisors focus on third-party risk.
#Why do instant payments put pressure on the core?
Traditional systems such as wires and ACH run during set hours, and the receiving bank can delay posting money to customer accounts until later in the day[4]. Many older cores were built around overnight batch processing: they collect the day's transactions and update balances in one big run. Instant payments are different. The Kansas City Fed explains that they require fully automated integration with the bank's core and the ability to process payments in real time, 24 hours a day, 365 days a year[4]. Learn more in instant payments explained.
#How do banks modernise a core?
The Kansas City Fed describes three broad options[1]. Each trades speed and cost against risk.
Three ways to modernise a core banking system
Full replacement
Swap the whole core in one programme. It brings the biggest change but carries the highest risk and cost.
Component-based replacement
Replace one piece at a time, such as deposits first and loans later, while the old core keeps running.
Wrap and augment
Add a next-generation core that plugs into the legacy core through APIs, so new products run on new technology while old accounts stay put.
None of these is quick. Full core conversions can take several years and cost millions, if not hundreds of millions, of dollars[1]. That cost is one reason young neobanks, which start with a modern core, can launch features quickly, while large banks move more slowly.
#What happens when a core migration goes wrong?
The UK bank TSB is the textbook case. In April 2018 it moved its customer and corporate data onto a new IT platform. The data migrated, but the platform immediately had technical failures; all its branches and a significant proportion of its 5.2 million customers were affected, and it took until December 2018 to return to business as usual[5]. In 2022 the FCA and the PRA fined TSB a total of £48.65 million, finding it failed to organise and control the migration and to manage the risks of its outsourcing to a critical third-party supplier[5]. TSB had paid £32.7 million in redress to customers[5].
Common beginner mistakes about core banking
Confusing the app with the bank's system
A slick app can sit on a decades-old core. The app is only the front end.
Assuming 'real time' everywhere
An app may show a payment instantly while the core posts it later in a batch, which is why pending items appear.
Thinking a new core is a simple software update
Core conversions can take years and cost hundreds of millions of dollars[1].
Ignoring the supplier
Many banks rely on a few external core providers, so a provider's problem can become a bank's problem.
The bottom line
The core banking system is the quiet centre of every bank: the official ledger that every app, card and payment depends on. Old cores are reliable but rigid, which slows instant payments and new products, and replacing them is costly and risky. Understanding the core explains why banks change slowly and why a failed upgrade can affect a large share of a bank's customers at once.
Frequently asked questions
Is the core banking system the same as the banking app?
No. The app is the customer-facing layer. The core is the back-end system that holds official balances and records[1].
What programming language do core banking systems use?
It varies. The Kansas City Fed notes that many older cores are coded in outdated programming languages on mainframe hardware[1]; next-generation cores are designed to support a real-time customer experience.
Do neobanks have their own core banking system?
Some build their own and others license one from a provider. Banks that rely on a partner bank may not have a core of their own at all.
Why does my bank app go offline for maintenance at night?
Many older cores run overnight batch jobs and planned upgrades, during which some services pause. Systems built for instant payments must run 24/7[4].
Sources
- Core Banking Systems and Options for Modernization (Payments System Research Briefing) — Federal Reserve Bank of Kansas City, 2024 Primary
- Information and Communications Technology resilience and reliability (speech by Patrick Montagner) — European Central Bank — Banking Supervision, 2025 Primary
- Market Structure of Core Banking Services Providers (Payments System Research Briefing) — Federal Reserve Bank of Kansas City, 2024 Primary
- The Role of Core Banking Services Providers in Facilitating Instant Payments — Federal Reserve Bank of Kansas City, 2024 Primary
- TSB fined £48.65m for operational resilience failings — Financial Conduct Authority, 2022 Primary
_mainframe_computer_system_at_Living_Computer_Museum_(strongly_edited_image).jpg){kind=link}
.jpg){kind=link}
.jpg){kind=link}
