Traditionally, core banking solutions were designed to serve the requirements of an efficient OLTP (on line transaction processing) system. Core banking applications in India are currently more than 10 years old. The period saw a great amount of data churning. The inherited dirty data got cleansed or made irrelevant vis-à-vis the data retention requirements of IT act.
The eco system was evolving, in the meanwhile. The telecommunication networks got denser and smart phones became ubiquitous. Payment systems in India, developed a new face under the aegis of National Payment Corporation of India. Aadhaar by UIDAI gave a momentum for remote branchless banking. More fintech startups and established players entered the telecom and mobile space. Mobile banking, door step banking and branchless banking did not just remain mere buzz words, but became a reality. The core banking solutions in vogue, required either to be replaced or tweaked to demands of the changing delivery options to customers. Moreover, lots of satellite standalone systems were paddled as quick fixes for these new age requirements, posing a challenge when it comes to integration with core banking solutions. The time is now ripe for redefining the traditional core banking solution.
The typical shelf life of a core banking software is set to reduce in the future, but so are the implementation woes with Software as a Service (SaaS) availability. National Bank for Agriculture and Rural Development (NABARD) has successfully led one of the biggest IT transformations in the Indian banking industry by enabling banking operations of 201 state and district co-operative banks move to a single cloud-based core banking solution. This has enabled rural customers to access basic banking facilities such any branch banking, SMS notifications, NEFT, RTGS and access to ATMs.
However just the availability of core banking software on the cloud would be the equivalent of having old wine in a new bottle. What we need today is a new age software that is truly CBS
Maker / checker is the fundamental requirement that must be satisfied in a financial transaction. All the core banking solutions have this feature. The feature is random and is not supported by a workflow. Typical core banking solution provides a maker / checker workflow that is:
A true CBS system should be multilingual to support the vision of inclusive banking. The following features are desirable
Single sign on features
The core banking software of the future should support single sign on to applications that are not supported by core banking software
A good branchless banking solution should address major financial services; savings, loans, transactions, and insurance. It should support
Share accounting and payroll services (Credit unions and co-operative banks)
The solution should support the following features -
Apart from the above features, Next Generation Core Banking Solution has to be developed as a "mobile first" application with cutting edge security which could be based on blockchain technologies.