More articles
All Articles
This article is intended for financial institutions in Israel, including those going through a regulatory licensing process, and addresses a common dilemma: developing a loan and mortgage management system in-house or buying one. We examine the myths around control and flexibility, analyze the real costs and procurement considerations, and present the advantages of ready-made solutions built for local regulation, to support a sound strategic decision.
Financial institutions in Israel, from the large banks to non-bank credit companies, often find themselves at an important crossroads. The core dilemma is whether to build an in-house loan and mortgage management system from scratch, to extend an existing system with new modules or capabilities, or to buy an existing solution from a specialist vendor.
The prevailing view is that in-house development delivers complete control and unlimited flexibility. A closer look at reality, however, shows that the decision is far more complex and is shaped by cost and procurement considerations, timelines and regulatory compliance.
Developing in-house sounds attractive because it promises a precise fit to the organization's unique needs and the potential for full control. On closer inspection, however, the path turns out to be full of hidden challenges.
In-house development projects require an enormous upfront investment of time and resources, from in-depth analysis through recruiting development teams, testing, implementation and ongoing maintenance. The result is long timelines, often stretching over years, and budgets that tend to exceed the original estimate.
Extending an existing system is not as simple as it looks either. Older, heavier systems that were not built from the outset as core credit management systems require extensive code changes every time a product, track or regulatory requirement is added. Each module added this way increases complexity and technical debt, and in many cases the need to replace the system eventually arises.
The risks of in-house development are especially significant. Technology changes quickly, internal teams may struggle to keep up with the scope of requirements and the knowledge involved, and there is a high risk of accumulating technical debt.
For a financial institution, managing credit in Excel spreadsheets or in outdated, non-dedicated systems creates serious legal, regulatory and operational risk. Such situations can lead to critical errors in managing credit portfolios worth tens of millions of shekels.
The regulatory dimension in Israel may be the most critical point of all when it comes to a credit system. A system for granting and managing credit, and especially a loan and mortgage management platform, must meet the strict requirements of the Bank of Israel and the Capital Market, Insurance and Savings Authority.
These requirements include the Fair Credit Law, reporting to the Israel Money Laundering and Terror Financing Prohibition Authority, and ongoing reporting to credit databases. Staying current with frequent regulatory changes, and implementing them quickly and accurately in an in-house system, is a complex and costly task that demands ongoing expertise.
The root of the problem with choosing in-house development lies in three main factors: high upfront and maintenance costs, long and unpredictable timelines, and the sheer complexity of regulatory compliance.
Development costs are not limited to development itself. They also include recruitment, training, information security and continuous quality testing. These factors make the project's costs difficult to predict in advance.
Changing regulatory requirements call for specialized expertise and the ability to respond quickly. Developing in-house means placing that burden on the organization, rather than relying on the accumulated knowledge of a specialist vendor.
A point often overlooked in the in-house development debate is that a core financial system is not a generic software project. It is a specialization in its own right: interest calculations of every type, amortization schedules, indexation mechanisms, the full range of fees, arrears interest, collateral management, early and partial repayments, payment freezes, switching tracks and pledged properties during the life of the loan, and regulatory reporting. Each of these involves hundreds of edge cases that surface only in real operation against live portfolios.
The core business of a lender is lending: underwriting, risk management, customer relationships and growth. Developing a core system in-house effectively means opening a second business alongside it, a full software house with everything that entails: recruiting and retaining developers, knowledge management, information security, quality control, version management and round-the-clock support. This is not something a financial institution can do on the side, alongside its main activity.
This kind of specialization is built through years of real-world operation, and there is no shortcut to it. An organization that chooses to build from scratch starts this learning curve at the very beginning, while the portfolios it manages, its customers and the regulator are already there, expecting a system that works.
Buying an existing solution, by contrast, offers clear advantages. Platforms developed by highly experienced software houses, such as those of CAV Systems, have already been through the development, testing and regulatory compliance stages.
These solutions are designed to serve both the banking and the non-bank sectors and offer comprehensive functionality, including management of collateral, balances, repayments, arrears, payment freezes, multiple tracks and products, and the full credit lifecycle.
For a deeper look at why a non-bank lender needs dedicated software rather than a generic solution, see: Core Banking Software for Non-Bank Lenders.
Buying a ready-made system makes it possible to start operating on shorter timelines, with a budget known in advance. It also avoids many of the risks of building from scratch and allows the organization to focus on its core business.
Avoiding "data migration costs" at a later stage is another significant advantage of an informed choice made up front. Many organizations are forced to replace unsuitable systems after a few years, leading to huge expenses on data migration and process repair.
One of the fundamental differences between developing in-house and buying a ready-made solution is economies of scale. A platform such as CAV Systems' was not developed for a single organization but for a range of financial institutions: banks, insurance companies and licensed credit providers. Every capability one organization required, and every regulatory adaptation made for it, is developed once and becomes available to all the organizations using the system.
The economic implication is clear: the cost of development and maintenance is shared among many institutions rather than falling entirely on one organization. When a regulatory change is announced, it is implemented in the platform within days and reaches all clients, whereas in an in-house project every such change is a separate development task competing for resources in the organization's priority queue.
Behind an established platform stands a business strength that is hard to replicate: dozens of person-years of specification, development, implementation and support, accumulated over years of work with financial institutions. The CAV Mortgages system has been in active use at financial institutions in Israel for about three decades, since 1997, and has been implemented and running at institutional organizations for more than 25 years. Today it serves organizations that manage more than NIS 40 billion and serve tens of thousands of customers in the financial sector.
Organizations that have chosen the system include Bank of Jerusalem, Clal Insurance, Harel Insurance, The Phoenix and Mimun Yashir.
The practical implication is simple: an organization that buys an existing solution builds on a system that works, one that has been tested and is running in production at large clients. In a sense, serious organizations have already carried out comprehensive QA on the system on its behalf: interest calculations, amortization schedules, indexation, fees and exceptional scenarios have been tested again and again against live portfolios and strict regulatory requirements. A system developed in-house will encounter these edge cases for the first time precisely when it is already managing real portfolios of real customers.
Non-bank credit providers going through a regulatory licensing process often face the same dilemma: build an in-house system in the belief that it will provide complete control, or buy an existing solution. A close review of the regulatory requirements, including anti-money laundering and credit database reporting, usually reveals the extensive work involved in developing from scratch.
An informed decision process includes an honest assessment of timelines, budget and internal resources against those of a ready-made solution. For most organizations, a cloud solution built for Israeli regulation enables market entry on a shorter and more predictable timeline, with a budget known in advance and without the risks of building in-house. This allows the organization to focus on its core business rather than on building technology infrastructure from scratch.
Deciding between developing in-house and buying requires careful analysis. First, the organization needs a clear and unambiguous definition of its needs and of the regulatory requirements the system must meet.
Second, it is advisable to carry out a comprehensive Total Cost of Ownership (TCO) analysis. This analysis should weigh not only the initial development costs but also the costs of maintenance, upgrades, regulatory adaptations, information security and risk management over the years.
Finally, the organization should assess the timelines and internal resources available to it, and compare them with the availability and implementation speed of ready-made solutions developed by specialist vendors in the field.
A financial institution that wants to minimize risk, shorten timelines and stay focused on its core business will usually find that buying a dedicated loan and mortgage management system from an experienced vendor offers a significant strategic advantage.
Solutions such as those offered by CAV Systems, for example the CAV Mortgages platform, provide a holistic answer to all market requirements. They are fully adapted to Israeli regulation and allow the financial institution to focus on business growth.
CAV Systems offers credit solutions backed by about three decades of experience in Israel's financial sector, delivered on AWS cloud infrastructure with a flexible SaaS model that meets the changing needs of the local market. The right choice affects the organization's stability, efficiency and profitability for many years.
The dilemma between developing in-house and buying a loan and mortgage management system is not a simple one, but a thorough analysis reveals the significant advantages of ready-made solutions. A core financial system is a specialization, and a platform built for many institutions, tested and running at large clients for about three decades, brings economies of scale and accumulated experience that are hard to replicate through in-house development. These solutions shorten timelines, reduce operational and regulatory risk, and enable fast adaptation and updates. A strategic choice of an existing solution from a specialist vendor is the key to growth and stability for financial institutions, especially those going through a regulatory licensing process.
It is a common myth that in-house development provides unlimited flexibility. In practice, the high costs of maintenance, upgrades and regulatory adaptations, together with long timelines, can significantly limit flexibility over time. A proven existing solution, developed and supported by specialists, may offer greater flexibility and a faster response to change.
When buying a system from an external vendor, especially in a cloud (SaaS) model, the costs of purchase, implementation and maintenance are known in advance and usually fixed. This allows the financial institution to plan its budget with confidence, without the surprises and hidden costs typical of in-house development projects.
Managing credit without a dedicated system, for example in Excel spreadsheets, exposes a financial institution to many risks. These include human error, non-compliance with the regulatory requirements of the Bank of Israel and the Capital Market, Insurance and Savings Authority, difficulty managing risk and collateral, and exposure to information security vulnerabilities. This can lead to heavy fines and serious reputational damage.
A system developed for many financial institutions benefits from economies of scale: every capability and every regulatory adaptation is developed once and made available to all the organizations using the system, and the cost of development and maintenance is shared among them rather than falling on a single organization. In addition, years of real-world operation at large clients expose edge cases and exceptional scenarios and allow them to be addressed in advance, so an organization that buys the system builds on a solution that has already been tested and is running in the field.
In-house development may be worthwhile only for exceptionally large financial institutions with unlimited budgets, very large development teams and unique, innovative business requirements that no solution on the market addresses. For most organizations, and especially those managing credit portfolios worth tens of millions of shekels, the risks and costs of in-house development outweigh the potential benefits.
.webp)
