Refresh: Unpaid VA work is a process problem first. Follow this escalation ladder: verify delivery, send factual reminders, pause work, document, and protect your next engagement.
13 min readThe moment you realize payment is not coming
You checked Wise. Nothing. PayPal is empty. The invoice was opened two weeks ago. No transfer.
As a virtual assistant, you may have logged 40, 80, or 160 hours. The client still sends "one quick thing." Your rent date does not move.
This guide is for that moment. What to do in the first hour, the first week, and when to stop hoping and start protecting.
Step 0: Breathe, then verify facts
Before an angry email, confirm:
| Check | Why it matters |
|---|---|
| Invoice sent to billing contact | Managers approve work. Finance pays. |
| Due date and currency match the agreement | Net 30 (pay within 30 days) vs Net 15 (pay within 15 days) changes your timeline |
| Deliverables were accepted | "I didn't like it" can block payment |
| No open revision dispute | Clients sometimes freeze pay during vague dissatisfaction |
| Correct payment method on invoice | Wrong Wise email causes silent failure |
If anything is unclear, your first message asks for facts. It does not demand payment yet.
Script:
Hi [Name], checking on invoice [#] for [period/deliverable], sent [date], due [date] for [amount]. Can you confirm it reached the right person on finance? Happy to resend or fix any detail.
Step 1: First follow-up (1–3 days after due date)
Assume good intent. Busy founders forget. Finance batches weekly.
Rules:
- 3–5 sentences
- Include invoice number, amount, due date, work period
- One clear ask
- No guilt, no threats
Template:
Hi [Name], following up on invoice [#] for VA support [dates], total [amount], due [date]. Work included [brief list]. Please let me know if finance needs anything else, or when to expect payment. I can resend the PDF if helpful.
Reply on the same thread as the original invoice.
Step 2: Second follow-up (5–7 business days)
Tighten the ask. Make it easy to answer yes or no.
Template:
Hi [Name], checking in again on invoice [#] ([amount], due [date]). Hours/deliverables for [period] were completed and confirmed on [date]. Can you confirm payment status, or tell me what is blocking processing?
Do not:
- Mention how much you need the money
- Threaten legal action yet
- CC their whole company
- Keep shipping new work while waiting
Step 3: Pause new work
Silence plus new requests is the most common VA trap. Client sends tasks. You finish them. Old invoice stays open. Your leverage drops.
Script:
I want to keep momentum, but I need invoice [#] resolved before the next batch of tasks. Can we confirm payment timing this week? Once aligned, I am ready to continue.
Professional, not punitive.
Step 4: Escalation email (14+ days overdue)
Build a paper trail on one screen.
Include:
- Agreement excerpt or onboarding email (rate and terms)
- Delivery proof (approved tasks, timesheet, handoff email)
- Invoice PDF and send date
- Prior follow-up dates
- Two options: pay by [date] OR a 15-minute call
Template:
Hi [Name],
Summary for invoice [#]:
- Agreed rate: [rate] | Terms: [Net 15 / biweekly]
- Period: [dates]
- Deliverables completed: [list]
- Invoice sent: [date] | Due: [date] | Amount: [amount]
- Prior follow-ups: [dates]
Please confirm payment by [date], or suggest a time for a brief call. Future work will require [deposit / weekly pay / shorter terms] once we close this invoice.
Thank you, [Name]
Archive every message. You may need this for platform disputes or tax records.
Step 5: Platform-specific actions
Upwork or OnlineJobs.ph
- Open a payment dispute per platform rules
- Do not move off-platform before payment is resolved
- Log hours in the platform tracker
Direct client (Wise / PayPal)
- PayPal: dispute only if terms apply and you have delivery proof
- Wise: no platform dispute. Contract and email trail are your protection
Retainer with ongoing access
- Pause access to email, calendar, tools until payment clears
- Do not delete work in anger. You may need it as evidence
Red flags: escalate faster
End or restructure if non-payment pairs with:
- "We'll pay after the next phase"
- Requests for more unpaid work
- New stakeholder disowns prior approval
- Payment method changes mid-project
- Ghosting after a large monthly batch
Use the Client Red Flag Checklist before the next engagement.
What NOT to do
| Reaction | Why it backfires |
|---|---|
| Keep working to "prove loyalty" | Trains client to pay you last |
| Public social media callout | Hurts your brand. Rarely collects debt |
| Legal threat in message one | Closes dialogue when delay may be admin |
| Accept "paid when we fundraise" | Speculative payment is not payment |
| Undercharge next month to "keep them" | Rewards non-payment |
Protecting the next client
After non-payment, update your defaults:
- Shorter terms: Net 15 or weekly instead of Net 30
- Deposit: first two weeks upfront for new clients
- Written SOW (scope of work document): scope, hours cap, payment rhythm
- Numbered invoices with reference instructions
- Time logging export weekly
See payment terms every VA should put in writing.
Emotional reality
Non-payment feels personal because VA work is embedded. You were in their inbox and calendar. It is not personal. It is cash flow priority.
Structure gives you something to do besides refresh your bank app. Follow the ladder. Document. Pause.
Related guides
This guide works best with the rest of your protection stack. Start inside Salag: Invoice Generator.
Related guides:
- Invoice Generator
- Late payment follow-up
- Document work clients can't dispute
- Client ghosted recovery
- How to invoice US clients
How Salag helps
- Payment Reminder. Wording for each escalation step.
- Invoice Generator. Invoices finance teams can process.
- Time Ledger. Hour and task evidence if disputes appear.
- Payment Method Risk Check. Check how future clients pay.
Related: What to do when a client goes silent before payment.
- Invoice Generator
- How to invoice US clients
- Wise to GCash fees
- Deposit requirements
- Late payment follow-up
- Payment terms examples
- Proof documentation
- Ghosted recovery playbook
Bottom line
When a client doesn't pay you, treat it as steps, not a panic spiral. Verify, remind, pause, document, update terms.
Move safer. Not faster.
In short
When a client doesn't pay you, stop adding unpaid work. Verify the invoice and deliverables. Send a short factual reminder with invoice number and due date. Then escalate: second follow-up, pause new tasks, documented summary, updated terms.
Common questions
When a client doesn't pay you, stop adding unpaid work. Verify the invoice and deliverables. Send a short factual reminder with invoice number and due date. Then escalate: second follow-up, pause new tasks, documented summary, updated terms.
Verify the invoice was sent to the right contact, confirm deliverables were approved, then send a short factual reminder referencing invoice number and due date. If silence continues, escalate in steps: second reminder, pause new work, summary email with documentation, updated terms for future work.
Send a first reminder 1–3 business days after the due date. Send a second follow-up 5–7 business days later if there is no response. Pause new work before sending emotional or legal threats.
No new milestones or deliverables should ship until overdue invoices are resolved or a written payment plan is agreed. Continuing unpaid work trains clients to deprioritize your invoice.
Only if late fees were in the original agreement or invoice terms. If not, you can propose updated terms for future work, not retroactive penalties without consent.
Consider ending the engagement when silence exceeds 30 days, the client requests more unpaid work, payment methods change without explanation, or disputes appear after delivery was already approved.