Run annual compliance

1. Establish the entity calendar

List entity type, registrations, financial period and recurring obligations. Separate national filings from local and activity-specific requirements.

Build an obligation register with one row per entity, registration and reporting period. Record the applicability reason, authority, source of the due date, preparation owner, approver, filing owner and evidence needed to close the row. Keep the internal preparation target separate from the statutory due date.

Start with the source-backed calendar, then adapt the company checklist or LLP checklist to the actual entity. Neither an old spreadsheet nor another business’s calendar establishes your current obligations.

2. Close and reconcile the records

Resolve bank, customer, vendor, payroll and tax differences before using the accounts in returns or corporate documents.

• Match bank balances and identify payments or receipts still awaiting allocation.
• Review customer and supplier balances, credit notes, disputed items and advances with the relevant business owner.
• Reconcile payroll expense and outstanding deductions to the approved payroll records.
• Compare tax workings and return data with the books, documenting timing differences rather than forcing unexplained totals to agree.
• Record proposed adjustments, their supporting evidence and who approved them before circulating the closing version.

Keep an exception log for missing invoices, unreconciled balances and disputed treatment. Give each item an owner, the affected return or report, and a next action. A difference marked “under review” should remain visible to the person preparing the filing.

3. Coordinate approvals and filings

Schedule management review, professional work and required approvals in sequence. A prepared form is not the same as a completed filing.

Use distinct statuses such as waiting for records, prepared, awaiting approval, submitted and acknowledgement retained. Check the entity identifier, reporting period, attachments and approved figures before submission. If payment or processing is outstanding, record that status instead of marking the entire task complete.

Example: a draft return is ready but a reconciliation changes one of its figures. Update the working paper, obtain the necessary approval for the revised version, and confirm that the submitted copy matches it. Keeping only the earlier draft can leave the next year’s team working from the wrong starting point.

4. Archive and carry forward

Retain acknowledgements, signed records and reconciliations. Move unresolved items and new event-based obligations into the next period’s worklist.

Store the final working paper, approved document, submitted copy, acknowledgement and related payment evidence together under the relevant entity and period. Record who can retrieve the archive and who owns any follow-up query. Keep sensitive records in controlled storage rather than attaching them to public enquiry messages.

At the handover, reconcile opening balances and carry-forward schedules to the completed closing records. List unfinished corrections separately with their dependencies. A new financial year does not resolve a previous period’s unanswered portal query or missing acknowledgement.

Bring these facts to the first discussion

• Prior-year filings and acknowledgements
• Books and reconciliation status
• Entity and registration list

Watch the dependency

An annual calendar cannot cover every event. A director change or capital issue needs its own action even if all recurring filings are current.

Ask the business to flag changes when they occur: ownership, office locations, banking arrangements, new activities and workforce expansion. Maintain an event log beside the recurring calendar, then assign each change for applicability assessment. This connects day-to-day decisions to the records and filings they may affect.

How responsibilities are agreed

You confirm business facts and approve decisions. Kosha’s engagement identifies the documents, coordination and filings included, together with any specialist adviser or authority dependency. The service links below explain the relevant workstreams and their limits.