Keep invoice item codes as text when exporting to a spreadsheet

Where the extra work starts

Protect identifiers through export and re-import so a faster extraction does not create a slower cleanup job.

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.

Check the actual stored value, not only a display format. Adding visible zeros later cannot establish how many zeros the source originally contained, and it cannot recover digits lost through numeric conversion.

A practical way to get it right

Create a small test set with a leading-zero code, an ordinary alphanumeric code and a long numeric-looking code. Record their exact source strings and source locations. Keep the raw extracted identifier separate from any normalized or lookup value used later.

When importing CSV into Excel, inspect the preview and set identifier columns to Text before loading or converting them. Do not rely on double-clicking the CSV and accepting automatic interpretation. Save a workbook copy if you need types and review notes that a plain CSV cannot carry.

Re-export and re-import the test using the same route the receiving colleague will use. Compare every character with the source strings. If a conversion already changed a code, return to the source or preserved raw data rather than guessing a fixed width.

Microsoft: Keeping leading zeros and large numbers recommends importing numeric-looking identifiers as Text. Apply that before conversion, especially for codes with leading zeros or more than fifteen digits.

What this looks like on a real task

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

The second row may survive an uncontrolled import while the others fail, so one successful code is not a sufficient test. Copy the three-column comparison and add the receiving application's actual result. The long example is an invented identifier, not a financial account number. Preserve the string exactly even if it is never used in arithmetic.

Catch the cases that create rework

A custom numeric format can make a cell display zeros while its underlying value remains numeric. That may be unsuitable when the file will be used by another program. A later format change also cannot repair digits already lost. Check the formula bar or raw import representation and compare with source evidence.

If a code's length varies legitimately, do not pad every row to the same width. Record the source value and investigate unexpected variation with the reviewer.

Microsoft: Import or export text and CSV files explains that opening CSV uses default interpretation settings. Use a controlled import and inspect the resulting identifier column rather than assuming the exported string survived.

Decide whether the change is worth keeping

The acceptance check is an exact string match after the complete handoff route, including re-import. Keep a few representative identifier cases in the repeatable test set whenever the export format or receiving system changes. ParseMill's public invoice example includes a leading-zero item for inspection, but your own downstream import settings still need to be tested.