-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug in expired short option position from Vanguard #105
Comments
Probably we need to add something here: To be honest that kind of transaction is beyond me. What output would you expect to see for this kind of transaction? |
Fair enough. Selling puts is often a stupid thing to do anyway so you could argue not supporting it is doing people a favor. :)
I want a transaction so that when the assignment happens the option position goes away. The first transaction below is what ledger-autosync produces for buying the stock (which is correct). The second transaction is what I manually added to fix things to note that the option position goes away.
|
Thanks for the example! Is the only information about the put available in the |
I think there is a bug in processing expired short option positions from Vanguard.
What happened is I sold 20 puts for $0.25 and they were assigned to me (i.e., the person who bought the puts exercised them early and sold me 2000 shares of stock). The buy of 2000 shares shows up correctly but the short puts never go away.
Below is an example of what ofxclient is downloading which ledger-autosync is having trouble parsing:
I end up seeing something like the following in the output:
which is the opening position where I sell the puts but the
"Z9713494Z"
position never gets closed out in the output of ledger-autosync.I can't follow the python code very well but it seems like the second
"Z9713494Z"
transaction is ignored inconverter.py
.This may well be a bug in Vanguard's OFX output but it seems odd that
converter.py
isn't even seeing the second"Z9713494Z"
transaction.The text was updated successfully, but these errors were encountered: