What to do
A freight invoice can contain several charge types for a shipment. Keep the shipment reference, charge description, and printed amount together so transportation, fuel, handling, and other rows remain distinguishable. Do not equate shipment count with invoice count.
This task concerns rows inside a carrier bill, rather than a single delivery charge added to a goods invoice.
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 |
|---|---|---|
| One shipment, several rows | SHIP-DEMO-1: transport 40.00; fuel 6.00 | Two charge rows belong to one shipment group. |
| Separate documents | Same shipment appears on freight and duty documents | Keep the documents distinct; review their types before classifying a duplicate. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Shipment reference | Printed tracking or shipment identifier for the charge group. |
| Charge description | Exact printed name of each charge or reduction. |
| Charge amount | Printed amount for that charge, with sign and currency. |
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 invoice-level fields before reading the shipment-level detail.
- Preserve row grouping and charge labels in the review worksheet.
- Reconcile group totals with the printed invoice summary without inventing missing charges.
Errors to avoid
- Do not merge freight and import-related documents solely because tracking references match.
- A discount row needs its printed sign retained.
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