For a freelancer, the invoice is not paperwork at the end of the job. It is the job — everything before it was unpaid work on the assumption that this part goes smoothly.
Most of what makes it not go smoothly is decided long before you send anything.
Before the work: three things in writing
The rate and what it applies to. Hourly, daily or fixed. If hourly, whether travel, calls and email are included. Vagueness here becomes a discount later, because the ambiguity always resolves in the client's favor.
Payment terms, explicitly. Net 14 or net 30, stated in the agreement rather than appearing for the first time on the invoice. If a client has 60-day terms as policy, you want to know before you start, not after you have delivered.
Who receives the invoice. Not "the client" — a name and an email, and whether it needs a purchase order number. A missing PO is the most common reason an invoice sits unpaid for a month at a larger company, and nobody tells you; it simply does not enter the system.
That last one takes thirty seconds at kick-off and saves weeks.
What goes on the invoice
The rule: enough detail that nobody has to ask a question, no more.
An invoice that says "Consulting — $4,800" invites scrutiny, because it gives the person approving it nothing to approve. One that lists 47 individual time entries invites a different kind of scrutiny, line by line, and at least one query.
The middle is right. Group by project or workstream, show the hours and rate, and give each group a description a non-specialist can understand:
Homepage redesign — concepts and two revision rounds 14.5 hrs @ $133 $1,928
Component library — build and documentation 22.0 hrs @ $133 $2,926
Launch support — QA and fixes 4.5 hrs @ $133 $599
Attach the detailed entries as a second page if the contract calls for it, or if it is a first invoice with a new client and you would rather pre-empt the question. Which is why the descriptions on your time entries matter: "fixed the thing" cannot go in front of a client, and rewriting three weeks of entries at invoicing time is how a twenty-minute job becomes an afternoon. See a time tracking policy worth writing.
Also include, because their absence causes delay: invoice number, issue date, due date as an actual date rather than "net 30", your payment details, tax registration number if you have one, and the PO number if there is one.
Send it immediately
The correlation between how quickly you invoice and how quickly you are paid is strong, and the causes are unglamorous: your work is fresh in the client's mind, the budget is still open, and the person who commissioned it has not moved teams.
Invoice on completion, or monthly on a fixed date for ongoing work. Do not let invoices accumulate for a quarterly admin session — every week of delay in sending is a week added to being paid, plus the risk that the approver changes.
Bill progressively on anything long
For work over a few weeks, do not wait until the end.
A deposit up front — 30–50% is normal and entirely standard — plus monthly billing for work in progress. This does two things: it fixes your cash flow, and it surfaces a client's payment problems early, while your exposure is one month rather than the whole project.
A client who will not pay a deposit is giving you information. Listen to it.
Chasing, without damage
Most late payment is administrative rather than adversarial. The invoice is sitting in someone's approval queue, or it never arrived, or the PO was missing. Chasing works best when it assumes that.
A sequence that works:
- Three days before due — a short, friendly note. "Invoice 0142 is due Friday — anything you need from me?" This catches the missing-PO problem before it becomes lateness.
- On the due date, if unpaid — a factual note that it is due today.
- Seven days late — direct, and copy in accounts payable if you have the contact.
- Fourteen days late — a call. Email has stopped working at this point and the call almost always resolves it.
- Beyond thirty days — stop work on anything ongoing, and say that you are. Continuing to deliver while unpaid teaches a client that the terms are decorative.
Keep every message brief and unemotional. The apologetic version — "so sorry to chase, I know you're busy" — reads as though you are doing something wrong, and you are not: you are asking to be paid for work you have delivered.
Track what happens after
Two numbers, worth five minutes a quarter:
Days to payment, per client. Some clients are reliably 45 days regardless of your terms. That is not a problem if you know it and price and plan for it. It is a serious problem if you assumed 14.
Time spent on admin, per client. Track invoicing and chasing like any other work. A client whose $5,000 project consumed six hours of chasing is not paying what you think — see effective hourly rate. It is often the same client every time, and knowing that is what turns a vague irritation into a rate adjustment at renewal.
