Importing from any broker

Upload a CSV or XLSX file from any broker or trading platform. The system auto-detects the format or uses AI extraction as a fallback.

Last reviewed

Preparing your file

If your broker is not listed on our supported brokers page, you can still import your transaction data. Most brokers offer a way to download your trading history as a CSV or XLSX file. Here is how to find and prepare your export:

Finding your broker’s export option

  1. Sign in to your broker’s website or app
  2. Look for sections labelled “Reports”, “Statements”, “Transaction History”, or “Trade Book”
  3. Select a date range that covers all the trades you wish to import
  4. Choose CSV or XLSX as the download format (avoid PDF if a spreadsheet option is available)
  5. Download the file to your computer
For the best results, ensure your CSV or XLSX includes at minimum: a date column, transaction type or direction (buy/sell), security name or ticker symbol, quantity, and price. The more columns your file includes, the more accurately the system can parse your transactions.

How auto-detection works

When you upload a file, the import wizard follows a multi-step process to identify and parse your transactions:

Step 1: Format detection

The system first checks whether your file matches any of the specifically supported broker formats (for example Interactive Brokers, Hargreaves Lansdown or AJ Bell), by the column headings rather than the file name. If a match is found, the dedicated parser for that broker is used for the highest accuracy. If the headings match but that parser cannot read any of the dates in your file, the system moves on to the next step instead of importing nothing.

Step 2: AI extraction (fallback)

If no specific parser matches or can read your file, the system uses AI extraction as a fallback. Your file is analysed to work out what each column means, matching up dates, symbols, quantities, prices and transaction types with the standard transaction format. You can also correct the mapping yourself: the review step offers a “Fix column mapping” option that suggests a mapping and lets you change it.

Step 3: Review and confirmation

Regardless of the detection method, you always have the opportunity to review parsed transactions before they are imported. Rows that need attention carry a confidence badge, and you can correct any misidentified fields.

Recommended file structure

While the AI extraction can handle most common formats, providing a well-structured file improves accuracy. The ideal file should include these types of columns:

  • Date: Trade or settlement date in any common format (DD/MM/YYYY, YYYY-MM-DD, etc.)
  • Symbol / ticker / name: An identifier for the security traded
  • Type / direction: Whether the transaction was a buy, sell, dividend, etc.
  • Quantity: Number of shares or units
  • Price: Price per share or unit
  • Amount / total: Total transaction value (optional but helpful)
  • Currency: Transaction currency code, if multi-currency (optional)
  • Commission / fee: Brokerage fees, if applicable (optional)

Supported transaction types

The AI extraction recognises the following common transaction types across different broker formats:

  • Buy / Purchase: Acquiring shares or units
  • Sell / Sale: Disposing of shares or units
  • Dividend / Distribution: Income payments
  • Split / Stock split: Corporate action adjustments
  • Transfer in / Transfer out: Account transfers

Step-by-step import

Follow these steps to import a file from any broker:

  1. Open Import statements in the sidebar, under Estate & assets → Portfolio
  2. Drag and drop your CSV or XLSX file, or click to browse
  3. The system will attempt to identify the broker format automatically
  4. If no specific parser matches, AI extraction will analyse your file
  5. Review the parsed transactions: rows that need attention carry a confidence badge
  6. Correct any misidentified fields (security names, transaction types, amounts)
  7. Confirm the import to create your transaction records

Screenshot, for illustration only

The broker statement importer on the first of its three steps, upload, review and confirm, asking what kind of statement is being imported, whose it is and which account it belongs toThe broker statement importer on the first of its three steps, upload, review and confirm, asking what kind of statement is being imported, whose it is and which account it belongs to
The broker statement importer on the first of its three steps, upload, review and confirm, asking what kind of statement is being imported, whose it is and which account it belongs toThe broker statement importer on the first of its three steps, upload, review and confirm, asking what kind of statement is being imported, whose it is and which account it belongs to
The importer on its first step, upload, where you say what kind of statement it is, whose it is and which account it belongs to.
If the AI extraction produces low-confidence results, try simplifying your file before re-uploading. Remove any summary rows, headers that span multiple columns, or non-transaction data (account balances, disclaimers) from the top and bottom of the file. Clear column headers in the first row produce the best results.

Common issues

File has no clear column headers

Some broker exports include multiple header rows, merged cells, or summary information before the actual transaction data begins. A spreadsheet is read by scanning the top of the sheet for the real heading row, so a title block above the table is usually no problem. A CSV is less forgiving: its headings must be on the first line. If a CSV is not recognised, open it in a spreadsheet application, remove the non-data rows from the top, and re-save it as a comma-separated UTF-8 CSV.

Unrecognised security names or symbols

Different brokers use different naming conventions. If a security is not automatically matched, you can manually select the correct security during the review step, and apply that choice to every other row carrying the same name in one go.

Multi-currency files

If your file contains transactions in multiple currencies, ensure there is a currency column that identifies the currency for each row. Without one, the currency may need correcting by hand during review.

PDF files from unsupported brokers

Apart from the Indian CAS, no broker has a dedicated PDF reader: any other PDF is read by AI extraction, which works best with CSV and XLSX files. If your broker only provides PDF statements, try contacting them to request a CSV or spreadsheet export. Many brokers offer this option even if it is not prominently displayed.

Large files

For AI extraction, your whole file is read to determine the column mapping, so rows deep in a long export are not missed. Very large files may take longer to process. Consider splitting multi-year exports into separate files if processing is slow.

Data security

Your uploaded files are processed using our self-hosted document processing system. AI extraction runs on our own servers, and your financial data never leaves them without your approval: sending a statement to a cloud model for a second read is something you choose after the first result, never the default. The file itself is kept in your document vault so you can open the original statement alongside the imported rows, and you can delete it from there whenever you wish.

Before you import

These parts of the Statement import guide apply to every broker:

Related pages

Can’t find what you’re looking for?

Our support team is here to help. Contact us and we’ll get back to you as soon as possible.

Contact us

We use cookies to improve your experience. See our Cookie policy (opens in a new tab) for details.