Client sent a Net-60 freelance contract with no late fee — what do you push back on first?

You open the PDF. Payment is Net-60. There is no late interest, no right to pause work, and IP might already transfer on delivery. The rate looks fine. The cash-flow math does not.

This is a common package in agency and enterprise paperwork. The goal is not to win every clause. It is to decide what you change first, what you trade, and what you walk away from.

This article is general information for freelancers and indie consultants. It is not legal advice. Laws on interest, penalties, and collection differ by place. For a large deal or a dispute, talk to a lawyer where you work.

What Net-60 actually costs you

Net-60 means the client may pay up to sixty days after the invoice trigger (usually the invoice date). On a $6,000 project that is two months of you financing their payables cycle.

Long terms are not automatically unfair. They become a problem when they stack with:

• No deposit on a fixed-fee job
• No late fee or interest after the due date
• Payment only after “acceptance” with no review deadline
• IP or final files delivered before the last invoice clears

If those four show up together, you are taking most of the timing risk.

Push-back order (what first)

When time is short, negotiate in this order. Each step buys cash-flow protection without rewriting the whole MSA.

1. Shorten the clock — or price the wait

Ask for Net-15 or Net-30 as the default.

If the client’s AP team will not move off Net-60, do not argue culture. Price it:

• Raise the fee (many freelancers use roughly 5–15% for a long payable cycle — pick a number you can defend), or
• Keep Net-60 but require a larger kickoff deposit, or
• Offer a small early-pay discount so Net-30 becomes the rational choice for them.

You are not being difficult. You are naming the cost of capital.

2. Put money in before you start

For fixed-fee work, aim for 30–50% on signing (or on kickoff), with the rest on milestones or delivery. For hourly work, bill weekly or biweekly instead of one balloon invoice at the end.

A deposit does more for you than a polite Net-30 sentence that nobody’s AP desk will honor on day one.

3. Add a late-payment consequence that is modest and lawful

A clause that does nothing after day 61 invites silence. A workable pattern many freelancers use:

• Interest or a late charge at a modest monthly rate, capped at whatever your governing law allows
• A short written notice
• The right to pause further work (and sometimes withhold final source files) until undisputed overdue amounts are paid

Do not invent a punitive percentage because it “looks serious.” Extreme rates can be unenforceable where you live. If you are unsure, keep the number conservative and emphasize the pause-work right — operational leverage often collects faster than interest math.

4. Define when the clock starts

Net-60 of what? Spell it out:

• Invoice date, or
• Delivery, or
• Written acceptance within a set number of days — with silence = acceptance

“Paid when the stakeholder is happy” with no deadline is not a payment term. It is an open tab.

5. Only then: IP and cancellation

Once payment timing is less dangerous, check two siblings that decide your leverage if the invoice stalls:

• Does ownership transfer on creation/delivery, or only after full payment?
• If they cancel mid-project, is there a kill fee or payment for work in progress?

Those topics deserve their own read — see IP that transfers before payment and what a fair kill fee looks like. For a structured primer on net terms and late fees, use the payment terms guide.

Sample negotiation email (short)

You can adapt this. Keep it calm and specific.

Thanks for sending the agreement. I’m aligned on scope and timeline. On commercial terms I’d like to adjust three items so cash flow stays workable on both sides: 1) Payment Net-30 from invoice date (or Net-60 with a 40% kickoff deposit). 2) A simple late-payment provision and the right to pause work after written notice if an undisputed invoice stays unpaid. 3) IP in the deliverables assigns after that invoice is paid in full; until then you get a review license only. Happy to jump on a quick call if your AP team needs a different structure.

Most reasonable clients will move on one or two of these. If they refuse all three and the project is large relative to your runway, that is data — not a personality conflict.

Red flags that mean “slow down”

• Net-60 plus “pay when paid” by an end client you never met
• Invoices must clear an unnamed portal with no approval SLA
• Broad set-off rights that let them withhold your fee over unrelated disputes
• Acceptance criteria that are purely subjective with no review window
• Final editable files due before any substantial payment clears

Any one of these is negotiable. Several at once is a reason to shrink scope, raise price, or decline.

How to review the PDF you were just sent

Read payment, acceptance, IP, and termination in one pass — they interact. If you want a second pair of eyes on the wording before you reply, you can paste the draft into ClauseClear and get the risky clauses explained in plain English. It is a review aid, not a substitute for a lawyer on a high-stakes deal.

When the commercial terms are agreed, send invoices that match the contract (same entity name, PO, due date, currency). A clear invoice template helps if you need one quickly.

Bottom line

On a Net-60 draft with no late fee, fix the payable cycle first (shorter terms, deposit, or priced wait), then add a lawful late consequence and a clear invoice clock, then tidy IP and cancellation. You do not need a perfect MSA. You need a package you can survive if AP is slow.