Skip to main content
GullySystem
A practical guide

Filing due date tracker template for a multi-client practice

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 4 min read

In this guide 6 sections
The short answer

Keep one row per client and obligation. Columns hold the statutory date, an earlier internal date, the owner, a status and a proof field for the filing receipt, so every row shows who acts next. Sort by internal date each Monday. Review every amber or red row.

One row per client and obligation

The unit is the obligation. One company may owe an annual return, quarterly payroll filings, a VAT return, a board resolution and a licence renewal, each with its own row and its own dates.

Every period gets a fresh row. Last quarter’s closed row stays as history instead of being overwritten, which matters when an authority asks what you filed and when.

Start with a master list of the obligations you handle, grouped by entity type, because a company, a partnership and an individual owe different things. Build the rows from that list. Memory always misses something.

  • Client and entity type
  • Obligation name and period covered
  • Authority the filing goes to
  • Statutory due date
  • Frequency: monthly, quarterly, annual or event-driven

Two dates, not one

The statutory date belongs to the authority and is the last day, not the target, so the team should work to an internal date set earlier.

Choose the margin by obligation. A simple monthly return needs a few days of slack, while an annual filing that waits on audited figures, a director’s signature and a board approval needs weeks.

Sort by the internal date. Once that date passes, the row turns amber, and amber is where a missed statutory deadline gets caught before the authority notices.

Owner, status and the next action

Every row names one owner. Name a person, not a team. Add a reviewer where the filing needs a second signature, such as an annual return or a payroll summary sent to the authority.

Use a short list of statuses that everyone shares, such as papers awaited, in preparation, in review, with client for approval, filed and closed. Free text cannot be sorted.

Add a next action and its date. A note such as chase bank statements on Tuesday tells a colleague exactly what to do when the owner is out sick, and it takes ten seconds to write.

  • Owner and reviewer
  • Status from a fixed list
  • Next action and its date
  • Link to the client folder

Proof that the filing happened

Finished work does not close a row. A row closes only when you hold proof: the acknowledgement number, the filing date and the receipt saved in the client folder.

Record the acknowledgement reference in one column and the file location in another, so when an authority writes six months later you can answer in a minute.

Note which preparer filed. Note whether the client approved the final figures, and if approval came by email, link that message to the row so nobody has to hunt for it later.

Keep it alive week to week

A tracker dies when updates lag. Fix a weekly slot. Walk only the amber and red rows.

Add new rows at onboarding, not later, because the day a client signs the coordinator should create every obligation from the master list and set the first internal dates.

Once the sheet passes a few hundred rows, or several people edit at once and versions drift, consider practice software that generates rows and sends reminders by itself. Export the sheet before you switch.

  • Monday review of amber and red rows
  • New client rows created at signing
  • Closed rows archived each quarter
  • Master obligation list reviewed yearly

Filing due date tracker sheet

A spreadsheet template with one row per client and obligation, whose second tab holds the master obligation list used to create rows at onboarding. Columns run left to right: client, entity type, obligation, period, authority, statutory date, internal date, owner, reviewer, status, next action, action date, acknowledgement number, filing date and folder link.

Open a blank worksheet to print

Questions owners ask

Can a spreadsheet really handle a whole practice?

For a small client list, yes. Past a few hundred rows, or when several people edit at once, versions drift and reminders depend on memory, and that is where software earns its place.

How far ahead should the internal date be?

It depends on the obligation. Simple recurring returns need a few days of slack, while annual filings that wait on approvals or audited accounts need several weeks. Set the margin per type.

What about filings with no fixed date?

Event-driven filings, such as a change of director or a new registered address, start the clock on the day the event happens. Add the event date as a column, then calculate the due date from it by the rule that applies to that filing.

How long should we keep closed rows?

Keep them at least as long as your professional rules require and as long as the authority may reopen a matter for review. Check the periods with your regulator.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Share Your Requirements