Invoice workflow
Turn invoice PDFs into reviewed, reusable data.
Preview the planned path for English printed vendor invoices: preflight a batch, focus on exceptions, approve an immutable result, then reuse the same export recipe next month.
Fixed schema, visible evidence
The production contract requires every non-derived value to carry a page and normalized bounding box. Missing or low-confidence critical fields must stay blocked until a person confirms them.
- Vendor name
- Invoice number
- Invoice date
- Due date
- Currency
- Subtotal
- Tax
- Total
- Purchase order number
1. Upload and preflight
Confirm one invoice per PDF, see hard limits, region, retention and estimated page credits before upload.
2. Review exceptions
Compare the source with raw, normalized and reviewed values. Corrections preserve evidence and audit history.
3. Export and reuse
Approve a versioned snapshot, download deterministic outputs, and save an immutable RecipeVersion.
Production acceptance requires self-hosted processing, an independently verified region, pinned image and execution-bundle hashes, and a working 24-hour deletion lifecycle. The current preview provides none of those cloud operations.