What to do

Treat long invoice and account references as text from the start. A spreadsheet can display numeric-looking identifiers in scientific notation and may lose precision for long numbers. Returning the cell to a wider display cannot recover digits that have already been changed.

An identifier containing E can also be interpreted as exponent notation by automatic conversion.

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
Long referencePrinted identifier 123456789012345678Import as text and compare every digit.
Exponent-like codeSupplier reference 12E04Preserve the exact code rather than allowing a numeric interpretation.

Suggested review columns

ColumnDefinition or instruction
Raw invoice referenceExact source identifier before spreadsheet interpretation.
Imported referenceValue after text-typed import for comparison.
Conversion issueWhether digits, exponent-like text, or length changed.

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. Locate identifier columns before opening the CSV with automatic defaults.
  2. Assign a text type in the import process or Power Query.
  3. Reimport from the untouched file if precision or code characters were lost.

Errors to avoid

  • Do not assume widening the column reverses numerical precision loss.
  • Do not use arithmetic operations on document identifiers.

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: Leading zeros and large identifiers: Microsoft Support. 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