Freelance payment terms, explained without the jargon

Payment terms are the part of freelance work nobody teaches and everybody is expected to know. They show up in proposals, contracts, and invoices, written in a kind of accounting shorthand that assumes you already understand it. Most freelancers learn the terms the slow way, by getting burned once and then quietly editing their template. This guide is the version of that knowledge written down before the burn.

Net terms: the calendar, not the deadline

When an invoice says "Net 30," it means payment is due thirty calendar days after the invoice date. Not business days. Not from the date the client received it. Not from the date the work was approved. Calendar days, from the date printed on the invoice. This matters because the difference between thirty calendar days and thirty business days is more than a working week, and your client's accounting software will use the calendar version regardless of what you intended.

Net 30 became the freelance default because it matches the billing cycles of large companies. If you work primarily with enterprises, fighting the convention will cost you more energy than it saves. If you work with smaller businesses, Net 14 or Net 7 is widely accepted and shortens your cash conversion cycle dramatically. The right number is the shortest one your clients will accept without negotiation, and you only learn that number by trying it.

Deposits and progress payments

A deposit is money paid before work begins. A progress payment is money paid at a defined milestone during the work. Both exist for the same reason: they shift cash flow risk away from you and toward the client, which is exactly where it belongs when you are committing weeks or months of capacity to a single project.

A standard deposit for project work is between 25% and 50% of the total fee, payable on signature of the agreement. For longer projects, splitting the remainder into milestone-based progress payments — for example, 25% on signature, 25% at first delivery, 25% at revision approval, 25% on final delivery — keeps both sides aligned and removes the awkward conversation that happens when a project drifts and you are still owed everything.

Clients sometimes resist deposits, particularly procurement teams at larger companies who have policies against paying for undelivered work. The workaround is to frame the deposit as a "kickoff fee" or "engagement fee" that covers discovery, planning, or onboarding work delivered in the first week. The work is real, the deliverable is concrete, and the policy objection disappears.

Late fees, written so they actually work

A late fee is a charge added to an invoice that has passed its due date. The charge usually compounds monthly until the invoice is paid. The standard rate in professional services is 1.5% per month, which is roughly 18% annualised — high enough to be motivating, low enough to be defensible.

Late fees only work if they are written into the original agreement. Adding them to an overdue invoice retroactively is unenforceable in most jurisdictions and damages the relationship even when the client pays. The right place for a late fee is the contract, repeated as a footer line on every invoice. Most clients will never trigger the fee, but the existence of the clause is itself the incentive.

Kill fees and cancellation terms

A kill fee is a payment owed when a client cancels a project before completion. It exists because freelance capacity is non-refundable — if you reserved three weeks for a project that gets cancelled in week one, the other two weeks are usually lost. A typical kill fee is 50% of the remaining unpaid balance, or full payment for any work already in progress, whichever is greater.

Kill fees are not punitive. They are insurance. Clients who understand creative work accept them without friction. Clients who push back on kill fees are usually signalling something else — uncertainty about the project, internal disagreement about budget, or a habit of cancelling work without consequence. The pushback itself is information worth listening to.

Escrow, holdbacks, and milestone releases

Escrow is money held by a neutral third party — a platform, a lawyer, or sometimes a bank — and released when defined conditions are met. It is common on freelance marketplaces and in larger contracts where neither party fully trusts the other yet. Escrow protects both sides, but it also introduces fees and friction, so it is rarely worth the overhead for short engagements.

A holdback is similar but kept by the client rather than a third party. A typical holdback is 10% of the project fee, retained until a defined warranty period — often thirty or sixty days after delivery — has passed. Holdbacks are common in software, construction, and any work where defects might surface after delivery. If a client requests a holdback, negotiate the warranty period to be as short as possible and make sure the release trigger is objective, not subjective.

Currency, taxes, and the small print that matters

If you invoice in a currency different from your bank account, the conversion rate and any wire fees should be defined in the contract. The default in most freelance work is that the client covers all transfer fees, including any intermediary bank charges. Make this explicit on the invoice — a single line, "Bank transfer fees payable by sender" — and you will rarely receive a short payment.

Taxes vary by jurisdiction and by the relationship between you and the client. As a general rule, the invoice should show the pre-tax amount, the tax rate, the tax amount, and the total separately. If you are not registered for tax, say so on the invoice — "VAT not applicable, supplier not registered" — to preempt the question.

Payment terms are not boilerplate. They are the operating system of your freelance business, and the defaults you accept today will compound into months of saved or lost time over the next year. Choose them deliberately, write them clearly, and review them every time you raise your rates.