NET 60 vs NET 30: How to Negotiate Freelance Payment Terms

"NET 60" means the client can wait 60 days after receiving your invoice before paying you. On a $15,000 project, that's a two-month, interest-free loan you never agreed to.

Payment terms are one of the most negotiable parts of any freelance contract, and most freelancers never try.

What NET actually means

NET 30, NET 60, NET 90 — the number is the number of days the client has to pay an invoice. NET 30 means 30 days from invoice date. NET 60 means 60 days.

For a freelancer invoicing monthly, NET 60 means you're always waiting two months for each payment. In practice, large companies often pay late even against NET 60 — so you're looking at 75–90 days in reality.

The industry standard for freelancers is NET 15 to NET 30. NET 60 is standard for enterprise vendor contracts and was never designed with independent contractors in mind. You're being slotted into a payment process that treats you like a Fortune 500 supplier.

The three clauses that actually get you paid

1. A short payment window.

"Client shall pay all invoices within 15 days of receipt."

Even if you accept a longer window under client pressure, start at 15. You'll often land at 30, which is a reasonable outcome.

2. Late payment interest.

"Invoices not paid within the payment window shall accrue interest at 1.5% per month (18% per annum) from the due date until paid in full."

This clause rarely gets enforced — you're not going to send a client an interest invoice. But its presence changes behavior. Clients with accounts payable teams notice payment clauses; those teams don't like accruing interest liabilities.

3. Right to suspend services.

"If any invoice is not paid within 30 days of the due date, Contractor may suspend all services under this Agreement upon 5 days written notice. Services shall resume upon receipt of all past-due amounts. Contractor shall not be liable for any delays or damages resulting from a payment-related suspension."

This is the clause with teeth. It transforms late payment from an annoyance into a business risk for the client. Projects have deadlines; pausing work has consequences they care about.

Upfront payments and milestone structure

The most effective protection against late (or non-) payment is a payment structure that doesn't let the client get too far ahead without paying.

A standard structure for fixed-price projects:

25–50% upfront on signing. 25–50% at a defined midpoint milestone. Balance on final delivery.

Never deliver your final work before receiving your final payment. This is the single most common freelancer mistake. The moment they have the files, your leverage disappears.

Add it explicitly: "Final deliverables will be transferred to Client upon receipt of the final payment. Contractor retains possession of all work product until full payment is received."

What to do about "our AP process requires NET 60"

This is the standard pushback from enterprise clients. Their accounts payable system is set up for NET 60 and changing it requires IT tickets and approvals.

Two responses that work:

Accept NET 60 with interest from day 1: "Client's standard payment term of NET 60 is accepted; however, interest at 1.5% per month accrues from invoice date, not from the due date." This prices the float. Some clients will suddenly find a way to pay faster.

Add a discount for early payment: "2/10 NET 60 — Client receives a 2% discount if payment is received within 10 days of invoice." Accounts payable teams love early payment discounts; it's a legitimate reason to prioritize your invoice.

Expense reimbursement timing

If your contract includes expense reimbursement, make sure there's a separate clause covering timing — not just "reimbursable expenses shall be paid." Some clients treat expense reimbursements as optional or batch them quarterly:

"Approved expenses shall be reimbursed within 15 days of submission of receipts, regardless of the standard invoice payment window."