Understanding Suivi: compliance seen by service
Why Suivi exists, what each row really represents, and how it replaces the tracking workbooks firms used to keep by hand.
Where Suivi comes from
Before ComptaFlow, a firm's compliance tracking lived in dedicated workbooks: Suivi_T2.xlsx for corporate tax, client_TPS_TVQ_DAS.xlsx for sales taxes and source deductions, Suivi_Tenue_de_livre.xlsx for monthly bookkeeping. Each workbook answered the same question for one service: where does every client stand?
Suivi is the living version of those workbooks: one grid per service, fed automatically by the generated tasks, never retyped by hand. Where the Tasks board answers "what am I doing today?", Suivi answers "where does THE FIRM stand on this service?".
What a row means
By default, Suivi shows one row per client for the service you are viewing: that client's open instance nearest its deadline (the pick is deterministic, always the same for the same data). The row carries the deadline, the status in your firm's workflow, the checklist progress, and the task's assignee.
The late-only mode changes the grain: every open overdue period becomes its own row. A client who owes three late GST/QST returns occupies three rows; the backlog becomes visible and countable instead of hiding behind a single "late" flag.
How services are grouped
Suivi's grids are organized in groups derived from the catalog's categories: bookkeeping (books and sales taxes), payroll, personal slips, and year-end (corporations, trusts, nonprofits). If your firm customizes its categories, the groups follow.
One deliberate special case: instalment schedules (personal instalments, GST/QST instalments) do generate dated tasks, but they are excluded from the Suivi grids. They are payment reminders, not a production flow to move through stages; they live on the task board and the calendar.
What the firm gains
- The master view: what is late, what is coming, and who owns it, service by service, with nothing compiled by hand.
- Effective follow-up: a task marked blocked (waiting on the client) stays visible in the grid with its reason; "we were waiting on them" becomes dated management information.
- Team load: the assignee column shows how a service's work is really distributed.
- The same number everywhere: Suivi reads the same tasks as the board, the calendar, and the reports; it cannot tell a different story.
To act on this
- Follow a service's deadlines in Suivi: the grid, the filters, and the late-only mode, step by step.
- See deadlines on the calendar: the same tasks, month view.
- Understanding fiscal deadlines: where the dates in the grid come from.