Generate a client's compliance tasks and deadlines

Turn on a service for a client and let the system create the dated filing and payment tasks the client owes.

Who this is for: managers who set up the recurring filings and deadlines a client owes.

Before you start

The client must already exist in the system.
Make sure the client's details that drive deadlines are correct first, especially the fiscal year-end and, for partnerships, the partner composition. These determine the dates that get generated. If the client has no recorded year-end, December 31 is used.

Open the client you want to set up.
Go to the client's Services tab.
Enable the service you want the client to receive.
The system creates the filing tasks (and a separate payment task when the payment date differs from the filing date) for the service's upcoming periods: the current occurrence for an annual filing, the next two quarters for a quarterly one, the next three months for a monthly one. As each future period approaches, its task appears automatically overnight — you never need to generate ahead. Each task gets a due date computed for the obligation, then rolled forward if it would land on a weekend or a Quebec statutory holiday.
The new tasks appear in your task list. Each starts in the "not started" status and is assigned to the service's assignee, the person set for that service on the client's Services tab; if the service has no assignee, the tasks are created unassigned. The list shows open work due within the selected horizon (one month by default) — widen the due-date filter to see instances generated further ahead.

A deadline that lands on a Saturday, Sunday, or Quebec statutory holiday is moved forward to the next business day, and the moved date is the one you see.
Enabling a service never creates tasks for periods that are already over. To catch up a past filing or remittance that is still owed, create it from the Tasks page: choose "Service task (past period)", pick the client, the service, and the past periods you need (up to five years back) — the due dates are computed for you.
Disabling a service removes its future, not-yet-finished tasks. Tasks you have already completed are kept as history.
If you later change the client's fiscal year-end or partner composition, the client is flagged for recalculation and these tasks are regenerated to match.
If you change a service's assignee later, every open (not yet finished) task of that service moves to the new person, including tasks that had been reassigned by hand, and the new assignee receives one summary notification (unless they opted out of assignment notifications). Finished tasks keep their history.
Re-enabling or regenerating the same service does not create duplicate tasks. Periods that already exist are left as they are.

Only upcoming tasks exist: the next occurrence of an annual filing, the next two quarters, the next three months (payroll keeps its own short window). Future tasks appear automatically as their period approaches. Past periods are only created by you, deliberately, from the Tasks page.
One-off (custom) tasks are never created by this process. They are created by hand.