Net 30 means the full invoice is due 30 days from the invoice date. It is the most common payment term in commercial contracts, and it is worth knowing early that it is a convention rather than a rule — negotiable in both directions, and a great deal less fixed than it looks. Payment terms settle four things: how much is owed, what triggers the obligation to pay, when payment is due, and what happens if it is late. Most small business cash flow trouble traces back to payment terms that were accepted at signature without much thought, because at signature they are the least interesting page in the document. This guide covers how each element works and which ones are worth pushing on.
The short version
Net 30 means payment is due 30 days after the invoice date. Check what actually triggers the clock — invoice date, delivery, or acceptance — because “on acceptance” with no defined acceptance window can delay payment indefinitely. Add a late fee, take a deposit, and tie milestones to dates rather than approvals.
Payment terms are the contract provisions specifying the amount owed, the event that makes it payable, the deadline for payment, and the consequences of paying late.
What Net 30 Actually Means
Net 30 means the full invoice is due 30 days from the invoice date. Net 15 and Net 60 work the same way with different windows. Occasionally you will meet something like “2/10 Net 30”, which looks like a serial number and is simply an offer: take 2 percent off if you pay within 10 days, otherwise the full amount is due at 30.
The common misunderstanding is that Net 30 is standard in some binding sense — that it is the default the world falls back on. It is not, and the fallback is considerably less generous. Where a contract says nothing at all about timing, the Uniform Commercial Code provides that payment for goods is due at the time and place the buyer receives them, absent agreement otherwise. So silence does not hand anyone a 30-day grace period. It usually means payment is due on receipt. Every longer term exists because somebody negotiated for it — which is worth remembering when you are told that 60 days is just how it works.
Net 30 vs Net 15, Net 60, and Due on Receipt
All the net terms work identically and only the window changes. The number is simply the count of days from the trigger date until full payment is due.
- Due on receipt. Payment expected immediately. Common for small jobs, new clients, and deposits. Best for supplier cash flow, and the hardest for a client’s systems to actually process.
- Net 15. Two weeks. A reasonable middle ground, and often accepted where Net 30 was only ever the opening position.
- Net 30. The commercial default across most of the United States, and the number most accounts payable departments are quietly configured around.
- Net 60 and Net 90. Common when selling to large corporates and government. Perfectly manageable when expected and priced in; genuinely damaging when it turns up as a surprise after the work is finished.
- 2/10 Net 30. Two percent off for paying within 10 days, otherwise the full amount at 30.
Whether a discount like 2/10 Net 30 is worth offering depends entirely on what the cash is worth to you today. Two percent to move money forward by twenty days is expensive in annualised terms — properly expensive, the kind of number that makes a bank loan look reasonable. It earns its place when you genuinely need the cash earlier. It does not earn its place as a routine sweetener you have stopped noticing.
One practical note on Net 60 and beyond. Large buyers rarely move their standard terms, and it is usually not obstinacy: payment cycles are set centrally, by people several floors and one org chart away from whoever you are negotiating with. Where the days are genuinely immovable, stop pushing on them and ask for a deposit or milestone payments instead. You are far more likely to win a change to the payment structure than to the payment window, because the structure is the bit your counterpart is actually allowed to agree to.
What Actually Starts the Payment Clock?
One of three events, depending on what the contract says: the date you issue the invoice, the date you deliver, or the date the client formally accepts the work.
And this is the part of the whole article worth slowing down for. Whether the clock starts on invoice date, delivery, or acceptance matters more than whether the window is 30 days or 45. Everyone negotiates the number. Almost nobody negotiates the trigger, which is the thing that decides whether the number means anything at all.
- On invoice date. Cleanest for the supplier. The clock starts when you send the invoice, and it starts whether or not anyone is paying attention.
- On delivery. Reasonable enough, though arguments about what counts as delivered can push it around.
- On acceptance. The riskiest formulation by a distance. If the contract does not define an acceptance period, the client can decline to accept indefinitely, and the payment obligation simply never starts.
Acceptance criteria belong in the statement of work. If acceptance is the trigger, insist on deemed acceptance: language saying deliverables are automatically accepted if the client raises no written objection within a set number of days, commonly five to ten business days. Without it, “Net 30 on acceptance” is not a 30-day term at all. It is a clock with no hands, and the other party is holding them.
Recurring services follow a different pattern again. The trigger is the billing period rather than a deliverable, and the question becomes whether you invoice in advance or in arrears. Billing monthly in advance means you never fund more than the current period. Billing in arrears means you carry the cost of the work first and then wait out the net terms on top of that. Over an ongoing engagement that choice does not happen once — it repeats every single month, which is why it is worth settling at signature rather than during the first cash flow squeeze.
Where the work runs under a master services agreement, the payment terms usually live in the master agreement rather than in each statement of work, and that cuts both ways. Negotiating them once changes every project that follows. Accepting them without much thought at signature locks them in for the life of the relationship. Before trying to change payment terms in a project document, check which document actually governs them — a term you negotiated into a statement of work may not survive a conflict with the master agreement sitting above it.
Deposits and Milestone Payment Terms
Front-loading payment is the most effective protection available to a small supplier, and it is an entirely normal thing to ask for. Asking feels awkward exactly once; not asking feels awkward every month afterwards.
- Deposit up front. A quarter to a half before work starts. It covers your early costs and quietly filters out the clients who were never going to pay.
- Milestone payments. Split larger engagements into stages with payment at each. Tie milestones to dates or defined deliverables, never to somebody’s subjective approval.
- Final payment on completion. Keep the last tranche modest, because it is the one most likely to be argued over.
- Ownership on payment. State that intellectual property transfers only on payment in full. It is standard, and it gives the obligation real weight.
These structures matter most in freelance and consulting agreements, where one late-paying client can account for a large share of a month’s revenue.
Late Fees and What They Are Really For
A late payment clause typically sets interest — often expressed as a monthly percentage — or a fixed administrative fee. States regulate maximum interest rates, so a figure chosen for dramatic effect may turn out to be unenforceable.
Here is the thing about late fees, though: the practical value is rarely the money. Most suppliers never actually charge one. Its real function is to give you a legitimate, unembarrassing reason to chase an overdue invoice — you are not nagging, you are mentioning the clause — and to signal at signature that payment timing is something you keep track of. A contract with no late-payment consequence signals the opposite just as clearly.
Check for a suspension right too: the ability to pause work while an invoice is materially overdue. Without one you may be contractually obliged to keep delivering to a client who has stopped paying, which is the worst position on this entire page.
How to Negotiate Payment Terms
Payment terms are among the most negotiable provisions in any contract, for a simple reason: they cost the other side timing rather than money. Three approaches that work:
- Trade length for certainty. Offer Net 45 in exchange for a larger deposit, or a small discount for Net 10.
- Anchor to your costs. “Our subcontractors invoice us at 15 days” is concrete, verifiable and awkward to argue with.
- Fix the trigger, not the window. If you win only one point, make it deemed acceptance. It turns a vague obligation into a dated one.
The same principle that governs SaaS contract negotiation applies here: the terms easiest to win are the ones the other side does not measure. Procurement teams report on payment days. Nobody’s procurement team reports on acceptance windows.
ContractClerk checks payment terms during review, flags acceptance triggers with no deemed-acceptance window, and highlights missing late-payment and suspension rights before you sign. It is one of the checks in the pre-signing pass that most owners skip.
Payment is due in full 30 days from the invoice date. Net 15 and Net 60 follow the same pattern with different windows. Always confirm whether the contract starts the clock at invoice date, delivery, or acceptance, because that choice affects timing more than the number itself.
Generally not at a rate you choose. Without a contractual late payment clause you may be limited to statutory interest, which varies by state and is often lower. Including a late fee provision at signature is far easier than asserting one afterwards.
Yes. Deposits of 25 to 50 percent are standard for project work, particularly for freelancers, agencies, and trades. A client who objects to any deposit at all is worth a second look, because it often signals cash flow problems on their side.
It is a clause stating that deliverables are automatically accepted if the client raises no written objection within a set period, typically five to ten business days. Without it, a payment obligation triggered by acceptance can be postponed indefinitely by simply not responding.
Only if the contract grants a suspension right. Without one, stopping work may itself be a breach even where the client is overdue. Ask for the right to suspend performance once an invoice is materially late, with written notice first.
In advance, where cash flow is the constraint. Billing ahead of the period means the client funds the work; billing after it means you fund the work first and then wait out the payment terms on top. The gap between the two is a full billing cycle plus the net terms, and on a recurring service it repeats every period rather than happening once.
The Bottom Line on Payment Terms
Payment terms are where a perfectly profitable contract turns into a cash flow problem. The number of days matters far less than what starts the clock and what happens when it runs out. Fix the trigger, take a deposit, and make sure you can stop work if you are not being paid. Those three changes will do more for a small business than any amount of arguing over Net 30 versus Net 45.
This article is general information, not legal advice, and does not create an attorney-client relationship. Contract law varies by state and by situation. For high-stakes agreements, have a licensed attorney review the document.