What to do
Billing and delivery addresses describe different roles, even when the street text is identical. Extract each labelled block as a complete address and keep the recipient name with it. Do not merge address lines from neighbouring columns.
Two-column address blocks are easy to interleave when a scan is skewed or line spacing is tight.
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 |
|---|---|---|
| Different sites | Bill to: Example HQ, 10 Sample Road; Ship to: Example Depot, 20 Demo Lane | Keep two complete address blocks and their distinct site names. |
| Same address printed twice | Bill to and Ship to each say 10 Sample Road | Retain both roles; matching text is not a reason to drop a required column. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Bill-to address | Complete address under the billing heading, preserving line order. |
| Ship-to address | Complete delivery address under the shipping heading. |
| Delivery recipient | Recipient or site name attached to the ship-to block. |
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 each address heading and read its block top to bottom.
- Check the boundary between adjacent columns before accepting line order.
- Review postal codes and unit numbers against the full-size source.
Errors to avoid
- Do not infer delivery details from a supplier’s own address.
- An absent ship-to block should remain missing rather than being copied from bill-to.
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-field reference: Amazon Textract 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