Check an invoice that uses different header wording

Where the extra work starts

Test the headings your suppliers use so you find unsupported or misread columns before those errors reach a workbook someone relies on.

Upload a representative supplier invoice, inspect its extracted fields and line items beside the PDF, then download Excel. Put the awkward invoice in your trial too: the useful result is less total work after corrections.

ParseMill recognizes supported invoice heading alternatives, including Quantity or Qty and Price, Rate or Unit Price. A familiar alternative can work without recreating a legacy exact-label setup. Merged or multi-level headings still need a specific fit test; support for Unit Price is not a promise to understand every heading.

A practical way to get it right

Copy the visible headings into a comparison sheet and preserve spelling and punctuation. Check the PDF text layer too, since a heading that looks normal may copy with different characters or spacing. Separate a simple supported label change from a structural change such as a merged or two-line header.

Run a representative invoice with the changed wording through the trial. Review the mapped fields against the source rather than relying only on nonempty output. Keep the result with its source layout so you can compare a later supplier change with the version you actually tested.

If a heading or layout is not recognized correctly, document the limitation and compare correction effort with a reviewed manual route. Do not edit the source invoice's wording merely to make the test appear successful, and do not claim that a failed match means the source has no data.

Adobe: Copy content from PDFs describes text selection and copying and how to check document restrictions. Use a heading copy check to reveal character or line-break differences hidden by the rendered appearance.

What this looks like on a real task

Synthetic example. The people, references and figures below are invented to demonstrate the method.

Qty and Unit price are supported alternatives in the invoice workflow, so both are useful trial cases. Copy the comparison and include the source page for each heading. Check that the resulting quantity and unit price match their source columns; recognized wording does not by itself establish correct row mapping.

Catch the cases that create rework

A visually single heading may be composed of separate text fragments or contain a hidden line break. Test copying and inspect alignment. If a label changed alongside column order, review both changes; correcting one does not prove the other is handled.

Avoid replacing all output blanks with guessed values after a header mismatch. Re-establish the mapping or use reviewed transcription so the resulting register remains source-backed.

Microsoft: Power Query PDF connector documents detected-table import and multiline limitations in Power Query. That reinforces the need to inspect structure; it does not establish semantic header matching in ParseMill.

Decide whether the change is worth keeping

The fit record should show the current labels, any mapping problems and the method chosen. For a successful bounded test, compare all required fields and row counts with the source and retain the tested configuration. Use the public invoice example to understand the supported shape, while treating your own document's header comparison as a separate decision.