What to do
Treat a printed SKU or part number as an identifier. Preserve leading zeros, punctuation, and letter case in the raw value. Keep supplier and buyer item references separate when both are present, rather than selecting one based on familiarity.
Characters such as O, 0, I, and 1 require a clear source image when they appear in tightly printed item codes.
Two worked review cases
These cases are fictional teaching data, not measured extraction results. Use the source excerpts to practise deciding what belongs in the reviewed output.
| Case | Fictional source excerpt | Review decision |
|---|---|---|
| Leading zeros | SKU 0007-A; description Example fitting | Keep 0007-A as text. |
| Two code systems | Supplier S-77; customer C-041 | Retain both references under their respective roles. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Supplier item code | Exact supplier SKU or part number printed for the row. |
| Customer item code | Separate buyer reference when explicitly labelled. |
| Item description | Description belonging to the same row as the codes. |
These are suggested staging-sheet columns. Printed facts can inform field descriptions in Parzable’s Schemas view; source references, review statuses, and decisions must be supplied by your own review process.
A practical review sequence
- Locate the code column and establish whether it belongs to supplier or customer.
- Compare similar-looking characters at full source size.
- Import identifiers as text and check them again after saving the destination file.
Errors to avoid
- Do not remove hyphens simply to make identifiers look numeric.
- Do not infer a missing code from the product description.
Use the case worksheet with a small sample
Download this page’s worked-case worksheet. It contains the two fictional cases above and a blank row for your own review exercise. Keep any real source documents in your agreed storage process.
For the broader product workflow, see the related guide. Parzable accepts PDF/image inputs and downloads CSV. Suggested structures here are review targets; nested item rows, automatic approvals, and destination integrations are not guaranteed.
Reference and scope
Further reading: Invoice structure: Microsoft Document Intelligence documentation. External documentation provides background for the topic; it does not establish Parzable’s implementation or performance. References checked 18 October 2026.
Examples and review decisions on this page are authored illustrations. Confirm unresolved business, payment, or accounting decisions through the responsible reviewer.
Put the workflow to work
Try your own invoice in Parzable
Create an account, define a schema, and test a small sample. Review extracted values before using them. See current plans and page allowances.
Try Parzable