I am using Quicken Classic for Windows and am on the most recent build: 27.1.67.7. I think I've discovered an issue I'd like to pass along related to date formats. The issue is related to whether you are using a month/day/year format - as is standard in the US - or day/month/year format - more typically used internationally or by the military.
I had this issue originally back in Nov 2025 - where the reconciliation for my holdings as I downloaded transactions from Fidelity defaulted to a month/day format - rather than day/month - as I have set on my computer system. I was making updates on 02-Nov - or 11/02. My Fidelity accounts were all showing holding quantities from 10-February - or 02/10. I reset accounts - and that fixed the issue…but recently - I had to re-instate a back-up - and when I did so..the same problem occurred. I was downloading transactions on 02-May - or 05/02 - and my Fidelity accounts reverted to showing me quantities from Feb 04…or 02/04.
I believe I changed my system configuration then to go back to the typical date/time format I prefer to use - DD/MMM/YYYY - and when I restated the back-up - that's what caused the mismatch. This time - to resolve the issue - I didn't reset the Fidelity accounts - I simply changed the date/time format on my system to the MMM/DD/YYYY and that resolved the issue - everything matched.
My feedback to the development team is that, as you look at download data and date/time formats, you should probably check to see what date/time format is being used by a user's system, and adjust whatever sync information is needed so that everything matches what's in the system. If I can provide additional feedback to help you make this improvement, please reach out to me. I will also make a mental note to not select the date/time format I prefer to use on my system, since Quicken cannot handle any format other than MMM/DD/YYYY in the US.
I have yet to determine if time formats affect this as well. For example - I prefer to use a 24-hour clock - so 1:23pm is 13:23 on my system. Perhaps this also affects syncing data - but I would imagine it is a rather simple programming fix to coordinate syncing data to a user's preferred date/time format.
