Binds records to documents.
Checks client and invoice identifiers, recipient details and the approved document hash before preparing a job.
NeverIgnored / Dispatch
The right file.
The right person.
A document workflow should know when to proceed — and when to stop. Dispatch is a reference implementation for checking invoice batches and preparing approved drafts.
Synthetic records. This browser simulation does not read files, send emails or run the reference implementation.
01 / CHECK02 / APPROVE03 / PREPARE
| Approve | Document / recipient | Check | Draft state |
|---|
Review the records, then approve the eligible items.
Local simulation result
What the reference implementation does
Checks with a purpose.
Requires a deliberate approval.
An approved manifest is the source of truth. The software does not infer the correct recipient from the contents of an invoice.
Remembers completed work.
A local ledger tracks jobs across restarts. Uncertain outcomes stop for reconciliation instead of blindly retrying.
Inspectable technical proof
Small enough
to examine.
A Python reference implementation, tests and synthetic batch support this demonstration. The inspection bundle is available on request. The demonstration prepares local email files; it has no connected mail provider.
Request the technical proof ↗- Match the document and recipient.
- Require an explicit approval.
- Stop uncertain or repeated jobs.
Before production
A sound starting point.
A defined next step.
A live deployment needs an authorised mail adapter, access controls, scheduling, monitoring, backups and an agreed retention policy. Provider acceptance is not proof of inbox delivery.
Document header and hash checks are not malware scanning or a guarantee that the invoice contents are correct. A person must review the input records.
Discuss a document workflow ↗