You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When outputting KDVP for 2024 the following transactions are produced:
<ISIN>CA6979001089</ISIN>
<Code>PAAS</Code>
<Name>PAN AMERICAN SILVER CORP</Name>
<IsFond>false</IsFond>
<Row>
<ID>0</ID>
<Purchase>
<F1>2022-04-27</F1>
<F2>B</F2>
<F3>200.0000</F3>
<F4>23.2713</F4>
<F5>0.0000</F5>
</Purchase>
<F8>200.0000</F8>
</Row>
<Row>
<ID>1</ID>
<Purchase>
<F1>2023-03-03</F1> <!-- I think this is not right! -->
<F2>B</F2>
<F3>100.0000</F3>
<F4>14.9581</F4>
<F5>0.0000</F5>
</Purchase>
<F8>300.0000</F8>
</Row>
<Row>
<ID>2</ID>
<Sale>
<F6>2024-05-31</F6>
<F7>300.0000</F7>
<F9>20.1470</F9>
</Sale>
<F8>0.0000</F8>
</Row>
I think that may not be correct.
The first 4 trades have already been closed in 2022.
There are 2 buy orders in 2022-04-27 and 1 buy order in 2023-03-03, which together bring the balance to 400 (spread across 2 different accounts)
On 2024-05-31 2 sell orders happen disposing 300 shares. If we disregard the account IDs, I think that this transaction, based on FIFO, taps 300 shares from 2022-04-27.
This is a diff with ib-edavki output on the left hand side, and how I think that should be on the right hand side:
Something that I have been wondering about is whether FURS take into consideration each individual account separately and that's why ib-edavki acts this way, or are we forced to merge all our trades together when reporting?
The text was updated successfully, but these errors were encountered:
pronebird
changed the title
Incorrect FIFO?
Incorrect FIFO or cross-account currents
Feb 22, 2025
FURS requires FIFO over all accounts and brokers, so your observation is correct.
ib-edavki should support that behavior. In the past we've had IBUK -> IBCE and IBCE->IBIE changes, so we already faced multiple possible accounts in the past and it has worked.
Hence, this is a bug that might require some debugging on your actual data.
@pronebird can you check if ISIN changed between purchase and sale? I had the same issue and this was the reason. I also have a quick (and dirty) fix ready to update all trades with the latest ISIN.
Edit: I see you included ISIN in the note above and that's not it. :/
Hi,
Not sure if that's a bug, basically this is a transaction history:
When outputting KDVP for 2024 the following transactions are produced:
I think that may not be correct.
In other words:
This is a diff with ib-edavki output on the left hand side, and how I think that should be on the right hand side:
Something that I have been wondering about is whether FURS take into consideration each individual account separately and that's why ib-edavki acts this way, or are we forced to merge all our trades together when reporting?
The text was updated successfully, but these errors were encountered: