I need to get paid on time

Recommended next links

Late payment is one of the fastest ways to turn freelancing into chronic stress. It doesn't just affect your bank account; it changes how you operate:

• you accept worse projects because you need cash now,
• you hesitate to enforce boundaries because you feel exposed,
• and you do everything in emergency mode.

The trap is thinking late payment is “just a client personality thing.” Sometimes it is. More often it's a system problem: unclear terms, unclear process, and no consequence for ignoring the due date.

The goal of this page is simple: make getting paid boring. Boring means everyone knows the terms, the invoice can't get “stuck,” follow-ups happen on a schedule, and there's a clear boundary when invoices are overdue.

This path helps you reduce late payment by changing the system:

• your agreement (SOW terms),
• your invoicing clarity,
• your follow-up cadence,
• and your enforcement policy.

If you want the full evergreen guide, read:

• Invoicing + getting paid on time

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

• Invoice Template + Late Payment Sequence

Codex summary

Getting paid on time is mostly policy plus process. You want payment to feel automatic and predictable, not emotional and improvised. The core levers are boring on purpose:

• a written scope with clear payment terms (including what happens when invoices are overdue),
• an invoice that matches the client's AP requirements,
• a repeatable follow-up cadence that asks for a payment date,
• and a work-pause rule you actually enforce.

What to do next (today + this week)

If you're already overdue, your goal is to create momentum and a paper trail. You're not trying to “win an argument.” You're trying to get a clear commitment and a predictable next step.

Today:

1. List every unpaid invoice, sorted by days overdue.
2. For each invoice, confirm you have the basics in one place: invoice # (or reference), invoice date, due date, amount, who it was sent to, and the last follow-up date.
3. Send the next follow-up for each invoice (don't batch it “later”). Keep it short and ask for a payment date.
4. For any invoice that is meaningfully overdue, decide your boundary (work pause, deliverable hold, escalation) before you write the email.

This week:

5. Update your SOW and invoice templates with clearer terms and a work-pause clause.
6. Switch new work to deposits or milestone billing if risk is high (or if this client has a pattern).
7. Add a weekly “accounts receivable” review block to your calendar so you don't get surprised again.

Step 0: Diagnose why payment is late (so you pull the right lever)

Late payment looks like one problem, but it usually comes from one of a few causes. Diagnose first, then choose the response. For each overdue invoice, try to answer these questions:

1. Is the invoice correct and complete (right entity, details, due date)?
2. Has someone confirmed they received it (or that it's in the portal)?
3. Is there a known blocker (PO, vendor onboarding, approval owner)?
4. Is there any dispute tied to scope or deliverable acceptance?

If you can't answer #2, your next message is not “checking in.” It's “can you confirm receipt, and who owns approval?” If you can answer #2 and #3, your follow-up becomes a simple request for a payment date.

1) Process friction (paperwork and routing)

Your invoice is “in the system” but stuck: wrong email, missing PO, vendor onboarding, the bill-to entity is wrong, or nobody knows who owns approval.

Fix: ask for the exact process and the right contact (accounts payable, finance, procurement).

2) Payment run schedules (not personal, just slow)

Some companies pay vendors on fixed schedules (for example, weekly or twice a month). That can be compatible with freelancing, but you need to know it up front so you can set terms that match reality.

Fix: align due dates and billing cadence to their process (or reduce risk with deposits/milestones).

3) Cash issues (their problem becomes your risk)

Sometimes a client is slow because they're strained. You don't need to psychoanalyze it. You just need to reduce exposure.

Fix: stop extending credit. Deposits, milestones, and smaller phases.

4) Disputes and “silent QA”

Occasionally payment is late because the client is unhappy, confused, or waiting on internal sign-off tied to deliverables.

Fix: ask directly if there's a dispute, clarify acceptance criteria, and document decisions. (Your SOW should make “done” boring.)

Step 1: Follow up on a cadence (polite → firm → consequences)

You don't need perfect wording. You need a consistent cadence that asks for a payment date and escalates on schedule.

Use:

