Make your invoices collect themselves. The lever isn’t more chasing — it’s fewer clicks to pay, consistent timing, and smart prioritization you can run on autopilot.
The gap: even with reminders, you’re leaking cash if the pay link is buried, timing ignores time zones, and every account gets the same tone.
Why it matters: clean cadence + one-click pay + focused calls typically pushes more invoices into the “paid by Day 7–14” window and lifts working capital without adding headcount.
Field lesson: the biggest uplift isn’t a harsher email — it’s frictionless payment and early clarity. Put the pay link top line, offer a plan before the final notice, and route exceptions fast.
Standard operating playbook (do this once; it runs every invoice)
- Invoice design: first line shows amount + due date + a single, bold pay link. Add a QR code if customers pay on mobile. Keep terms in one sentence.
- Tokens: store per-invoice fields: [NAME], [INV], [AMOUNT], [DUE_DATE], [PAY_LINK], [PHONE], [SEGMENT], [LATE_COUNT].
- Timing windows: schedule by customer time zone. Avoid weekend sends for first two touches; shift to Monday 9–11am local.
- Subject line formula: “Action: [INV] — [AMOUNT] due [DUE_DATE]” for business email deliverability. Avoid ALL CAPS or “Final” early on.
- Cadence at creation: Due-3 heads-up; Due-day reminder; Due+5 friendly; Due+12 firmer + plan; Due+20 final + phone flag. Auto-pause on payment or dispute.
- Segments: Low risk = gentler copy; Medium = earlier plan offer; High = phone by Day 12; VIP = human review before final.
- Click tracking: if no click on Due+5, bump priority score and queue for a 60–90 second call.
- Phone play: call script aims for a date or plan in one call; log reason code (cash flow, dispute, wrong contact, other).
- Consolidation: multiple open invoices = one weekly statement, not five emails. Cap touches to one every 72 hours.
Copy-paste assets (ready to use)
- Subject lines (choose one):
- “Action: invoice [INV] — [AMOUNT] due [DUE_DATE]”
- “Quick heads-up: [INV] due [DUE_DATE] — pay link inside”
- “[NAME], can we wrap up [INV] today? [AMOUNT]”
- Voicemail (30 sec): “Hi [Name], this is regarding invoice [INV] for [AMOUNT], due [DUE_DATE]. You can pay at [PAY_LINK]. If timing’s tight, call [PHONE] and we’ll set a short plan. Thanks.”
- Payment-plan default: “Two instalments: 50% today, 50% in 14 days. Reply ‘PLAN’ to confirm and we’ll send both links.”
Robust AI prompts (paste into your AI assistant)
- Personalized reminder writer: “You are an AR collections assistant. Draft a 5-step reminder sequence for a customer segment = [SEGMENT] with late_count = [LATE_COUNT]. Use our cadence: Due-3, Due, Due+5, Due+12 (offer a two-instalment plan), Due+20 (final + phone). Each email ≤60 words, clear, polite, with placeholders [NAME], [INV], [AMOUNT], [DUE_DATE], [PAY_LINK], [PHONE]. Return as a numbered list with subject lines.”
- Reply triage to next action: “Classify this customer reply into: Paid, Dispute, Needs Plan, Wrong Contact, Out of Office, Other. Extract any date. Recommend the exact next message (≤60 words) and whether to pause automations. Respond in JSON: {category, promise_date, recommended_message, pause}.”
What to expect
- More payments in the first 7–14 days post-due as pay friction drops.
- Clearer focus for phone calls (top 10 scored accounts first).
- A few tweaks after the first billing cycle as tone and timing are tuned.
Scoreboard (track weekly)
- % invoices paid by Due+7 and Due+14.
- Days Sales Outstanding (DSO) trend.
- 30+ day AR as % of total AR.
- Click-to-pay rate and reply rate.
- Promise-to-pay kept rate.
- Average touches per invoice (target: under 3).
Mistakes that stall cash — and fixes
- Hidden pay link → Put it in the first line and as a button; add a QR code for mobile payers.
- Same tone for all → Apply segment-specific copy and shorten gaps for high-risk.
- No stop rules → Auto-pause on payment or dispute; one touch per 72 hours.
- Only email → Add a short call by Day 12 for high-value or repeat-late accounts.
- Weekend blasts → Send business hours in the customer’s time zone.
One-week action plan
- Day 1: Add tokens to your invoice template and place the pay link on line 1. Verify all links work.
- Day 2: Segment customers (Low/Medium/High/VIP) and record late counts. Create the 5-touch cadence and stop rules.
- Day 3: Generate segment-specific templates with the AI prompt above. Insert subject line formulas.
- Day 4: Implement priority scoring and a 90-second call script. Set a daily “Top 10” call list.
- Day 5: Turn on reply classification with the JSON prompt; route Disputes to a human inbox immediately.
- Day 6: Live test on 10 invoices. Check deliverability, clicks, payments, and reply routing.
- Day 7: Review metrics; adjust timing by time zone; lock in default plan terms (2 instalments over 14 days) if allowed by policy.
Insider tip: schedule the entire cadence the second you issue the invoice. Don’t wait for lateness — you’re building a rhythm that removes decision fatigue and keeps money moving.
Your move.
