Why missed
Starting on good faith
You're excited to work with them. You don't want to signal distrust before the project starts. The late-fee clause gets left out in the spirit of goodwill.
Work is done. Invoice is sent. Days pass. Then weeks. The client is "getting to it." Your cash flow isn't.
Free. No registration. No card. No catch.
What it means
Late payment is what happens when a client takes longer to pay than you agreed — or, more often, than you didn't agree, because the contract never specified a due date, a consequence, or a remedy.
"Invoice received — processing." "Finance team is backed up this week." "Check is in the mail." Thirty days becomes sixty. The work was delivered on time. The payment wasn't.
Most agreements don't specify a hard due date, a penalty for lateness, or the right to stop work. Without teeth, the invoice is just a suggestion. Clients with their own cash flow pressure optimize accordingly.
You paid your suppliers, your staff, your software — on time. Your client didn't extend you the same courtesy. The gap between outflows and inflows is what kills small businesses, not bad clients.
Why it's missed
Why missed
You're excited to work with them. You don't want to signal distrust before the project starts. The late-fee clause gets left out in the spirit of goodwill.
Why missed
Many contracts say "payment due upon completion" or "net 30" without defining when day one starts. "Net 30 from when?" becomes a dispute.
Why missed
Without a late fee or suspension-of-work clause, you have no lever. You can send a polite email. That's it. The client knows it.
What can go wrong
Your commitments don't pause because the client is late. Payroll, rent, software — all due on schedule. The receivable gap becomes your problem to bridge.
Without a suspension clause, you may be obligated to keep delivering even while the invoice sits unpaid. More exposure, same problem.
The longer an invoice ages, the lower the collection probability. At 90 days, most small business receivables are effectively uncollectable without legal action.
Small claims or a collections agency costs money and time. The $2,000 invoice becomes a $1,200 recovery after fees. The contract was the cheaper fix.
Red-flag wording
These phrases are everywhere in boilerplate. They feel professional. They provide no protection.
Red flag
When is completion? Who decides? If the client disputes whether work is done, this phrase starts the payment clock nowhere.
Red flag
Net 30 from invoice date? Delivery date? Approval? "Net 30" alone is a range, not a date. Disputed start = disputed due date.
Red flag
Agreed where? In an email? A phone call? Not in the contract, where it can be enforced.
Red flag
Without a stated consequence for lateness, there is no consequence. You can ask. You can't enforce.
Red flag
If you can't pause work for non-payment, you're obligated to keep delivering into a non-paying relationship. That clause matters.
Safer pattern
Late payment protection isn't one clause — it's a system. A deposit clause gets money before work starts. A milestone clause ties delivery to payment checkpoints. A late-fee clause creates a cost for delay. A suspension clause gives you the right to stop.
BizDraft includes all four by default, calibrated to the project type and payment schedule you describe.
Most affected
Template
Ongoing work, recurring invoices, rolling exposure. Late payment risk is highest here.
See template →Template
Solo operators are most exposed — no AR team, no leverage, no buffer.
See template →Template
High-value, high-exposure. A single unpaid invoice can represent weeks of work.
See template →Free. Five minutes. Yours to keep.
Draft your agreementRelated risks
Risk
"Upon completion" isn't a date. The clause that kills cash flow before the invoice is even sent.
Read →Risk
Client walks mid-project. Without a kill fee, you absorb the cost of work already done.
Read →Risk
Without a clean exit, you may be stuck in a non-paying relationship with no contractual way out.
Read →