Late payment checklist: find the blocker and follow up

An overdue invoice needs a clear record, a payment contact, and a next follow-up date.

Start by checking possible process blockers:

• unclear payment terms,
• missing paperwork (POs, vendor forms),
• internal approval delays,
• or an unresolved disagreement about the work.

This checklist is for your own records when payments start drifting. It’s meant to get you from “I feel awkward” to “I ran the process” in one sitting.

If you want the maintained evergreen system behind this template, read:

• Invoicing + getting paid on time

If you want plug-and-play scripts, open:

• Invoice Template + Late Payment Sequence

If you need contract language that supports enforcement, read:

• Freelance contracts: the clauses that matter

And use:

• Statement of Work (SOW) Template

When to use this checklist

Use this workflow to investigate overdue invoices and delayed payouts. It does not report an increase in late payments across the market.

Use it when you notice:

• multiple invoices slipping past due,
• a client’s “we’re processing it” loop repeating,
• or platform payouts arriving later than expected.

This template does not claim that any specific platform or client behavior changed. It gives you a process to run when late payment shows up.

Who it affects

This template is for:

• freelancers with invoices outstanding past due,
• anyone relying on platforms for payouts,
• contractors working with companies that have procurement/AP processes,
• freelancers whose cashflow stress is rising because money is drifting.

If you don’t have invoices out yet and you’re preventing late payments proactively, start with:

• Invoicing + getting paid on time
• Statement of Work template

What to do this week

Do these three actions in order. Timebox: 30–60 minutes total.

1. Run the follow-up sequence on every past-due invoice (today).
2. Check the agreed payment and pause terms before changing delivery. Propose revised terms for future work where needed.
3. Change your billing terms for new work if risk is high: deposits or milestone billing.

Scripts and templates:

• Invoice Template + Late Payment Sequence
• Statement of Work (SOW) Template

Prevention checklist

Confirming billing details before work starts can prevent avoidable delays. Clarify the process and agree boundaries while the project is calm.

Run this at kickoff (or retroactively this week if you’re already mid-project):

