Net 15 Payment Terms: What They Mean, How to Use Them, and Invoice Examples

Net 15 payment terms mean the full invoice amount is due 15 calendar days after the invoice date. Invoice dated June 1 with net 15 terms? Payment is expected by June 16.

Quick summary:

Net 15 is a standard invoice payment term used in B2B transactions to set a clear payment deadline. It sits between the immediacy of "due upon receipt" and the longer net 30 window that many enterprise buyers expect. Choosing the right payment term is a cash flow decision, not just an invoicing detail.

When to use each term:

• Net 15: Seller needs faster cash flow, buyer can realistically pay within 15 days. Good for small to mid-size deals and established relationships.
• Net 30: Buyer has a structured AP cycle or expects standard procurement terms. Common default for enterprise B2B.
• Due upon receipt: Deposits, milestone payments, or prepayment models where both parties agree to immediate payment.

What net 15 means on an invoice

Net 15 means the buyer has 15 calendar days from the invoice date to pay the full amount. The countdown starts on the date printed on the invoice unless the contract specifies a different trigger, such as delivery date or receipt date. When the agreement is silent on the starting point, the invoice date is the default assumption, though not a universal rule.

Confirm contract language when there is any ambiguity about when the clock starts. A mismatch between the invoice and the master service agreement can stall payment and create unnecessary back-and-forth with accounts payable. What should be a 15-day cycle can stretch to five or six weeks if AP flags a discrepancy and routes the invoice back for clarification.

What does "net" mean on an invoice?

"Net" in this context means the total amount owed. The number after it (15, 30, 60, 90) indicates how many days the buyer has to pay that total. Net payment terms define this payment window as a standard part of commercial invoicing.

Businesses that use net 15 terms typically want faster collections without requiring same-day payment. Net 15 works when the buyer relationship supports a quicker cycle and the invoice amount doesn't require multiple layers of internal approval.

Some invoices include early payment discounts alongside net terms, written as something like "2/10 net 15," meaning a 2% discount if paid within 10 days, with the full amount due by day 15. Early payment discounts show up more often on longer net terms like net 30 or net 60, where the extended timeline makes the discount worth chasing.

Payment due upon receipt meaning

Payment due upon receipt means the seller expects payment as soon as the buyer receives the invoice. QuickBooks defines it operationally as immediate payment or payment by the next business day. There is no built-in grace period.

Actual payment timing still depends on the buyer's internal process and the contract terms governing the relationship. A large enterprise buyer running AP batches on Tuesdays and Thursdays will not cut a check the afternoon an invoice lands in someone's inbox.

Due on receipt works best when both parties agree to the expectation before the invoice is sent. Without that alignment, the wording creates friction rather than speed.

Net 15 vs net 30 vs due upon receipt

Picking between these terms depends on how a seller's cash needs line up with their buyer's actual payment behavior. B2B payment terms exist on a spectrum that balances customer accommodation with the seller's need for predictable cash flow.

Net 15 payment terms

Net 15 gives buyers enough time to receive, review, and process an invoice through a basic approval workflow without stretching collections out to a full month. For sellers with tighter working capital needs, it is a practical middle ground.

Most AP departments at smaller companies can process an invoice in under two weeks if it arrives clean, coded correctly, and matches a PO. Once you add a second or third approval layer, 15 days gets tight.

Net 30 payment terms

Net 30 is widely considered the default B2B payment term, though prevalence varies by industry and company size. Many procurement departments and AP teams are built around a 30-day cycle, and net 30 slots into that rhythm.

Sellers issuing invoices on net 30 may not see payment for five to six weeks once invoice delivery time and buyer processing delays are factored in. That gap widens further if the invoice gets kicked back for a coding error or a missing PO reference.

Due upon receipt payment terms

Due upon receipt is the most aggressive payment term a seller can use. It suits deposits, milestone payments, or situations where the seller has already delivered value and wants immediate compensation. Freelancers, consultants, and small service providers use it frequently.

