What to Do When a Client Refuses to Pay

You delivered the work. You sent the invoice. And now the message is some variation of “we’re not paying.” The fastest way to lose leverage in a nonpayment situation is to react emotionally instead of following a clear process.

Below is a practical playbook freelancers can use immediately—focused on verification, documentation, and an escalation ladder you can justify.

1) Start with immediate actions (before you argue)

When a client refuses to pay, your first job is to make the situation “verifiable.” You’re not trying to win a debate—you’re trying to establish the facts and reduce ambiguity.

Verify the invoice and the deliverables

Before contacting them again, do a quick checklist:

• Invoice accuracy: amount, dates, project/job reference, payment terms, and any milestones tied to payment.
• Deliverables shipped: confirm what you delivered, when, and through what channel.
• Scope alignment: if the work changed, confirm you have written change approval (even if it’s “yes, go ahead” in email).

This is also where you catch simple issues that can be fixed fast (wrong PO number, missing milestone reference, invoice sent to the wrong mailbox).

Check the contract/terms you agreed to

Pull the agreement (or proposal with accepted terms) and locate the parts that matter most for nonpayment:

• Payment schedule: when invoices become due (e.g., Net 15/30, upon acceptance, after milestone date).
• Acceptance criteria: what counts as “accepted,” and whether the client must report defects within a timeframe.
• Dispute process: whether the contract says how disputes must be raised and by when.
• Late fees/interest: if your jurisdiction/contract allows it and it’s included in your terms.

If the client’s refusal is based on “quality,” “timing,” or “expectations,” you’ll want to compare their complaint to the acceptance criteria.

Confirm what they’re actually disputing

Clients often refuse payment without clarity. Your goal is to force a specific claim.

Ask yourself:

• Are they disputing scope (work not included)?
• Are they disputing quality (work doesn’t meet requirements)?
• Are they disputing acceptance (they didn’t formally accept or report issues in time)?
• Are they disputing process (they claim they never approved something)?

Then, in your next message, request the dispute in a structured way (more on communication templates below).

The leverage in nonpayment isn’t confrontation—it’s clarity backed by documentation.

2) Gather documentation that actually moves the case

Once you’ve verified basics, assemble the evidence. Think of your file like a small “case packet” you can reference across emails, escalation steps, and any potential collections/ADR process.

Include as many of these as you have:

Core documents

• Agreement / signed contract (or proposal and acceptance trail).
• Statement of work / project scope and any approved amendments.
• Invoice(s) plus proof of when you sent them.

Communication and approval trail

• Email thread showing what was approved, requested, and delivered.
• Approval messages (e.g., “looks good,” milestone sign-off, or documented review/approval).
• Change requests and your responses.

Proof of delivery and acceptance

• What you delivered: files, links, repos, screenshots, or exported artifacts.
• Acceptance criteria and where it’s documented.
• Review cycles: dates the client reviewed, what feedback they gave, and what you changed.
• Confirmation of completion: anything that indicates the client considered the milestone finished.

Time and work records (when relevant)

• Timesheets / activity logs (especially for hourly or T&M work).
• Meeting notes or call recordings (only if your practices comply with local law and your contract).
• Session deliverables (design drafts, outlines, prototypes) tied to dates.

If you’re missing a piece (like acceptance documentation), don’t panic. You can still strengthen your position with what you do have—but you’ll want to be transparent about what was agreed.

Many freelancers also find they’re dealing with deeper process gaps—missed acceptance steps, vague scope, or weak invoicing cadence. A quick way to sanity-check those blind spots is the Freelance Business Check.

3) Use an escalation ladder (and keep it professional)

Escalation works best when it’s predictable. Move from friendly to formal without changing your core message: what is owed, why it’s owed, and what happens next.

Below is a common ladder you can adapt to your contract and local norms.

1. Polite reminder (fact-based)

• Short, neutral tone.
• Restate invoice details and due date.
• Ask for a specific dispute if they believe payment isn’t due.

2. Formal notice (written record)

• Reference contract terms (payment schedule, acceptance/dispute process).
• Attach the invoice and relevant delivery/approval proof.
• Set a clear deadline for resolution.

3. Stop-work / withhold future work (where applicable)

• If the contract allows it, pause further work until payment is settled.
• Avoid threats you can’t carry out—state your operational boundary instead.

4. Late fees/interest (if included in your terms)

• Only apply if your agreement says you can.
• Calculate carefully and show your math.

