Set up recurring services and cadences
Recurring work fails at the definition layer: which clients get monthly bookkeeping, who files GST/HST quarterly versus annually, what the standard price is. When none of that exists as structured data, each period's calendar is rebuilt from memory. Cadence changes arrive by email and quietly never make it into the plan.

Firms define recurring work in the SpidNums Services catalogue: each service has a type, a code, a frequency — one-time, monthly, quarterly, semi-annual or annual — and a default price. Assigning a service to a client, with per-client overrides where needed, sets a next-due date, and that date is what drives the Reminders feed and the SLA colours.
How firms run it, step by step
Build the catalogue once
Create the firm's typed services — bookkeeping, GST/HST, T4, T5, year-end financial statements, corporate tax, personal tax — each with a code, a default frequency and a default price.
Services catalogue
Assign services per client
Attach each client's actual services to their record. Assignment is what creates the next-due date, so an unassigned service is invisible to the deadline feed by design.
Services catalogue
Override where a client differs
Price and cadence override per client, so the quarterly GST/HST default coexists with the one client CRA has on monthly, without duplicating the service.
Services catalogue
Let next-due drive the feed
Each assigned service's next-due date flows into Reminders, grouped Overdue, Due soon and Upcoming — the recurring calendar exists without anyone rebuilding it each period.
Reminders
Watch the cadence on the dashboard
The recurring-revenue chart shows what the assigned services add up to, which is also a quick audit for clients missing an obvious service.
Dashboard & SLA
Services catalogue
Reminders
Dashboard & SLA
Related use cases
Features used
Go deeper
Frequently asked questions
Does SpidNums automatically create projects for recurring work?
Recurring work is driven by service frequency and next-due dates: the catalogue sets the cadence and the Reminders feed raises each period as it approaches. Opening the period's project in Task Master is a deliberate step taken when the work starts — which is also the moment you know who is doing it.
What service frequencies does SpidNums support?
One-time, monthly, quarterly, semi-annual and annual. Frequency is set on the service in the catalogue and can be overridden per client, so a quarterly default coexists with the handful of clients on a different reporting period.
Can two clients pay different prices for the same service?
Yes. Each service carries a default price in the catalogue, and per-client assignment supports overrides — so the standard bookkeeping rate can differ for the client with triple the transaction volume without creating a second service.
See this workflow with your own client list in it.
A tailored demo walks the exact steps above with your services and deadlines.