Net 30 vs Net 60: Practical Invoice Due Date Guide

Net 30 generally gives the customer 30 days after an agreed starting event, while Net 60 generally gives 60 days. The starting event may be the invoice date, receipt of a valid invoice, acceptance, delivery, or another contract event.

• Net 30: shorter collection cycle for the supplier and less payment time for the customer.
• Net 60: longer payment window for the customer and a longer receivables period for the supplier.
• Neither label tells you by itself whether to count calendar days or business days.

If the agreement only says Net 30, many systems count 30 calendar days, but the contract or customer policy controls. If the parties mean business days, say so and identify the weekend and holiday calendar. An EOM term first anchors the calculation to the end of the invoice month; EOM + 15 then adds 15 days from that anchor.

Also state what happens when the calculated date falls on a weekend or holiday: move to the next business day, move to the previous business day, or keep the original date.

For an invoice dated June 8, 2026, a simple calendar-day calculation gives July 8 for Net 30 and August 7 for Net 60. If the written term instead uses business days, or starts after acceptance rather than the invoice date, the due dates will be later.

For EOM + 15, the same June invoice first anchors to June 30 and then adds 15 days, producing July 15 before any weekend or holiday adjustment.

A longer term can help a customer align payment with its approval and cash cycle, but it also extends the supplier's receivables period. A shorter term can improve collection timing but may not fit a large customer's procurement process.

This is a workflow comparison, not financial or legal advice. Check local law, customer onboarding rules, purchase orders, and the signed contract before changing payment terms.

Suppose a supplier invoices 12,000 on June 8 and pays materials and payroll before the customer settles. Under the simple examples above, Net 30 targets July 8 while Net 60 targets August 7. The second term leaves the same receivable outstanding for roughly another month. That does not prove Net 60 is unacceptable, but it changes how much working capital the supplier must carry and how long it waits before a late-payment workflow can begin.

The supplier can respond operationally by requesting a deposit, milestone billing, a shorter term, or an approved credit limit. Any financing cost, discount, or legal remedy needs separate professional review. The due-date calculator only makes the timing assumption visible; it does not recommend a commercial decision.

A larger customer may require purchase-order matching, receipt validation, manager approval, and a scheduled payment run. If that process regularly takes more than 30 days, agreeing to Net 30 while operating on a longer internal cycle creates avoidable disputes. Net 60 may fit the workflow better, but the parties should still name the starting event and require timely rejection of invalid invoices.

A clear process can be more valuable than a shorter label. For example, the contract can state that the clock starts when a valid invoice reaches a named address, define what makes an invoice valid, and require the customer to report defects within a fixed period. The displayed due date should then be generated from that documented event.

GOV.UK states that businesses can agree their own payment date and that, when no payment date has been agreed, payment generally becomes late 30 days after the customer receives the invoice or the goods or service, whichever is later. Its commercial late-payment guidance also describes usual 30-day treatment for public authorities and 60 days for business transactions, with longer business terms possible when fair to both parties.

Those statements are a UK reference and do not define terms for every country or contract. Jurisdiction, transaction type, consumer status, public-sector rules, and mandatory law can change the result. Use the linked official pages for their current wording and obtain advice for binding rights or remedies.

Before issuing the invoice, test the rule in both parties' systems. Confirm whether each system adds days from the invoice date or starts the next day, whether it treats EOM as the current or following month end, and whether it moves a weekend result. Store the original unadjusted date and the adjusted payable date as separate fields when possible. That makes a one-day discrepancy easier to diagnose.

After payment, compare the actual receipt date with the stated term, but do not silently rewrite historical due dates when holiday data changes. Preserve the policy version and assumptions used at issuance. A repeatable audit trail is more useful than a spreadsheet cell whose formula and holiday range are no longer known.

Replace an ambiguous label with a complete rule that both accounting systems can reproduce.

• Name the starting event: invoice date, receipt, acceptance, delivery, or month end.
• Say calendar days or business days.
• Identify the governing country, weekend, and holiday calendar when business days apply.
• State the weekend and holiday adjustment rule.
• Print the resulting due date on the invoice and confirm it against the contract.

This guide compares operational timing assumptions. It does not determine the governing starting event, counting basis, EOM interpretation, weekend adjustment, late-payment right, interest, tax treatment, or acceptable commercial term. Those decisions depend on the signed agreement, applicable law, and each party's systems.

The dated examples use fixed calendar arithmetic and the UK official references only for their stated UK context. They are not universal definitions of Net 30 or Net 60 and do not establish a due date in another jurisdiction.