The customer-friendly collections cadence: 3 reminders, 1 report

A steady reminder rhythm beats heroic chasing. In SaaS and B2B, the goal is simple: get paid on time without torching the relationship.

This post gives you a cadence we run every day: three reminders and one weekly report. It is light enough for a small team, but strong enough to stop overdue AR from creeping up.

Why cadence matters in SaaS AR

The cost of “random chasing”

Most AR mess happens in the gaps. Teams send a reminder late, then follow up whenever someone remembers. Customers feel ambushed. Your team feels awkward. Cash slips.

A predictable cadence fixes two things:

1. Your buyers know what to expect.
2. Your team knows what to do next.

Stripe and other billing platforms point to gradual, consistent reminders with a human tone as a core dunning best practice.

What “customer-friendly” actually means

Customer-friendly does not mean soft. It means:

• Clear dates and amounts.
• No guilt trips.
• Easy next step (pay link, PO request, portal link).
• Quick handling of replies.
• Escalation that is about process, not emotion.

Think “polite train timetable”, not “panic sprint”.

The 3-reminder, 1-report cadence (overview)

Here is the high-level flow:

1. Reminder 1 (pre-due): a calm heads-up.
2. Reminder 2 (due date): a simple nudge.
3. Reminder 3 (overdue): firmer, still respectful, with a clear path to resolution.
4. Weekly AR report: one page on risk, blockers, and actions.

We plug into your tools, read every reply, tag the reason, and push blockers to your team so cash keeps moving.

Step-by-step: how to run the cadence

Reminder 1 – pre-due “heads-up”

Timing: 7–10 days before due date for net-30 terms.

Goal: prevent surprise and surface blockers early.

What it says:

• Invoice number, amount, and due date.
• “Flag any issues now so we can fix them before due.”
• A link to pay or portal step.

Tone: friendly and practical.

Why it works: pre-due reminders catch missing PO and portal onboarding before they turn into 45-day delays.

Reminder 2 – due-date nudge

Timing: on the due date (morning, customer’s timezone).

Goal: make paying today the easy default.

What it says:

• “Invoice is due today.”
• Pay link / portal action.
• A short “reply if you need anything”.

No long story. No passive-aggressive “as per our records”.

Reminder 3 – overdue escalation (still polite)

Timing: 5–7 days after due date, then weekly if needed.

Goal: get a committed next step.

What it says:

• “Invoice is now overdue by X days.”
• Clear ask: “Please confirm payment date or tell us what is blocking it.”
• If you have a CS owner, copy them after a threshold.

You are not threatening. You are making the path obvious. ICAEW guidance on chasing debtors also stresses starting informally but being clear about next steps if delays persist. 

Realistic overdue email snippet

Subject: Quick check-in on invoice 10482 (now overdue)

Hi Jamie,

Hope you’re well.

Invoice 10482 for £6,400 was due on 18 November and is now 7 days overdue.

Can you confirm when payment is scheduled?

If anything is blocking it (PO, portal step, or a query on the invoice), reply here and we’ll sort it today.

Pay link: [link]

Thanks,
BSB AR Team (on behalf of Acme Software)

Short, direct, no drama.

The weekly AR report – what it must include

Timing: same day each week.

Audience: founder/COO/finance lead.

Keep it one page. The job is visibility and decisions, not a data dump.

Minimum sections:

• Total outstanding, total overdue, and over-30-day AR %.
• Top 10 overdue invoices by value and age.
• New disputes this week and status.
• Blockers list with owner and next action.
• Expected cash next 14 days (based on confirmed dates).

Reply triage: the part most teams miss

The cadence is only half the system. The other half is what you do with replies.

Stripe highlights that reminders should adapt based on customer response and status. That is where teams often fall over.

Late vs dispute vs missing PO/portal

Every reply fits one of four buckets:

1. Late but fine
   • “Paying next week”
   • Action: confirm date, set follow-up on that date.
2. Dispute / query
   • “We were billed for extra seats”
   • Action: tag as dispute, ask for specifics, loop in the right internal owner.
3. Missing PO / vendor setup
   • “Need a PO before we can pay”
   • Action: ask for PO process and internal buyer details.
4. Portal / onboarding step
   • “Please submit in Coupa/Ariba”
   • Action: do the portal workflow or push it to the internal team if access is needed.

How we push blockers to your team

We read every reply the same day, tag the reason, then post the blocker into your internal channel with a clear ask.

Example:

• Blocker: Missing PO.
• Owner: Sales Ops.
• Ask: “Can you confirm PO contact and process for Globex? They won’t schedule payment until PO is raised.”

That speed is what keeps the cadence polite. If you reply slowly, even the nicest reminder feels pushy.

A simple cadence table you can copy

Step	Timing (net-30)	Who gets it	Purpose	If they reply…
Reminder 1	7–10 days pre-due	Billing + owner	Prevent surprise, catch blockers	Tag reason, fix blocker
Reminder 2	Due date	Billing	Nudge payment today	Confirm pay date
Reminder 3	5–7 days overdue, then weekly	Billing + add buyer/CS if needed	Secure a date or escalation path	Tag reason, push blocker
Weekly report	Same weekday	Founder/COO/Finance	Visibility + decisions	Agree actions, re-prioritise

Metrics that tell you if it’s working

Track these weekly:

• Over-30-day AR % (value).
• Median days to pay (by customer cohort).
• Reply-to-pay conversion (replies that end in payment within 14 days).
• Dispute rate (count and value).
• “Blocker ageing” (days a blocker stays open internally).

You do not need a BI project. A clean sheet and consistent tags are enough.

Common pitfalls (and fixes)

• Pitfall: sending the same reminder three times. Fix: escalate purpose, not tone. Each reminder should add clarity or a next step.
• Pitfall: no owner for replies. Fix: one inbox, one person accountable daily.
• Pitfall: late internal action on PO/portal steps. Fix: push blockers into the channel where work happens, not into a quiet spreadsheet.
• Pitfall: founders only see AR when it’s ugly. Fix: weekly one-pager, even in good weeks.

What a small team can do this week

1. Lock the three dates into your billing tool or calendar.
2. Write one template per step. Keep them short.
3. Create four reply tags (late / dispute / PO / portal).
4. Decide your internal blocker channel and owner.
5. Send a one-page AR report on Friday.

That is it. Cadence first. Perfection later.

A short scenario

You send Reminder 1 to a mid-market customer. They reply: “We need this in Ariba and a PO raised.”

Because you caught it pre-due:

• You submit in Ariba that day.
• You ask for the PO contact.
• Your sales ops owner raises the PO within 48 hours.
• Payment lands on time.

Without that heads-up, you would have found out after the due date, and the invoice would drift into “next month”.

Next step

If you want this cadence running without adding headcount, we can take it on.

We plug into your tools, run the three reminders, read every reply, tag the reason, and push blockers to your team so cash keeps moving. Polite, on-brand reminders. Zero damage to relationships.

See “Lite AR Essentials”, “Managed AR Ops”, and “AR + Portals & Onboarding” on our Services page. If you’d rather talk it through first, Get in touch.

---

Want a predictable, customer-friendly chase process without hiring a full AR role?

Read about our options: Lite AR Essentials, Managed AR Ops, and AR + Portals & Onboarding. Each one includes reply triage and weekly reporting. Visit services to see what fits your stage.

---

Compliance & clarity: This post is general AR operations guidance, not legal or accounting advice. Adapt to your contracts and local rules. We have not used any private client data, and any examples are illustrative.