Skip to main content
All CollectionsImporting dataCommon issues
CSV import: timestamps are not in UTC timezone
CSV import: timestamps are not in UTC timezone
R
Written by Robin Singh
Updated over a week ago

Have you exported a CSV or Excel file from your broker only to notice that the timestamps are not reported in UTC time?

Most platforms will stick to the standardized UTC timestamps but some will report all timestamps using a specific timezone or using the user's local timezone. If your files are being reported using a different timezone then you may need to specify the timezone of the file when you import it to Koinly.

Koinly is able to automatically detect the timezone of your file if it is specified either in the column headers or in the fields themselves. If the timezone is not specified in the file then Koinly will assume that the reported timestamps are in UTC time.

You can easily fix this by specifying your file's timezone when importing it.
If your files are not in UTC, you need to choose the timezone the timestamps are in when importing. For example, if your file's timestamps are in EST, you need to choose EST in the dropdown instead of "Auto-detect / UTC"

Did this answer your question?