obnexo

Company-year planning checklist

Company Compliance Calendar Generator

Bring conditional annual planning dates and separate-cycle reminders into one working view.

For ordinary later private-company accounts, use the registered ARD as the year end and verify the aligned CT-period assumptions. First accounts, confirmation statements, VAT and payroll receive no calculated dates. Reviewed 29 September 2026.

Company Compliance Calendar Generator

Build a conditional later-company planning checklist; first-year, confirmation-statement, VAT and PAYE dates require separate facts.

Choose the calendar date. Your browser controls the date order; for example, 26 September 2026.

VAT registered?
Payroll active?
Are these the company's first accounts?

Calculated rows are conditional; reminders are not deadlines

A company compliance calendar brings obligations, owners and evidence into one working view. It helps an accountant plan work; it does not replace Companies House or HMRC records, discover every obligation or file anything automatically.

The Obnexo generator uses one company year end and three yes/no facts: VAT registration, active payroll and first accounts. For later accounts it shows three conditional planning dates. For first accounts it withholds accounts and tax dates. Confirmation statements, VAT and payroll remain checklist prompts, not calculated deadlines.

Rule summary

What the public calendar actually does

Four inputs create conditional annual planning rows and separate checklist prompts. The generator does not verify official records, supply missing history or create internal practice dates.

ObligationLater accounts: what appearsFacts still to verify
Companies House accountsPrivate-company planning dateRegistered ARD, ordinary later period, no change or extension
Corporation Tax paymentNormal CT payment planning dateActual CT period end; no instalment regime
CT600 filingOrdinary return planning dateOne CT period equals accounts period; no later notice/exception
Confirmation statementChecklist only; no dateActual review-period end and official due date
VAT / PAYEChecklist if Yes; no dateSeparate registrations, periods, paydays and schemes
First accounts / first CTNo annual dates; review promptsIncorporation, ARD history, notice receipt and HMRC periods

Worked examples

How the result behaves in practice

Established private company: three different rules

Registered ARD and one full CT period both end on 30 April 2026. These are later accounts, with no changed period, extension, instalments or later CT filing condition. VAT and payroll are active.

The calendar shows accounts on 31 January 2027, CT payment on 1 February 2027 and CT600 filing on 30 April 2027. Confirmation, VAT and PAYE remain undated prompts. Confirm each assumption against the records.

First year: do not manufacture annual dates

A private company incorporated on 1 January 2025 has first ARD 31 January 2026. Select First accounts: Yes.

The calendar withholds accounts, CT payment and CT600 dates. The dedicated Accounts tool, given the reviewed ordinary first-account facts, gives 1 October 2026. Check activity start and HMRC periods separately before planning any tax dates.

Turn the result into an action plan

Check the company number, registered ARD, filing history, first/later accounts and any period-change or extension evidence on Companies House.

Confirm HMRC accounting-period dates, notice-service facts and whether the normal Corporation Tax payment rule applies before using the tax planning rows.

Generate the checklist, then reconcile each calculated date with the relevant dedicated tool and official account. Investigate differences rather than choosing the more convenient date.

Add confirmation-statement, VAT and payroll source facts from their own cycles. Label them separately from dates calculated from the year end.

Assign an owner and internal records, preparation, review and submission dates. Refresh the working view when source facts change and confirm acceptance or payment, not just an attempted submission.

Read the guide

Company compliance calendars for UK accountants

Read the supported rule, assumptions and worked examples behind this tool.

Assumptions and limits

This tool gives a practical estimate and depends on the assumptions shown below.

Assumptions

  • The entered year end is the registered ARD for ordinary later private-company accounts, with no changed-period or extension adjustment.
  • For tax dates, verify the actual CT period, normal payment regime and ordinary filing conditions. The calendar does not collect those facts.

Limits and rule basis

  • The calendar is a planning checklist, not an exhaustive statutory calendar, official record, compliance certificate or filing system.
  • Annual dates assume ordinary later private-company accounts at the registered ARD, an aligned single CT period and the normal CT payment/filing rules. Changed periods, extensions, instalments and later notice conditions need separate verification.
  • First accounts and first CT periods have no calculated dates. Confirmation statements, VAT and payroll always require separate source facts; VAT/PAYE status flags only control reminders.
  • It does not determine dormant exemptions, public-company or LLP accounts deadlines, penalties, overdue status or specialist obligations. Use the relevant dedicated tool and professional review where needed.

Primary sources and review date

Reviewed on . Preserved source review from the accepted scoped statutory repair; this contract migration does not re-date that review.

Applies to: Current ordinary later-company planning rules; Companies House, CT payment and CT filing are separate date regimes.

Reviewed scope: Ordinary later private-company ARD and aligned standard CT facts must be verified. First-year dates withheld; confirmation, VAT and PAYE are undated separate-cycle reminders.

Review basis and change triggers

Reviewed model: company-compliance-calendar-generator: calendar-planning-reviewed-29 September 2026

  • A cited source or statutory regime changes.
  • Reviewed content, runtime adapter or domain implementation changes.
  • A new effective period falls outside the supported scope.