Back to Solutions
Deadline management

Accounting deadline tracking: plan every step before the filing date

Work backward from the filing deadline. Set dates for documents, preparation and review, plan for delays and keep proof of what was done.

Railway tracks branching at a junction in soft morning light.

A goods and services tax or harmonized sales tax (GST/HST) return is filed two days late. The client sent the bank statement only four days before the deadline. The bookkeeper needed it to compare the books with the bank records. There was then no time to catch a transaction recorded in the wrong category. The “file GST/HST” reminder worked, but it tracked only the final date. It did not track the earlier work needed to meet it.

This process helps you plan steps that must happen in order, prepare for delays and record what was done. Recurring tasks are useful, but they do not by themselves tell you what must finish before the next task can start.

Map the real deadline, not just the filing date

Start with the legal filing deadline and work backward. Canada Revenue Agency guidance generally gives monthly and quarterly GST/HST filers one month after the reporting period ends. Most annual filers have three months after their fiscal year-end, the end of their financial year. Individual sole proprietors with a December 31 year-end have a separate filing and payment split. Check the applicable rule. The final date is only the last step, not the only date to track.

When must the reconciliation be finished to leave time for review? When must the client send the documents needed for it? When should you remind the client so those documents arrive in time? Give each step its own deadline and responsible person.

Write the steps in the order they must happen

Write down the order of work so a new team member can follow it. For a quarterly GST/HST filing, the client first sends bank and sales records. The bookkeeper reconciles the period. The preparer reviews the return. Then the return is filed. That is four steps where something can go wrong, but only one is the legal deadline.

Bookwits does not automatically block a task until an earlier one is complete. Create clearly named tasks or subtasks in the right order. Set their due dates before the final deadline. The firm must check that order manually, as it would with a paper checklist. Bookwits helps the team see the work and due dates; it does not enforce the sequence.

Plan for the exception before it happens

Plan for a late client, an unexplained difference in the accounts or an unexpected staff absence. Decide what to do when a step may miss its internal due date. For example, notify the person leading the work if documents are still missing three business days before the reconciliation deadline. Do not wait until that deadline is missed to raise the issue.

Write the exception rule down the same way the chain itself is written down. An exception handled quietly by one person, once, is not a process; it is a favour that will not be repeated consistently by someone else six months later.

A worked example: one quarter, four steps, one late client

Internal deadlines working backward from a quarterly GST/HST filing due June 30
StepInternal due dateWhat actually happened
Client sends recordsJune 10Arrived June 18 — eight days late
Bookkeeper reconcilesJune 17Started June 19, flagged as exception
Preparer reviewsJune 24Completed June 26, compressed window
Return filedJune 30Filed June 28 — two calendar days before the due date, after a compressed review

The return was filed two calendar days early. A calendar alone would show an on-time result. But the delay log shows that every later step had less time because the documents were late. There was no spare time elsewhere to handle another problem, even with two days left before filing was due. Next quarter, the client might be twelve days late instead of eight. Tracking only the final filing date would hide that risk.

Keep proof that a deadline was actually met

Keep a dated record of who did each step and when. Saying “we filed on time” is not the same as showing it. Canada Revenue Agency guidance explains that late GST/HST filing can bring penalties and interest. Repeated failures have more serious consequences. Internal task history, along with the filed return, helps explain the timing if a client later disputes it.

Bookwits keeps an activity history on tasks, including status and due-date changes, which can serve as that internal evidence trail. It does not determine the legal deadline itself, calculate penalties, or file anything — those remain the preparer's responsibility, informed by the applicable rules for that return and that client.

Frequently asked questions

Can Bookwits automatically stop a task from starting until an earlier one is finished?

No. There is no built-in dependency or blocking feature. The chain has to be represented through clearly ordered tasks and earlier internal due dates, maintained as a deliberate practice.

Does the software calculate the actual CRA filing deadline for us?

No. Filing deadlines depend on the specific filer type, reporting period and fiscal year-end, and must be determined by the preparer using the applicable CRA rules, not generated automatically.

Why track internal dates if the return was filed on time?

Did the team have to rush every earlier step to catch up? That warns of trouble next period, even if filing happened a day or two before the deadline. Internal dates show the risk sooner than a reminder for only the final deadline.

Sources and further reading