Dunning is the automated sequence of reminders for overdue invoices. Servicio ships with a sensible default: friendly at 3 days, firmer at 7, escalating at 14, final notice at 30.
The default cadence
- Day 3 after due date: friendly reminder email. "Hey, just a nudge — this one is a few days past due."
- Day 7: second email + SMS. "Still open — let us know if there is an issue."
- Day 14: escalation. "Action required. Please reach out if there is a problem."
- Day 30: final notice. "This is our last automatic reminder. We will pause future service until this is resolved."
How it works under the hood
When an invoice is issued with a due date, the scheduler creates four dunning_actions rows keyed to that invoice — one per step. Each has a scheduled_for timestamp. A cron runs every 10 minutes, picks up any action whose time has come, and fires the appropriate message template.
When the client pays, all pending dunning actions on that invoice are auto-cancelled. No more reminders. The cadence stops gracefully.
Customizing per tenant
You can override the cadence for your shop under Settings → Dunning (coming Q3 — currently configured via support):
- Shift the day intervals (e.g., 5/10/21/45 instead of 3/7/14/30).
- Remove a step (e.g., skip the day-7 SMS).
- Change the templates used at each step.
Per-client overrides
For clients on net-30 or net-60 terms, you can adjust their individual dunning:
- Set their
payment_terms_dayson the client detail page. - Due dates are computed from this value (default 0 = due on issue).
- Dunning still runs, but from the updated due date, so a net-30 client does not get dunned on day 3 for an invoice issued yesterday.
AI-drafted reminders
For manual collections (outside the automated cadence), the invoice detail page has a "✨ Draft AI reminder" button. Click it; Claude drafts a tone-appropriate reminder based on the invoice age, history with the client, and any prior reminder count. Edit and send.