Weekly, monthly, quarterly or yearly, every N periods. The schedule shows you the next three dates while you are still setting it up, so you can see the rhythm before you commit to it. For work with a fixed end and named milestones rather than a rhythm, that is a contract instead.
Draft or issued
Raise it as a draft you look at first, or tick Issue it without asking me, which marks the schedule Sends itself: each invoice is then raised already marked sent and counts as owed from its date. Neither way emails it to your client; send it from its page or share its link. Starting with drafts and moving to Sends itself once you trust it is the safer order. Either way it becomes an ordinary invoice once it is issued, with the same chasing behind it.
Two brakes, on purpose
- A maximum number of invoices. A schedule everybody has forgotten about cannot bill a client forever.
- Bounded catch-up. If a schedule has not run for eight months, it raises the ones it missed up to a limit and logs the rest, rather than emitting a silent flood of documents into somebody's inbox.
Safe to run twice
Each schedule moves its own clock forward as it raises. A job that fires twice, or a retry after a timeout, finds a date in the future and does nothing.
Plan limits apply to a machine exactly as they do to a person: if the workspace is at its invoice ceiling the schedule pauses itself and says so, rather than failing silently every morning.