For larger B2B relationships, due on receipt can be unrealistic. A buyer with a structured AP workflow will likely treat it as aspirational rather than binding, especially if the contract specifies different terms. The invoice shows up overdue on day one in the seller's aging report, which muddies aging data without changing when the money actually arrives.

When should a business use net 15 terms?

Net 15 makes sense when the seller needs faster cash flow and the buyer can realistically pay within that window. Smaller projects, recurring invoices with established customers, and relationships where the seller has pricing leverage are all good candidates.

Businesses with thin margins or seasonal cash needs often benefit from shorter terms. If a customer has a track record of paying on time, shifting from net 30 to net 15 can meaningfully improve working capital without damaging the relationship.

Net 15 also works well as a default for new customer relationships. Getting a buyer to move from net 30 to net 15 after six months of invoicing is a harder conversation than setting the expectation in the first contract.

When should a business avoid net 15?

Enterprise procurement cycles rarely align with a 15-day payment window. If the buyer's AP team needs three weeks just to get an invoice through intake, coding, and approval, net 15 on the invoice will not change actual payment behavior. It will generate overdue notices that annoy the customer and clutter the aging report.

Sellers in competitive markets where buyers expect net 30 or longer may lose deals by insisting on net 15. Payment terms are part of the commercial offer. Buyers weigh them alongside price, scope, and service quality.

If a seller doesn't have the collections process to follow up on day 16 when a net 15 invoice goes unpaid, the shorter term offers no real benefit. Terms only work when someone enforces them.

Invoice payment terms examples: net 15 and due upon receipt

Clear payment terms on the invoice reduce confusion and speed up payment. The term should be visible, specific, and tied to a concrete date.

Net 15 invoice example

A clean net 15 invoice note looks like this:

Payment Terms: Net 15Invoice Date: July 1, 2025Payment Due: July 16, 2025

Payment is due within 15 days of the invoice date. Please remit payment by the due date listed above.

Tying the term to a specific due date removes ambiguity about when the 15-day window ends. Buyers should not have to calculate the date themselves. A surprising number of invoices state "net 15" without printing the actual due date, which is an easy fix that meaningfully reduces payment delays.

Due upon receipt invoice example

For invoices requesting immediate payment:

Payment Terms: Due Upon ReceiptInvoice Date: July 1, 2025

Payment is due immediately upon receipt of this invoice. Please remit payment at your earliest opportunity.

Including "at your earliest opportunity" softens the wording slightly while still communicating the expectation. Some finance teams prefer the more direct "Payment is due upon receipt of this invoice" with no qualifier.

Common mistakes with invoice payment terms

Ambiguous or missing terms. An invoice with no payment terms leaves the due date open to interpretation. Buyers will default to their own internal schedule, which may be 45 or 60 days. State the term explicitly on every invoice.

Mismatch between invoice and contract. If the signed agreement says net 30 but the invoice says net 15, the buyer's AP team will follow the contract. Every time. Inconsistencies create disputes and delay payment. Invoice terms should mirror the governing agreement exactly.

Unrealistic terms for the buyer's workflow. Printing "due upon receipt" on an invoice to an enterprise customer with a structured three-week AP cycle does not accelerate payment. It just makes the invoice appear overdue from day one, which undermines aging data for actual collections prioritization.

No follow-up process. A payment term without a corresponding reminder and escalation workflow is just a suggestion. Finance teams that set terms but don't track aging or send reminders will see the same late-payment patterns regardless of what the invoice says.

Ignoring disputed invoices. When a buyer disputes a line item, the payment clock effectively stops. Many AR teams keep the original due date in their aging report and treat the invoice as late, when the real issue is a pricing or scope disagreement that needs resolution before payment can move forward. Disputed invoices need a separate workflow, not just another reminder email.

How finance teams enforce payment terms in practice

