# Importing of Degiro transaction and dealing with stock splits

**URL:** <https://community.mycapitally.com/t/importing-of-degiro-transaction-and-dealing-with-stock-splits/146>\
**Category:** Issues\
**Tags:** imports\
**Created:** [June 26, 2024, 7:14pm UTC](https://community.mycapitally.com/t/importing-of-degiro-transaction-and-dealing-with-stock-splits/146 "2024-06-26T19:14:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![David1](https://community.mycapitally.com/user_avatar/community.mycapitally.com/david1/32/58_2.png) [@David1](https://community.mycapitally.com/u/David1)\
**Post date:** [June 26, 2024, 7:14pm UTC](https://community.mycapitally.com/t/importing-of-degiro-transaction-and-dealing-with-stock-splits/146/1 "2024-06-26T19:14:32Z")

</div>

When I do a transaction import from a Degiro trasnactions.csv file, whenever there is a recorded stock split, the degiro transaction file has a buy and a sell transaction.

Capitally also introduces a split traction (correctly) post import. However because of the buy/sell transaction, the recorded share count is incorrect. It effectively multiplies by the split ratio.

Manually I can of course look for each split and delete the corresponding buy and sell transaction to get the correct share count.

However it would be nice if these transactions could be detected by the importer and highlighted so the user can allow the imported not to load the buy/sell record

---

<div class="post-metadata">

**Author:** ![rafal](https://community.mycapitally.com/user_avatar/community.mycapitally.com/rafal/32/18_2.png) [@rafal](https://community.mycapitally.com/u/rafal)\
**Post date:** [June 27, 2024, 9:44am UTC](https://community.mycapitally.com/t/importing-of-degiro-transaction-and-dealing-with-stock-splits/146/2 "2024-06-27T09:44:37Z")

</div>

I “love” when brokers pull this sort of magic tricks. Could you send me a CSV with such two rows to [support@mycapitally.com](mailto:support@mycapitally.com) or here?

There’s imports revamp near in the pipeline, and depending on how Degiro is doing this, it might be supported in the new version.

---

<div class="post-metadata">

**Author:** ![srikanth\_akkiraju](https://community.mycapitally.com/letter_avatar_proxy/v4/letter/s/0284c7/32.png) [@srikanth\_akkiraju](https://community.mycapitally.com/u/srikanth_akkiraju)\
**Post date:** [August 29, 2026, 8:13am UTC](https://community.mycapitally.com/t/importing-of-degiro-transaction-and-dealing-with-stock-splits/146/3 "2026-08-29T08:13:30Z")

</div>

was there a resolution for this one? I am new user and i still see many issues with how stock splits from degiro is being handled