What to do
Transcribing printed bank details does not establish that they are authentic, current, or authorized for payment. If those fields are needed, preserve the exact text and source reference, restrict access appropriately, and follow the organization’s separate payment-verification process.
Do not add payment fields to a general extraction schema when the destination has no need for them.
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 |
|---|---|---|
| Changed details | A new invoice displays different payment details from prior records | Route for independent verification through the approved known contact channel. |
| Not needed | A spend-analysis sheet needs only supplier, date, and total | Leave bank details out of that dataset. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Printed payment reference | Exact remittance reference where required. |
| Bank detail source | Source location for the details, without claiming validation. |
| Verification status | Separate status owned by the authorized payment process. |
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
- Confirm a business need before collecting payment-related fields.
- Compare transcription with the source without declaring the details verified.
- Use the established payment-control process for new or changed instructions.
Errors to avoid
- Do not interpret a valid-looking account format as proof of authenticity.
- Do not use contact information on the questioned invoice as the sole verification channel.
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: Payment-instruction verification: FBI IC3 guidance. 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