Import trades from Lightspeed

Export your Lightspeed blotter or Account Trade History as CSV, then upload it in Rize Trade under Add Trades > File upload with broker set to Lightspeed.

For the general import flow across all brokers, see How to import your trades.

Export from Lightspeed

Download a CSV from the Lightspeed website blotter for the account and date range you want to import.

1. Log in to the Lightspeed website.
2. Go to Reports > Account List.
3. Click the account number you want to export.
4. Open Blotter and set the date range that covers your fills.
5. Click the CSV button to download the file.

Tip: If an upload fails, confirm the file still has the required headers (Symbol, Price, and Qty) before you try again.

Upload in Rize Trade

After you have the CSV, import it from Add Trades with Lightspeed selected. For the general upload flow, see How to import your trades. Lightspeed-specific settings:

• Set broker to Lightspeed.
• Set Time zone to match the timestamps in your export. Required.
• Trade Date is only needed when your export has times but no dates (no Trade Date or Raw Exec. Time column). Pick the day the fills happened. Leave it empty for a normal blotter export.
• Accepted types: CSV or TXT. Max 50 MB. If your file is larger, see "File too large": how to break up your import file.

After upload, open Settings > Import History to confirm status, trade count, and duplicates. If a job stays queued, fails, or shows an error screen, follow Import queued or something went wrong.

Tip: If dates look shifted after a successful import, fix the time zone and re-upload. See Why are my entries and exits on the wrong dates?.

Formats Rize Trade accepts

Rize Trade reads three Lightspeed layouts: the general flexible export, Account Trade History, and a headerless fallback.

General flexible format

Most blotter CSVs use this layout. Required fields are symbol, price, and quantity. Side and date/time come from the columns below when present.

| Column | Required? | Notes | | --- | --- | --- | | Symbol | Required | Ticker or instrument symbol. Rows that only contain a CUSIP (no trade symbol) are skipped. | | Price | Required | Fill price. | | Qty or Quantity | Required | Share, contract, or size amount. | | Side or Buy/Sell | Recommended | Maps to buy or sell (see side values below). | | Raw Exec. Time | Recommended | Full date and time of the fill when present. | | Trade Date | Optional | Trade date. Combined with Execution Time (or another time column) when both exist. | | Execution Time | Optional | Time of the fill; used with Trade Date. | | Time | Optional | When the file has no date column at all, used with the Trade Date you pick on the upload screen. | | Commission Amount | Optional | Commission on the fill. | | FeeSEC, FeeTAF, Fee1, Fee2 | Optional | Fee fields when present in the export. | | Security Type | Optional | Instrument type when included. | | Transtype | Optional | Only rows where Transtype is Trade are imported. Other values are skipped. |

The Integration Guide highlights these columns for a clean import: Raw Exec. Time, Symbol, Side, Qty, and Price.

Account Trade History format

If the first line of the file names it as Account Trade History, Rize Trade reads the column headers from the second line. Symbol, Price, and Qty are required:

| Column | Notes | | --- | --- | | Exec Time | Execution date and time. Rows without it are skipped. | | Side | Buy or sell side of the fill. | | Qty | Quantity. Required. | | Symbol | Instrument symbol. Required. | | Price | Fill price. Required. | | Strike | Option strike when present. | | Exp | Expiration when present. | | Type | Instrument or option type when present. | | Spread | Spread label when present. |

Headerless files

If the file has no header row, Rize Trade reads columns in this order: date, time, symbol, qty, price, side, and any columns after that. Dates in headerless files use MM/DD/YY or MM/DD/YYYY plus a time value. Prefer a headed blotter export so the mapping stays clear.

How side values are read

Side maps to buy or sell from either a Buy/Sell column or a Side column.

• Buy/Sell column: values such as buy or cover map to buy; sell or short map to sell.
• Side column: values that start with B or equal BOT map to buy; values that start with S or equal SLD map to sell.
• If neither column gives a side, a negative quantity is read as a sell and a positive one as a buy.

How dates and times are read

Rize Trade picks the richest date/time available on each row, in this order:

1. Raw Exec. Time as a full datetime when present.
2. Trade Date combined with Execution Time (or another time column) when both exist.
3. When the file has no date column at all: Time paired with the Trade Date you pick on the upload screen.
4. On headerless files: date as MM/DD/YY or MM/DD/YYYY plus the time column.

A row with a date but no execution time is skipped rather than imported at midnight.

Set Time zone on the upload screen to match the timestamps in your Lightspeed export so fills land on the correct session.

Rows that are skipped

Some rows are intentionally left out so only real fills enter your journal.

• Rows where Transtype is present and is not Trade.
• Rows whose symbol is CUSIP-only (no tradeable symbol).
• Rows with no execution time.

Why your import might be rejected

When something is off, Rize Trade shows a clear message. Lightspeed-specific rejections are below; for generic errors (file too large, wrong file type, empty file, missing account/broker/time zone), see Fix any import problem.

This Lightspeed export has times but no dates

Message: This Lightspeed export has times but no dates. Pick the Trade Date above, or export again with the Trade Date column included.

Cause: The file has no Trade Date or Raw Exec. Time column, and no Trade Date was picked on the upload screen.

Fix: Pick the Trade Date for these fills and upload again, or export again with the Trade Date column included.

Missing required columns in Lightspeed file

Message: starts with Missing required columns in Lightspeed file. Found headers: and ends with Expected: Symbol, Price, Qty.

Cause: The file is missing one or more of Symbol, Price, and Qty (or Quantity).

Fix: Export again from Blotter without removing or renaming those headers. Confirm the file still includes Symbol, Price, and Qty before uploading.

No trades imported: rows have no execution time

Message: starts with No trades imported: and ends with row(s) have no execution time. Export again with the Execution Time column included.

Cause: Rows have a date but no time of fill, so none could be imported.

Fix: Export again with the Execution Time (or Raw Exec. Time) column included, then re-upload.

No valid trades found in the Lightspeed file

Message: No valid trades found in the Lightspeed file.

Cause: Headers are present, but no rows could be turned into trades. This is often empty values, only skipped Transtype rows, or CUSIP-only symbols.

Fix: Export filled trades (Transtype Trade) with real symbols, prices, and quantities, then re-upload.

Account Trade History file has no data rows

Message: Account Trade History file has no data rows.

Cause: The file was recognized as Account Trade History, but it has no trade lines under the header.

Fix: Re-export Account Trade History for a range that includes executions, or use a standard blotter CSV instead.

Missing required columns in Account Trade History file

Message: Missing required columns in Account Trade History file.

Cause: The Account Trade History export is missing one of the columns needed to build trades: Symbol, Price, or Qty.

Fix: Export Account Trade History again without changing column names, or switch to a blotter CSV with Symbol, Price, and Qty.

No valid trades found in Account Trade History file

Message: No valid trades found in Account Trade History file.

Cause: The Account Trade History layout was recognized, but no rows produced usable fills.

Fix: Confirm the export includes filled executions with symbol, side, qty, price, and exec time populated, then upload again.

Failed to read Lightspeed file

Message: starts with Failed to parse Lightspeed file: followed by more detail.

Cause: The file structure could not be read as a Lightspeed export.

Fix: Download a fresh CSV from Lightspeed Blotter or Account Trade History. Upload the original download without converting it to Excel, Numbers, or PDF.