Protect long numeric-looking identifiers from spreadsheet precision loss

An identifier is not a quantity

Preserve it as text before conversion so the workbook still matches the original record when someone uses it for a lookup.

Test an invoice with the dates, quantities or amounts you find hardest to copy accurately. ParseMill puts extracted invoice fields beside the source for review and correction before export. Open the downloaded workbook in your usual spreadsheet application and check those values there too.

Preserve an untouched source string and define exact equality as the acceptance rule. Approximate numeric equality is inappropriate for identity: two references differing in their final digit can refer to different records.

Use a deliberately difficult fixture

These are invented identifiers, not personal or financial data. Their only purpose is to expose conversion loss. Copy them into a controlled test file as text and keep that file as the expected reference for your import and export checks.

Microsoft: Keeping leading zeros and large numbers documents Excel’s automatic numeric conversions and text-preserving import. Use the import path and controls available in your actual Excel version, then verify the resulting values.

Run the round-trip check

1. Create a source fixture with the identifiers in an explicit text column. Record the intended character count and exact expected strings.
2. Import through a workflow that lets you declare the column as text before numeric conversion. Inspect automatic type-detection steps and remove or replace any unsafe conversion.
3. Save or export using the intended delivery format, then reopen it through the recipient’s normal import process. Do not assume that a CSV file carries spreadsheet type metadata.
4. Compare each reopened identifier character by character with the expected reference. Check leading zeros, length and final digits, not merely the displayed prefix.

Microsoft: Power Query data types describes numeric precision limits and text representation. A sufficiently wide display column does not change the precision of an already numeric value.

Repair from evidence, not formatting

If two distinct fixture identifiers collapse to the same value, stop using that imported column as a key. Recover it from the original text source and repeat any joins or deduplication that depended on it. Adding zeros or changing a number format does not establish the missing digits.

Check downstream software too. A correct workbook can be damaged when its CSV export is reopened automatically. Include the recipient application and import settings in the handoff so the preservation rule survives delivery.

Record the actual test result

This article supplies a fixture and expected outcomes; it does not claim that your spreadsheet has passed them. Acceptance requires three distinct exact strings after your own round trip, with the first retaining both leading zeros. Record the application version and result.

Use the same fixture when evaluating ParseMill exports. Confirm identifier fidelity before relying on those fields for matching, reconciliation or record updates.