Net 30 vs Due on Receipt: which to use

What Net 30 actually means

Net 30 means the invoice is due 30 days after the invoice date. If you issue an invoice on June 1, the payment is due on July 1. The word "net" just means the full amount with nothing taken off, so Net 30 is the full balance, no discount, due in 30 days.

Most US and UK businesses count from the invoice date, not the date the client opened the email or signed for the package. That's the standard, and it's what accounts payable teams assume unless your invoice says otherwise. If you want to count from a different starting point, say so in writing. Something like "Payment due 30 days from receipt of invoice" makes the rule explicit and removes the back-and-forth.

There's one common variation worth knowing: Net 30 EOM, which stands for end of month. That means the 30-day clock doesn't start the day you send the invoice, it starts on the last day of the month the invoice was issued. So an invoice sent on June 5 with Net 30 EOM is due 30 days after June 30, which is July 30. Bigger clients with monthly payment schedules runs sometimes ask for this. It buys them up to a full extra month, so don't agree to it lightly on a small invoice.

A few practical notes. Net 30 is calendar days, not business days, unless the contract says otherwise. Weekends and bank holidays count. If the due date lands on a Sunday, most clients will pay the Monday after and that's fine. And Net 30 doesn't require the client to wait 30 days, it just means they have up to 30 days. Plenty of well-run finance teams pay on day 7 or day 14 if the invoice is clean and the bank details are clear.

What Due on Receipt actually means

Due on Receipt means the invoice is payable as soon as the client gets it. In theory, that's the moment the email lands. In practice, almost nobody pays inside the hour. A reasonable client reads Due on Receipt as "pay this within a few business days", and that's usually how it shakes out.

The term has a real use case: it signals urgency without committing to a specific number. It tells the client this isn't something to file under "review at month end". It's meant to be paid now. For a one-off job, a small invoice from a new client, or a final bill on a job that already had a deposit, Due on Receipt is the polite way of saying don't sit on this.

The honesty piece matters. If you genuinely need the money within 24 hours, say that. Write "Payment due within 24 hours of receipt" or "Payment due on or before [specific date]". Due on Receipt without a date can read as vague, and vague terms get paid last. Clients pay invoices with hard dates faster than invoices with soft language, every time.

Where Due on Receipt can irritate clients is on bigger invoices to established companies. A $12,000 invoice sent Due on Receipt to a company with a establihed payment cycle is going to bounce internally. The finance person will look at the term, look at their schedule, and pay it on the next normal run anyway. So all you've done is mark yourself as a vendor who doesn't understand how their payment cycle works. For invoices over a few thousand dollars to companies that have an actual accounts payable team, Net 30 reads as professional and Due on Receipt reads as pushy.

When to use Net 30

Net 30 is the right call when you're billing a bigger client, an agency, a company with an accounts payable team, or anyone whose finance process isn't a single person paying bills from their phone. These clients run on cycles (weekly or bi-weekly), a payment approval queue, and a system that pays invoices based on the date written on them.

If you put Due on Receipt on an invoice to a company like that, the invoice still gets paid on their next cycle. You don't get paid any faster. Net 30 lines up with their process, gets your invoice into their queue without friction, and gets you paid on a predictable schedule.

There's also the relationship piece. Bigger clients value vendors who feel easy to work with. A vendor who insists on Due on Receipt on a $20,000 project, then chases the invoice on day 3, comes across as anxious. A vendor who sends Net 30, gets paid on day 28, and just moves on, comes across as someone with their act together. The second vendor gets called again. The first one doesn't.

Use Net 30 when:

