Operating design
Define the controls before connecting software.
Problem
Staff retype vendor, date, total, tax and currency.
Approved input
Approved receipt image
Bounded AI role
Extract five fields beside the source
Human checkpoint
Bookkeeper verifies every amount, category and duplicate
Failure path
Reject unreadable documents; never trigger payment
Data classification
Financial document; potentially sensitive
Measurement
Field accuracy; review minutes
Safe first test
Use synthetic receipts with blur, tax and currency variations
Implementation sequence
Move from a synthetic test to a reversible decision.
- Document the current manual path and baseline.
- Prepare the synthetic cases named above, including failures.
- Run the AI step without production writes or customer communication.
- Have the named reviewer compare every result with its source.
- Measure corrections, delay, exceptions, and reviewer effort.
- Keep, revise, or stop the test; retain the manual rollback path.
Questions
Before using this workflow
Should the workflow create a payment?
No. Extraction and payment approval are separate processes. The workflow must never trigger or release payment.
What data should be tested first?
Use synthetic receipts that include blur, tax, multiple currencies, duplicates, and unreadable fields.
What should the reviewer verify?
A bookkeeper should compare every proposed vendor, date, subtotal, tax, total, and currency value with the source.