Freelancers talk about late payment as a chasing problem. It's mostly a structuring problem, decided weeks before the invoice exists.
By the time you're sending a third reminder, the decisions that determined whether you'd be paid on time were made at quote stage. Here are the six that matter.
1 · A deposit, always
Standard in every adjacent industry and still treated as awkward in this one.
A deposit does three things: it covers your exposure if the project collapses, it filters out clients who were never going to pay, and it establishes at the start that payment is a normal part of the relationship rather than an awkward topic introduced at the end.
Clients who object to a reasonable deposit are giving you real information, early, for free.
2 · Stage the payments
Deposit, a milestone at shoot or first cut, balance at delivery.
If a client goes quiet at eighty percent complete (and some will) you've been paid for most of it. Staging converts a catastrophic risk into a manageable one, and it's the single most protective structural choice available.
3 · Balance on delivery, not on approval
The most important line in this article.
If payment is conditional on their sign-off, their indecision is free and you're financing it. A client who takes six weeks to approve has cost you six weeks of cash flow and paid nothing for the privilege.
Tie payment to your delivery of the agreed deliverables. That's the thing you control, and it's the thing you did.
4 · Terms on the invoice from the first one
A payment period and a late fee, stated. You can always choose not to enforce a late fee. You cannot invoke one that was never there.
Having terms also changes the conversation from a personal request to a process. "The terms are 14 days and we're at 30" is a different message from "any update on that invoice?" The first is administrative, the second sounds like begging and invites a negotiation.
5 · A response window in the agreement
One line:
"Feedback due within 10 working days of each delivery. Beyond that, the project may be paused and rescheduling is subject to availability."
Nobody objects to this at signing. It's the clause you'll be grateful for, because it gives silence a consequence that exists before the silence does. See when a client goes quiet.
6 · Invoice the day you deliver
Not at month end. Not when you get round to it.
Most payment cycles start when the invoice is received, so a week's delay in sending is a week added to every subsequent step. And it lands you after their payment run instead of before it. This is the cheapest improvement available and the most commonly skipped.
The things that don't help
Chasing harder. Politeness or firmness barely moves the outcome once terms are absent.
Discounting for early payment. You're paying to be paid what you're owed.
Being flexible to keep the relationship. A client who pays late once, with no consequence, has learned what your terms mean. Precedent is the whole game.
Assuming an invoice is being looked at. Most late payment isn't refusal, it's an invoice sitting in an inbox that isn't finance's. Which leads to the practical fix below.
Make it easy to actually pay you
Half of late payment is friction, not intent.
Get the right recipient at kick-off. Ask who invoices should go to. Often it isn't your contact, and an invoice sent to a marketing manager can sit for weeks before being forwarded.
Get a PO number if they use them. In organisations that require one, an invoice without it is unpayable and will bounce silently.
Put everything they need on it. Your bank details, tax number, the agreed reference. Anything missing is a round trip.
Sequential invoice numbers. Gaps and duplicates cause questions. Most tax authorities expect a sequence anyway.
Say what it covers. Deliverables and usage granted, briefly. The person paying is frequently not the person who read the agreement.
When it does go wrong
A short, unemotional ladder: a reminder at due date, a second at seven days restating the terms, a third naming the next step.
What actually resolves it is rarely persuasion. It's escalation to someone in finance, and what they need is a clean record: what was delivered, when, against which invoice number. If you have that, most late payment clears in one message.
Where Acumin fits
Narrow and worth being precise about, because the honest limit matters here.
Acumin records invoices. It does not process payments. Connect-only doctrine: it never handles the money, which is also why there's no commission. You're paid directly, however you already get paid.
What it does provide is the record: numbers minted sequentially per creator per year, drafts editable and sent invoices fixed, and (for Delivery Room invoices) the invoice attached to the booking, the versions and the delivery dates. So "what was delivered, when, against which invoice" is a lookup rather than an archaeology exercise through email.
Standalone invoices cover off-platform clients too, with a revocable share link, so all of your invoicing can live in one place rather than three. Invoicing through Acumin.
How to use this tomorrow
Open your quote or agreement template and check for four things: a deposit, staged payments, balance on delivery rather than approval, and a feedback response window.
Add whatever's missing before your next quote goes out. That's ten minutes, once, and it's most of the defence.
Related: Invoicing through Acumin is the mechanics. Managing expectations across a project prevents most of the silences that precede late payment.