Seven reasons clients pay late, and the fix for each
Seven specific defects that delay payment, what each one costs in days, and the exact change that removes it, from AP routing to payment run timing.
Most late payments have a cause you could have found before the invoice went out. The cause is almost never that the client decided not to pay you; it is that something in the paperwork or the timing made paying you the slower option, and slow options win by default inside every finance department.
What follows is seven defects. Each has a mechanism, a rough cost in days, and one change that removes it. Diagnose before you chase — the wrong reminder aimed at the wrong defect just repeats the delay.
Start from the symptom
What you observe | The defect it usually is | Section |
|---|---|---|
Silence, then payment lands in a batch with others | Payment run timing | 4 |
Silence, and it never lands | Routed to the wrong person | 1 |
"Can you resend it?" | Rejected in AP and nobody told you | 2 |
"We need to check this against the scope" | Unquoted change | 3 |
"We're still reviewing" | No acceptance trigger | 6 |
Paid, but always around three weeks late | Ambiguous start of the payment period | 5 |
Consistently last in the queue | Being late costs them nothing | 7 |
1. The invoice went to the person who briefed you
The project contact hired you, approves your work, and cannot pay you. In an organization of any size, the payment instruction lives with accounts payable or a shared finance inbox, and your invoice reaches it only when your contact forwards it. That forward is an unscheduled favor competing with their own workload.
Cost in days: however long the forward sits in their inbox. If they are on leave, the invoice does not exist for the duration of the leave.
The fix is two questions at kickoff, not at invoicing. Which address do invoices go to, and does a purchase order or cost center reference have to appear on them. Send to accounts payable, copy the project contact. The person who can pay then holds the document, and the person who wants the work to continue knows it is outstanding.
2. The invoice was rejected, not delayed
Accounts payable departments rarely refuse an invoice. They fail to match it, and it drops into an exceptions queue where it sits until someone works the queue. In many organizations nobody notifies the vendor at all, so from your side it looks identical to being ignored.
Federal agencies in the US publish exactly what they need before their payment clock starts, which makes the list a usable specification for everyone else. A proper invoice under 5 CFR 1315.9(b) carries the vendor's name, invoice date, the contract or other authorization for delivery, the invoice number and any agreed account number, the description, price and quantity supplied, shipping and payment terms, the taxpayer identifying number, banking information, and a named contact with a telephone number. Anything missing makes the invoice improper. The agency returns it and the clock restarts on the corrected version — and agencies are required to return it within seven days, which is a courtesy private clients do not owe you (5 CFR 1315.4).
Cost in days: the full length of your terms, twice, because the second invoice starts from zero.
The fix is a fixed header block you never re-decide, plus one behavior: if an invoice is more than three days past due with no acknowledgement of receipt, ask whether it was accepted into their system before you ask when it will be paid. Those are different questions and only one of them is answerable by the person you are emailing.
3. Scope changed and nobody re-quoted
This is the defect that looks like a pricing problem and behaves like a payment problem. Work expands during delivery, you absorb it because raising it mid-project feels awkward, and then the invoice arrives carrying a number that does not match anything the client approved. It now needs a second approval from someone who was not in the room.
Cost in days: however long it takes to reach whoever holds the budget and win a second approval, on a calendar that was never part of your project plan. Sometimes the cost is worse than days — the client pays the originally approved amount and disputes the rest.
The fix is a re-quote before the extra work starts, not an explanation after it finishes. A one-page priced change note with a valid-until date, sent for written approval, converts an argument into an administrative step. The free quote generator will produce one as a PDF in the browser with no signup, which removes the last excuse for doing it verbally. The rule underneath it: nothing gets built that has not been priced and approved in writing, including work that is obviously small.
4. The invoice missed the payment run
Most finance functions pay on a cycle rather than on demand — a weekly, fortnightly or monthly run with a cut-off a few days before it. Your invoice does not get paid on day 30. It gets paid in the first run after the day it becomes payable, and if it lands a day after the cut-off it waits for the next one.
This is the defect nobody diagnoses, because it produces no conversation at all. The client is not late by their own reckoning. They are on cycle, and you are on the wrong side of it.
Cost in days: up to one full cycle, on every invoice you send that client. Against a monthly run, that is most of a month.
The fix is to ask, once, in the same breath as the accounts payable address: how often do you run payments, and is there a cut-off. Then set your delivery and invoicing rhythm so invoices clear approval before the cut-off rather than after it. Where the run is monthly and your terms are short, that usually means invoicing earlier in the month, not shortening the terms further. Shortening terms against a monthly cycle achieves nothing; moving the invoice five days earlier can save you the whole cycle.
5. Nobody agreed when the clock starts
You think the payment period runs from delivery. The client's system starts it on receipt of the invoice, or on approval of the invoice, or on the first day of the month following receipt. All of these are defensible, and the difference between the loosest and the tightest reading can be most of a month.
The law gives you a default where the contract is silent, and it favors the invoice, not the delivery. Under Directive 2011/7/EU, Article 3(3)(b), the EU default B2B period is 30 calendar days from the debtor's receipt of the invoice, or from receipt of the goods or services where the invoice date is uncertain. Article 3(4) caps a contractual acceptance or verification procedure at 30 calendar days unless something longer is expressly agreed and not grossly unfair to you. In the UK, where nothing is agreed, payment is late 30 days after the customer receives the invoice or the goods and services, whichever is later.
The fix is to write the due date on the invoice as an actual calendar date rather than as "Net 30," and to state in the contract that an internal approval procedure does not extend the payment period. The first removes the disagreement; the second removes the loophole.
6. There is no acceptance event, so "still reviewing" is free
If your contract has no definition of acceptance, review can continue indefinitely at no cost to the client. Every week of review is a week of your capital funding their project, and nobody inside the client's organization experiences that as a cost, because it isn't one for them.
Cost in days: unbounded. This is the only defect on this list with no natural ceiling.
The fix is a deemed-acceptance clause with a short fuse. Deliverables are deemed accepted five working days after delivery unless the client gives written notice of specific defects. Federal contracting uses the same device: acceptance is deemed to occur on the seventh day after actual delivery unless the agency accepts earlier (5 CFR 1315.4). A branded client portal where the client approves a deliverable with a click helps here for a reason that is not about convenience: it produces a timestamp, and a timestamp is what turns a milestone into an invoice trigger.
7. Paying you late costs the client nothing
If your terms are silent on consequences, you are the cheapest source of credit that client has. A supplier who charges interest gets paid before a supplier who does not, and nobody in accounts payable has to be cynical for that to happen — the queue simply sorts itself that way.
Cost in days: whatever the rest of their supplier list will tolerate. You inherit the worst terms in the room.
The fix is a stated consequence in the contract and a footer line on the invoice recording it. In the EU and the UK the entitlement exists whether or not you wrote it down, but stating it changes behavior before you ever have to use it. What you can charge, and the exact wording that states it without sounding like a threat, belongs in how to write an overdue payment letter that gets paid.
Why this list is worth working through in order
Six of these seven defects are fixed before the work starts, in the contract or at kickoff, and cost you nothing after that. Only the payment run is genuinely the client's, and even that one is knowable by asking a question most freelancers never ask.
The reason to fix them structurally rather than chase harder is that chasing is unpaid labor and the defects are permanent until removed. A missing purchase order reference will delay every invoice you send that client for as long as the relationship lasts. Fix it once and the delay disappears from every future invoice, which is not something a well-written reminder ever achieves.
Worth being honest about what tooling does and does not solve here. Most invoicing tools will tell you an invoice is overdue; where they differ is whether the overdue invoice is connected to the project it came from, so you can see whether the problem is a rejected document or an unapproved change. That distinction is the substance of the FreshBooks alternative comparison, and it matters because defect 2 and defect 3 look identical from an accounting ledger and completely different from a project record.
What to change before your next invoice goes out
Add three fields to your kickoff checklist: accounts payable address, purchase order or cost center reference, and payment run frequency with its cut-off date. All three come from one email to the project contact in week one.
Put a deemed-acceptance clause and a stated late-payment consequence into your contract template, so they apply to every engagement rather than to the ones where you remembered.
Stop starting unquoted work. A priced change note takes ten minutes and removes the most expensive delay on this list.
The prevention system these seven defects sit inside, covering deposit structure, milestone triggers, invoice timing and content, is in the freelancer's guide to getting paid on time, and what to do once an invoice is already overdue is in a reminder schedule that works without souring the relationship.
Worklyn's Scope Watch flags a project running past its approved budget while there is still time to re-quote, which is the point at which defect 3 is cheap to fix rather than expensive.