5. Collections / ADR options

• Some contracts include arbitration/mediation clauses.
• Where appropriate, consider a collections agency or legal avenues.
• Keep in mind costs, time, and your desired outcome (full payment vs. partial settlement).

What to avoid during escalation

• Long emotional emails. They feel honest, but they reduce your credibility.
• “You owe me because you promised.” Use terms and documentation instead.
• Over-offering fixes with no acceptance loop. If you do extra work, document it as change, and clarify payment implications.

4) Communication templates you can reuse

You don’t need to write from scratch every time. The goal is consistent messaging with the right level of detail.

Template A: Polite reminder (Day 1)

Subject: Re: Invoice #[number] — payment status request

Hi [Client Name],

I wanted to follow up on invoice #[number] for [milestone/deliverable] dated [date], due [due date].

As a reminder, the deliverables for this milestone were [brief description] delivered on [delivery date] via [link/channel].

If you believe the invoice is not due, could you please reply with the specific items you dispute and reference the applicable acceptance criteria or contract terms?

If I don’t hear back by [deadline], I’ll move forward with the next step under our agreement.

Thanks, [Your Name]

Tone notes: calm, factual, and short. Include: invoice number, deliverable reference, and a request for specific dispute.

Template B: Formal notice (after deadline)

Subject: Formal notice: unpaid invoice #[number] by [deadline]

Hi [Client Name],

This message serves as a formal notice regarding unpaid invoice #[number] for [amount]. The invoice was due on [due date] under our agreement dated [agreement date / reference].

Delivered for this invoice:

• [Deliverable 1 + delivery date]
• [Deliverable 2 + delivery date]

If you dispute payment, our agreement requires disputes to be raised with specific details by [contract dispute timeline] and tied to acceptance criteria. To date, I have not received a documented dispute outlining what is being rejected and why.

Please confirm by [deadline]:

1. whether payment will be made, or
2. the specific aspects of the deliverables you dispute (with references to acceptance criteria).

Otherwise, I will proceed to the next escalation step available under our agreement.

Sincerely, [Your Name]

Tone notes: firm, not hostile. Include: contract reference, delivered items, dispute requirements.

Template C: Withhold future work (operational boundary)

Subject: Work pause pending payment — invoice #[number]

Hi [Client Name],

Until invoice #[number] is paid (due [due date]), I will need to pause additional work on [project/task] to keep billing and scope aligned.

I’m available to discuss any specific acceptance issues so we can close them with minimal back-and-forth. If payment is processed by [date], I can resume work on [next milestone] promptly.

Thanks, [Your Name]

Tone notes: boundary and options, not threats. Include: what you’ll stop, what you’ll do instead (discussion), and a resume condition.

Template D: Settlement offer (optional, for pragmatic outcomes)

Subject: Proposal to resolve invoice #[number]

Hi [Client Name],

To resolve the unpaid balance for invoice #[number] in a timely way, I’m open to the following settlement approach:

• Payment of $[amount] by [date]
• Confirmation that the remaining balance is [waived/forgiven] (only if that matches our discussion)

If you’d prefer a different resolution, please share your proposal by [deadline], including any specific disputed items.

Best, [Your Name]

Tone notes: cooperative but anchored. Include: a concrete option and a deadline.

5) Safety note: don’t treat this as legal advice

Nonpayment can cross into legal territory depending on your contract, your jurisdiction, and the facts. Use this playbook as operational guidance, but for anything involving late fees/interest, collections, or formal legal steps, get advice from a qualified local professional.

If you want the prevention side of this story (so “refuse to pay” happens less often), build your invoicing and acceptance workflow around clear milestones, documented approvals, and consistent follow-ups. Even a straightforward client portal and centralized process can help you keep all the moving pieces in one place—without relying on memory or scattered email threads.

Related reading: How to Follow Up on Unpaid Invoices: Mistakes to Avoid · How to Deal With Difficult Freelance Clients (Step-by-Step)

Conclusion: Keep your process, protect your leverage

When a client refuses to pay, your best move is to switch from negotiation-as-emotion to negotiation-as-evidence. Verify invoice details and deliverables, confirm what’s disputed using your contract terms, gather a tight documentation packet, then follow an escalation ladder you can justify.

If you’d rather spend your energy on the work you’re paid for, make your next step easier by systematizing invoices, acceptance criteria, and client communication—tools like Jolix can help centralize those workflows so nothing important falls through the cracks.