Quicken Community is moving to Single Sign On! Starting 1/22/21, you'll sign in to the community with your Quicken ID. For more information: http://bit.ly/CommunitySSO
Options (calls and puts) from Fidelity don't match when closing a position

I trade Options through Fidelity. Quicken correctly downloads the initial option position, i.e., when I buy or sell a call or put quicken correctly lists it. However when I close the position Quicken doesn't correctly assign the close action to the correct opening position requiring me to enter multiple Placeholder transactions. What needs to be done to get closing transactions to correlate to the opening transactions? Is there a place to suggest features such as this for Quicken? And should this be a standard "trouble" ticket?
Tagged:
0
Answers
This is a problem. You should never allow placeholders. They are far more trouble than they're worth. I probably can't help you resolve them because I personally have never allowed them. But perhaps if you go into some detail about why you can't get rid of the placeholders, and what happens when you try, someone here may be able to assist.
This is the section of the amusement park called Fantasy Land. I have been complaining to Fidelity for many years about their Quicken issues. They just don't care.
@"Rocket J Squirrel" The opening transaction looks normal, for instance "action:ShtSell, Security: PUT (LAZR) LUMINAR TECHNOLOGIES DEC 18 20 $25 (100SHS)", however the closing transaction in the import looks like "action: CvrShrt, Security: Expired PUT 4853859R" (I have no idea what that code for the PUT represents). Within the opening and closing download's Security Detail is the symbol I am either selling or buying, i.e., LAZR201218P25. If this field in both transactions is matched, along with any additional uniquely identifying information, the code within Quicken would then match a ShtSell to CvrShrt, it could even pop up a question dialog if unsure. IMO, Quicken should be able to match these fields and correlate the two transactions as being associated to one Security, this isn't an impossible task, but it may require additional programming.