• Invoice Template + Late Payment Sequence

Principles:

• ask for a payment date (a commitment, not a vibe)
• keep everything in writing
• escalate based on time, not emotion
• when someone gives you a date, follow up the next business day if it slips

When you write follow-ups, keep them short. The point is to make it easy to reply with one sentence: “Payment will be sent on Tuesday.” Avoid long backstory unless you're correcting a specific blocker.

If you don't have a system yet, use a simple rhythm and stick to it: confirm receipt when the invoice is sent, request a payment date on/after the due date, and follow up on a steady interval until it's paid (or you enforce your boundary).

If a client promises “next week,” politely ask for an exact day. If they miss the day, follow up immediately. Don't let “soon” become a pattern.

Follow-up cadence scripts

Use these as defaults. Replace the placeholders, keep the thread, and attach the invoice PDF when it helps remove friction.

1) Receipt confirmation (right after sending)

2) First overdue follow-up (ask for a date + blockers)

3) Overdue + missed promised date (tight, factual)

The goal is not to be aggressive. The goal is to remove ambiguity. Ambiguity is what allows “we're processing it” to loop forever.

Step 2: Enforce a work-pause policy (the boundary that changes behavior)

If you keep working while invoices are overdue, you teach clients that due dates are optional.

A work pause is not a threat. It's how you stop extending credit. It also keeps you honest: you don't need to feel angry to enforce it, you just follow the policy you already set.

Work pause concept (not legal advice):

You don't have to announce a work pause with drama. You can do it like a process update.

Work-pause scripts

Use a two-step approach: a brief heads-up (so it doesn't feel sudden), then a pause notice if it's still unpaid.

1) Heads-up before pausing

2) Work-pause email (calm, procedural)

Put it in your SOW:

• Statement of Work (SOW) Template

Clause context:

• Freelance contracts: the clauses that matter

If you're scared to enforce this, that's a signal your terms aren't protecting you. Tightening terms is a pricing and risk decision, not a personality test.

