Getting Paid on Time as a Freelancer

Late payment is the freelance problem nobody budgets for. The work went fine, the client is happy, and the money is somewhere in an approval queue while your rent date approaches. Most of the fix isn't chasing — it's structure you set up before and during the project. Here's the playbook: terms, deposits, late fees, and the follow-up sequence, in that order, because that's the order of leverage.

Net terms: pick short, concede deliberately

"Net 14" means payment is due 14 days after the invoice date. The number you choose is a negotiation default, so choose it yourself instead of inheriting the client's.

Net 7–14 is a reasonable freelancer default. You're not a supplier with a warehouse financing inventory; you're a person who did the work already.
Net 30 is the corporate standard. Accepting it for a large client is normal — their accounts-payable process may genuinely be unable to move faster. Treat it as a concession you make knowingly, ideally traded for something (a deposit, a larger scope, a rate that reflects the float).
Net 45, 60, 90 exist at big enterprises. At that point you are lending the client money interest-free for months. If you take those terms, price them in, and never let them combine with milestone-free projects — you'd be carrying months of risk with zero paid checkpoints.

Two details that quietly matter: write the due date as a real calendar date on the invoice, and remember terms count from the issue date — sending the invoice a week late is the same as extending net terms by a week. The mechanics of a clean, unambiguous invoice are their own topic; see what belongs on a software development invoice.

Deposits: the strongest tool, the least used

A deposit converts "will this client pay?" from a hope into evidence, before you've sunk weeks into the work. Common structures:

Fixed-price projects: 30–50% up front, the rest on delivery or split across milestones. For new clients, closer to 50%.
Hourly engagements: a retainer covering the first week or two, drawn down against and topped up.
Milestone billing: effectively rolling deposits — each phase is paid before the next begins, so your maximum exposure is one milestone.

The awkwardness freelancers feel about asking evaporates with matter-of-fact wording: "I schedule projects on receipt of a 40% deposit; the remainder is due on delivery." No apology, no justification. Established businesses ask for deposits constantly; the ones that don't ask are signaling inexperience, and experienced clients know it.

A client who refuses any deposit on a substantial project is telling you something about priorities. It's not always disqualifying — large companies often genuinely can't prepay — but with small companies and individuals, treat refusal as a yellow flag and shorten your billing cycle in response.

Late fees: a clause that works by existing

A standard late-fee clause reads: "Overdue balances accrue interest at 1.5% per month." That's a contract term you invented, and it's fine.

What most freelancers don't realise is that in the UK and across the EU, you have a statutory right to interest and recovery costs whether or not your contract mentions them. These are not guidelines. They're legislation, with published rates.

UK: Late Payment of Commercial Debts (Interest) Act 1998

Under the Late Payment of Commercial Debts (Interest) Act 1998, a business invoicing another business (or the public sector) can claim:

Statutory interest at the Bank of England base rate + 8 percentage points. The applicable base rate is fixed twice a year — the rate in force on 31 December governs debts running January–June, and the rate on 30 June governs July–December.
Fixed compensation for debt-recovery costs, on top of the interest, on a sliding scale by debt size.

Debt amount	Fixed compensation
Up to £999.99	£40
£1,000 – £9,999.99	£70
£10,000 or more	£100

EU: Directive 2011/7/EU on late payment

The EU Late Payment Directive sets a floor across member states:

Businesses must pay within 60 days unless they expressly agree otherwise and the alternative isn't grossly unfair. Public authorities get 30 days, or 60 in exceptional circumstances.
Statutory interest of at least the European Central Bank reference rate + 8 percentage points.
A minimum €40 in recovery-cost compensation.

Note what that first bullet does: in the EU, "net 90" is not simply a term a large client can impose on you. It has to be expressly agreed and it has to survive a fairness test.

Why this matters even if you never invoke it

You almost certainly won't file a claim over a late invoice — the relationship costs more than the interest. But knowing the statutory position changes how you write and how you follow up. "Statutory interest under the Late Payment of Commercial Debts (Interest) Act, currently base rate plus 8%, applies to overdue balances" is a sentence a finance department reads differently than "1.5% monthly," because one of them is a fact about the law and the other is a request.

If you're outside the UK and EU, check your own jurisdiction before borrowing that language — the US has no federal equivalent, and late-fee enforceability varies by state.

Here's the honest part: most freelancers who have the clause never collect the fee, and it still works. Its job is to change the payment-queue math inside the client's finance process — invoices with stated consequences get sorted above invoices without them. Put it in the contract, restate it in the invoice terms, and treat actually charging it as an escalation you'll use rarely and deliberately (usually to create leverage for a settlement, not for the fee itself).

What beats a late fee for repeat offenders: pausing work. "I'll pick the next milestone back up once INV-0014 is settled" is calm, fair, and extremely effective, because it converts your unpaid invoice from your problem into a shared one.

The follow-up sequence

Write this once, reuse forever:

3 days before due (larger invoices): one line — "Quick heads-up that INV-0014 ($4,200) is due Friday. Anything you need from my side?" This catches the invoice that never made it into the payment system, which is a surprisingly common failure.
1–3 days after due: friendly and short. Assume process failure, not bad faith — most late payments are an invoice sitting in someone's queue. Attach the PDF again; don't make anyone search.
Two weeks after due: firmer. Reference the agreed terms and the late-fee clause. Ask for a specific payment date rather than a vague "soon."
Persistent lateness: shorten the relationship's terms going forward (net 7, or deposit-based), pause new work, and for serious amounts consider a formal demand letter — jurisdiction-dependent, and at that point worth an hour of a lawyer's time.

Keep every message short, factual, and free of apology or anger. The tone is easiest to maintain when the paperwork is airtight — sequential invoice numbers, clear terms, dated records — which is most of why the boring hygiene from how to invoice as a freelance developer pays off.

Reduce the surface area for delay

A few structural habits shrink the problem before terms even apply:

Bill more often. Monthly invoices concentrate risk; weekly or biweekly invoices mean smaller amounts, faster detection of payment problems, and less pain when one slips.
Make the invoice frictionless. Right entity, PO number if needed, unambiguous due date, one page. Every question an approver has to ask adds days.
Keep your records instantly available. When a client says "can you resend March's invoice?", the answer should take thirty seconds. A saved-invoice list with statuses (draft/sent/paid) is enough for most freelancers — no billing platform required.

None of this is dramatic. That's the point: getting paid on time is a systems outcome, and the system is small enough to set up in an afternoon.

Sources

Late Payment of Commercial Debts (Interest) Act 1998, legislation.gov.uk
European Commission, Late payment — Directive 2011/7/EU

This is general information about published statutory rules, not legal advice. Rates change and jurisdictions differ — check the current position before relying on it.