What we monitor: Companies House confirmation statement

How PenaltyProof monitors the confirmation statement deadline and what alert stages fire.

What we track

PenaltyProof reads the next_confirmation_due date from the Companies House API for every company on your list. The date is polled daily.

Alert stages (paid plans)

Advance alerts at 30, 14, and 7 days, plus on the day. Overdue at any day past due. Escalation at 7 and 28 days overdue. Additionally: a pre-filing checklist alert fires at 21 days before the due date (Pro/Practice only, cs_checklist_alerts_enabled); and a CS accuracy check at 14 days (ECCTA accuracy obligations reminder).

Free plan

Overdue alerts only.

What we do not monitor

We do not check the correctness of the filed information (registered office, PSC, shareholders). We detect only whether the filing is outstanding or submitted. PSC and officer change detection is implemented but gated off pending Celery provisioning — it is not currently active.

Cross-link

See /deadlines/confirmation-statement-deadline for penalty and timing details.

Common questions

What is the threshold for confirmation statement alerts?

Advance alerts at 30, 14, and 7 days plus on the day (paid plans). The pre-filing checklist fires at 21 days (Pro/Practice, cs_checklist_alerts_enabled flag). Overdue and escalation alerts follow the same cadence as annual accounts. Free plans receive overdue alerts only.

What configuration is needed?

No per-company configuration is needed. The next_confirmation_due date is read directly from the Companies House API.

Does PenaltyProof check PSC or officer accuracy?

No. We detect whether the confirmation statement has been filed as outstanding or submitted. PSC and officer change detection is implemented but currently gated off pending Celery provisioning.

Related articles