What to do
The supplier issues the invoice; the bill-to party is the customer receiving it. Capture their roles, not just two company names. A logo, remittance agent, branch address, and customer heading can all appear on the same page.
Check role labels and the document’s issuer details when the prominent logo is a marketplace or payment service.
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 |
|---|---|---|
| Ordinary layout | From Example Parts; Bill to Example Workshop | Supplier is Example Parts; customer is Example Workshop. |
| Payment intermediary | Issued by Example Studio; remit through Example Payments | Preserve the issuer and intermediary in different fields. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Supplier | Business identified as issuing the invoice, not its customer. |
| Bill-to customer | Customer name under the bill-to or billed-to heading. |
| Remittance party | Separate payee or remittance name if explicitly printed. |
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
- Identify the heading that describes the issuer rather than relying on logo size.
- Read the bill-to block and preserve the customer name independently.
- Compare supplier output with the known source document during review.
Errors to avoid
- Do not replace the supplier with a familiar customer name.
- A separate remittance address does not automatically change the issuer.
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