Most freelancers do not have a payment problem. They have a documentation problem that shows up as a payment problem three weeks after the work is delivered.
The clause below is the one I recommend to every freelancer I talk to, followed by the clause that looks protective and usually is not.
The clause that works
Payment. The Client will pay each invoice within 14 days of the invoice date. The invoice date is the date the invoice is sent. Time is of the essence for payment. If an invoice is disputed, the Client will pay the undisputed portion within the same period and notify the Supplier in writing of the disputed amount, with reasons, within 5 working days.
Four things are doing the work here:
- A number, not a mood. “Within 14 days” is testable. “Promptly” and “on receipt” are not.
- A defined trigger. The clock starts from the invoice date as defined, not from when their accounts payable team decides the invoice was “received”.
- A split for disputes. Without this, one disputed line item freezes the entire invoice. With it, the client must pay the rest and say what they are disputing.
- “Time is of the essence.” In many common-law jurisdictions this phrase strengthens your position if you ever have to enforce the term.
The clause that does not (usually)
“Late payments will incur interest at 2% per month.”
It reads tough. In practice it fails for three reasons:
- It comes out of thin air. If the contract does not also say how interest is calculated, from which date, and whether it compounds, a client can ignore it with near-impunity.
- It is often unenforceable between businesses. Several jurisdictions cap or restrict penalty interest in business-to-business contracts unless the rate is a genuine estimate of your loss.
- It is a percentage of a number they control. Clients who are slow payers know that chasing £8 of interest is not worth your afternoon.
The other half: consistency
The single most common reason a good clause fails is that the invoice contradicts it. Your contract says 14 days; the invoice footer says “Net 30”. Guess which one accounts payable reads.
Check these four places every time:
- The contract’s payment term.
- The invoice due date field (put an actual date, not “Net 14”).
- The invoice footer text.
- Your reminder email cadence.
The day-one email
Most late payments are not refusals; they are invoices sitting in a queue nobody owns. The fix is a polite, specific, same-day touch.
Subject: Invoice #1042 — £3,400 — due 10 November
Hi [Name], invoice #1042 for £3,400 was sent today and is due on 10 November. Could you confirm it has reached the right person for payment, and let me know if you need a purchase order number or a different billing entity?
If anything looks wrong, tell me which line and I will reissue it today — the rest can be paid on the original date.
That message does three things: it creates a paper trail, it gives them an easy way to flag a real problem, and it removes the “we never received it” excuse.
A short checklist before you send
- Payment term is a number of days from a defined trigger.
- Contract, invoice and footer agree.
- Due date is a real date, not a relative one.
- Disputed items must be identified in writing within a set period.
- Late fee is a fixed sum, invoiced separately.
- You have a name and email for the person who actually pays.



