Excel changed trade IDs: how do you preserve every digit?

A broker report and a spreadsheet can have identical row counts and financial totals but different operation identifiers. This can happen when a program turns a long ID into a number and loses its final digits. A subsequent table join may then attach a fee to the wrong execution. The two fictional IDs below let you check an import and export round trip without guessing which digits should be restored.

Why should a trade identifier remain text?

An ID answers which record, not how much money. Adding order numbers is meaningless. Every character can matter, including a leading zero. Profit, commission and volume are separate fields intended for arithmetic. Decide their types before building formulas in your trading spreadsheet. An attractive dashboard does not resolve an ambiguous record key.

Microsoft describes Excel's 15-digit numerical precision and recommends text for longer codes. This does not mean every broker uses long tickets. We are examining an import mechanism affecting an execution ID, order ID or another key. Inspect the raw representation rather than relying on an abbreviated cell display or a familiar-looking number.

Establish what the column identifies. In MT5, order and execution identifiers are distinct; DEAL_ORDER and DEAL_TICKET have different meanings. The same order number appearing alongside several fills need not be an error. Deduplication requires the appropriate key and a stated record definition. Removing every repeated label can remove legitimate operations.

How can two operations acquire the same key?

Compare complete character strings. Scientific notation in a display alone does not establish lost data: inspect the value and export. Do not append 1 to the first row and 2 to the second based on their order. Real history may be reordered, incomplete or contain additional operations. A damaged key does not retain enough information to choose the correct original.

How do you import without losing characters?

Keep an unchanged source copy outside the working workbook. Inspect a sample in a text editor, including the heading and complete IDs. Distinguish the provider download from a copy already saved by Excel. Calling a file original does not establish its provenance; record retrieval time and report scope separately. Use copies for experiments so the reference remains available.

Use a controlled text/CSV import and explicitly assign text type to identifier columns. Microsoft's guide describes this in Power Query. Inspect the query steps: if an earlier step converted the value numerically, changing to text afterwards cannot recover missing characters. Restart from the preserved source and correct the conversion sequence rather than formatting damaged values.

Excel's import options include automatic conversions for long numbers, leading zeros and some date-like strings. Availability varies by edition, so inspect your version. A setting on one computer does not establish settings on another. A shared workbook needs a documented import procedure, not only an assurance that it worked for its creator.

After loading, inspect a sample, save a copy and export it again. Read that file as text and compare it with the reference. This tests the whole source → import → export route. Showing all digits in a workbook is insufficient if a different representation later reaches your journal, another program or a joined table. Check the artifact actually used downstream.

What does the local ID comparator check?

Paste two lists: original IDs and IDs after the spreadsheet round trip. Use one identifier per line, without a CSV heading, other columns or quotation marks. Allowed characters are ASCII letters, digits, underscore, dot, colon and hyphen. Each list permits 10,000 nonempty lines and each ID permits 128 characters. Leading or trailing whitespace is an error; it is not silently trimmed. Each list also permits at most 20,000 total lines, including blank lines, and 1.5 MB. Letter case matters: ABC and abc differ.

The tool preserves zeros and compares occurrences of exact strings rather than numerical sums. It reports missing and additional identifiers and repetitions. In our example, both original IDs disappear and the new key occurs twice. A pattern consistent with truncation after digit 15 is a diagnostic hypothesis, not proof that Excel caused the difference. Reordering alone should not change occurrence counts.

The checker operates locally on pasted lists. It does not sign in to a broker, verify identifier authenticity or reconstruct trades. Matching lists do not validate prices, amounts, dates or fees. Compare appropriate scopes separately when reports cover multiple accounts. The same label outside a defined scope does not automatically refer to the same operation. Do not merge unrelated reports to force a match.

For a discrepancy, preserve both copies and locate the first transformation. Do not guess corrections. Linking executions to a shared position needs reliable relationships; checking identifiers prepares that input but does not itself allocate profit to robots. Record the reconciliation in your journal before using its statistics to assess performance.

What should you do before calculating from the report?

1. Select one identifier column and state the record it identifies. Preserve the source before opening a workbook. Inspect the longest IDs and leading zeros. Without the initial export, disclose that limitation instead of treating a later copy as a reliable reference.
2. Repeat the import with explicit text type for IDs, retaining appropriate numeric types for monetary fields. Check automatic-conversion steps and the exported result. Compare complete lists and occurrence counts, rather than only the first few cells displayed on screen.
3. If characters were lost, obtain the original file or request a fresh provider export. Do not reconstruct suffixes from row order. After reconciling keys, check joins, prices, costs and balance separately. Passing one check does not replace the others.