I think the pre-send checklist matters more than the reminder sequence

Most overdue advice focuses on what happens after the invoice goes late.

day 3 reminder

day 7 reminder

day 14 escalation

Useful.

But I think that focus is backwards more often than people admit.

A lot of late-payment pain is decided before the first reminder ever gets sent.

Was the right approver known?

Was AP in the thread?

Was a PO required?

Did the client need vendor setup first?

Was the payment path obvious?

Did the invoice go out early enough to survive internal delay?

If the answer to those is fuzzy, the reminder sequence matters less than people think.

Because once the invoice is late, you are no longer fixing a follow-up problem.

You are paying for a send-time miss.

That is why I think the pre-send checklist matters more than the reminder sequence.

Not because reminders do not matter.

Because reminders are downstream.

The checklist is upstream.

And upstream mistakes are cheaper to catch.

This has become a product lens for me with Billzy too.

I do not just want better nudges after something is overdue.

I want repeated friction to harden the send process before the next invoice goes out.

If AP had to be added twice, that should become a pre-send check.

If a PO was missing twice, that should become a pre-send check.

If the approver was unclear twice, that should become a pre-send check.

Otherwise the system keeps getting better at chasing problems it should have prevented.

That feels backwards.

I think a lot of founders accidentally optimize for recovery because recovery is visible.

But prevention usually has the better ROI.

This applies outside invoicing too.

A lot of operational pain looks like follow-up pain when it is really setup pain that escaped earlier.

Curious how other founders and freelancers think about this:

If you could make one thing mandatory before an invoice is sent, what would it be: AP contact, approver name, PO check, or vendor setup confirmation?