Step 3: AP process checklist (so invoices don't get “stuck”)

Late payment is often missing information or unclear ownership. “We're processing it” can mean anything. Your job is to learn the actual steps and write them down once.

Ask these during onboarding, or immediately when something goes late. You can copy/paste this checklist into your onboarding SOP.

AP process checklist

• Who is the accounts payable contact (name + email)?
• How should invoices be submitted (email, portal, both)?
• Is a PO required? If yes, who creates it and when should I expect the PO #?
• Do you require vendor onboarding (W-9, bank details form, portal setup)?
• What exact details must appear on the invoice (entity name, address, line item format)?
• What reference should I include every time (PO #, project code, cost center)?
• Who approves invoices internally (and what causes rejections)?
• What is your payment schedule (for example, weekly/biweekly/monthly runs)?

One simple question often surfaces the right owner quickly:

Then save the answers in your client onboarding SOP so you're not rediscovering the process under stress:

• Onboarding, delivery, and retaining clients

Step 4: Prevention checklist (so you chase fewer invoices)

Once you have the AP process, prevention is mostly about two things: clear terms and consistent ops. You're reducing the number of “special cases” where payment becomes a negotiation.

Before you start (agreement and scope)

• Use a SOW that defines scope and payment terms.
• Define when invoices are issued (deposit, milestone, or schedule).
• Include a work-pause clause for overdue invoices.
• Define acceptance criteria so “done” doesn't drift.
• Decide what changes mean (new scope equals new timeline and billing).

At kickoff (process and routing)

• Confirm the AP process (use the checklist above).
• Confirm who can approve invoices and who can push payment.
• Confirm any required references (PO, project code) before work starts.

Before sending an invoice (reduce friction)

• Make sure invoice details match the bill-to entity and AP requirements.
• Include a clear due date and payment method instructions.
• Include required references (PO #, project code) every time.
• Send the invoice to AP (or the portal), not just your project contact.

After sending an invoice (don't wait for “late”)

• Ask for receipt confirmation for new clients or new AP processes.
• Put the due date and your first follow-up on your calendar.
• Keep a single tracker for invoices and next actions.

Step 5: Change terms for new work (reduce risk immediately)

If payments are drifting, tighten your default terms. The point is not to punish anyone. It's to reduce how much credit you extend.

• require a deposit for projects (especially new clients)
• bill by milestone for multi-week work
• shorten net terms where you can (Net 7/14 instead of Net 30/60)
• make the payment method explicit (ACH/bank transfer/card)

If a client insists on long terms, don't argue about it. Reduce exposure: smaller initial scope, a paid phase 1, or a larger deposit so you're not floating the project.

Step 6: Build a weekly accounts receivable habit (10 minutes)

The simplest long-term fix is making follow-up a routine instead of a stress event. Once a week:

• review unpaid invoices
• schedule follow-ups
• decide whether any account triggers work pause
• update your tracker

This prevents “surprise overdue invoices” and reduces stress.

Minimal tracker fields (spreadsheet is fine):

• Client
• Invoice #
• Amount
• Invoice date
• Due date
• Status (sent / overdue / promised / paid)
• Last follow-up date
• Next follow-up date
• Notes (blocking reason, AP contact)

If you need a minimal system for this:

• Your solo operating system

Common mistakes (that keep late payment repeating)

These are easy to slip into, especially when you're busy. Fixing them doesn't require more aggression. It requires more structure.

• Sending one follow-up, then waiting weeks because it feels awkward.
• Being vague (“checking in”) instead of asking for a payment date.
• Continuing work while invoices are overdue.
• Sending invoices only to your project contact, not AP/Finance.
• Not learning the client's AP process, then treating delays as a mystery.
• Letting the SOW be vague, then payment becomes tied to moving goalposts.

FAQ

Should I use late fees?

Maybe. Late fees can help if they're enforceable in your jurisdiction and appropriate for your client type. But even without late fees, the biggest lever is usually a clear follow-up cadence plus a work-pause boundary.

Who should I follow up with: my contact or accounts payable?

Start with your day-to-day contact if they can route things internally, but don't stay stuck there. If payment is late, you want the AP owner in the loop (or at least a clear intro). A simple ask works: “Who owns approval and who owns payment on your side?”

What if they ask me to resend the invoice?

Resend it immediately, attach the PDF, and keep the thread. Then ask two questions: “Can you confirm receipt?” and “Can you confirm the payment date?” Resending without asking for the next step often just resets the clock emotionally, not operationally.

What if the client says “we only pay Net 60”?

Treat it as a risk decision. If you accept long terms, reduce exposure: require a deposit, bill milestones, or reduce the initial scope so you're not floating months of work.

What if I can't afford to pause work?

That's the real problem: you're in a position where a client can break terms and you have no leverage. Use this as a trigger to tighten terms for new work and build more stable lead flow. (This is also why consistent pipeline work matters.)

Should I call them or keep everything in email?

Email gives you a record and keeps the process calm. A short call can be useful when you need to identify the right AP owner quickly. If you do call, summarize the outcome in writing afterward: who owns it, what the blocker is, and the payment date.

What if they say “it's in the next payment run” but won't give a date?

Ask for the scheduled date of that run, or the date you should expect funds to arrive. “Next run” is not a commitment; a calendar day is.

What if there's a dispute?

Treat it as a separate conversation from payment logistics. Ask explicitly what the issue is, what “done” looks like, and what the acceptance decision will be. Then document the agreement. If acceptance keeps changing, that's a scope problem that your SOW should control.

What if they ghost?

Escalate procedurally: follow your sequence, document everything, and apply the consequence you already defined (work pause). If the amount is meaningful, consider formal escalation methods available in your context (platform dispute process, collections, small claims), and get local professional advice for your jurisdiction.

Recommended next links

• Evergreen payment system: Invoicing + getting paid on time
• Scripts: Invoice Template + Late Payment Sequence
• Contract support: Freelance contracts
• SOW template: Statement of Work template
• Client onboarding SOP: Onboarding, delivery, and retaining clients
• Lightweight tracking + routines: Your solo operating system