Net 60 Payment Terms: Due Date Math and Cash-Flow Tradeoffs

Quick answer

Payment-term guides from processors and AP platforms define Net X as "pay within X days." Stripe's net-terms explainer and vendor blogs on Net 60 use the same structure: the number is the day count, not a partial payment schedule unless you add installment language.

Always confirm whether day 0 is the invoice date, the goods-received date, or the approval date: large buyers sometimes redefine "Net 60" in their vendor portal.

Due-date examples

If the contract says "Net 60 from acceptance," a three-week acceptance delay silently becomes Net 81 from ship date: capture that in the CRM credit file.

When Net 60 is rational

Sellers accept Net 60 for strategic logos, high margins, or when inventory is customer-funded. Otherwise prefer shorter terms, progress billing, or card-on-file for SMBs. Model DSO impact before agreeing: moving a book of business from Net 30 to Net 60 can add roughly a month of receivables.

How the due date is computed

Under plain "net 60" language, start at the invoice date, add 60 calendar days, and that date is when payment is due. Contracts sometimes start the clock on delivery, acceptance, or end of month (EOM). Read the governing MSA before you trust the accounting system's default.

Example: invoice date 2026-10-01 with net 60 → due 2026-11-30 if using calendar days from invoice date. If the contract says "net 60 from acceptance," a slow acceptance certificate moves cash out.

Cash-flow and discount tradeoffs

Sellers funding payroll on net 60 invoices need either a cash buffer, invoice financing, or earlier milestone billing. Buyers pushing net 60 are shifting working capital onto the vendor.

Early-pay discounts (for example 2/10 net 60) need explicit math: compare discount yield to your cost of capital. Do not offer 2/10 if every customer takes 60 days anyway without penalty.

Late fees and interest clauses only help if you invoice them and the contract allows. Silence trains late payers.

Collections playbook aligned to net 60

Day 0: send invoice with PO reference. Day 45: polite reminder with copy of invoice. Day 60: due-date notice. Day 67: escalate to AP manager and your sponsor. Day 75+: evaluate hold-shipment rights under the contract.

Keep a single AR owner per strategic account so reminders do not collide. Log every promise-to-pay date.

Negotiation levers

If a strategic buyer insists on net 60, counter with deposits, milestone invoices, or a higher price that embeds the cost of capital. Giving both price and terms concessions stacks pain.

Offer net 45 as a midpoint, or net 60 with an early-pay discount that you actually honor through AP automation. Fake discounts destroy credibility.

For startups selling to enterprises, net 60 (or worse) is common. Raise the seed cash plan accordingly in place of pretending SaaS cash collection matches subscription marketing slides.

Put stop-work rights in the MSA after a defined delinquency. Unused rights still change negotiation tone when AR escalates.

Measure DSO by segment. If net 60 customers actually pay on day 75, your real term is net 75 and pricing should reflect that.

DSO math you can show the CFO

If half your revenue sits on net 60 and those customers actually pay on day 72, your cash conversion is closer to net 72. Multiply daily revenue by the extra twelve days to estimate trapped cash. That number belongs in pricing talks, not only in AR complaints.

Segment DSO by channel: enterprise net 60, mid-market net 30, self-serve card. Blended DSO hides which segment needs deposits.

Re-forecast weekly during the first quarter you introduce net 60 to a large logo. Liquidity surprises show up before the first late fee.

Contract clauses that make net 60 survivable

Pair net 60 with a deposit or progress invoice on custom work. Pure net 60 on a twelve-week build funds the customer with your payroll.

Define when the clock starts: invoice date, delivery, or written acceptance. Ambiguity becomes a free extension for slow AP teams.

State late interest and suspension rights even if you rarely enforce them. Silence invites permanent day-90 payers.

Worked calendar

Invoice dated 1 October, plain net 60 from invoice date means due 30 November. Reminder on 15 November, due notice on 30 November, escalation on 7 December if unpaid. Do not wait until January because of holidays.

If the MSA says net 60 from acceptance and acceptance lands 20 October, due becomes 19 December. Configure the ERP start rule to acceptance date or collectors will call too early and burn goodwill.

Portfolio rules for sales

Cap the share of new ARR sold on net 60 unless treasury signs off. Sales will otherwise maximize close rates by giving away cash timing.

Require credit checks above a threshold before net 60 is offered. Net 60 to an unknown buyer is an unsecured loan.

Publish an internal matrix: starter plan net 15 card, growth plan net 30, enterprise net 60 with deposit. Ambiguous whatever-they-ask destroys forecasting.

When a customer asks to stretch from net 30 to net 60 mid-contract, treat it as a commercial amendment with price or term trade, not a free AP courtesy.

Report promised versus actual days-to-pay by account executive. Patterns of chronic late logos should feed renewal pricing.

Treasury coordination

Share the net 60 pipeline with treasury before quarter close so revolver draws are planned. Surprises on day 58 are expensive.

If you factor invoices, confirm the factor accepts net 60 paper and what advance rate applies. Longer terms often cut the advance.

Hedge foreign-currency net 60 receivables if the notional is material; a sixty-day FX move can erase the deal margin.

Buyer-side playbook (so sellers know the other desk)

Buyer AP often parks net 60 invoices until a weekly payment run. If your invoice misses the run cutoff by one day, you quietly become net 67. Ask for the payment calendar during onboarding.

PO mismatches are the top reason net 60 invoices sit untouched. Validate PO, amount tolerance, and receipt of goods flags before day 10, not day 55.

Some buyers require invoices through a portal (Coupa, Ariba, and peers). Email PDF alone may never start the net 60 clock in their system. Confirm portal submission in writing.

If early-pay discounts exist, make the discount math obvious on the PDF header. AP clerks will not reconstruct 2/10 net 60 from a buried footnote.

For disputed invoices, freeze collections on the disputed lines only. Partial holds keep cash moving on clean lines while the fight continues.

Publish the internal rule that no AE may grant net 60 on a first order without a credit check packet attached to the opportunity. First-order net 60 is where write-offs concentrate.

Keep a one-page glossary in the finance shared drive that defines invoice, receipt, sales order, and credit memo with a sample PDF for each. New hires should open that page before their first customer email.

Put the net-60 policy PDF next to the MSA template in the deal desk folder so legal and sales stop negotiating from memory.

Train new AEs on the difference between contractual net 60 and courtesy delays; only the former belongs in the quote tool.

Archive every signed exception that grants longer than net 60 so renewals do not silently inherit one-off concessions.

FAQ

Does net 60 mean 60 business days?
Default reading is ordinary days on the calendar; treat bank holidays as still counting unless the MSA says the opposite. [Source: due-date math section]

Can the clock start on delivery instead?
Yes when acceptance or delivery language governs; mirror that rule in the ERP due-date field. [Source: due-date math section]

Is net 60 longer than net 30?
Yes; it doubles the seller's wait versus net 30, all else equal. [Source: plain meaning / this article cash-flow section]

Where do I put net 60 on documents?
Contract payment section and each invoice's terms line. [Source: this article; invoice vs receipt vs bill]