CSV import integration

Import trades from a trade-level CSV file

Import trades from a trade-level CSV into Trading Vault. One row holds a trade’s opening details and, if closed, its closing details. See an example and setup steps.

Understanding the format

What is a trade-level CSV?

“Trade-level” describes how the file is organized: one row represents one whole trade. The same row has its opening time, direction, price, and size. If the trade is closed, that row also has its closing time and price. It does not mean one row for every order or fill.

This format works well for a spreadsheet where you have already summarized each trade. If your broker statement lists the opening fill and closing fill on separate rows, use the execution-level CSV option instead.

Simplified CSV example
Trade ID,Symbol,Direction,Open time,Open price,Close time,Close price,Size
T-42,EURUSD,Long,2026-09-01 09:00,1.1000,2026-09-01 11:00,1.1050,1

This single data row describes one long EURUSD trade from open to close. The column names are illustrative; you map your own file’s columns in the profile.

Setup

How to import a trade-level CSV file

  1. Create and configure a profile

    Set up a profile for your trade-shaped file.

    1. In Trade Imports, choose New, select Custom CSV Trades, and choose the destination trade account.
    2. In the profile mapping, set the CSV delimiter, header setting, date and time formats, and report time zone.
  2. Map your columns

    Tell Trading Vault what each column in your file represents.

    1. Map symbol, direction, opening date and time, opening price, and size.
    2. Map closing date and price when present. Add a stable trade ID, costs, stop, target, strategy, or notes if your file includes them.
    3. If your file has a header, use a sample to suggest mappings, then review every suggestion.
  3. Upload, preview, and confirm

    Check the proposed import before adding trades to your journal.

    1. Upload the CSV to the profile.
    2. Review parsed dates, prices, quantities, matched trades, and invalid rows in the preview.
    3. Correct the mapping or source file if needed, then confirm the import.

What to know before importing

  • The header sample used to suggest mappings is read locally and is not uploaded or imported.
  • Use a consistent trade or position identifier when your source provides one; it helps later imports match existing records.
  • Custom CSV profiles are file uploads, not automatic broker connections. Uploads are limited to 4 MB.
  • Trade imports require an eligible membership.

If something needs attention

  • If dates or numbers parse incorrectly, check the delimiter, date format, time format, and report time zone.
  • If your file has multiple fills per trade, use the execution-level CSV format to preserve separate entries and exits.

File uploads show a preview before confirmation. After importing, import history can help you review unmatched or invalid rows.