Net 30
Net 30 means the buyer must pay the full invoice amount within 30 days of the invoice date, with no early-payment discount built into the terms.
Net 30 is the default payment term across most B2B invoicing in the UK, US, EU, and Australia. The buyer receives the invoice, has 30 calendar days from the date on the invoice to pay, and is not expected to pay any earlier. "Net" signals that the full amount is due, with no discount or holdback applied.
Common variants run on the same pattern. Net 15 shortens the window to 15 days, Net 60 lengthens it to 60. Net 30 EOM means 30 days from the end of the month in which the invoice was issued, which can stretch the real wait by another two to four weeks. "Due on receipt" is the opposite end of the same scale: payment is expected immediately when the invoice lands.
Whether Net 30 is fast or slow depends on the buyer. A small B2B operation paying via bank transfer can settle within a day if it wants to. A corporate accounts-payable team will almost always wait the full 30, sometimes longer, because their internal process is built around that cadence.
Common questions about Net 30
Does Net 30 start from the invoice date or the delivery date?
What is the difference between Net 30 and 2/10 Net 30?
Is Net 30 a legal requirement?
Use JupiterInvoice for Net 30
Net 30 on a JupiterInvoice invoice is a field, a label, and an audit trail your buyer can act on without an email back-and-forth.
Net 30 payment terms, explained
Net 30 means the invoice is due 30 days from the issue date. Here's what it means in practice, when to use it, and what to do when clients p...
Invoicing built for freelancers
Branded invoices with PO numbers, international payment details, and version history. The invoicing tool freelancers graduate to.
Let your customers edit their own invoice
Recipients add PO numbers, fix billing entities, and update AP contacts directly on the invoice. Every change is versioned and revertable.
Related terms
Send an invoice that handles net 30 properly
Free. No signup. Tax labels, payment terms, and PO numbers are first-class fields, not workarounds.
Create an invoiceNo signup required. Build now, save later.