The problem
Supplier invoices were checked by hand against a written procurement policy. Automating it only works if every decision can be traced back to the policy and audited later.
What we built
A pipeline that reads each invoice, extracts the fields with the exact text they came from, finds the relevant policy clauses and decides. Clean invoices approve themselves with the clause attached. Anything else lands in a queue where a person approves it in seconds, with the reason already written.
The result
Docket is our reference build. Swapping in a new document type, such as contracts, claims or expense reports, takes a new schema, a new policy and a new connection to the system of record.
- of automatic decisions cite a policy clause
- 100%
- to swap in a new document type
- 1 day