API Integration for Conveyancing: Bridging the Solvency Data Gap

A corporate seller disposes of a £2.4 million commercial freehold. The buyer's solicitors conduct standard due diligence, verify the seller's 'Active' status on public registers, and proceed to completion. Five days later, a winding-up order is made against the seller based on a petition presented to the court two weeks before contracts were exchanged.

Under Section 127 of the Insolvency Act 1986, any disposition of a company's property made after the presentation of a winding-up petition is void unless the court orders otherwise. The buyer loses the asset, the seller's liquidator claims the property for the creditor pool, and the conveyancing firm faces a severe professional negligence claim.

This scenario is the direct result of the 'notification gap'-the dangerous delay between a court filing and its appearance on public registers. For solicitors, conveyancers, and legal technology providers, manual checks are no longer sufficient to mitigate this risk. Integrating real-time corporate data via an Application Programming Interface (API) directly into case management systems has become a mandatory safeguard for commercial and high-value residential property transactions.

The Anatomy of the Solvency Notification Gap

A critical vulnerability in UK property law is the structural delay in insolvency reporting. When a creditor-often HMRC-presents a winding-up petition to the High Court or a regional District Registry, the company is immediately at risk of liquidation. However, this event is not instantly broadcast to the public.

The statutory process dictates that the petition must be served on the company, and a period (typically seven clear days) must elapse before the petition can be advertised in The Gazette. Only after the Gazette advertisement does the information eventually filter through to the Companies House register.

This creates a blind spot lasting anywhere from 7 to 14 days. During this period, the company remains 'Active' on Companies House, and standard credit reports will show no immediate signs of terminal distress. If a conveyancer conducts a manual check during this window, they will receive a false positive regarding the company's solvency.

Expert Analysis: Why Standard Due Diligence Fails

Relying on a static, point-in-time check at the start of a conveyancing file is a fundamental procedural error. Property transactions take months to complete, and a company's financial standing can deteriorate rapidly within that timeframe.

Legal professionals owe a duty of care to ensure they do not facilitate a void disposition. While a validation order can theoretically be obtained from the court to save a transaction under s.127, courts are highly reluctant to grant these retrospectively if the transaction dissipated assets that should have been available to unsecured creditors. The burden of proof rests entirely on the applicant to show the transaction was beneficial to the general body of creditors-a near-impossible hurdle when a property has been sold at a discount or the proceeds used to pay off specific directors rather than the company's debts.

To meet the rigorous standards of the Money Laundering, Terrorist Financing and Transfer of Funds (Information on the Payer) Regulations 2017, firms must also maintain continuous oversight of the corporate entities they transact with. An API integration solves this by replacing human memory and manual repetition with automated, continuous data retrieval.

Worked Example: The Voided Commercial Freehold

Consider the composite case of Apex Logistics Ltd purchasing a regional distribution depot from Meridian Haulage Ltd for £1.8 million.

On Day 1, Apex's conveyancers open the file. A paralegal checks Companies House. Meridian Haulage Ltd is listed as 'Active'. The latest accounts are filed, and there are no visible insolvency markers.

On Day 10, unknown to the buyer or their solicitors, HMRC presents a winding-up petition against Meridian Haulage Ltd at the High Court for £450,000 in unpaid PAYE and VAT.

On Day 14, the parties exchange contracts, and a 10% deposit (£180,000) is paid.

On Day 28, the transaction completes. The remaining £1.62 million is transferred, and the keys are handed over.

On Day 30, the winding-up petition is finally advertised in The Gazette.

On Day 45, a winding-up order is made. The Official Receiver is appointed as liquidator.

Because the property transfer occurred on Day 28-after the petition was presented on Day 10-the transaction is void under s.127 of the Insolvency Act 1986. The liquidator successfully reclaims the depot. Apex Logistics Ltd is left as an unsecured creditor for their £1.8 million, a sum they are highly unlikely to recover. Apex immediately issues proceedings against their conveyancing firm for failing to identify the pending petition prior to completion.

Had the conveyancing firm's case management system been integrated with a live court data API, an automated alert would have flagged the HMRC petition on Day 11, halting the exchange of contracts and saving the client's capital.

Essential API Data Streams for Conveyancers

To ensure a robust risk assessment, legal technology platforms must integrate several specific data streams beyond basic company status.

1. Corporate Identity and Governance

Verification of a corporate entity's standing is the baseline requirement. Direct API access provides:

2. Charges and Encumbrances

While HM Land Registry remains the definitive source for property titles, the corporate charges register reveals the seller's wider financial liabilities. Under Section 859A of the Companies Act 2006, companies must register charges within 21 days of creation.

Conveyancers must execute a thorough company charge check to identify floating charges or debentures. If a floating charge has crystallised into a fixed charge due to an insolvency event, the directors lose the authority to dispose of the company's assets. The API can pull MR01 (registration) and MR04 (satisfaction) forms directly into the workflow, ensuring the solicitor knows exactly which lenders must provide a deed of release before completion.

3. Director Risk Profiling

