Following the precedent of the officers bulk file (provided on request via customer care), I’d like to request access to a bulk extract of the charges register, structured to support lookup by chargee — i.e. with persons_entitled.name as the queryable primary key.
Use case
Forensic investigation and cross-border insolvency casework where bad actors are misusing charges. The REST endpoint /company/{company_number}/charges is keyed to the chargor company. There is no public route to answer “all UK charges where party X is the person entitled” without iterating every active company on the register, which is impractical under the API rate cap. The January 2026 thread (/t/bulk-charges-data/12617) reflects the same requirement from another user.
Requested schema - one row per (charge × person_entitled) pair
| Field | Source |
|---|---|
person_entitled_name |
charges.persons_entitled[].name (primary key) |
person_entitled_normalised |
optional, for join/dedupe |
chargor_company_number |
company |
chargor_company_name |
company |
chargor_company_status |
company |
charge_id |
charges |
charge_code |
charges |
status |
outstanding / fully-satisfied / part-satisfied / etc. |
created_on |
charges |
delivered_on |
charges |
acquired_on |
charges (where present) |
satisfied_on |
charges |
particulars_description |
charges.particulars.description |
transaction_id |
linkage to MR01/MR04 in filing history |
Flattening to one row per (charge × person_entitled) is essential - multi-chargee charges (syndicated security, debenture trustees) would otherwise be unjoinable on the chargee axis.
Scope
-
All registered charges from the post-6 April 2013 MR-form regime (earlier Form 395-era charges welcome if held in a comparable schema, even as a separate file)
-
All company statuses (active, dissolved, in liquidation, etc.)
Format and refresh
-
CSV or Parquet, UTF-8
-
Single snapshot acceptable; monthly delta preferred if supported
-
Cloud bucket delivery on the same model as the officers bulk file
Happy to sign data sharing terms or provide further information on the use case.