Late payment follow-ups work when they are short, factual, and escalated in steps. Copy these VA scripts for day 3, day 10, and day 21, plus what never to say.
9 min readWhy desperate follow-ups fail
Desperate sounds like:
- "I really need this for rent"
- "I've waited long enough!!!"
- "I guess you don't value my work"
- Five paragraphs of context the client will not read
Clients do not pay faster when you perform stress. They pay when their finance team can pay a clear invoice and when ignoring you has a consequence (paused work, not drama).
Professional follow-ups sound like billing follow-up, not a breakup text.
The escalation ladder (overview)
| Stage | Timing | Tone | Goal |
|---|---|---|---|
| Nudge | Due date + 1 to 3 days | Warm, assumptive | Unblock admin |
| Direct | + 5 to 7 business days | Calm, specific | Yes/no on status |
| Structured | + 14 days | Documented | Paper trail |
| Boundary | + 21 to 30 days | Firm | Pause work, new terms |
Match each stage to one channel (email preferred). Do not blast Slack, email, and SMS same day.
Script 1: Friendly nudge (due date + 1 to 3 days)
Subject: Invoice [#1042]: quick check-in
Hi [Name],
Following up on invoice #1042 for VA support ([date range]), USD $880, due [date].
Happy to resend the PDF or add anything finance needs. What date should I expect payment?
Why it works: Specific, short, assumes payment is coming, offers help.
Script 2: Assumptive help (they opened invoice but did not pay)
Subject: Invoice [#1042]: finance details?
Hi [Name],
I saw invoice #1042 may still be open on your side ($880, due [date]). If Wise details or a PO number would help, I can send them today.
Please confirm when finance will process so I can mark it on my end.
Why it works: No accusation. Positions you as easy to pay.
Script 3: Direct ask (5 to 7 business days after Script 1)
Subject: Payment status: Invoice [#1042]
Hi [Name],
Checking in again on invoice #1042 (USD $880, due [date]). Work for [period] was delivered and confirmed [date].
Can you confirm whether payment is scheduled this week, or if something is blocking processing?
Why it works: One question. Binary answer possible.
Script 4: Pause boundary (14 days overdue)
Subject: Invoice [#1042]: need alignment before next tasks
Hi [Name],
Invoice #1042 ($880, due [date]) is now [14] days past due. I want to continue supporting [project], but I need this invoice resolved before I take on the next task batch.
Please confirm payment by [date] or suggest a time for a 15-minute call to align.
Why it works: Consequence without insult. Future work is conditional, not withdrawn forever.
Script 5: Documented summary (21+ days, last structured email before walk-away)
Subject: Account summary: Invoice [#1042] open balance
Hi [Name],
Open balance: USD $880 | Invoice #1042 | Due [date] | [days] days overdue
Background:
- Agreed terms: [rate], Net [15], biweekly billing
- Period: [dates] | Deliverables: [brief list]
- Invoice sent: [date] | Follow-ups: [dates]
Please remit by [date] via Wise to [details] (reference: Invoice #1042).
If we continue after this is closed, future work will be on [weekly pay / deposit / Net 7] terms.
Thank you, [Your name]
Why it works: Finance forwards this. It is scannable. It shows you are organized, not emotional.
Script 6: Slack or chat (keep it shorter than email)
Hey [Name]: quick one: any update on invoice #1042 ($880, was due [date])? Finance need anything from me?
Chat is for nudge, not for 21-day escalation. Move serious stages to email for the trail.
What never to say (and what to say instead)
| Desperate / weak | Professional replacement |
|---|---|
| "Sorry to bother you again" | "Following up on invoice #1042" |
| "I hate asking but..." | "Can you confirm payment status?" |
| "You promised to pay Friday" | "Last week you mentioned Friday: did finance process?" |
| "I'll keep working while we sort it" | "I'll resume next tasks once #1042 is closed" |
| "Legal will contact you" (day 3) | Save legal language for last resort after documentation |
Tone principles that keep dignity
- Facts before feelings: invoice number, amount, date
- One ask per message: status OR date OR call, not all three essays
- Same thread: reply to original invoice email
- Business hours: Tuesday 9am client time beats Sunday 11pm
- Rhythm, not spam: wait 5 to 7 business days between stages unless client responds
Pair scripts with payment terms
Follow-ups land harder when terms were already agreed. If you never wrote Net 15 (pay within 15 days) or pause clauses, client hears your reminder as preference, not policy.
Use payment terms for virtual assistants before the next engagement.
Generate scripts with Salag Payment Reminder
The Payment Reminder tool builds follow-ups from your inputs:
- Invoice amount and due date
- Days overdue
- Tone (friendly, firm, final)
- Relationship context (retainer vs one-off)
Use it when you are tired and might write something you regret. Same structure as the scripts above; tailored to your invoice.
Also available inside Invoice Generator for Pro users tracking open invoices.
Related reading: chasing overdue invoices and client silent before payment.
After they pay (close the loop professionally)
Thank you, received $880 for invoice #1042 on [date]. Marked paid on my end. Next invoice for [period] goes out [date] as usual.
Gracious close preserves the relationship for retainers worth keeping.
How Salag helps
- Payment Reminder: AI-assisted scripts at each escalation stage
- Invoice Generator: clear invoices that make follow-ups factual
- Late Fee Calculator: model late fees if your terms include them
Bottom line
Follow up on late payment like a professional vendor: short, specific, escalated. Desperation delays payment; clarity speeds it. Copy the scripts, adjust brackets, send on rhythm. Your work deserves the same respect as any other line item on their books.
Move safer. Not faster.
In short
To follow up on a late payment without sounding desperate, send short, factual messages that reference invoice number, amount, due date, and completed work. Escalate tone in steps (friendly → direct → documented), never plead. Use the scripts below or generate tailored versions with Salag's Payment Reminder tool.
Common questions
To follow up on a late payment without sounding desperate, send short, factual messages that reference invoice number, amount, due date, and completed work. Escalate tone in steps (friendly → direct → documented), never plead. Use the scripts below or generate tailored versions with Salag's Payment Reminder tool.
Reference the invoice number, amount, due date, and deliverables already completed. Keep messages to 3 to 5 sentences. Assume administrative delay, ask one clear question, and avoid personal pleas or emotional language.
First follow-up: 1 to 3 business days after due date. Second: 5 to 7 business days later. Third: 14+ days with a documented summary and pause on new work.
Invoice number, amount, currency, due date, work period or deliverables covered, payment method details, and one ask (confirm status or payment date).
No. You are not rude for expecting agreed payment. Professional tone is neutral and factual, not apologetic or aggressive.