[Interactive Brokers (IBKR)]: Parser incompatible with new IBKR header names

[samsonluk]

Describe the bug
When running the IBKR converter, the tool fails to detect existing BUY transactions and repeatedly prints warnings such as:

No result found for buy action for <ISIN>! Please add this manually..

The issue occurs because the current IBKR Client Portal CSV export uses different column names (e.g. Buy/Sell, TradeDate, TradePrice, TradeMoney, CurrencyPrimary) which the converter does not recognise. As a result, all BUY actions are ignored and the converter assumes the buys do not exist.

This is not user error: the CSV is generated directly from the current IBKR interface and is valid.

---

Version
Export to Ghostfolio: __VERSION__ (the version printed in the console).
Running via npm, not Docker.
Command executed:

npm run start ibkr

---

Expected behavior
The IBKR converter should correctly parse CSV files generated by the current IBKR Client Portal and detect BUY transactions based on the actual column names provided by IBKR.
It should map new IBKR fields to the expected ones:

• Buy/Sell → Action
• TradeDate → Trade Date
• TradePrice → Price
• TradeMoney → Amount
• CurrencyPrimary → Currency

The conversion should complete without incorrectly warning about missing buy actions.

---

Provide error input

CSV header from IBKR (actual):

Buy/Sell,TradeDate,ISIN,Quantity,TradePrice,TradeMoney,CurrencyPrimary,IBCommission,IBCommissionCurrency

Sample CSV rows that trigger the issue:

BUY,20250610,US00775V1044,250,19.5,4875,USD,-0.634393125,USD
BUY,20250610,US0259328641,100,16.5,1650,USD,-0.134007717,USD
BUY,20250107,US04686J8383,88,25.11,2209.68,USD,-0.26533725,USD

Error output:

[i] No result found for buy action for US00775V1044! Please add this manually..
[i] No result found for buy action for US0259328641! Please add this manually..
[i] No result found for buy action for US04686J8383! Please add this manually..
...

This happens even though the BUY rows clearly exist in the CSV.

---

Additional context
IBKR recently updated column names in Client Portal trade CSV exports. The converter currently supports only older Flex Query field names, causing it to not detect BUY rows even when they are present.

This appears to be a compatibility issue with the latest IBKR CSV schema. Supporting the new IBKR column names (or adding auto-detection) should resolve the problem.

[dickwolff]

Hi,

When I try to look up the isin codes from the error on Yahoo Finance, I don't get any result there. They can't be found. This is what the error message from the tool is saying as well. As Yahoo Finance is also used within Ghostfolio, unfortunately there is nothing I can do. The converter seems to work as intended.

[samsonluk]

Thanks. Now I tried created isin-overrides.txt in project root:
US00775V1044=US00775V1044
US0259328641=US0259328641
US04686J8383=US04686J8383

and have .env:
ISIN_OVERRIDE_FILE=isin-overrides.txt

Why still can't override the lookup and generate the entry to e2g-output .Json?

[dickwolff]

Did you specify the path to the isin override file as an environment variable? To verify if the overrride works, you can set the environment variable ‎DEBUG_LOGGING‎=true.

[samsonluk]

I have finally figured it out. It was not related to setting the environment variable using the shell command "export" or placing them inside the .env file; both methods work. However, I discovered that if DEBUG_LOGGING is not set to true, the conversion will not occur.

Here are the combinations that I tested:

Non-working combination:

• .env
  • ISIN_OVERRIDE_FILE = "isin-overrides.txt"
  • DEBUG_LOGGING = false

Working combination:

• .env
  • ISIN_OVERRIDE_FILE = "isin-overrides.txt"
  • DEBUG_LOGGING = true

The latter setup works effectively.

[samsonluk]

The displayed message indicates the following::
[i] Starting Export to Ghostfolio v__VERSION__
[i] Found symbol override file. Loading..
[i] Restored 12 ISIN-symbol pairs and 12 symbols from cache..
[i] Processing file using IBKR converter
...
...
[d] Converted ISIN US0082528508 to symbol US0082528508 as it was overridden!
[d] getSecurity(): Found 0 matches by symbol US0082528508
[d] getSecurity(): No initial match found, trying by symbol US0082528508
[i] No result found for buy action for US0082528508! Please add this manually..

the entry for US0082528508 is still not present in the output when searching the specified JSON file:
$ cat ghostfolio-ibkr-20251208104822.json | grep US0082528508
$

[swissbuechi]

IBKR transactions (buy/sell) are still working fine for me with VT.

[samsonluk]

I apologize for the confusion, but the ISIN override feature in Export-To-Ghostfolio is not intended for the use case I am trying to implement. Specifically, I want to map ISIN=ISIN in the isin-overrides.txt to bypass the validation from Yahoo Finance. My goal is to generate entries with the failed ISIN like below:

{
"accountId": "xxxxxxxxxxxxxxxxxx",
"currency": "USD",
"dataSource": "MANUAL",
"date": "2025-06-09T23:00:00.000Z",
"fee": 0.634393125,
"quantity": 250,
"symbol": "US00775V1044",
"type": "BUY",
"unitPrice": 19.5,
"comment": "US00775V1044 (US00775V1044)"
},

and then manage them within Ghostfolio’s MANUAL custom asset.

[swissbuechi]

You can customize the mapping to a MANUAL symbol. Just put the ISIN from the .csv on the left and your MANUAL on the right like:

8262527=GF_BTC-CHF

PS: Due to a recent change to MANUAL symbols in Ghostfolio you may need to migrate some tables first.