Why Net 30 Is Bad for Cash Flow (and When It Still Makes Sense)
Why net-30 terms can hurt supplier cash flow: DSO math, cost-of-capital examples, early-pay options, and when net 15 or ACH-on-delivery beats net 30 terms.
Bottom line
The complaint that net 30 is bad usually means unpaid invoices sitting thirty-plus days tax operating cash. If you deliver in week one and collect on day thirty, you financed the customer's inventory or labor float. At a 12% annual cost of capital, $100,000 of average AR costs roughly $1,000 per month before collections labor and write-off risk. Prefer shorter terms, deposits, or ACH-on-delivery when you have leverage; keep net 30 when the buyer's procurement policy is rigid and margin already prices the float. For sample clause wording see net 30 payment terms example; for longer cycles see net 60 payment terms.
Is it right for you?
- Measure actual DSO vs contractual net 30
- Price cost of capital into large net-30 accounts
- Offer early-pay discounts only if the math works
- Move repeat SMB buyers to net 15 or card/ACH on invoice
- Use deposits on custom work
- Do not confuse “net 30 is standard” with “net 30 is free”
- Pair terms with invoice follow-up and collections playbooks
- Review net 60 requests as a margin problem, not a favor
Mini dataset: float cost
Assume average AR principal P and annual cost of capital r. Monthly float cost ≈ P × r / 12.
Row 1: P=$50,000, r=12% → ≈ $500/month. Row 2: P=$200,000, r=12% → ≈ $2,000/month. Row 3: P=$200,000, r=18% (expensive revolver / venture debt) → ≈ $3,000/month.
Row 4: Same $200,000 if customers actually pay in 45 days (DSO 45 on “net 30” paper) → you finance 1.5 months; at 12% that is ≈ $3,000/month on that slice, plus collections labor.
Add portal chasing, lockbox fees, and write-off risk. Those costs never appear in the contractual label “net 30,” which is why teams underestimate it.
Why teams still offer net 30
Enterprise procurement templates default to it. Sales teams fear win-rate collapse. Competitors advertise it. Those are real constraints, just price them.
If win-rate collapses without net 30, raise price, require deposits, or shorten only for SMB segments rather than pretending float is free.
Compare structures in net 15 vs net 30. Sometimes the winning move is net 15 for new logos under a threshold and net 30 only above it with credit checks.
Better patterns than silent net 30
Net 15 for SMB and freelancers who buy repeatedly. 30-50% deposit on custom SKUs. ACH auto-pay discounts that are smaller than your float cost. Milestone billing for projects. Card-on-file for low-ticket SaaS-like services.
Early-pay discount example: 1% 10 net 30 means the buyer pays 1% to pay 20 days early. Annualized rough cost to buyer is high; whether you should offer it depends on your r and whether buyers actually take it.
Operational pairings: invoice follow-up email, invoice-to-cash software. Terms without collections process still produce DSO 45.
Credit policy and exception handling
Publish a credit policy: who gets net 30, who gets prepay, what financials you require above a threshold, and who can approve exceptions.
Exceptions should expire. A one-time net 45 for a strategic logo that silently becomes standing policy is how AR balloons.
Watch concentration risk: three customers on net 30 holding 60% of AR is a treasury problem, not just a sales win.
Construction and lien-adjacent note
In construction, slow pay interacts with lien rights and waiver timing. Shortening terms does not replace correct lien waiver practice, see unconditional lien waiver template and the conditional vs unconditional guide.
Do not trade an unconditional waiver on unpaid work just to “be easy to work with” on net 30 paper. That stacks float risk with rights release risk.
Worked decision sketches
Sketch A , Agency with $80k AR, r≈12%. Silent net 30 costs roughly $800/month before labor. Moving half of clients to net 15 with ACH can cut float materially if DSO follows.
Sketch B , Manufacturer selling to big-box procurement. Net 30 or net 60 may be mandatory. Price the SKU to include float; negotiate deposits on custom runs.
Sketch C , SaaS with monthly invoices. Card-on-file beats net 30 for SMB. Reserve net 30 for enterprise with credit review.
Sketch D , Customer asks net 60. Treat as discount request. See net 60 payment terms and re-quote.
Internal controls and audit trail
Name owners for credit-policy exceptions, term-code changes in the AR system, and collections escalation. Every net-30 (or longer) exception needs an approver, an expiration date, and a dollar limit.
Quarterly sample: pull ten invoices that aged past contractual terms and confirm the exception approval, dunning steps taken, and whether DSO movement matched the promised cure.
Segregate duties so the same salesperson cannot alone extend terms and also release a credit hold without finance review.
When you migrate AR platforms, preserve term codes, exception flags, and early-pay discount markers on day one so a silent default-to-net-30 does not erase policy work.
Measuring whether terms changes worked
Track DSO, percent current, percent 1-30 / 31-60 / 61+, and cash collected within contractual terms. Changing invoice language without measuring DSO is theater.
Segment by customer size. Net 15 may work for SMB while enterprise stays on net 30 with priced margin.
After introducing ACH auto-pay, measure adoption and days-to-cash for adopters vs non-adopters.
If early-pay discounts are offered, measure take-up rate and whether the discount costs more than the float saved.
Review write-offs quarterly alongside terms policy. Loose terms plus weak credit checks show up as bad debt, not just slow cash.
Sales enablement without giving away the treasury
Give sales a one-pager: standard terms, allowed exceptions, approval matrix, and sample scripts for deposit requests.
Compensate thoughtfully: if commissions pay on booking while cash arrives at day 45, sales will always push longer terms. Align incentives or accept the AR cost explicitly.
For RFPs that mandate net 60, require a pricing uplift checklist before legal marks up the MSA.
Customer success should know when a “friendly extension” becomes a credit decision. Extensions beyond policy need the same approver as original exceptions.
Publish win stories where shorter terms closed faster because procurement saw deposits as normal for custom work, not only stories about discounting.
Systems that make shorter terms stick
Invoice on delivery triggers, not on the salesperson’s memory. Delayed invoicing recreates net 45 even with net 15 paper.
Portals that hide invoices add days. Confirm customers received the PDF and that PO numbers match on day one.
Dunning sequences should start before the due date with courtesy reminders, then escalate after due, see invoice follow-up guidance on this site.
Credit holds on future shipments for chronic late payers must be enforceable. Terms language without operational teeth will not fix cash.
When migrating AR platforms, preserve term codes and exception flags. Silent default-to-net-30 migrations undo months of policy work.
Board-level framing in one paragraph
Net 30 is not a moral failing; unpriced net 30 is a silent financing program for customers. Boards should see AR float cost next to revenue growth so sales wins are not celebrated while treasury sells equity to fund receivables.
Ask for a quarterly chart: contractual terms mix, DSO, float cost at current WACC or revolver rate, and exception aging. If exception aging rises, the policy is fiction.
Approve a credit policy annually the same way you approve expense policy. Terms are credit.
When M&A diligence appears, buyers discount businesses with long DSO and weak collections. Cleaning terms before a process can raise valuation more than a last-minute discount sprint.
Tie this article to invoice-to-cash tooling investments with a simple ROI: float saved plus labor saved minus software cost. If the ROI is negative, fix process first, then software.
Translate AR days into monthly financing cost using your actual weighted average cost of capital, then show the same chart with a ten-day terms pilot on the top twenty accounts. Boards react to dollars and concentration risk faster than to abstract DSO slogans. Keep the pilot reversible and time-boxed so sales can see the experiment design rather than a permanent decree.
Customer conversation patterns that protect cash
At proposal: state standard terms in the pricing sheet, not only in the MSA appendix nobody reads.
At kickoff: confirm AP contact, portal, PO, and invoice email. Wrong AP routing adds weeks.
At first late invoice: courtesy reminder with copy of terms and offer of ACH setup help.
At repeat late: credit hold warning with sales and success on the thread so the customer hears one company voice.
At strategic account review: show the cost of float and propose deposits on rush work rather than blanket net 45 expansions.
Script the early conversation so sales does not apologize for shorter terms. Frame deposits and ACH-on-delivery as shared risk reduction: you schedule crews confidently, they lock pricing without change-order fights caused by cash stress. Offer a documented discount for early pay only when margin math still clears after the discount.
When a strategic account insists on net 30, capture the exception with an expiration date, a credit limit, and a collections owner. Exceptions without owners become permanent policy by neglect. Review the exception list monthly with finance and sales leadership so float does not silently expand.
FAQ
Is net 30 illegal?
No, it is a commercial choice. The harm is cash timing, not legality.
What about net 60?
Same float math, worse. See the longer-cycle terms guide.
Does a lien waiver fix slow pay?
No. Waivers manage lien risk; they do not shorten DSO.
Should I always refuse net 30?
No. Refuse unpriced net 30. Priced net 30 with collections discipline can be fine.
Where do examples of term language live?
Open the sample-clause page linked from the verdict for ready-to-adapt wording.