The early confirmation statement trap, and how to avoid it

Batching confirmation statements is good practice. Clear the March filings in January, get them off the desk, move on. But for anyone who is both a director and a PSC, the verification deadline does not move with the filing. It stays pinned to the official confirmation statement date, and that is where firms get caught: the statement is filed, the job is ticked, and a verification window opens a month later that nobody is looking at.

Why does filing early not move the deadline?

For a director who is also a PSC, the 14-day verification window starts the day after the company's confirmation statement date, not the date you submit the filing. The statement date is a fixed point in the company's year. Filing early changes when the paperwork is lodged, but it does not change that anchor, so the verification window stays exactly where the statement date puts it. The two actions are governed by different dates that happen to share a name.

A worked example on the timeline

Take a company with a confirmation statement date of 31 March 2026, with a director who is also a PSC. Suppose the firm files the statement on 5 February to clear the backlog. The statement is now done, nearly two months early. But the person's verification window still runs from 1 to 14 April 2026, the 14 days after the statement date. The timeline below shows the gap between "filed" and "still must verify".

Why the trap is so easy to fall into

The trap works because it hides inside a sensible habit. Most firms track confirmation statements by when they file them, because that is the action they control. Verification, by contrast, is often something the client does themselves through GOV.UK One Login, on a date set by the statement rather than the filing. So the two events drift apart: one is logged in your workflow, the other sits on a date you may not be recording at all. Multiply that across a portfolio and the gaps stack up quietly.

It is worth being clear about who this affects. The 14-day window is specific to people who are both a director and a PSC. A director who is not a PSC verifies with the statement itself, so for them the timing lines up. The mismatch is a director-PSC problem, which is exactly the group it is easiest to assume you have already handled. For how the roles map to windows, see the three verification windows.

How to avoid the early confirmation statement trap

The fix is to separate the two dates in whatever you use to track compliance. Record the confirmation statement date as the verification anchor, independently of the filing date, and keep watching it after the statement is filed. The short checklist below is the habit that closes the gap.

1. Capture the statement date, not just the filing date. For every director-PSC, store the confirmation statement date as the thing that drives the verification window.
2. Don't close the task at filing. Filing the CS01 clears one obligation; leave the verification window open on your tracker until the person has actually verified.
3. Check Companies House data after the window. Confirm the verification start date has appeared on the appointment, so a self-verification doesn't slip past you unrecorded.
4. Review director-PSCs as their own group. They are the only ones with this 14-day clock, so give them a dedicated view rather than folding them into the general statement list.

Frequently asked questions