Awesome, thanks. This sounds good:
1) I'll add unit tests, try to clean up some of the questions and todos i
had, and develop more certainty around the problem and solution
2) I'll share with you my findings and the unit tests, and you can try
running it on your data to ensure things match
3)
- There's no dev list, this is it, not enough traffic to justify a separate
list.
- Your feature touches a very sensitive part of the booking process - one
I've struggled to get sort of right in the past, has a lot of weird
corner cases, it's been a bit of a whack-a-mole situation - I'd have to
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