[ ] Confirm invoice recipient: name + email (+ backup)
[ ] Confirm payment method and any portal/steps required
[ ] Confirm required references: PO number, vendor ID, project code (if any)
[ ] Confirm invoice terms: due date format and Net X (in writing)
[ ] Confirm who approves invoices and expected payment run cadence
[ ] Define acceptance criteria + review window in the SOW
[ ] Agree any work-pause rule before relying on it for overdue invoices
[ ] Choose risk-reducing terms for new clients: deposit or milestones
[ ] Put follow-up dates on your calendar (don't improvise later)
[ ] Keep billing updates in one thread per invoice

If you want one paragraph that prevents a lot of “we didn’t see it” loops, send this as part of your kickoff note:

Billing note: I'll send invoices to [AP email] with due date [Net X / Due on YYYY-MM-DD]. Please confirm any required fields (PO/vendor ID/project code) and the expected processing steps so payment doesn't stall later.

The late payment checklist

This is the operational checklist. Copy it into your notes and run it.

Step 1: Inventory (what is actually overdue?)

Make a short list:

• invoice number
• client
• amount
• due date
• days past due
• who you last contacted
• next follow-up date

A written inventory makes it easier to prioritize follow-ups and avoid contacting the wrong person or repeating a resolved request.

Step 2: Quick diagnosis (which pattern is this?)

You’re trying to answer: “Is this a process delay, a paperwork problem, or a risk signal?”

Use these common patterns.

Pattern A: “We didn’t know the invoice was due”

Typical signs:

• client acts surprised by the due date
• invoice had no due date, or terms were not clear
• invoice went to the wrong person

What it means:

• your system and their system didn’t align

What to do:

• resend invoice with clear due date
• confirm AP contact and required fields
• update your onboarding: “Invoices go to X, paid via Y, due Net Z”

Evergreen system:

• Getting paid on time

Pattern B: “Procurement / AP is slow”

Typical signs:

• client says “we need a PO”
• vendor onboarding forms appear mid-project
• “payment runs happen twice a month”
• you’re pushed into a portal you didn’t know about

What it means:

• there may be an incomplete procurement step to verify

What to do:

• ask for a payment date and confirm the process steps
• request the PO (or required reference numbers)
• consider milestone billing for future phases to reduce exposure

Contract layer:

• Freelance contracts: the clauses that matter

Pattern C: “Payment is always ‘next week’”

Typical signs:

• vague promises
• repeated “we’re processing it”
• no concrete payment date
• increasing ghosting

What it means:

• the cause is still unconfirmed; ask for a specific blocker, owner, and payment date

What to do:

• move from polite reminders to “action required”
• check whether your agreement allows a work pause and what notice it requires
• escalate calmly if non-responsive

Scripts:

• Invoice Template + Late Payment Sequence

Pattern D: “We have an issue with the work”

Typical signs:

• payment delay is tied to “concerns”
• they introduce new requirements or disputes after delivery
• they refuse to confirm acceptance criteria

What it means:

• there may be a genuine delivery issue or unclear acceptance criteria
• the reason for withholding payment needs to be stated and checked

What to do:

• refer to your SOW acceptance criteria and review windows
• propose a bounded fix if appropriate (with change request if it expands scope)
• document everything in writing

Use:

• Statement of Work template
• Change Request Addendum Pack

Pattern E: “Platform payout delays”

Typical signs:

• you’re paid through a platform
• your invoice is “approved” but payout date shifts
• platform support points to policy or batch schedules

What it means:

• payout schedules may be batch-based or policy-driven
• you still need runway and risk buffers

What to do:

• track payout cadence
• keep a runway buffer (so one delay doesn’t force bad decisions)
• consider reducing reliance on a single platform for revenue concentration risk

For a platform delay, check the official payout notice and your account status. Record the stated schedule and any support reference in your log.

Step 3: Run the follow-up sequence (procedurally, not emotionally)

The point of a sequence is to remove improvisation.

Example follow-up cadence; adapt it to your agreement, prior replies, and applicable requirements:

• Day 0 (due date): friendly reminder
• Day 3: past due + confirm payment date
• Day 7: action required; consider a pause notice only where permitted
• Day 14: final notice + escalation path

Use the exact scripts here:

• Invoice Template + Late Payment Sequence

Two rules:

1. Ask for a payment date (a commitment), not an apology.
2. Every escalation step should be something you will actually do.

Escalation ladder

This is the ladder you climb when “friendly reminders” stop working. You’re not trying to win a moral argument. You’re trying to get a concrete payment date (or a clear blocker) and reduce further exposure.

1. Confirm receipt. Make sure the invoice reached the right inbox and includes required reference numbers.
2. Ask for a date. Past due means you ask for the scheduled payment date, not reassurance.
3. Escalate the thread. If the person you’re emailing can’t resolve it, loop in the budget holder or project sponsor.
4. Work pause. Check the agreed trigger and required notice before pausing. Confirm any effect on delivery dates in writing.
5. Final notice. State the next step you will actually take if unpaid (formal notice, dispute process, collections, etc.).

Short scripts (templates) you can paste and adapt:

Subject: Invoice [#] past due (payment date?)

Hi [Name],

Invoice [#] for [Project] in the amount of [Amount] was due on [Due date]. Can you confirm the scheduled payment date?

If anything is missing on my side (PO/vendor form/portal step), point me to it and I'll complete it today.

Thanks,
[Your name]

Subject: Action required: invoice [#] (next steps)

Hi [Name] and [Sponsor],

Looping you in so this doesn't stall. Invoice [#] ([Amount], due [Due date]) is still outstanding.

Please reply with either:
1) the payment date, or
2) the blocker and the owner (PO, vendor setup, approval, etc.).

Thanks,
[Your name]

For the maintained, plug-and-play versions of these scripts, use Invoice Template + Late Payment Sequence.

When to pause work

A work pause can limit further unpaid exposure, but it must fit your agreement and applicable rules. An overdue invoice alone does not establish that you can suspend any obligation without notice or consequences.

Agree a pause trigger before you need it. Situations to consider when negotiating future terms include:

• an invoice is past due and there is no confirmed payment date,
• a client misses their own promised payment date (again),
• multiple invoices are past due,
• or your unpaid exposure is beyond your comfort threshold.

A simple clause (conceptual, not legal advice):

"If invoices are overdue, Provider may pause work until the account is current. Timeline commitments shift accordingly."

When you send the pause note, keep it factual and brief:

Subject: Work paused until invoice [#] is paid

Hi [Name],

Invoice [#] for [Amount] was due on [Due date] and is still outstanding. Per our agreement, I'm pausing work effective [Today] until the account is current.

Once payment is confirmed, I'll resume and send an updated timeline.

Thanks,
[Your name]

Put it in your SOW:

• Statement of Work template

Use the sample notice only when the referenced agreement actually permits the pause. If your right to pause is unclear, obtain advice before acting.

Step 4: Prevent repeat late payments (policy updates for new work)

Once you’ve stabilized the current overdue invoices, update your default terms for future work.

Options to discuss for future work:

Lever 1: Deposits

Deposits reduce exposure.

Use deposits when:

• it’s a new client
• it’s a large project
• the client has a history of slow payment
• your runway is thin

Lever 2: Milestone billing

Milestones align cashflow with progress and reduce risk.

Examples:

• 50% upfront / 50% on delivery
• 30/30/40 across three milestones
• monthly milestones for long engagements

Lever 3: Shorter net terms

Net terms are negotiable.

If a client insists on Net 60/90, you can counter with:

• a smaller phase first
• larger deposit
• or milestone schedule that reduces exposure

Lever 4: Tighten acceptance criteria

Payment disputes often happen when “done” is undefined.

Define acceptance criteria and review windows in writing:

• Statement of Work template

What to document (so you have leverage if you need it)

This is not legal advice. It’s operational risk reduction.

Your goal is simple: if someone new stepped in tomorrow (a manager, AP, a platform mediator, you-in-two-weeks), they should be able to see the facts quickly without digging through ten tools.

Keep:

• SOW/contract and any amendments
• invoices (with dates and terms)
• delivery proofs (emails, files, commit links, timestamps)
• written approvals or “looks good” messages
• follow-up emails and replies
• any policy or platform notices (if applicable)

Also keep a one-page timeline for each invoice:

Invoice: [#] | Amount: [Amount] | Due date: [Due date]

[YYYY-MM-DD] Sent invoice to: [Name / email]
[YYYY-MM-DD] Follow-up #1 (channel): [email/call/platform message] | Result: [no reply / replied / asked for info]
[YYYY-MM-DD] Follow-up #2 (channel): ... | Result: ...
[YYYY-MM-DD] Client committed payment date: [YYYY-MM-DD] (if given)
[YYYY-MM-DD] Escalated to: [Sponsor / AP / manager]
[YYYY-MM-DD] Work paused: [yes/no]
Notes: [missing PO? portal? dispute?]

This helps if you need to escalate via:

• formal notice,
• platform dispute processes,
• collections,
• or small claims (jurisdiction-dependent).

Common replies and what to verify

Record the client’s explanation without assuming a motive. Ask for the missing information.

• “We’re processing it.”
  Meaning: no specific date. Ask for a date.
• “It’s with AP.”
  Meaning: possibly true. Ask for the AP email and payment run schedule.
• “We need a PO.”
  Meaning: you’re outside procurement flow. Request PO and add it to your onboarding checklist next time.
• “We’re waiting on approval.”
  Meaning: unclear decision path. Ask who approves and when.
• “We found issues with the deliverable.”
  Meaning: acceptance criteria dispute. Reference SOW acceptance section and review windows.

FAQ

Should I charge late fees?

Only after checking your agreement and applicable rules, and if you’re willing to apply it consistently. If late fees aren’t in the contract, don’t improvise them midstream. Instead, stabilize payment now and update terms for future work (deposit, milestones, shorter net terms).

What if they ask for more work while invoices are past due?

Treat it as a policy decision, not a debate. If your rule is “accounts must be current,” then the next step is payment, not more delivery. If you choose to keep moving anyway, do it with reduced exposure (deposit or milestone billing) so you’re not compounding the problem.

What if they say “we never received the invoice”?

Assume process first. Resend, confirm the correct AP inbox, and ask for a reply that explicitly confirms receipt and the payment date. Then add “confirm invoice recipient” to your prevention checklist.

How many follow-ups is too many?

If the invoice is valid and due, follow-ups are not “begging.” They’re what keeps the process moving. Use a sequence and stick to it so you’re not sending random emotional pings.

What if they try to turn it into a quality dispute?

Keep it bounded and in writing. Reference the acceptance criteria and review window in your SOW, propose a specific fix if it’s legitimate, and treat new requirements as a change request. Don’t let “payment is late” quietly become “scope is now infinite.”

What if this is a platform payout delay?

Record the expected payout date, actual receipt date, account status, and support replies. Check any official notice before assuming a policy change. Your delayed payout alone does not show a platform-wide problem.

Evergreen Codex links

Bookmark the maintained versions:

• Payment system: Invoicing + getting paid on time
• Contract clauses: Freelance contracts: the clauses that matter
• Burnout/cashflow link: Boundaries and burnout
• Tax workflow (cashflow realism): Taxes: what to track weekly

Tools:

• Invoice Template + Late Payment Sequence
• Statement of Work (SOW) Template
• Change Request Addendum Pack

Dates and scope

Publication and update dates appear with the article. This checklist is general operational guidance, not a report about a particular client or platform and not legal advice.