The Best Payment Reminder Schedule for Due on Receipt Invoices (Day-by-Day, Because Net 30 Rules Are Too Slow)

Most reminder advice is written for net 30. Nudge before the due date, follow up a week after, get firm at two weeks, escalate at 30 days. That's a fine playbook when the client has a month to pay.

It falls apart the moment your invoice says "due on receipt." A week of silence on a net 30 invoice is a quarter of the payment window. A week of silence on a due-on-receipt invoice is the whole window, several times over. So here's the best payment reminder schedule for due on receipt invoices, and the net 7 version too, with actual days attached.

First, when is due on receipt actually late?

Legally, "due on receipt" means the money is owed the day the client gets the invoice. Practically, nobody pays the same day, and holding them to it makes you look unreasonable before you've even started chasing.

The realistic window is 2 to 3 business days. That covers a client who opens the invoice tomorrow, approves it the day after, and whose bank transfer takes a day to land. Most people who use due-on-receipt terms treat day 3 as the line where "not yet paid" turns into "late."

Two things make this work. Put the window in writing on the invoice itself ("Due on receipt. Please pay within 3 business days."), and count from the day you can prove they received it, not the day you hit send. A quick "did this land?" note on day 1 kills the "never got it" excuse and starts the clock.

The core rule: shrink the gaps to match the terms

On net 30, reminders are usually spaced about a week apart. That gap is roughly a quarter of the payment term. Apply the same ratio to a 3-day window and you get gaps of a day or two, not a week.

That feels aggressive if you're used to net 30, but it isn't. The client agreed to short terms. A reminder every couple of days is the pace those terms imply. What actually annoys clients is a reminder that arrives after they've already paid, or one that sounds angrier than the situation warrants.

The day-by-day schedule for due on receipt invoices

Day counts start from the day you send the invoice. Weekends don't count, so "day 3" on a Friday invoice is Wednesday.

Day 0: Send the invoice. State the window in the terms line, include the payment link or bank details in the body of the email, and name the amount in the subject line. Half of "late" due-on-receipt invoices are late because someone had to open a PDF to find out how to pay.

Day 1: Confirm receipt. One line, no ask for money. "Just checking this came through and there's nothing missing on my end." This is the cheapest reminder you'll ever send, and it's the one that matters most on short terms because it establishes the receipt date.

Day 3: First real reminder. The invoice is now late under the window you wrote on it. Friendly, short, includes the pay link again. Here's the one I use:

Subject: Invoice #1042 ($1,800) – due on receipt

Hi Sam,

Quick nudge on invoice #1042 for $1,800, sent Monday with due-on-receipt terms. I haven't seen it come through yet. The pay link is here: [link], or the bank details are on the invoice.

If it's already on its way, ignore this and thanks!

Dana

Day 5: Second reminder. Same facts, slightly firmer. Drop the "ignore this if paid" line and replace it with a question that requires an answer: "Can you let me know when this is scheduled to go out?" A question gets a reply where a statement gets silence.

Day 7: Firm reminder, and mention what happens next. One week on a due-on-receipt invoice is the equivalent of 60 days on net 30. Say plainly that the invoice is a week overdue and that late fees apply from day 10 (if your contract allows them) or that work on the next deliverable pauses until it's settled. Don't threaten anything you won't do.

Day 8 or 9: Pick up the phone. Email has now failed three times. A two-minute call almost always surfaces the real reason: the invoice is sitting in someone's approval queue, the client thought they'd paid, or there's a dispute nobody mentioned. If you get voicemail, follow it with a one-line email saying you called.

Day 10: Apply the late fee and send the final notice. Only if the fee was in your agreement. Run the numbers through a late fee calculator so the amount is right and defensible, then state it once, calmly. The final notice should also say what happens at day 14.

Day 14: Escalate. Stop work if there's ongoing work to stop. Send the final demand. At this point you're in standard collections territory and the due-on-receipt clock no longer matters. Treat it like any other seriously overdue invoice.

The net 7 version

Net 7 gives you a real due date, which lets you send a pre-due nudge. Everything else is the same schedule, shifted so the first real reminder lands the day after the due date.

| Day | What to send |

|---|---|

| 0 | Invoice, with pay link in the email body |

| 1 | Receipt confirmation |

| 5 | Pre-due nudge ("due Friday, here's the link") |

| 8 | First reminder (now late) |

| 10 | Second reminder with a direct question |

| 14 | Firm reminder, late fee or pause mentioned |

| 15 or 16 | Phone call |

| 17 | Late fee applied, final notice |

| 21 | Escalate |

The pre-due nudge on day 5 does a lot of work. On short terms, most late payments are forgotten payments, and a reminder two days before the due date catches most of them before they're late at all.

Adjusting for the client, not the calendar

The schedule above is the default. Two situations justify changing it.

Company clients with an AP department can't pay in 3 days no matter how many reminders you send. If you're invoicing a business with a formal approval process, due on receipt is the wrong term. Move them to net 7 or net 15 and chase that properly, rather than sending five reminders into a queue that was always going to take two weeks.

Clients who've paid fast every time earn a slower cadence. If someone has paid within 48 hours for the last six invoices, skip the day 3 reminder and go straight to a day 5 check-in. The point of the schedule is to be predictable, not rigid.

Writing the reminders once

The hardest part of this cadence isn't the timing. It's the tone drift. Day 3 should sound relaxed, day 7 should sound serious, and day 10 should sound like someone who has already decided what happens next. Writing each one from scratch while you're irritated is how you end up sending the day 10 email on day 3.

Draft the full sequence once, when nothing is overdue. The payment reminder email generator will give you a starting point for each stage, and the late payment email toolkit has the firmer ones already written. Then you're just filling in the invoice number.

The best payment reminder schedule for due on receipt invoices isn't complicated. Confirm receipt on day 1, remind on day 3, again on day 5, get firm on day 7, call by day 9, and escalate by day 14. The only real mistake is borrowing the net 30 timeline and wondering why a "quick" invoice took six weeks to collect.

If sending nine emails on a two-day rhythm sounds like a lot to track by hand, automated payment reminder software can run the whole sequence for you.