Most late payments start with the invoice
Freelancers tend to think of late payment as a client problem. Often it is. But a meaningful share of it starts earlier, with an invoice that was hard to pay: it went to the wrong person, it didn't carry a reference the client's finance system needed, or it arrived without a due date so it joined the pile of things with no deadline.
None of that is dramatic. It's just friction, and friction is what pushes an invoice from the top of someone's inbox to the middle of next month.
Getting the document itself right is the cheapest improvement available, because it costs one afternoon and then applies to every invoice you ever send.
What every invoice must contain
Copy this structure. The order matters less than the completeness — a missing PO number or an unclear due date is what sends an invoice back round the loop.
1. The word "Invoice"
Sounds trivial. It isn't — finance systems and inboxes both sort on it, and a document headed "Summary of work" gets filed differently from one headed "Invoice."
2. A unique invoice number
[e.g. 2026-014]. Sequential, never reused. This is how a client's accounts team refers to it, and how you find it later.
3. Issue date and due date — both
Not "payable in 14 days." Write the actual date: [Due: 14 August 2026]. A specific date is a deadline; a duration is a suggestion someone has to calculate.
4. Your details
Trading name, address, and tax registration number if you have one. Missing tax details are one of the more common reasons an invoice gets returned unpaid.
5. Their details — including the right name
The legal entity, not the brand. And addressed to the person or department who actually processes payment, which is frequently not your day-to-day contact.
6. A purchase order or reference, if they use one
Larger clients often can't pay without it. Ask at kickoff whether one is needed rather than discovering it when payment stalls.
7. Line items that match the scope
Use the same wording as your scope of work. When the invoice says "Brand identity package — logo, lockups, brand sheet" and the scope says the same, there's nothing to query.
8. Any approved extras, listed separately
[Change order 1 — additional landing page, approved 4 July]. Separating them shows the client exactly what they agreed to and when.
9. Subtotal, tax, total
Shown as three lines even when tax is zero. Ambiguity about whether a figure includes tax causes short payments.
10. How to pay
Bank details, or a payment link, or both. Currency stated explicitly. For international clients, say who covers transfer fees — otherwise you receive the amount minus a deduction you didn't expect.
11. Your payment terms, restated
One line: [Payment due within 14 days. Late payments may incur interest at 2% per month.] Restating it here means the terms travel with the document.
The two that matter most: a specific due date, and sending it to whoever actually pays. Those two alone resolve a large share of "we never received it" and "it's in the system" delays.
When to send it
Immediately on the trigger, whatever the trigger is. Deposit invoice the moment the scope is signed. Milestone invoice the day the milestone is delivered. Final invoice on delivery, not a week later when you get round to admin.
Delay costs twice. It pushes the payment date back by however long you waited, and it signals that your own deadlines are flexible — which makes theirs feel flexible too.
If invoicing is the task you keep postponing, the fix is usually scheduling rather than discipline: a fixed half-hour each Friday, or invoicing as the final step of your delivery checklist so it can't be separated from the work.
Choosing your payment terms
Payment terms are the window between issuing an invoice and payment being due. Shorter is better for your cash flow, but only if it's realistic for the client's process.
- Due on receipt — reasonable for small projects and individual clients. Can read as aggressive to a company with an approval chain.
- Net 7 — good default for solo freelancers working with small businesses.
- Net 14 — the most common compromise, and comfortable for most clients.
- Net 30 — standard for larger companies. Often non-negotiable, because it's set by a finance policy rather than by your contact.
Agreeing net 30 with a company that pays net 45 in practice is worse than agreeing net 45 honestly. Ask at kickoff what their actual payment cycle is, then plan cash flow around the real number rather than the agreed one.
Tools, briefly
Invoicing software matters less than most comparison articles suggest. What you need is: a consistent template, sequential numbering, a record of what's outstanding, and a payment method your clients can actually use.
A spreadsheet plus a well-built document template does all four, and is what many freelancers use for years without problems. Paid tools add automatic reminders and reconciliation, which start to matter somewhere around fifteen to twenty invoices a month.
On payment methods: bank transfer costs you nothing but is slower and higher-friction. Card and payment-link options cost a percentage but get paid faster, and for a client who needs to expense something, they're often the difference between paying today and paying eventually. Offering both is usually right.
If it goes unpaid
Have a sequence rather than a feeling. The most common failure is not that freelancers chase badly — it's that they draft three follow-ups and send none of them, because each one feels like a confrontation to be initiated rather than a scheduled step.
The full four-stage sequence, with wording for each stage, is on the payment reminder email page. In outline: a neutral nudge the day after the due date, a firmer note at day seven, a formal one at day fourteen, and a final notice at day thirty.
Common questions
What should a freelance invoice include?
Eleven things: the word Invoice, a unique sequential number, both issue and due dates, your details including any tax registration, the client's legal entity and the person who processes payment, a purchase order reference if they use one, line items matching your scope wording, any approved extras listed separately, subtotal and tax and total, payment instructions with the currency stated, and your payment terms restated.
What payment terms should a freelancer use?
Net 7 or net 14 suits most solo freelancers working with small businesses. Larger companies frequently impose net 30 through a finance policy your contact cannot override. Ask at kickoff what their actual payment cycle is, because agreeing net 30 with a company that pays in 45 days is worse than planning honestly around 45.
When should I send an invoice?
Immediately on whatever triggers it — deposit invoice when the scope is signed, milestone invoice the day the milestone is delivered, final invoice on delivery. Delay pushes the payment date back by however long you waited and signals that your own deadlines are flexible.
Should I put a due date or payment terms on an invoice?
Both, but the specific date matters more. 'Payable within 14 days' requires the reader to calculate something; 'Due: 14 August 2026' is a deadline they can act on. Restate the terms as a separate line so they travel with the document.
Do I need invoicing software as a freelancer?
Not initially. A consistent document template plus a spreadsheet tracking what is outstanding covers everything essential. Paid tools add automated reminders and reconciliation, which start to earn their cost somewhere around fifteen to twenty invoices a month.