UK Pensions Regulator Penalty & Determination Tracker avatar

UK Pensions Regulator Penalty & Determination Tracker

Pricing

from $0.01 / 1,000 results

Go to Apify Store
UK Pensions Regulator Penalty & Determination Tracker

UK Pensions Regulator Penalty & Determination Tracker

Reads TPR's public enforcement pages: Escalating Penalty Notice fines (auto-enrolment, scheme return, climate change), and Determinations Panel decisions - employer/scheme, district, amount, case type. Official govuk source, no other Store Actor covers TPR enforcement.

Pricing

from $0.01 / 1,000 results

Rating

0.0

(0)

Developer

Halil Erdogan

Halil Erdogan

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a month ago

Last modified

Categories

Security

Limited permissions

Share

Reads The Pensions Regulator's (TPR) public enforcement-activity pages - the official record of every fine and Determinations Panel decision TPR is required to publish under section 89 of the Pensions Act 2004.

Two data sets, either or both:

  • Penalty notices - every govuk table on TPR's penalty-notices page: Escalating Penalty Notices for automatic-enrolment breaches (both those paid but still non-compliant, and those unpaid and taken to a court order), scheme-return fines, climate-change governance/reporting fines and value-for-members fines. Each row gives the employer/scheme name, district and amount, plus the reporting period and case category it was published under.
  • Determination notices - every published Determinations Panel decision, grouped by pension-scheme year, with the entity name and a link to TPR's own notice page.

Why this is useful

Pensions/compliance consultants, insolvency and debt-recovery firms, HR and payroll software vendors, and journalists covering workplace pensions all want to know who TPR has fined or taken formal action against - today they have to read TPR's site by hand, page by page. This Actor turns those pages into structured, scheduled, diffable data. No Apify Store Actor currently covers TPR enforcement.

How it works

TPR publishes these pages at

thepensionsregulator.gov.uk/en/document-library/ enforcement-activity/penalty-notices
and .../determination-notices as plain, public govuk-frontend HTML - no login, no API key, no rate limit stated. robots.txt on thepensionsregulator.gov.uk only disallows /umbraco (the CMS admin path), unrelated to these pages. This Actor sends the same GET request a browser would and parses the same public HTML TPR already serves to anyone.

Input

FieldDescription
pagesWhich page(s) to read: penalty-notices, determination-notices, or both (default: both).
watchLabelFree-text tag copied onto every row - lets you tell several scheduled watches apart.
maxItemsCap on total rows pushed across the selected pages (safety cap; both pages together are currently well under 500 rows).

Output (one row per dataset item)

type (penalty_notice / determination_notice / error), watch_label, case_category, case_subcategory, reporting_period, fields (the raw table row as an object - e.g.

{"Employer name": ..., "District": ..., "Paid": ...}
for penalty notices; column names follow TPR's own table headers, which differ slightly by table), entity, notice_title, notice_url, source_page, source_url, status, message, scraped_at.

status is only set on the single explanatory error row pushed when a page fails to load (http_error / network_error); it is free of charge.

Pay-per-event

One charged event, enforcement-item-found, fires once per penalty-notice table row or determination-notice link. The explanatory error row (if a page fails to load) is free.

Typical use

  • Schedule monthly (TPR updates these tables periodically, not daily) and diff against the previous run to catch newly published fines.
  • Filter the fields.Employer name / entity column against your own client or portfolio list to flag a match.
  • Compare amounts across reporting_period to track enforcement trends by case category (automatic enrolment vs. climate-change reporting, etc.).