<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=656789255406301&amp;ev=PageView&amp;noscript=1">
Category: Case Study
Vertical: Government
Est. read time:

HM_Land_Registry_logoIn less than three months, HMLR replaced the effortful and error-prone tasks with an automated process to improve financial planning.

The new MuleSoft-based solution has proved to be flexible, secure and scalable.

Results at a Glance:
The number of APIs in Production. 240 hours to build an API.
The reuse rate is defined as % of APIs with multiple consumers.
hours saved in development alone due to APIs' reuse.

When you buy or sell a house, flat or land, the details about your ownership are recorded with His Majesty's Land Registry (HMLR) to protect your property rights. The organisation stores over 25 million titles. Each registered title is linked to information about the extent of the land, details about the owners, any charges (mortgage), benefits, restrictions and even the likelihood that the property will flood.


HMLR required a robust and effective way of managing their operational planning data, and an Anaplan DataHub was introduced as a single source for finance and operational data. This strategic tool was key to the organisation's being able to make more effective decisions that were data-driven. To see ongoing benefits from the DataHub, the data within needed to be as real-time as possible. Yet this process required a series of repetitive manual tasks to extract and load the information.


Operational information was extracted from a DB2 database or data warehouse using a MicroStrategy (MS) management information reporting application. The finance team would then pull information from an MS-generated report to manually create or amend operational models in the Anaplan Data Hub. HR and financial data were retrieved from the Oracle database to compensate for the lack of details provided by the original MS report. Finally, the team manually manipulated and uploaded these details into the Anaplan model.



  • Manual extracting and submission of data is inefficient and prone to errors;
  • Lack of automation in critical financial processes, including operational reconciliations;
  • Increased risk of fraud and abuse due to manual tasks;
  • Various siloed data sources without a single point of truth;
  • Duplicate records and data consistency issues due to manual processing.


How we made it work

HMLR required an integration solution to automate the process of data extraction and real-time consolidation. To start with, the organisation engaged our MuleSoft experts to run a  1-day MuleSoft Test Workshop. During the event, the HMLR team evaluated whether MuleSoft's integration platform would be the right fit for the organisation's needs. Following the workshop's success, HMLR selected MuleSoft as their integration enabler.


API-led solution for HM Land Registry.


The project applied an API-led connectivity approach to the design (as shown above) to decouple the backend data sources and the receiving Anaplan app. This abstraction layer reduced the dependencies and provided opportunities for reusability for future integration projects.


HMLR Anaplan Solution Overview – Logical View

Data flow solution - logical view.


Starting your API-led integration initiative?

Our Kick-start Integration Kit is a perfect solution for organisations that have chosen MuleSoft as the primary transformation enabler and are looking to get started fast.


Momentum gained

Applying Kick-start Integration Kit (KiK), our process-based solution, we helped HMLR set up a solid foundation with reusable APIs, launch the project and demonstrate value in only 90 days. This approach helped design the solution right from the start and follow a series of best practices, thus minimising the need for additional rework and reducing the project delivery time.


Key deliverables achieved

HMLR is an excellent example of how fast a company can start realising the benefits of MuleSoft and API-led connectivity. HMLR's three integration projects delivered over a 15-month timeframe benefitted from the foundations laid during this project. As a result of API reuse and out-of-the-box connectors provided by MuleSoft, the team delivered the consequent projects three(!) times faster than the original estimations. Furthermore, even within the first project, the team successfully reused several System APIs and, thus, accelerated the delivery.


  • 16,800 hours of development and over £1,680,000 in savings.

    22 APIs were reused 70 times. Building 70 separate direct system connections would take 16,800 development hours (240 hours to build an integration x 70 integrations) and cost over £1,680,000 (the average developer rate is £100).

  • 62,86% reuse rate, defined as % of APIs with multiple consumers.
  • Actionable insights and data consolidation to get instant answers to revenue opportunities and cost concerns;

  • Single source of truth - access to near real-time transactional data from various sources;
  • Provide foundations and reusable assets to facilitate and accelerate future integration deliveries.
API reuse HMLR