OperationsNeverIgnored DispatchWorking demonstration
The right invoice. The right person. Once.
Sending invoices is where small mistakes get expensive: the wrong email address, an old version, the same bill twice. Before anything goes out, Dispatch asks three questions. If any answer is wrong, it stops and tells you why.
- Right person?The email address is the one you approved for that customer.
- Unchanged?The invoice is exactly the version you approved.
- Not sent before?It hasn’t already gone out.
Technical log (for the curious)
Example invoices for the fictional businesses from our design studies. This page doesn’t read files or send email; it shows how the checks behave.
Checks every invoice the same way
Customer, invoice number, email address and a fingerprint of the approved file are compared before anything is prepared.
A person always approves
Your approved list is the source of truth. Dispatch never guesses who an invoice is for from what’s written on it.
Remembers what’s been done
A record of every prepared email survives restarts. If something’s unclear, it stops and asks instead of trying again.
A Python reference implementation, tests and a synthetic batch sit behind this demonstration; the inspection bundle is available on request. A live deployment needs an authorised mail adapter, access controls, scheduling, monitoring, backups and an agreed retention policy. Hash checks aren't malware scanning, and a person still reviews the input records.