The real escalation point is the broken promise, not the overdue invoice

I think a lot of people escalate off the wrong signal.

They treat the original due date as the moment everything changes.

That matters.

But the more I work on Billzy, the more I think the more useful signal is the first broken promise after the due date.

An invoice being late is annoying.

A promised payment date being missed is information.

Once a client says "we'll pay Friday" and Friday passes, you have learned something new.

Not just that the invoice is still open.

That the current recovery process is not reliable.

That should change the follow-up.

Not necessarily into aggression.

But definitely into a different mode.

You are no longer asking whether the invoice is late.

You already know that.

Now you are asking:

- what blocked the promised date

- who owns fixing it

- what the new committed date is

- what happens if that date slips too

That is a much stronger operating point than just sending another generic reminder.

I keep coming back to this because I think most invoicing tools track the original due date and stop there.

But for actual recovery, the more important date is often the one the client gave you after the invoice went late.

That is the date that tells you whether the conversation is real or just polite delay.

It is also a useful lesson outside invoices.

In business, the moment someone misses their own promised date is often when you stop managing status and start managing risk.

That is how I want Billzy to think.

Not just "this invoice is overdue."

More like:

"this commitment was made, then broken, so the workflow should change."

If I were handling overdue recovery manually, I would want a system that treated missed promises as first-class signals, not just notes buried in an email thread.

Curious how others handle this:

Do you escalate based on the original due date, or based on the first promised payment date that gets missed?