Risks › No payment deadline

No payment deadline.
"Upon completion" isn't a date.

The most common cash-flow killer in service contracts. The work ends. The clock on payment never started because the contract didn't set one.

Draft an agreement that prevents it

Free. No registration. No card. No catch.

What it means

In plain English.

A payment deadline is the specific date or trigger that starts the payment clock. Without one, "due" is a vague notion that the client interprets in their favor. "Upon completion" and "upon delivery" are not dates — they're events that can be disputed, delayed, and indefinitely deferred.

What it looks like

"Payment due upon completion" — but the client says the project isn't complete yet. Or "upon delivery" — but the client disputes whether what was delivered matches what was promised. The clock never starts.

Why it's so common

Template language defaults to "upon completion" because it's simple and sounds professional. Nobody writes it thinking about what happens when the client defines completion differently than the provider does.

Why it matters

Cash flow depends on predictability. If you can't project when you'll be paid, you can't manage your business. A specific payment trigger turns a vague promise into a date you can plan around.

Why it's missed

It seems clear enough until you need to enforce it.

Why missed

"Completion" seems obvious

Until the client says the logo needs one more round, or the report needs revisions, or they're waiting on a stakeholder approval. "Complete" in the client's eyes can recede indefinitely.

Why missed

The invoice date isn't written in

Many contracts trigger payment from "invoice date" but never say when the invoice gets sent. Net 30 from an invoice that hasn't been issued yet is still no deadline.

Why missed

No backup if the event is disputed

Even well-written trigger events can be disputed. A contract needs a fallback: if the trigger event is in dispute, payment is due on [specific date].

What can go wrong

The downstream consequences.

Indefinite float

The client owes you but isn't technically late, because the deadline was never set. You have no legal leverage to enforce payment on any timeline.

Late fees don't apply

Late fees are calculated from the due date. No due date = no late fees. Your late-fee clause is useless without a payment trigger.

Dispute over deliverable status

The client uses "completion" as leverage. "We'll pay when it's done — and it's not done because X." A specific date sidesteps this entirely.

Cash flow forecasting breaks

You can't plan your business if receivables have no due date. Payroll, vendors, overhead — all require predictable inflows.

Red-flag wording

These phrases feel like due dates. They aren't.

Every one of these appears in common contract templates. All of them are ambiguous when the client wants to delay.

Red flag

"upon completion"

Completion is subjective. Clients can — and do — dispute whether work is complete.

Red flag

"upon delivery"

What counts as delivery? Email? Upload? Formal handoff? If disputed, the clock never started.

Red flag

"when the project is finished"

Finished by whose definition? Same problem, different words.

Red flag

"net 30" with no trigger date

Net 30 from when? Without an anchor date, net 30 is as vague as "upon completion."

Red flag

"payment as mutually agreed"

If the mutual agreement isn't written in the contract, it's nowhere. This phrase is a placeholder for a deadline that was never set.

Safer pattern

The clause that puts a date on it.

The fix is to replace event-based triggers with date-based triggers wherever possible, and to define the event precisely where event-based triggers are necessary. A calendar date cannot be disputed the way "completion" can.

BizDraft writes specific payment triggers by default — tied to invoice date, delivery of specific milestones, or a fixed calendar date — calibrated to your project structure.

The pattern

Use invoice date as the trigger. "Payment is due within [N] calendar days of the invoice date. Provider will issue invoices on [specific schedule or trigger]."
Define delivery precisely. "Delivery is deemed to occur when Provider sends the deliverable file to Client's designated email address. Payment is due [N] days from the delivery date."
Add a fallback date. "If the parties dispute whether delivery has occurred, payment is due [N] days from the date Provider sent the disputed file."
Use milestones for long projects. "The project is divided into three milestones. Payment for each milestone is due within 7 days of milestone completion, as specified in Exhibit A."

Most affected