The Best Payment Reminder Schedule for Net 30 Invoices (Day-by-Day Cadence)

Net 30 has a built-in trap: because the client has a whole month to pay, it feels rude to say anything before day 30. So most freelancers stay silent for 30 days, then scramble to write an awkward "just checking in" email on day 35.

That silence is exactly why net 30 invoices go late. The best payment reminder schedule for net 30 invoices starts before the due date, touches the client on specific days, and gets slightly firmer at each step — so no single email has to do all the heavy lifting.

Here's the exact cadence, day by day.

The net 30 follow up timeline at a glance

| Day | Touch | Tone |

|-----|-------|------|

| Day 0 | Invoice sent + confirmation ask | Neutral, administrative |

| Day 23 | Pre-due reminder | Helpful heads-up |

| Day 31 | Due date passed | Friendly, assumes oversight |

| Day 37 | Second overdue reminder | Direct, asks for a date |

| Day 44 | Firm reminder | Businesslike, mentions consequences |

| Day 60 | Final notice | Formal, states next steps |

Six touches total, and only four of them happen after the due date. That's the whole system. Now let's talk about why each day is where it is.

Day 0: Send the invoice and get a confirmation

This one gets skipped constantly, and it's the touch that makes every later reminder easier.

When you send the invoice, ask one small question: "Can you confirm this landed and everything looks right?" You're doing two things — confirming the invoice didn't vanish into a spam folder or the wrong inbox, and surfacing any disputes now, while you still have 30 days of runway instead of finding out on day 35 that "accounting had a question."

If you don't hear back within a few days, nudge for the confirmation. That's not chasing payment; it's chasing receipt. Totally different social contract.

Day 23: The pre-due reminder (the one that does most of the work)

One week before the due date, send a short heads-up:

Hi Sam — quick note that invoice #204 ($3,200) is due next Friday, March 28. Payment details are on the invoice, but shout if you need anything resent. Thanks!

This is the highest-leverage email in the entire sequence. Companies paying on net 30 terms usually run payment batches — weekly or biweekly check runs, approval queues, that kind of thing. A reminder seven days out gives your invoice time to get into the last batch before the due date instead of the first one after it.

It also can't offend anyone. Nothing is late yet. You're just being organized.

Why day 23 and not day 27 or 28? Because you want a full business week of buffer. If your reminder lands on day 28 and their check run is Thursdays, you've already missed the window.

Day 31: The day-after nudge

Don't wait until the invoice "feels" late. The day after the due date (or the next business day), send this:

Hi Sam — invoice #204 was due yesterday and I haven't seen the payment come through yet. It may just be crossing in the mail — if it's already been sent, ignore me! Otherwise, could you let me know when it's scheduled?

The tone here assumes an oversight, because it usually is one. But sending it on day 31 instead of day 40 does something important: it teaches this client that your due dates are real. Clients pay the invoices that get chased promptly and sit on the ones that don't.

Day 37: Ask for a specific date

One week overdue. Drop the "ignore me if" softening and ask a direct question:

Hi Sam — following up on invoice #204, now a week past due. Can you tell me when payment is scheduled? If there's an issue holding it up on your end, I'd rather know now so we can sort it out.

The key move: ask for a date, not just payment. "It's in process" is not an answer — a date is. (If they give you a date, hold reminders until then, and resume the day after if it passes. If you want scripts for each of these stages, the late payment email toolkit has copy-paste versions from friendly to final.)

Day 44: Two weeks overdue — introduce consequences

This is where most people either go silent (bad) or go nuclear (also bad). The right move is calm and specific:

Hi Sam — invoice #204 is now two weeks past due and I haven't gotten a payment date from you. Per my payment terms, invoices unpaid 15 days past due accrue a late fee of 1.5% per month. I'd much rather receive payment than apply the fee — can you get this scheduled this week?

Two things make this work. First, you're citing a policy, not making a threat — the fee is a rule that exists, not a punishment you're inventing in the moment. Second, you're giving them a clean way out: pay this week, no fee. (If you're not sure what a reasonable fee looks like on your invoice amounts, run the numbers through a late fee calculator first.)

If you never set up late fee terms, skip the fee line but keep the firmness: "This is now significantly past due and I need a payment date this week."

Day 60: Final notice

A month past due on net 30 terms means the friendly phase is over. The day-60 email is short, formal, and names what happens next:

Sam — invoice #204 remains unpaid 30 days past its due date, despite multiple reminders. If payment isn't received by April 30, I'll need to pause current work and consider further collection steps. Please treat this as a final notice.

Only state consequences you'll actually follow through on. If you name a pause date and then keep working, every future deadline you set with this client is fiction.

Adjusting the cadence for repeat clients

For a brand-new client, run the full sequence as written — the early touches (day 0 confirmation, day 23 pre-due) matter most when you don't know their payment habits yet.

For a long-term client who reliably pays on day 32 every month, you can drop the day-31 nudge and let the pre-due reminder carry the load. And if a client consistently pays on day 45 no matter what you send, the problem isn't your reminder cadence — it's your terms. Compare what net 15 or net 21 would do to your cash flow with a net terms calculator before your next contract renewal.

Automating the whole sequence

Here's the honest problem with this schedule: it's six touches per invoice, each anchored to a different date, each with a different tone. With one invoice, that's manageable. With eight open invoices on different clocks, you're either living in calendar reminders or you're missing days — and a net 30 invoice chasing cadence only works if the days are consistent.

This is exactly the kind of thing worth setting up once and never thinking about again:

1. Write your five reminder templates (pre-due through final notice) one time.
2. Set the trigger days relative to the due date: −7, +1, +7, +14, +30.
3. Have the sequence stop automatically the moment an invoice is marked paid.
4. Keep a manual pause option for when a client gives you a payment date.

Whether you build this with calendar blocks and saved drafts or let software run it, the sequence itself doesn't change. The best payment reminder schedule for net 30 invoices isn't clever — it's just consistent: a heads-up before the due date, a prompt nudge after it, and steady escalation until the money lands.

Tools like automated payment reminder software can run this exact sequence for you, so every invoice gets chased on the right day without you tracking a single date.