Start with these documented workflow families
The website includes invoice, purchase-order, bill-of-lading and COA-related examples. Their presence is not proof that every field in every supplier layout is supported.
Use this matrix as a preparation checklist and record the exact approved profile/version before operational use.
| Family | Candidate header fields | Repeating structure | Important limitation |
|---|---|---|---|
| Invoice | Supplier; invoice reference; date; currency | Line items and amounts | Not payment approval or bank-detail verification. |
| Purchase order | Order reference; revision; parties | Items and schedules | Not authority to amend the purchasing system. |
| Bill of lading | Shipment references; parties; ports | Cargo and container rows | Not customs or cargo-release acceptance. |
| COA | Certificate; product; batch; issue date | Parameters; results; units; limits | Not laboratory verification or quality release. |
Record the actual capability contract
- Exact approved profile and template revision.
- Required field definitions and missing-value behaviour.
- Accepted input type, file size and page limits.
- Permitted output formats and plan restrictions.
- Representative fixture and reviewed expected values.
- Review reasons and downstream acceptance criteria.
When a required field is not available
Treat a new field, new document family or schema redesign as an explicit onboarding or configuration request. Do not substitute a visually similar field or infer coverage from another product's site.
Language coverage, handwriting, source coordinates and non-PDF input support need their own verification. List unsupported cases clearly rather than hiding them behind a broad accuracy claim.
Evaluate your document workflow
Start with representative permitted files, the fields you need and a clear review decision.