Quick Answer
When a client imposes their own payment terms, the terms themselves are often less negotiable than everything around them. Before agreeing, find out whether the number is a genuine procurement policy or just a preference someone typed in an email — the two look identical in writing and only one is fixed. If Net 60 truly cannot move, trade it rather than absorb it: ask to invoice more often so each clock starts earlier, request a deposit, pin down exactly what event starts the count, or price the delay into the rate. Accepting a longer cycle in exchange for nothing is the only genuinely bad outcome.
Sooner or later a client sends back your proposal with their own payment terms attached — usually Net 60, sometimes Net 90, occasionally wrapped in a twelve-page vendor agreement. The instinct is to treat it as a yes-or-no question. It almost never is. The number itself is often the least negotiable thing in the document, while everything around it — when the clock starts, whether you get a deposit, how often you invoice, what happens if approval stalls — is wide open, and nobody at the client's end expects you to ask. This guide covers how to tell whether the terms are genuinely fixed, what a longer cycle costs you in cash, the seven things worth trading for it, and five scripts for pushing back without sounding difficult.
First, Find Out If the Terms Are Actually Fixed
Imposed terms arrive in three forms, and they look nearly identical in writing while being wildly different in how much they can move. Work out which one you are holding before you respond, because the answer changes the entire conversation.
| How it arrived | Who decided it | How movable |
|---|---|---|
| A line in an email — "we normally pay on 60 days" | The person hiring you, often quoting a half-remembered norm | Very — frequently collapses to your terms when questioned once |
| A clause in a vendor agreement or MSA you are asked to sign | Legal, from a template that predates you | Somewhat — redlines are normal and expected, but each round costs days |
| A setting in a procurement or AP system | Finance policy, applied to every vendor | Rarely for the number — but almost everything else still is |
The distinction matters because freelancers routinely accept the first type as though it were the third. One question — "is that a company policy, or is there room to agree something between us?" — separates them, and it is an ordinary thing to ask. If the answer is a policy, ask which parts of it are policy: payment terms and invoicing frequency are usually set by different people, and the second person has not been asked.
It is also worth knowing who actually pays you before you negotiate with anyone. At a company of any size, the person commissioning the work does not control the payment run, and our guide to how clients actually process invoices covers the accounts payable side — vendor onboarding, W-9s, purchase orders and supplier portals — that quietly adds weeks on top of whatever number you agree.
What Net 60 Actually Costs You
Before deciding whether a longer cycle is acceptable, it helps to know what you are being asked to absorb. The answer is not a percentage and it is not a loss — it is a fixed amount of your own money that you stop being able to touch.
Suppose you bill $8,000 a month. On Net 30, at any given moment roughly one month of billing is sitting unpaid: about $8,000 of your work exists as an invoice rather than as cash. Move to Net 60 and that steady-state figure roughly doubles to $16,000. The difference — $8,000, one month of billings — is the real price of the change.
Two things about that number matter. The first is that it is a one-time step, not a recurring loss — you do not lose $8,000 every month, you lose the use of $8,000 once, for as long as the client is on those terms. That is why longer terms are survivable for a business with a cushion and dangerous for one without: the entire cost lands in a single month.
The second is that the painful month is the transition. In the month you switch a client from 30 to 60 days, the invoices that would have paid arrive 30 days later instead, so collections from that client fall to roughly nothing for one cycle while your own costs carry on. Plan for that month specifically. It is the part that catches people out, and it is entirely predictable.
The exposure question nobody asks
Longer terms also double how much of your revenue is at risk with one client at any moment. On Net 30 you have about a month of work exposed if a client disputes an invoice, goes quiet, or fails; on Net 60 it is two. If a single client is most of your income, the terms conversation is also a concentration-risk conversation — and that is a legitimate thing to say out loud in a negotiation.
If you want to know what your terms are costing you in practice rather than in theory, measure the gap between the terms you offered and the days you are actually paid in — our guide to freelance invoicing best practices covers how to calculate days sales outstanding per client. A client on Net 60 who reliably pays on day 58 is a very different proposition from one on Net 30 who pays on day 75.
Create Professional Invoices in Minutes
Stop spending hours on invoicing. InvoiceBloom lets you create, send, and track invoices — so you can focus on the work that matters.
Free to create. No credit card required.
Negotiate the Trigger Before You Negotiate the Number
This is the most valuable thing in this guide and the thing almost nobody raises. "Net 60" is meaningless on its own, because it does not say 60 days from what — the same two words can describe four quite different waits.
| Trigger | What it means in practice |
|---|---|
| Invoice date | The clock starts when you send it. The only version where 60 days means 60 days. Always ask for this one. |
| Date of receipt | Starts when the invoice lands in their system — adds however long the email sits, or the portal takes to register it. |
| Date of approval | Starts when someone signs off. With no deadline on approval, the total wait is unbounded — this is the dangerous one. |
| Month end or a fixed payment run | Counts from the end of the month rather than the invoice, which can add most of another month depending on the date you invoiced. |
Approval-triggered terms deserve particular attention. "Payment due 60 days following approval of the invoice" gives the client an open-ended right to not start your clock, and the delay is usually not malice — it is one person on leave. The fix is short and almost never refused: ask for a deemed-approval clause, something like "the invoice is deemed approved if no written objection is received within five business days of receipt." That turns an unbounded wait into 65 days you can plan around.
Terms that count from the month end have their own arithmetic, which our guide to Net 30 and other payment terms breaks down in full — including why an invoice dated early in the month can wait nearly twice its stated term. Read that before agreeing to anything with "EOM" in it.
Seven Things to Ask For Instead
When the number genuinely will not move, stop pushing on it and trade it instead — the one bad outcome here is absorbing a longer cycle and getting nothing for it. These are ordered roughly by how often they are granted.
| Ask | Why it works |
|---|---|
| Invoice more often | Monthly instead of on completion means each clock starts earlier. This is an invoicing-schedule question, not a terms question, so it is usually granted by a different person and far more easily. |
| A deposit up front | Cuts the exposed amount immediately and often sits outside the terms policy entirely, because it is raised as its own line rather than as a change to payment terms. |
| A defined clock trigger | Costs the client nothing and removes weeks of hidden delay. The cheapest thing on this list to say yes to, which is why it is the easiest to win. |
| The delay priced into the rate | Entirely reasonable if raised at proposal stage. Almost impossible to raise after you have quoted, so it has to come up now. |
| A cap on open exposure | "Net 60 applies up to $X of unpaid work; beyond that, work pauses until an invoice clears." Protects you without asking them to change any policy. |
| A late fee written into the agreement | Makes the deadline mean something. Sometimes struck out by legal, but asking costs nothing and its presence changes how the invoice is treated. |
| An early payment discount | Some AP departments have a standing policy of capturing these. Genuinely expensive to you, so treat it as a last resort rather than an opener. |
Two of those need a caution before you use them. An early payment discount looks cheap and is not — giving up 2% to be paid twenty days sooner is an expensive trade once annualized, and our guide to early payment discounts works through what each common term really costs before you offer one. And late fees only work when the amount is defensible and stated in advance; our guide to how much late fee to charge covers typical rates, grace periods and the state caps that make an aggressive fee unenforceable.
On deposits, the mechanics of crediting one against the final bill are worth getting right before you propose it — our guide to when to send an invoice covers how to bill the balance so the numbers reconcile. And if you are considering pricing the delay into your rate, check the change actually survives contact with your costs first; the profit margin calculator will tell you what margin you are working on, and the freelance rate calculator what the new rate needs to be.
Five Scripts for Pushing Back
Tone does most of the work here. None of these are confrontational, none of them threaten to walk, and all of them are things a supplier says to a client every day of the week.
Script 1: Testing Whether the Terms Are Real
"Thanks — before I confirm, is Net 60 a fixed company policy or is there room to agree terms between us? My standard is Net 15, and I'd rather ask than assume. If it is policy, no problem at all, I'd just want to talk through a couple of small things around invoicing frequency."
Script 2: When Procurement Says It Cannot Move
"Understood, I'll work to Net 60. Two things that would make it work comfortably on my side, neither of which changes your payment terms: I'd invoice monthly rather than at the end of the project, and I'd ask for 30% up front at kickoff. Both are pretty standard for engagements this length — can you confirm those work?"
Script 3: Pinning Down the Clock
"One clarification on the terms — is the 60 days counted from the invoice date, or from approval? If it's from approval, could we add that the invoice is deemed approved if there's no written objection within five business days? That way a colleague being on holiday doesn't quietly turn 60 days into 90 for either of us."
Script 4: Refusing Pay-When-Paid
"I can't sign clause 8 as written — it makes my payment conditional on your client paying you, which is a timeline neither of us controls. I'm happy with the 60 days themselves. Could we replace it with: 'Payment is due within 60 days of the invoice date regardless of Client's arrangements with third parties'?"
Script 5: Accepting, in Writing
"Confirming what we agreed so it's all in one place: Net 60 from invoice date, invoices monthly on the last working day, 30% deposit at kickoff, and work pauses if unpaid invoices go above $10,000. I'll put these on every invoice. Let me know if I've misremembered anything."
Script 5 is the one people skip and the one that matters most. A concession agreed verbally with the person who hired you does not exist as far as accounts payable is concerned. Get it into an email, and make sure it reaches whoever set up your vendor record.
What to Never Accept
Most imposed terms are merely inconvenient. A few are structurally bad and worth holding a line on, even at the cost of the engagement.
- Pay-when-paid. Your payment becomes conditional on the client's own client paying them — a timeline nobody in your contract controls, and one you cannot chase. Our freelance contract guide covers this and the other clauses worth striking, with replacement wording.
- Terms with no stated trigger. "Net 60" alone in a signed agreement is an argument waiting to happen, and you will be the one arguing.
- Approval-gated terms with no approval deadline. An unbounded wait dressed as a number. Deemed approval fixes it in one sentence.
- Retroactive application. New terms should apply to new work. Work already delivered was priced and scheduled against the old ones.
- Terms that contradict a contract you have already signed. A vendor portal's default settings do not override an executed agreement — but if you go along with them for a few invoices, expect that to be raised later.
Once You Have Agreed, Make the Long Clock Survivable
Accepting Net 60 is not the end of the problem, it just changes its shape. Four habits do most of the work of keeping it from hurting.
- Invoice the same day you finish, every time. On a 60-day cycle, a week of your own delay is a week you never get back — and it is the only part of the wait entirely within your control.
- Complete the vendor setup before the first invoice, not with it. Onboarding runs sequentially, so a W-9 sent alongside your invoice adds its own processing time to your terms rather than overlapping with them.
- Start following up earlier, not later. A long cycle means a problem discovered on day 60 is already two months old. Our guide to handling late-paying clients covers the escalation schedule and, more usefully, the questions that surface a stuck invoice while there is still time to unstick it.
- Put the agreed terms on the invoice itself. Not in the covering email — on the document, where the person paying it will see them.
That last point is where a bit of tooling helps. In InvoiceBloom, you set the due date on each invoice yourself, so a Net 60 client's invoice simply carries a different due date from a Net 15 one, and the payment instructions box is the place to spell out the agreed wording — "Net 60 from invoice date, as agreed 21 August". Because payment instructions default to whatever you have saved on your account, you can set that once and have it print on every invoice you send, in any theme. It is free to use, with everything included. One caveat worth knowing about any invoicing tool, ours included: marking an invoice overdue is a status you set, not something a passing due date does on its own — which is why the follow-up habit above is doing the real work, not the software.
If your client is overseas, note that longer cycles are simply the norm in some markets rather than a negotiating position — our guide to invoicing international clients covers which regions commonly run on 60 to 90 days, and how transfer time stacks on top of whatever you agree.
When to Walk Away
Sometimes the honest answer is no. The signals worth taking seriously are not the terms but what surrounds them: a client who will not put the terms in writing, who applies new terms to work already delivered, or who refuses a deposit while also refusing to shorten the cycle. Long terms from a company that pays reliably on day 60 are a cash-flow problem you can plan for. Long terms from a company that treats the due date as an opening offer are a different thing entirely, and no clause protects you from it.
The practical test: if this client paid you on their stated terms every single time, would the engagement still be worth having? If yes, negotiate the trade and take the work. If no, the terms were never the real problem.
Frequently Asked Questions
Do I have to accept a client's payment terms?
No. Payment terms are a term of the contract like the rate or the scope, and they are agreed between you rather than imposed. What is true is that at larger companies the number itself may be genuinely fixed by finance policy, in which case pushing on it wastes goodwill you could spend elsewhere. The productive approach is to establish which category you are in — a preference typed by the person hiring you, a clause in a template agreement, or a system-level policy — and then negotiate the things around the number, which are almost always still open.
What does moving from Net 30 to Net 60 actually cost me?
Roughly one month of your billings, tied up permanently rather than lost. If you invoice $8,000 a month, about $8,000 sits unpaid at any moment on Net 30; on Net 60 that steady-state figure roughly doubles to $16,000, and the $8,000 difference is money you can no longer touch for as long as the client is on those terms. It is a one-time step rather than a recurring loss, which is why the month you switch is the hard one — collections from that client drop to near zero for a single cycle while your costs continue.
Can a client change payment terms after we have already started?
They can ask, and it happens most often when a company rolls out a new procurement system or gets acquired. They cannot unilaterally change terms you have already agreed in a signed contract, and new terms should apply to new work rather than to invoices already issued. If you receive a notice like this, reply in writing confirming that existing invoices remain on the original terms, and treat the change as a fresh negotiation — including the opportunity to ask for something in exchange, which is easier now than it will be later.
What should I ask for if Net 60 genuinely cannot be changed?
Invoice more frequently, ask for a deposit, and pin down what starts the clock — those three are granted most often because none of them requires anyone to change a payment-terms policy. Invoicing monthly instead of at project end starts each clock earlier; a deposit reduces how much of your work is exposed at any moment; and confirming the count runs from the invoice date removes weeks of hidden delay at no cost to the client. Beyond those, a cap on total unpaid work, a stated late fee, and pricing the delay into your rate are all reasonable asks if raised before you quote.
What does "payment due 60 days after approval" mean?
It means the 60-day count does not begin until someone at the client signs off on your invoice, so the total wait is however long approval takes plus 60 days. With no deadline on the approval step, that total is unbounded — an invoice sitting in an absent manager's queue simply has not started its clock. Ask for a deemed-approval clause stating that the invoice is treated as approved if no written objection arrives within a set window, commonly five business days. That converts an open-ended wait into a predictable one, and it is rarely refused because it costs the client nothing.