Use case · Cross-cutting/DOC
Paper in, records out.
Read without a template, validated against your records, and a person on anything the agent is not sure of.
Any inbound document·Validated against records·Exceptions reach a person
Paper in, records out
Draft invoice
Low confidence, a person looks
ILLUSTRATIVE · NOT REAL FIGURES
The inbound queue/01
A mailbox is not a workflow.
Try it/02
Set the confidence floor.
Draft created · 5
Invoice 99% Delivery note 97% Order 93% Remittance 90% Certificate 86%
A person sees it · 5
Invoice 95%Σ Invoice 81% Delivery note 74% Form 66% Invoice 52%
A document that fails the arithmetic or tax check goes to a person whatever its confidence (the Σ one).
ILLUSTRATIVE · NOT REAL FIGURES
The limits/03
What the agent may and may not do.
May read
Inbound documents, and the master and transaction records needed to validate them
May do
Create draft documents, resolve parties and items, and flag for review
May not do
Submit a document, release a payment, or overwrite a master record
Thresholds
A confidence floor per document type, below which a person always sees it
Validation
Arithmetic and tax checks must pass before a draft is offered at all
Provenance
The source file attached to every record it produced, permanently
Correction
A person's correction is recorded against the document, not silently applied
Measure it/04
How to tell it worked.
Runs on/05
The modules it spans.
Next to this/06
The whole platformNext step