• The client is a company with a finance team, not a single owner-operator.
• The invoice is over a couple of thousand dollars.
• You have a written agreement or recurring relationship in place.
• The client specifically asked for Net 30 (more common than you'd think).
• You're happy to wait up to 30 days for the money without it hurting cash flow.

If a 30-day wait would put you in a tight spot, that's a cash-flow problem to solve another way: a deposit, milestone billing, or a smaller buffer in your account. Trying to fight Net 30 on a client whose whole company runs on it usually ends with you switching the term to Net 30 anyway, just two emails later.

When to use Due on Receipt

Due on Receipt is the right call when the client is new, the job is small, and trust hasn't been earned yet. It's also the right call for one-off work that doesn't have a recurring relationship behind it, where waiting a month for the money is a real risk and not a process step.

Think about a first job for a brand-new client. You have no payment history, no contract you've already invoiced against, and no idea whether they pay on time. Due on Receipt protects you. It says the work is done, the bill is due, and we close this out before either of us moves on. If they don't pay, you learned something important before doing more work.

Same logic applies to small invoices. A $250 invoice for a quick design tweak doesn't need a 30-day window. Most individual customers and small business owners will pay it the day they see it, because it's small enough to clear without a process. Putting Net 30 on a $250 invoice tells them they have a month to think about it, and a month later they've forgotten.

Use Due on Receipt when:

• It's the first invoice with a new client and you have no payment history.
• The invoice is small enough that the client can pay it from their phone in a minute.
• The job is a one-off with no future work depending on it.
• The client is an individual or sole owner, not a finance department.
• You've already collected a deposit and this is the final small balance.

One more thing. Due on Receipt doesn't give you the right to chase the client on day 2. A polite reminder is fair on day 5 or day 7. Anything sooner reads as pushy, even when the term technically supports it. The goal is to get paid and keep the door open for next time.

Set your default terms once

Some small businesses bounce between Net 30 and Due on Receipt invoice by invoice, and the result is messy. Some clients see one term, some see another, and you spend time picking the wording every single time you send a bill. Pick a default. Stick to it.

For most freelancers, consultants, and small service businesses, Net 14 or Net 15 is a sensible default. It's long enough to feel professional to a finance team, short enough that you don't wait a full month for cash, and it's right in the middle of what clients expect. If most of your work is for bigger established companies, default to Net 30 instead, because that's what they'll pay on anyway.

If you mostly do small jobs for individuals and small business owners, Due on Receipt as a default makes sense. The invoice gets paid quickly and you don't have to remember which client got what term.

The key is consistency. A client should never get one invoice from you with Net 30 and the next with Due on Receipt unless there's a real reason. Pick a number, write it into your standard invoice template, and only deviate when the client asks. This saves you mental load and keeps your billing predictable.

A practical note: writing "Payment due in 14 days" or "Payment due in 30 days" on every invoice gets old quickly when you're sending them by hand. The fix is to set the wording once in a template, then let the tool fill it in. Examples of clean default wording you can copy:

• Net 14: "Payment due within 14 days of invoice date."
• Net 30: "Payment due within 30 days of invoice date."
• Due on Receipt: "Payment due on receipt of invoice."
• Net 30 with late fee: "Payment due within 30 days of invoice date. A 1.5% monthly late fee applies to overdue balances."

Other terms worth knowing

Net 30 and Due on Receipt are likely the two you'll use most, but there's a small family of related terms that show up often enough to be worth recognising.

Net 7: Payment due 7 days from the invoice date. Used when you want fast payment but want to look more professional than Due on Receipt. Common on small ongoing service work, like a weekly cleaner or a freelance editor billing on a tight cycle.

Net 14 (or Net 15): Payment due 14 or 15 days from the invoice date. The middle ground that a lot of freelancers and small agencies live on. Feels professional, gets the money in within two weeks, and works for most client types.

Net 45: Payment due 45 days from the invoice date. Less common, usually requested by larger companies with slow internal cycles. Push back if you can, because 45 days is a long time to wait, and most clients will accept Net 30 if you ask.

Net 60: Payment due 60 days from the invoice date. The standard for some big enterprise buyers, government contracts, and certain industries. If a client asks for Net 60, you either build it into the price, ask for a deposit up front, or both. Two full months of waiting impacts your cash flow.

2/10 Net 30: An early-payment discount term that reads "2% off if you pay within 10 days, otherwise the full amount is due in 30". On a $5,000 invoice, paying inside 10 days saves the client $100. Some clients chase the discount, some don't. The math works out to roughly a 36% annualised return for paying early, which is why bigger finance teams take it. Only offer it if the cash speed-up is worth the 2% to you.

EOM (end of month): Adds onto another term, like Net 30 EOM. The clock starts at the end of the month rather than the invoice date. Common on monthly billing cycles. Be careful with it, because invoicing on the 2nd of the month with Net 30 EOM means you wait almost two months for the money.

How to write the term on the invoice

The cleanest payment term is the one the client can't misread. That means a specific date, in plain English, in a spot on the invoice they can't miss. Most invoices have a Terms section near the bottom or a Payment Terms field near the top, and that's where this line belongs.

Beat jargon with a date. "Payment due by July 1, 2026" reads cleaner than "Net 30" to most people. The number Net 30 is fine to also include for the finance team, but a written date is the version that gets paid first. Some clients will read "Net 30" and have to do the math, and a slow finance person will park your invoice until they get to it.

Good wording you can copy into your Terms section, depending on which term you settled on:

• "Payment due by [date]. Net 30 from invoice date."
• "Payment due on receipt of invoice. Please settle within 5 business days."
• "Payment due within 14 days of invoice date. Late payments are subject to a 1.5% monthly fee."
• "50% deposit on signing, balance due within 15 days of project completion."

One thing to avoid: the bare phrase "ASAP". It tells the client nothing, sets no deadline, and gives you no ground to stand on if they pay 60 days later. If you need it fast, set a date.

If you charge late fees, write the rate into the Terms section on every invoice, not just the first one or the ones where the client is already late. Something like "A late fee of 1.5% per month applies to overdue balances" is enough. The fee isn't enforceable if it was never disclosed, and putting it on every invoice means you can apply it without a separate conversation.

Last note: include your preferred payment methods near the terms. Bank transfer details, a payment link, or a mailing address. The faster and easier it is for the client to pay, the more often you get paid on time. For more on the full invoice structure, see How to invoice clients, and for the late-fee specifics see Late fees: when and how to charge.