Net 30 Vs Net 60
Net 30 and Net 60 are payment terms that describe when an invoice becomes due after the invoice date. “Net 30” typically means the buyer pays within 30 calendar days of the invoice date, while “Net 60” means payment is due within 60 calendar days. These terms affect cash flow for the seller and working-capital planning for the buyer, even when the product or service is delivered earlier.
In practice, the invoice date matters more than the delivery date unless the contract states otherwise. For example, a shipment delivered on May 1 with an invoice dated May 3 can still be due 30 or 60 days from May 3. Many disputes start when one side counts from delivery and the other counts from invoice issuance, which is why the wording on the invoice and the purchase agreement should match.
Payment terms also interact with internal processes like receiving, approvals, and invoice matching. A buyer may receive goods quickly but still delay payment if the invoice fails a three-way match against the purchase order and receiving record. That delay can stretch the effective payment timeline beyond Net 30 or Net 60, and it rarely shows up in the contract language.
Common Misreads And Risks
People often treat Net 30 and Net 60 as guarantees that money moves on a predictable schedule. The terms describe a due date, not the date the seller will actually receive funds. Banking cutoffs, payment method timing, and approval workflows can shift the real payment date by several days.
Another frequent mistake is assuming “30 days” means “one month.” Calendar days can cross month boundaries, so a Net 30 invoice dated January 31 is due March 2 in a non-leap year. If your accounting system expects month-based logic, the due date can land on an unexpected day and trigger late-fee clauses or internal alerts.
Supporting dependencies matter. For buyers, the invoice often depends on purchase order creation, receiving confirmation, and accounts payable review. For sellers, the invoice depends on correct billing details, tax treatment, and proof of delivery or service completion. When either side’s records are incomplete, the invoice can sit in a “disputed” or “on hold” queue, which changes the practical meaning of Net 30 or Net 60.
Some contracts add modifiers like “Net 30 from receipt” or “Net 60 after acceptance.” Those phrases shift the clock to receipt or acceptance, which can be later than invoice date. If the contract is silent, many parties default to invoice date, but that default varies by jurisdiction and contract interpretation, so the safest approach is to read the exact wording.
How To Choose Terms
Map The Due Date Clearly
Write down the exact due-date rule from the contract and invoice: “from invoice date,” “from receipt,” or “from acceptance.” Then test it with a real example using your calendar. If you use QuickBooks Online (I last checked its invoice due-date behavior in late 2024), confirm whether it treats due dates as calendar days and whether it stores the invoice date separately from the due date. Small mismatches between systems create avoidable disputes.
For buyers, align receiving and invoice dates so the due date reflects the intended timeline. For sellers, include the invoice date and due date on the invoice itself and keep a copy of the purchase order and delivery confirmation. When the due date is explicit, fewer emails turn into “we counted from the wrong date” arguments.
Model Cash Flow Impact
Net 60 usually improves buyer cash flow but increases seller financing needs. A simple way to quantify the difference is to estimate how much revenue you expect to be outstanding at any time. If a seller issues $100,000 per month in invoices, moving from Net 30 to Net 60 can roughly double the average accounts receivable balance, assuming similar sales volume and no major collection delays. The exact number depends on payment patterns, seasonality, and dispute rates.
For buyers, longer terms can reduce short-term liquidity pressure, but it can also increase the risk of supply interruptions if the seller’s cash position deteriorates. Sellers may respond by tightening credit, requiring deposits, or offering discounts for faster payment. Those responses are not guaranteed, yet they show up often enough that planning should include them.
Use Negotiation Levers
Many agreements include a discount for early payment, such as “2/10 Net 30,” which means a 2% discount if paid within 10 days, otherwise due in 30. Even when a discount is not offered, you can negotiate partial payments tied to milestones: 50% on order, 50% on delivery, with a Net 30 or Net 60 balance for the remainder. Milestone billing reduces the seller’s financing burden and can make longer terms more acceptable.
Another lever is dispute handling. If the contract defines a clear dispute window (for example, “disputes must be raised within 10 days of invoice receipt”), it prevents indefinite holds. Buyers should also define what constitutes a valid dispute, since vague claims can delay payment and damage supplier relationships.
Track Payments With Receipts
Both sides should track the same event that starts the clock. Buyers can use an accounts payable workflow that records invoice receipt date, approval date, and payment date. Sellers can track invoice status and keep proof of delivery or service acceptance. When payments are made by ACH or wire, the settlement date can differ from the “sent” date, so record the bank confirmation.
In a practical workflow, you can set reminders for 5 days before the due date and again on the due date. If you use an ERP with versioned approval rules (I’ve seen teams adjust approval thresholds in SAP around 2023 releases), document those changes so the due-date logic stays consistent across departments.
Educational Case Examples
Scenario A (Buyer counts from receipt): A buyer’s contract says “Net 30 from receipt,” and the receiving team logs receipt on May 10. The seller issues an invoice dated May 3. The buyer pays on June 9, counting 30 days from May 10. The seller initially objects because they counted from invoice date and expected payment on June 2. The dispute resolves once both sides confirm the contract language and update their invoice templates to show “due date: June 9.”
Scenario B (Seller expects Net 60 from invoice date): A seller provides services and issues an invoice dated April 1 with “Net 60.” The buyer’s internal approval takes 20 extra days because the invoice lacks a reference number from the purchase order. The buyer pays on June 30, which is within 60 days of invoice date but later than the buyer’s internal target. The seller learns to require the purchase order reference on every invoice to reduce holds, and the buyer learns to route invoices to approval immediately after receipt.
Net 30 Vs Net 60 Checklist
| Decision Factor | Net 30 | Net 60 | What To Verify |
|---|---|---|---|
| Due Date Clock | Often from invoice date | Often from invoice date | Contract wording: invoice vs receipt vs acceptance |
| Seller Cash Need | Lower average receivables | Higher average receivables | Average monthly invoices and typical payment timing |
| Buyer Liquidity | Less time to pay | More time to pay | Approval workflow and invoice matching delays |
| Dispute Risk | Shorter window to resolve | Longer exposure if disputes linger | Dispute definition and required notice timing |
| Operational Fit | Works with faster AP cycles | Works with slower AP cycles | Whether invoices get held for missing PO references |
Step-by-step checklist for choosing terms:
- Confirm the clock start: invoice date, receipt date, or acceptance date.
- Calculate due dates for two sample invoices that cross month boundaries.
- Estimate average outstanding receivables for the seller and average payable float for the buyer.
- Check dispute and hold procedures, including how long invoices can remain “pending.”
- Align invoice fields with your matching system (purchase order number, line items, tax fields).
- Decide whether early-payment discounts or milestone billing are needed to balance risk.
Common Mistakes To Avoid
One mistake is treating “Net 60” as a promise that payment will arrive on day 60. In reality, payment processing can add days, and some buyers schedule payments in weekly batches. If a seller expects funds on a specific day, they may misread a batch schedule as a breach.
Another mistake is ignoring invoice completeness. Missing purchase order numbers, inconsistent line-item descriptions, or mismatched tax details can trigger holds. A buyer’s accounts payable team may not have authority to pay an invoice that fails internal controls, and the seller may not learn why until after the due date.
Some agreements also include late-fee or interest clauses. If you accept Net 60 without reviewing those clauses, you can end up paying penalties due to administrative delays rather than actual nonpayment. Read the contract section that governs late charges and the method for disputing charges.
Finally, people sometimes negotiate Net 60 verbally and then receive invoices with Net 30 printed on them. The written invoice terms can conflict with the purchase agreement. The safer approach is to confirm the payment terms in the purchase order and in the invoice template before work starts.
FAQ
Does Net 30 Count Calendar Days?
Most contracts treat Net 30 and Net 60 as calendar days, but the exact rule depends on the agreement. Check whether the contract defines “days” and whether it references invoice date, receipt date, or acceptance date.
What Happens If The Invoice Is Disputed?
Disputes typically pause or redirect payment until the issue is resolved, but the contract must define the process. Look for a dispute notice deadline and whether the buyer must pay undisputed amounts.
Can A Buyer Pay Earlier Than Net 30?
Yes. Early payment is common, and some contracts add discounts for early payment. If there is no discount clause, early payment still reduces the seller’s receivables and can improve future negotiation leverage.
Is Net 60 Better For Buyers?
Net 60 usually improves buyer cash flow by extending the due date, but it increases the seller’s financing burden. The “better” choice depends on your ability to manage approvals and on whether the seller can sustain longer receivable cycles.
Do Net Terms Apply To Services?
Net terms apply to invoices for goods or services when the contract ties payment to an invoice due date. Service contracts often add acceptance milestones, which can shift the clock beyond invoice date.
Author's Insight
Net 30 and Net 60 are simple labels, but the practical outcome depends on contract wording and internal payment workflows. The most common failure mode is a mismatch about what event starts the clock, followed by invoice holds caused by missing purchase order references or incomplete line-item data.
For decision support, treat payment terms as a system: due-date rules, dispute procedures, and the matching steps between procurement, receiving, and accounts payable. When those pieces align, Net 30 and Net 60 behave predictably enough for planning.
If the contract is silent or inconsistent across documents, you can reduce risk by writing the due date on the invoice and confirming the clock start in the purchase order. That approach prevents the “we counted from different dates” pattern that shows up in many payment disputes.
Key Takeaways
- Net 30 and Net 60 describe invoice due dates, not guaranteed payment arrival dates.
- Confirm whether the clock starts from invoice date, receipt date, or acceptance date.
- Net 60 typically increases seller accounts receivable and buyer payable float, affecting cash flow on both sides.
- Invoice completeness and dispute procedures often matter more than the label on the invoice.
- Use a due-date checklist with sample dates that cross month boundaries to prevent avoidable disputes.