Analysing the history of a company's officers provides vital context. API tools cross-reference director names against the Insolvency Service register of disqualified directors. Identifying a director associated with multiple failed entities-a hallmark of phoenixism-provides a necessary red flag, prompting enhanced due diligence.

Comparison of Solvency Data Sources

Understanding the latency of different data sources is critical for legal risk management.

| Data Source | Update Frequency | Latency from Court Filing | Reliability for Pending Petitions |

| :--- | :--- | :--- | :--- |

| Companies House | Daily | 10 to 21 days | Low (Only shows post-Gazette data) |

| The Gazette | Daily | 7 to 14 days | Medium (Requires statutory advertisement) |

| Insolvency Enquiry Line | Real-time | None (Manual phone call required) | High (But highly inefficient for volume) |

| Corp-Intel API | 3x Daily | Under 24 hours | Highest (Aggregated directly from court lists) |

Traditional Manual Checks vs Corp Intel API

Traditionally, conveyancing firms manage solvency risk through highly manual, unscalable processes. A paralegal or trainee solicitor is tasked with checking Companies House WebCHeck at file opening, and perhaps again just before exchange. To check for pending winding-up petitions, the fee earner must physically call the Insolvency Service Enquiry Line, wait on hold, and ask the operator to search for a specific company name. This process is entirely point-in-time. If the call is made on a Tuesday, and the petition is presented on a Wednesday, the firm remains exposed if completion occurs on Thursday.

Corp Intel fundamentally changes this workflow. By aggregating data directly from the High Court and regional District Registries, the Corp Intel API delivers machine-readable cause list data straight into the firm's Case Management System (CMS).

Instead of manual phone calls, the CMS automatically triggers a winding up petition search at critical milestones: file opening, pre-exchange, and pre-completion. Furthermore, by utilising free company monitoring endpoints, the system establishes a persistent watch on the entity. If a petition is filed, a charge is registered, or a director resigns at any point during the transaction lifecycle, the fee earner receives an immediate, automated alert within their existing software environment. This provides a definitive, auditable trail of 'due enquiry', protecting both the client's funds and the firm's professional indemnity insurance.

Implementation Framework: Integrating Solvency Data

Firms and legal tech vendors looking to integrate these capabilities should follow a structured deployment methodology to ensure compliance and technical stability.

1. Workflow Mapping: Define the exact trigger points within the CMS. Best practice dictates API calls should fire automatically at onboarding, 48 hours prior to exchange, and on the morning of completion.

2. Technical Audit: Ensure the existing CMS (e.g., Leap, Peppermint, Eclipse Proclaim) supports RESTful API architecture and can parse JSON data structures. Map the API response fields (e.g., `petition_status`, `court_reference`) to custom fields within the matter file.

3. Establish Webhooks: Rather than constantly polling the API, configure webhooks to receive push notifications if a monitored company's status changes during the transaction window.

4. Compliance Review: Update internal Data Protection Impact Assessments (DPIAs) to reflect the automated processing of corporate and director data. Ensure the integration adheres to ICO guidance on automated processing.

5. Pilot Phase: Deploy the integration to a single conveyancing team or a subset of files. Monitor the error handling for edge cases (e.g., companies with identical names but different registration numbers) before rolling out firm-wide.

FAQ

Q: Why is a Companies House search insufficient for pre-exchange solvency checks?

A: Companies House only records insolvency events after they have been formally reported by the court or the insolvency practitioner, usually following advertisement in The Gazette. A winding-up petition can be active for weeks before it appears on the public register, making the company 'insolvent' in the eyes of the court while still appearing 'Active' to a casual searcher.

Q: How does an API integration handle false positives in court lists?

A: Court cause lists often use trading names or misspelled corporate entities rather than precise Company Registration Numbers (CRNs). A sophisticated API uses fuzzy matching and cross-references registered office addresses and director names to categorise matches as 'Clear', 'At Risk' (requiring manual fee-earner review), or 'Active Proceedings'.

Q: Can a voided property transaction be saved after a winding-up order is made?

A: It is possible to apply to the court for a validation order under s.127 of the Insolvency Act 1986. However, courts rarely grant these retrospectively for property disposals unless the purchaser can prove the transaction was at market value and the proceeds directly benefited the general body of unsecured creditors. It is a highly expensive and uncertain litigation route.

Q: What is the difference between a fixed and floating charge in this context?

A: A fixed charge is attached to a specific asset (like a commercial building) and prevents the company from selling it without the lender's consent. A floating charge hovers over a class of assets (like stock or unattached equipment) and allows the company to deal with them in the ordinary course of business. If a company faces an insolvency event, a floating charge 'crystallises' into a fixed charge, instantly freezing the directors' ability to dispose of those assets.

Q: Does automated API checking satisfy our regulatory AML obligations?

A: Yes, provided the system is configured correctly. API integration automates the identification of Ultimate Beneficial Owners (UBOs) via PSC registers and provides a consistent, time-stamped, and auditable trail of due diligence, which is exactly what the SRA and external auditors look for during compliance reviews.

***

Protect your firm and your clients from the severe consequences of the solvency notification gap. Integrate definitive court and corporate data directly into your workflows. Learn more about our developer-friendly endpoints and implement a reliable winding up petition search today.