What to do

Separate invoice identity from shipment identity, and keep each charge type attached to the shipment it describes. A carrier bill can contain several shipments and several charges per shipment. Start with a representative sample before relying on a particular nested output shape.

The suggested fields below are a review design, not a claim of a dedicated Parzable carrier integration.

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.

CaseFictional source excerptReview decision
Several shipmentsInvoice DEMO-F1 lists SHIP-A 40.00 and SHIP-B 60.00Two shipment groups belong to one 100.00 invoice summary.
Separate duty documentA freight bill and a duty document refer to SHIP-AClassify both sources before marking either a duplicate.

Suggested review columns

ColumnDefinition or instruction
Carrier invoice numberIdentifier of the complete billing document.
Shipment references and chargesPrinted shipment IDs with charge descriptions and amounts retained together.
Invoice total and currencyPrinted summary value for the entire document.

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

  1. Capture invoice-level fields first and identify shipment section boundaries.
  2. Request charge detail with descriptions rather than an unexplained list of amounts.
  3. Review grouping and normalize any item data separately before destination import.

Errors to avoid

  • Parzable’s batch CSV is file-based, not a guaranteed one-row-per-shipment export.
  • Do not merge shipment charges and invoice totals into one summed column.

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: Carrier explanation of separate freight and duty documents. 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