-
Notifications
You must be signed in to change notification settings - Fork 625
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
Please allow "Sell" transactions totaling $0 #2103
Comments
Duplicate of #2094 |
Whoops, sorry - closing :) |
This isn’t a duplicate of #2094, but it is a clear “won’t fix”. Use outbound delivery instead of sell. |
Then perhaps for UI clarity, it would be better to display that info on the dialog - i.e. "Sell with an amount of $0 should be input as Outbound Delivery," vs "Input required for sub-total." |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There seems to be a check in the software preventing any sale where the amount totals $0 (it shows the error "Input required for 'Total'). In the case of cryptocurrency, it would be much more convenient if this were allowed. Why? In PP, fees are always paid out in 'currency,' not in 'securities' - but in crypto, fees are paid in the crypto itself (i.e. ethereum gas). To document this in PP, it takes 2 transactions each time: a Sell transaction to convert the crypto to USD, followed by a Fees transaction for the same amount. However, if "Sell" transactions weren't prevented from having a total of $0, this could be documented as just one "Sell" where the amount equals the fees. i.e. in the Sell dialog, the amount is $10, fees is $10, thus credit total is $0. The result is the as desired: the crypto 'shares' were removed, you booked $10 in fees, and no change to your USD holdings - but it took half as many transactions.
As my transaction history grows increasingly cluttered with Sell, Fee, Sell, Fee, Sell, Fee, I think it'd be a lot more crypto-friendly to just remove this 'total can't be $0' check :)
The text was updated successfully, but these errors were encountered: