Quick answer
Store card identifiers as text before entering or importing them into Excel. A padded display does not prove that the original characters are stored. Recheck CSV imports separately, and confirm the reader's output format and receiving cell with your actual cards.
The worked examples explain software handling. They are not reader measurements or proof of card authentication. Sources and scope · Read our editorial method
If an intended card-ID string such as 00123456 becomes 123456 in Excel, check the worksheet’s data handling before changing the reader. Digit-only input can be interpreted as a number. Use text when the exact characters must match another system.
Check text storage before reader testing
In a blank worksheet, select A2:A10 and choose Text in the Home tab’s number-format control before entering data. Manually type 00123456 into A2. This is an invented identifier for checking software handling, not a real card UID or device output. The instructions and expected results below are examples to reproduce, not a report of an Excel or reader test.
In separate General-formatted cells, enter:
| Check | English formula | Expected when A2 contains the exact text |
|---|---|---|
| Stored type | =ISTEXT(A2) |
TRUE |
| Character count | =LEN(A2) |
8 |
| Exact content | =EXACT(A2,"00123456") |
TRUE |
The examples use English function names and logical values. Use the function names, argument separators and displayed logical values appropriate to your Excel language. A result is useful only alongside the agreed source string; character count alone cannot establish the correct value.
A custom display format can make a number look padded with zeros while leaving its underlying value numeric. Changing an already converted cell to Text does not recover its original characters. Excel numbers also have a limit of 15 significant digits. If characters have been lost, obtain the original from an authoritative source; do not infer it from a padded display.
Recheck CSV imports from the original file
Opening a CSV directly lets Excel interpret columns using its current defaults. A correctly prepared workbook therefore does not establish that the next CSV import preserves the same IDs. CSV quotation marks do not define an Excel column’s data type.
Download the small CSV example. It contains these invented reference strings, plus a character-count column:
| Identifier reference | Expected character count |
|---|---|
00123456 |
8 |
00000001 |
8 |
1234567890123456 |
16 |
These are software test inputs, not card numbers, UID lengths or a manufacturer’s output contract. Keep the source file unchanged; directly opening and saving it after numeric conversion could lose the reference you need for comparison.
For desktop Excel with Data → From Text/CSV, inspect the preview. Disable automatic type detection where that option is available, or choose Transform Data and ensure the identifier column is Text before loading. Review Applied Steps: an earlier numeric Changed Type step can already have altered the value. Replace that conversion from the original text instead of appending Text conversion after it. Compare all loaded strings with the references above, including the 16-character entry.
Check the delimiter and resulting field values. Keep a workbook copy, and check the destination system’s import rules separately. Microsoft documents Automatic Data Conversions settings for Microsoft 365 and Excel 2024 on Windows and Mac; these settings do not directly control Power Query imports. Menu availability differs by version.
Then test the real keyboard workflow
D-Logic describes PR-301 HID output as entering the UID into the selected text field; CDC ACM is a separate serial-output path. Confirm the delivered mode, firmware tier, hexadecimal or decimal representation, byte order and supported prefix/suffix settings.
Select the intended cell before presenting an actual card. Test what happens after any requested Enter or Tab ending, focus changes, card removal and repeated presentation. Record which cell receives the value and whether an unintended extra record is accepted. Text formatting cannot manage application focus.
NXP gives no general recommendation for converting UID bytes into an integer. Compare an actual card against the agreed representation, not this article’s invented strings. UID input alone is not card authentication.
Prepare a useful project enquiry
Record Excel version, OS, reader configuration, the approved input representation and the observed stored result. Use the UID procurement checklist for wider selection, or review the card-ID application.
Ask about your card-ID workflow. Include your card protocol, receiving application, sample quantity and destination. You can insert the project’s existing checklist on the enquiry page. Do not include card keys, passwords or personal cardholder records.
If two systems show different numbers for one card, compare the hexadecimal, decimal and byte-order examples before changing records. The examples are invented calculations, not reader measurements.
Sources and scope
Software behaviour and feature scope checked against these official references on 7 October 2026. The procedure is editorial guidance; no Excel version or reader/card combination was measured for this article.
- Microsoft: leading zeros and large numbers, number formats, text and CSV import/export.
- Microsoft Power Query: data types and automatic detection, Text/CSV connector.
- Microsoft Excel: Automatic Data Conversions scope, IS functions, LEN, EXACT.
- D-Logic: JustID manufacturer description.
- NXP: AN10927 UID handling.
Questions to consider
Will changing a converted cell to Text restore the original zeros?
No. Reimport or re-enter the identifier from an authoritative source. A later format change cannot identify which characters were lost.
Is a zero-padded display enough to verify an identifier?
No. A custom number format can pad the display while leaving the stored value numeric. Check text type and exact content against the agreed source.
