Blog

Due on Receipt vs Net 30: Which Payment Term Gets You Paid Faster?

Due on receipt sounds faster than Net 30, but it often isn't. Here's what each term really means, how clients treat them, and how to choose for each client.

Published 2026-11-11

Start 30-day trial

Ask ten freelancers which payment term gets them paid fastest, and most will say "due on receipt". It sounds urgent. It leaves no room. In practice, it's often slower than a clear Net 14 or Net 30, because it doesn't give the client a date to put in their system, or you a date to remind them about.

Here's what each term means, how clients really treat them, and how to choose.

What "due on receipt" means

Due on receipt means payment is expected as soon as the client receives the invoice. There's no grace period.

The problem is that "receipt" isn't a date. The client's accounts team may log your invoice on Monday, approve it on Thursday, and pay it in the next weekly run. From their side, that's "on receipt". From yours, it's a week late, and you have no specific day to point to.

Due on receipt works best when:

  • the client is a small business or an individual who pays from their own inbox;
  • the amount is small and the work is already delivered, such as a one-off design fix;
  • you're invoicing at the point of sale, such as a workshop or a session paid on the day.

What "Net 30" means

Net 30 means the full amount is due within 30 calendar days, usually from the invoice date. It's the standard in a lot of B2B work, and larger clients' systems are built around it. Full details are in what does Net 30 mean.

Net 30 works best when:

  • the client is a larger company with approval steps and scheduled payment runs;
  • their procurement policy requires it;
  • you've priced the wait into the project.

How clients actually behave

From years of chasing invoices, the pattern is consistent:

  • Clear dates get scheduled. An invoice that says "Due 14 March" goes into the AP system with that date. People in finance work from dates.
  • Vague terms get deprioritised. "Due on receipt" and "ASAP" have no date to schedule against, so the invoice waits for the next routine run, or for someone to notice it.
  • Large companies override your terms. If their policy is Net 45, a "due on receipt" invoice will be paid on day 45 anyway. Better to agree terms in the contract than to discover this later.

The fastest term is the shortest one the client's process can actually meet, written as a date.

A simple way to choose

Use the client's size and process, not your preference:

  • Individuals and micro-businesses: due on receipt or Net 7, with a pay link in the email.
  • Small businesses with a bookkeeper: Net 14.
  • Mid-size companies with an AP team: Net 30.
  • Enterprises and public bodies: whatever their policy says, agreed in writing before you start, plus a PO number on every invoice.

Then make it concrete. Instead of "due on receipt", write "Due 7 March 2026". Instead of "Net 30", write "Net 30, due 2 April 2026".

Legal defaults, briefly

If you don't agree terms at all, the law may fill the gap:

  • In the EU, the Late Payment Directive sets a default of 30 days after the client receives the invoice for B2B payments.
  • In the UK, statutory interest can start 30 days after the later of delivery or receipt of the invoice, if no date was agreed.
  • In the US, there's no general federal default for private invoices, but several state and city freelancer laws default to 30 days after the work is completed. See US freelancer payment laws.

"Due on receipt" doesn't override these rules. It's your request. The statutory default is what you can enforce if no other date was agreed.

What to write on the invoice

Due on receipt (small client):

Payment due on receipt (by 7 March 2026). Pay by card here: [link], or by bank transfer to the details below.

Net 14:

Terms: Net 14. Due date: 17 March 2026.

Net 30 (larger client):

Terms: Net 30. Due date: 2 April 2026. PO number: 4500123456. Please quote INV-1042 as the payment reference.

Make whichever term you pick stick

The term on the invoice is only half the job. The other half is what you do around the due date:

  1. Send the invoice the day the work is done. Every day you wait is a day added to the payment cycle. See the same-day invoicing habit.
  2. Confirm it arrived. Especially for new clients. A quick "Just confirming you received invoice INV-1042" catches wrong addresses early.
  3. Send a pre-due nudge three to five days before the date. See payment reminder before the due date.
  4. Follow up the day after it's due, then at a steady rhythm. See the reminder ladder.

FAQ

Is due on receipt legally enforceable?

It's a valid contractual term if the client agreed to it. If they didn't, statutory defaults may apply instead, such as 30 days in the EU and UK.

How many days is "due on receipt"?

Technically zero. In practice, many clients pay within a week. If you need a specific date, write it.

Is Net 30 better than due on receipt?

For larger clients, often yes, because it matches their payment process and gives everyone a date. For individuals and small businesses, a short term with a date usually gets paid faster.

Can I change my payment terms for an existing client?

Yes, but agree it in writing first and apply it to new work, not invoices already sent.

Let the dates do the chasing

DueChat puts a clear due date and a pay link on every invoice, and sends polite reminders in your name before and after it's due, stopping when the client pays. €19/month or €190/year after a 30-day trial. See pricing.

Get paid faster with polite chase that runs itself.

30-day Pro trial, card required at checkout. Cancel before day 30 to pay nothing, then €19/month or €190/year.

  • Scheduled 7/14/30-day reminders in your name until you are paid.
  • Stripe pay links on your account; you keep control of funds.
  • Confirm-before-send for sensitive steps, with a clear audit trail.
Start 30-day trial