Guide
Both send the same five reminders. One depends on a person remembering; the other depends on a schedule. Here is what actually changes when a firm moves from chasing by hand to a fixed collection ladder — and where manual chasing is still the right answer.
The two approaches are usually described as opposites, but they run the same playbook. The difference is who executes it.
Judged on the things that decide whether an overdue invoice is actually collected, not on how modern either approach sounds.
| Dimension | Manual chasing | Collection ladder |
|---|---|---|
| Who sends it | A person, when they remember | The schedule — every day, unattended |
| Timing accuracy | Slips under workload; often batched at month end | Fixed days: −3, 7, 35, 50, 65, 95 |
| Volume of email | Per invoice — five overdue invoices can mean five emails | Per customer — one email listing everything overdue |
| Tone consistency | Depends on the sender's mood and seniority | Tone matched to the rung, every time |
| Data freshness | Whoever is chasing may be working from a stale export | Balance, days late and PDFs read on the day of sending |
| Record for disputes | Scattered across sent items and personal notes | Every rung logged per customer |
| Cost of scaling | Grows linearly with clients and invoices | Flat — the ladder runs the same at 5 clients or 50 |
| Best fit | A few invoices, delicate relationships, first contact | Repeatable AR across many customers and ledgers |
Firms rarely abandon manual chasing because the emails are badly written. They abandon it because of these four failure modes, all of which are about process rather than prose.
Six rungs, one per customer, escalating in tone but never in volume. This is the cadence Settl runs by default — the wording is yours, the timing is not negotiable.
The invoice exists and is due shortly. Most late payments are avoided here, before anything is technically overdue.
Warm and factual: did the invoice arrive, is payment scheduled. No leverage used yet, because none is needed.
The conversation moves to the number: amount outstanding, days late, and a request for a payment date.
A short restatement with the total due across all open invoices, so nothing is buried in an earlier thread.
Terms are applied: late fee if the engagement allows it, work paused until the balance clears. Stated as policy, not as a threat.
The last step before collections, repeated on a fixed interval until the invoice is settled or written off.
A ladder is a policy, and policies are blunt. Keep a human in the loop for the exceptions: a first conversation with a large new client, a payment plan being negotiated, or an account where a written reminder would do more harm than a phone call. The honest position is not that automation replaces judgement — it is that judgement should be spent on the handful of accounts that need it, not on sending day-7 emails forty times a month.
A fixed sequence of reminders sent at set intervals after an invoice is issued — for example a pre-due heads-up, a check-in at day 7, a firm follow-up at day 35, an urgent warning at day 65 and a final notice at day 95. Each rung has a defined day and a defined tone, so the next step never depends on someone remembering to send it.
For a handful of invoices, manual chasing is fine. Once a firm is chasing across several client ledgers, a ladder is better on the things that decide whether a reminder actually goes out: it does not depend on memory, it batches one email per customer, it keeps the tone consistent, and it leaves a record of what was sent and when.
No — the failure mode clients notice is inconsistency, not automation. A scheduled ladder sends one calm, factual email per customer per stage from the firm's own address. What reads as impersonal is five separate emails about five separate invoices in one week, or silence followed by an abrupt final notice.
The design work is quick: pick your rungs, days and tone, then write one template per rung. The slower part is connecting the source of truth for open invoices and payment status, so balances, days-late figures and attached PDFs are current on the day the email is sent. Firms that already keep clean AR in QuickBooks Online or Xero are most of the way there.
Yes. Settl sends reminders as the firm — its own name, sender address and tone — from a private instance, so the ladder reads as the firm's own process rather than a third-party system.
Every morning Settl reads the firm's open invoices, groups them by customer, and sends the right reminder at the right rung — 7, 35, 50, 65, 80 and 95 days past due — with the PDFs attached, from the firm's own mailbox, white-labelled. No aging report to work through, no rung to remember.
Book a demo See how it works