Compare deposits, milestones, net terms, late fees, and kill fees.
Key takeaways
- State currency, tax treatment, invoice method, and due date.
- Define milestone evidence and a short dispute window.
- Explain late fees only where lawful and reasonable.
Payment terms that work in practice
For a $6,000 project, a 40% deposit, 30% approval milestone, and 30% delivery milestone creates three objective payment events. The contract should also say when an invoice is considered received, how long the client has to dispute it, and whether work pauses on an overdue balance.
Run a contract-specific review
Model the payment clause as a timeline before signing. Mark the deposit date, each invoice trigger, the due date, the grace period, the reminder date, and the point at which work may pause. If two people reading the clause produce different dates, the trigger needs clearer wording.
1. Choose the trigger
Use a calendar date or an observable milestone, not a vague phrase such as when convenient.
2. Allocate cash-flow risk
Use a deposit or short milestones when the freelancer must reserve significant capacity or purchase inputs.
3. Separate disputes
Require the client to identify the disputed amount and still pay undisputed invoices on time.
4. Define collection steps
Sequence reminder, grace period, suspension, restart conditions, and permitted recovery costs.
Stress-test the difficult case
Test the clause when the client accepts the work but its accounts-payable process misses the due date. Decide whether approval, invoice receipt, a purchase-order number, or vendor onboarding controls the clock. Address currency, transfer fees, sales tax, withholding, and rejected payments when the parties are in different jurisdictions. If the client can delay payment by withholding an internal reference number that the freelancer cannot create, the schedule is not operational. The agreement should assign responsibility for prerequisites and preserve a clear due date when an internal process fails.
Verification pass before signing
Run a sample invoice through the complete clause before signing. Use the actual fee, milestone date, payment method, and weekend or holiday rules to calculate the invoice date, due date, grace period, late notice, and possible suspension date. Confirm who receives each notice and what evidence proves delivery. Then test a partial dispute: identify the disputed amount, the undisputed amount, the response deadline, and the work status while the issue is reviewed. Save the calculation as a project record so both parties administer the same timeline.
Evidence to retain
Retain the signed schedule, invoices, delivery acknowledgements, reminder messages, dispute notices, and proof of each payment.
Worked example
For a $6,000 project, a practical schedule might use a $2,000 booking deposit, $2,000 after an approved prototype, and $2,000 before release of final source files.
What to verify
1. Scope
State currency, tax treatment, invoice method, and due date.
2. Trigger
Define milestone evidence and a short dispute window.
3. Evidence
Explain late fees only where lawful and reasonable.
4. Fallback
Give both sides a written process for disputed charges.
Build the decision record
| Review item | Record before signing |
|---|---|
| Choose the trigger | Use a calendar date or an observable milestone, not a vague phrase such as when convenient. |
| Allocate cash-flow risk | Use a deposit or short milestones when the freelancer must reserve significant capacity or purchase inputs. |
| Separate disputes | Require the client to identify the disputed amount and still pay undisputed invoices on time. |
| Define collection steps | Sequence reminder, grace period, suspension, restart conditions, and permitted recovery costs. |
Warning signs
- A due date without an invoice-delivery method.
- A late fee that conflicts with local law.
- Final files released before cleared payment.
Questions to resolve before signing
- What would prove that “choose the trigger” is satisfied if the parties later disagree?
- What would prove that “allocate cash-flow risk” is satisfied if the parties later disagree?
- What would prove that “separate disputes” is satisfied if the parties later disagree?
- What would prove that “define collection steps” is satisfied if the parties later disagree?
Sources and further reading
- IRS: Independent contractor status
- U.S. Copyright Office: Works made for hire
- FTC: Endorsements and testimonials
External sources explain general rules and terminology. Your signed agreement, current policy, jurisdiction, provider documents, and individual facts control the actual outcome.
Open the related ContractFixPro tool