Skip to content

My import came in short or wrong

Read the preview, correct invalid rows and timestamps, and verify the trades that were actually saved.

2 min read

First separate the source file from the preview and the saved trades. A row in a file can be an execution, a summary, or something the importer cannot interpret. The analysis shows what it detected before you decide what to save.

Check the export you supplied

Export the detailed executions for the period you need. Check that the file includes the instrument, quantities, prices and timestamps needed to reconstruct the trade. Compare one expected execution in the source with the corresponding entry in the preview.

Open the existing analysis if it is available. Review the selected destination account and any mapping or validation messages before choosing rows. An analysis can finish successfully while still identifying rows that need correction.

Check time and destination

  1. Inspect a missing or misplaced execution in the preview. Check that the source timestamp includes the intended date and offset, or that the import is using the intended source time zone.
  2. Confirm which destination account is selected and which rows are checked. Review any warnings about a possible duplicate or unsupported row before committing the selection.
  3. Choose Import trades and wait for the saved result. Use the same account and date range in Trades to locate the imported records.
Open trade import

Resume or correct the existing work

If you closed the dialog during analysis, look for its saved analysis before uploading another copy. When you correct a file, verify the preview against the original result before importing again. Similar rows can represent legitimate separate executions, so review which records were already saved.

For a support request, include the importer used, the expected and saved counts, the selected account, and a small example of a rejected row with sensitive fields removed.

Did this article answer your question?