Blog article
See all stories »

Why Mortgage Lenders Need to Consider the Power of ERP for Loan Lifecycle Management

More than fifty years ago, SAP pioneered the concept of Enterprise Resource Planning (ERP) for manufacturing. The concept was simple:  a single platform with a single data model to support shared services (i.e., HR, Finance, Procurement) and core business functionality (i.e., Planning, Operations, Inventory, etc.). The concept took off, especially as organizations looked to cope with software limitations of Y2K and modernize their operations. Benefits included a more complete and consistent view of the organization along with actionable insights to make intelligent business decisions (i.e., “The Intelligent Enterprise”). It was no surprise that the model was adopted in manufacturing-centric sectors and then spread to other industries looking to benefit from frictionless processes and consistent, readily available management information.

With complex business processes and many subject to strict time constraints, Mortgage Lending also can be well served with the same “ERP Concepts” that are benefitting other industries like manufacturing, energy, resources, retail, hospitality, etc. Leveraging a common data model across loan pre-qualification, originations, fulfillment, servicing and default management can break down the organizational silos that exist across most mortgage companies. 

Organizationally, many mortgage lenders, especially large commercial banks that both originate and service loans, run their operations as separate profit and loss centers, with distinct operational hierarchies. Technology decisions are made unilaterally for each business, in part because there is no marketplace software offering that serves both origination and servicing functions. The commercial terms for licensing software are also different for each segment. Origination software licenses range from 3 - 5-year terms, whereas servicing subscriptions can be 5 - 10-year commitments. There is considerable value in placing both discrete processes on a common platform to optimize value over the life of loans.

One of the anomalies in mortgage lending is that 78% of borrowers will refinance their primary residences with different lenders than the ones they used to get their initial mortgages. Most loan officers lack real-time consumable customer information to anticipate when their customers are likely to need new mortgages. The top complaint of originators is that they do not have access to borrower data. Many loan officers grow their businesses by acquiring or soliciting leads from external sources; this results in the cannibalization of other loan officers’ existing, profitable books. Lenders lose business every day because of an inability to accurately and efficiently utilize business insights and data to proactively market new origination products to existing customers.   

A common mortgage platform creates a view into individual and portfolio loan attribute risk modeling. As market dynamics influence borrower incomes, cash flows, real estate property values, insurance rates, taxes, etc., the ability to use risk-based modeling to proactively evaluate loan level action (e.g., refinance, modification, program change, asset sale, retention strategies) is a mitigant to default and portfolio value erosion. 

One of the most beneficial aspects of a single ERP platform is the unification or “containerization” of business process micro-services onto a single UI and data layer. This reduces the scope of individual software solutions that must be deployed, integrated and maintained by trained professional system administrators which has a dramatic impact on total cost of ownership (e.g., licensing, testing, QA, maintenance, release management).

Mortgage companies should seriously consider leveraging better manufacturing technology systems to originate and service mortgages. The benefits of modernizing decades-old, legacy technologies with next-generation manufacturing software are: 

  • streamlining training and employee onboarding
  • simplifying access to customer and loan data
  • reducing costs per loan and enhancing customer profitability
  • improving borrower retention
  • reducing defects and communicating better with investors

Having spent three decades in financial services working with legacy and emerging mortgage technologies on behalf of mortgage banks, servicers and government-sponsored enterprises, I’ve seen these challenges and perceived risks from several perspectives. The underlying platforms that currently support U.S. mortgages are ripe for disruption. With the current market headwinds of rising interest rates and reduced overall transaction volumes, margin compression is the single most critical top-of-mind concern for mortgage industry executives. This type of market stress makes it the right time to evaluate alternatives to aging systems.

What are your challenges with handling mortgage loans and their underlying technologies?

3594

Comments: (1)

David Bomser
David Bomser - SAP Fioneer - Miami, Fl 08 September, 2023, 13:00Be the first to give this comment the thumbs up 0 likes

*Y2K:  For those not in the workforce at the turn of the millennium, Y2K refers to the Year 2000 issue which many predicted would cause the end of commercial civilization as we knew it. Because by the end of late 20th century, most installed enterprise software had been written in COBOL, a 3rd generation language which had been around since the 1960s, and it was feared that the year in date formats, which was often just represented only in 2 digits (97, 98, 99 etc.) would switch to 00 at the turn of the century, causing extreme chaos as it would be indistinguishable from the year 1900. Much remediation was carried out in the years leading up to 2000 with programs being rewritten, often with COBOL programmers coming out of retirement to do it, on lucrative contracts. This also gave birth to the offshore development industry as more COBOL programmers were required than availalble. However, as the enterprise software in use at the time like ERP was so systemic and complex, it was often more practical to upgrade to a modern ERP system. In reality, there were few problems when the clocks ticked over on Jan 1, 2000, probably because of all the remediation work ahead of time.

Now hiring