Scope: what data this covers

This guide is about HM Land Registry Price Paid Data for England and Wales only. The HM Land Registry collection page says the dataset contains sale prices of properties in England and Wales submitted to HM Land Registry for registration.

That scope matters. If you are researching a property outside England and Wales, this guidance does not tell you how another nation’s system works. Even within England and Wales, the dataset is about transactions lodged for registration, not a live feed of every sale as soon as contracts complete.

The most common reason: registration lag

HM Land Registry’s guidance says the time between a property sale and registration varies, and typically ranges between 2 weeks and 2 months. It also says the two most recent months of data are incomplete and do not indicate final monthly volumes.

In practice, that means a sale completed recently may still be absent from a sold-price search simply because the transaction has not yet moved through registration and publication. HM Land Registry also says that, occasionally, the interval is longer than two months. Where that happens, the affected sales cannot be updated for publication until they are lodged for registration.

So if you are checking a sale that completed very recently, missing data on its own is weak evidence. It tells you there is no matching published record in the dataset you searched at that moment. It does not, by itself, prove that anything is wrong.

Coverage limits: not every transfer appears in Price Paid Data

HM Land Registry says its Price Paid Data includes residential property sales in England and Wales that are sold for value and lodged for registration. It also lists exclusions.

According to the guidance, the dataset excludes sales that have not been lodged with HM Land Registry and sales that were not for value. It also excludes several specific transaction types, including right to buy sales at a discount, some transfers involving an existing mortgage, some transfers between parties on divorce by way of gift, compulsory purchase transactions, court-order transfers, certain trustee appointments, transmissions or assents, and transactions involving more than one property.

This is an important limitation for property research. A missing record may reflect the dataset’s rules rather than a search failure. It is better to record the absence as an evidence gap than to infer motive or irregularity from it.

Why a record might appear differently later

HM Land Registry says it sometimes needs to make changes to Price Paid Data. Its guidance explains that records in monthly files can be added, changed or deleted, using record-status markers.

The guidance also says that when a transaction changes category type because it was originally misallocated, the original record is deleted and a new one is added in the correct category with a new transaction unique identifier. That means a record can move rather than simply being edited in place.

For researchers, the practical point is simple: one search result is a snapshot, not a permanent verdict. If you downloaded or reviewed only one monthly extract, later amendments may explain why a record appears, disappears or looks different in a later version.

  • A means a record was added in the monthly refresh.
  • C means a record was changed.
  • D means a record was deleted.
  • A category correction can create a delete in one category and an addition in another, with a new unique identifier.

Search issues can also hide the result

HM Land Registry’s search guidance says public data is captured at the time of registration, so later county or postcode changes will not be reflected on earlier sales. It also says you may need to try several search approaches to get a more comprehensive report for your location criteria.

Its examples include searching by both town or city and district, trying current and previous area names, and using wider searches before filtering by locality. The guidance also notes that administrative areas can change over time, which affects how older transactions are described in the dataset.

So a missing Land Registry sold price result may sometimes be a search-method problem rather than a genuinely absent record. This is especially relevant where places have overlapping postal, town, district or historic area names.

  • Try the postcode and the date of sale if you know them.
  • Test both town or city and district terms.
  • Check whether the district or authority name has changed over time.
  • Use a wider location search, then narrow the results by locality or address fields.

A factual checklist for a missing recent sale

Use this checklist to keep your research evidence-based and calm. It does not predict when a record will appear.

First, confirm jurisdiction. This guidance only supports England and Wales, because that is the scope HM Land Registry states for Price Paid Data.

Second, check timing. If the sale was very recent, note that HM Land Registry says registration typically takes between 2 weeks and 2 months, and sometimes longer.

Third, check that you are looking in Price Paid Data rather than assuming every completed sale appears immediately.

Fourth, broaden the search method. Try the postcode, address elements, town or city, district and possible historic area labels.

Fifth, remember dataset exclusions. If the transfer was not for value or falls within an excluded type described by HM Land Registry, it may not appear in Price Paid Data.

Sixth, if you believe the information is wrong or that a sale is missing, HM Land Registry says you can use its change a sales record form, and that you will need both the postcode and date of sale to complete it.

  • Confirm the property is in England or Wales.
  • Record the completion date you are checking against.
  • Allow for the stated registration lag before drawing conclusions.
  • Retry the search with alternative place descriptions.
  • Check whether the transaction could fall outside Price Paid Data coverage.
  • If needed, use HM Land Registry’s correction route with the postcode and date of sale.

Fictional worked example

Fictional example: a business researcher checks a flat sale said to have completed three weeks ago in Wales and cannot find it in a sold-price search.

A careful note would be: no matching published Price Paid Data entry found today using the address searched. HM Land Registry says the dataset covers sales submitted for registration in England and Wales, that registration typically takes 2 weeks to 2 months, and that the two most recent months are incomplete. On that evidence alone, the absence is consistent with normal registration lag.

The next step would not be to label the transaction suspicious. It would be to log the date checked, rerun the search later, test alternative address or district terms, and only then consider whether the case looks more like a search issue, an excluded transaction type or a possible error worth raising with HM Land Registry.

Limitations and next checks

This guide does not tell you whether a particular sale should definitely appear, when it will appear, or whether a missing entry reflects an error. The supplied HM Land Registry evidence supports only a careful explanation of timing, scope, exclusions and amendments.

For business research, the sensible next step is to keep a dated note of what you searched, which dataset or report you used, and which address terms you tried. Readers should then check the original HM Land Registry guidance and decide whether the property, date and transaction type fit the dataset before relying on the absence of a record.

Sources & further reading

  1. How to access HM Land Registry Price Paid Data - GOV.UK Accessed 21 October 2026
  2. HM Land Registry: Price Paid Data - GOV.UK Accessed 21 October 2026