Choosing the right term is only part of getting paid on time. The operational work is applying terms consistently across every invoice, sending reminders at the right intervals, and escalating when invoices age past due.

Most B2B finance teams manage some combination of invoice generation, approval routing, payment reminders, and collections follow-up. When these steps are manual and disconnected, terms get applied inconsistently, reminders go unsent, and overdue invoices sit untouched until someone pulls an aging report at month-end.

One pattern that shows up repeatedly: a company sets net 15 terms in the contract, but the invoice goes out three days late because of a manual handoff between the delivery team and billing. Then the reminder triggers based on the invoice date, not the send date, so the customer gets a past-due notice before they've had a full 15 days. These small process gaps erode customer trust and make payment terms feel adversarial rather than professional.

Workflow automation helps by connecting the contract-to-cash process end to end. When an invoice is created with net 15 terms, the system should automatically calculate the due date, schedule reminders before the due date, and flag the invoice for collections if payment has not arrived by day 16.

Where LedgerUp fits

Every breakdown described above, contracts that say net 15 while invoices print net 30, reminders that fire before the buyer has had a full payment window, overdue invoices that sit unnoticed until month-end, traces back to the same root cause. The steps between signing a contract and collecting payment are managed in disconnected systems, or in no system at all.

LedgerUp works as the workflow layer that connects contracts, billing, approvals, reminders, collections, and payment reconciliation into a single enforced sequence. When a contract specifies net 15 terms, LedgerUp pulls those terms into the invoice automatically, calculates the correct due date, triggers pre-due-date reminders on the right schedule, and routes overdue invoices into a collections queue on day 16. No manual handoffs between delivery teams and billing. No spreadsheet tracking that drifts out of sync by mid-quarter.

For finance teams managing net 15 and net 30 terms across dozens or hundreds of customers, each with different agreements, approval chains, and exception paths, the difference between a 15-day collection cycle and a 45-day one usually comes down to whether the workflow between those systems is automated or stitched together manually. LedgerUp's contract-to-cash automation workflow maps out how each step connects, from contract terms through invoice generation, approval routing, reminder cadence, and reconciliation.

Teams that recognize the patterns in this article (late invoice sends, mismatched terms, stale aging reports, reminder gaps) are typically one process layer away from fixing them.

FAQ

Is net 15 business days or calendar days?

Net 15 refers to 15 calendar days, not business days. 15 business days equals roughly three weeks, closer to net 21 in calendar terms. If the agreement specifies business days, that interpretation applies. Check the contract language or clarify with the customer before invoicing.

What does net 15 terms mean?

Net 15 terms mean the full invoice amount is due within 15 calendar days of the invoice date. It is a standard B2B payment term that sets a short but defined payment window.

Is payment due upon receipt the same as net 15?

No. Due upon receipt requests immediate payment when the buyer receives the invoice. Net 15 gives the buyer a 15-day window. The two terms set very different expectations for timing and buyer flexibility.

Can I put due upon receipt on an invoice?

Yes, "due upon receipt" is a valid and commonly used invoice payment term. It should match what the customer expects and what the contract allows. If the signed agreement specifies net 30, printing "due upon receipt" on the invoice will not override those terms.

Do weekends and holidays affect the net 15 due date?

The 15-day count includes weekends and holidays because net 15 refers to calendar days. If the calculated due date falls on a weekend or bank holiday, payment is generally expected on the next business day. Stating the exact due date on the invoice avoids confusion about whether a Saturday or holiday shifts the deadline.

Can I charge a late fee on overdue net 15 invoices?

You can charge late fees only if the right to do so is established in the contract or invoice terms that the buyer agreed to before the work was performed. Simply printing a late fee policy on the invoice after the fact may not be enforceable. The most effective approach is to include late payment terms (such as a percentage per month on overdue balances) in the master service agreement or statement of work, and reference those terms on every invoice.

Book a LedgerUp Demo