On Sunday, May 12, 2024 at 9:13:46 PM UTC+7 nugget@gmail.com wrote:
What would be the beancounter's way of handling this?
I dont know anything better than manually resolving the "No position
matches" errors one at the time by matching and correcting the cost bases.
Since my personal investm
Yes, IBKR actually confirmed exactly this to me: in the opening
transactions, fees get included in the cost bases. not so in the closing
transactions. This seems the standard, so rather a general thing than a
IBKR-specific issue.
What would be the beancounter's way of handling this?
I dont kno
This is (probably, I've never looked at what FlexQuery reports) IBKR adding
the transaction costs to the cost basis (which is how US tax accounting
works). So when you buy something it will have a (very slightly) higher
cost basis than whatever the order execution said.
On Saturday, April 13, 2
just to add, my pdf activity statements from IBKR also state those two
different costs ("T.Price") in activity statements from 2022 and today, so
the numbers are clearly coming from them
On Saturday 13 April 2024 at 10:30:58 UTC+2 nug get wrote:
> Hi everyone
> I recently closed some positions
Hi everyone
I recently closed some positions I held at InteractiveBrokers, for which i
have a nice API-based ingestion pipeline to beancount. However I noted lots
of "No position matches"-Errors.
Turns out, the reported cost basis / Trade prices of the closed positions
are very slightly off (b
