# UK Pensions Regulator Penalty & Determination Tracker (`hllerdgn80/uk-pensions-regulator-penalty-tracker`) Actor

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.

- **URL**: https://apify.com/hllerdgn80/uk-pensions-regulator-penalty-tracker.md
- **Developed by:** [Halil Erdogan](https://apify.com/hllerdgn80) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.01 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## UK Pensions Regulator Penalty & Determination Tracker

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

| Field | Description |
|---|---|
| `pages` | Which page(s) to read: `penalty-notices`, `determination-notices`, or both (default: both). |
| `watchLabel` | Free-text tag copied onto every row - lets you tell several scheduled watches apart. |
| `maxItems` | Cap 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.).

# Actor input Schema

## `pages` (type: `array`):

Which public enforcement-activity pages on thepensionsregulator.gov.uk to read. penalty-notices = Escalating Penalty Notices, scheme-return fines, climate-change and value-for-members fines (govuk tables). determination-notices = Determinations Panel decisions (link list grouped by scheme year).

## `watchLabel` (type: `string`):

Optional free-text tag copied onto every output row (and onto the single error row if a page fails to load), so you can tell runs apart when you schedule this Actor repeatedly.

## `maxItems` (type: `integer`):

Stop after pushing this many rows in total across the selected pages (safety cap). Both pages together currently hold well under 500 rows.

## Actor input object example

```json
{
  "pages": [
    "penalty-notices",
    "determination-notices"
  ],
  "maxItems": 500
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("hllerdgn80/uk-pensions-regulator-penalty-tracker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("hllerdgn80/uk-pensions-regulator-penalty-tracker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call hllerdgn80/uk-pensions-regulator-penalty-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hllerdgn80/uk-pensions-regulator-penalty-tracker"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/4dltNupQxNwklsH7Q/builds/gbCU5aga1Y7GQlsue/openapi.json