I think a lot of people only let invoices fail in the most expensive place possible:
after they are sent,
after the due date passes,
after follow-up starts,
after the cash is already late.
That feels normal because invoicing is usually treated like a send-first, diagnose-later process.
But the more I work on Billzy, the more I think that is backwards.
I think invoices should be allowed to fail before they are sent.
Not fail in a dramatic way.
Fail like a useful system check.
For example:
- approver unknown
- AP path unclear
- PO or vendor setup missing
- terms not aligned with the client's actual payment behavior
- no clear payment route beyond the main contact
If those things are weak, I think the invoice should be treated as not ready.
Because once you send it anyway, you are often just moving a hidden problem into a later, more expensive part of the workflow.
And then when the invoice goes late, it looks like a reminder problem.
But sometimes the reminder is not the real issue at all.
The invoice was fragile before it even left your side.
That is why I keep thinking invoicing needs something closer to a preflight check.
Not just:
"was the invoice created?"
More like:
"is the payment path strong enough that sending this is actually responsible?"
That feels much more useful to me than getting very good at chasing invoices that should have failed a basic readiness check.
This has become a product lens for me with Billzy too.
I do not just want overdue recovery logic.
I want the system to surface the weak spots early enough that some bad invoices never get sent in a fragile state at all.
Because the cheapest late-payment fix is often the one that happens before the invoice exists as a problem.
I think this applies outside invoicing too.
A lot of messy operations are allowed to proceed because nothing forces them to fail early.
And when systems stop weak work early, they usually save a lot of cleanup later.
Curious how other founders and freelancers think about this:
If you could block invoice sending on one missing condition, what would you choose first: approver name, AP contact, PO/vendor setup, or payment terms fit?