Why was this post closed when it is an acknowledged issue without providing a resolution?
Hi @ddemoney, Thank you for reaching out to the Quicken Community!
If you haven't done this yet, I suggest reviewing our support article about how matching transactions work in Quicken. In that thread, multiple users reported different types of issues involving transaction matching, duplicate transactions, and Reminders.
Our support team has requested additional information to better understand what may be causing the issue. Since the behavior can vary depending on the transaction details and the user's account setup, each scenario needs to be reviewed individually.
To help us better understand what you're experiencing, could you please provide the following information?
This information will help us determine how Quicken is matching the downloaded transaction and whether there is a pattern that may need further investigation.
I look forward to your reply and appreciate your help in providing these details!
The transaction date, the download date, and the posted dates are always within a few days of each other. Sometimes the transaction date is a day or two after, sometimes it is a day or 2 before. The amount and payee match; however, the category in the entry created by Quicken is almost always wrong (typically empty). If I delete the incorrect entry created by Quicken, it will then match to the correct entry which was already in the register. This seems to be tied to specific accounts - in some accounts it happens almost every time for several recurring bill payments & income entries; in other accounts, it never happens.
This problem has been occurring for several months and was first reported in the post I referenced above - which was closed by Quicken without giving any explanation as to why or whether it is being fixed. It seems that when a community post is closed, you owe your users an explanation as to why.
Hi @ddemoney, I understand why the closure of the previous post would be frustrating, especially since you’re still experiencing the issue. I also appreciate the information you’ve provided so far. The post was closed after 30 days without activity. This does not mean that the underlying issue was considered resolved.
Duplicate transactions can occur for different reasons and in different scenarios. While the symptoms may look similar, the underlying cause can be different, which is why our team is requesting screenshots of the duplicate transactions along with the transaction details.
Without that information, it is difficult for our team to determine which scenario is affecting your account and investigate the appropriate cause.
If you’re still experiencing this behavior, please provide the requested screenshots and details in this thread. That information will help our team continue investigating the specific behavior you’re seeing. [CTP-16657]
I am not crazy about putting my personal financial information in a public discussion group. If you can tell me specifically what you would be looking for, I can provide those details.
Also, after the most recent Quicken upgrade (R69.29), the behavior changed slightly - OSU now matches the downloaded entry to the correct entry in the register, but the duplicate entry is still there (this is based on a single case, I will have to wait for more transactions to see if it is persistent).
Hi @ddemoney, I completely understand your hesitation about posting personal financial information in a public discussion. You do not need to post any sensitive information here.
Our escalation team is requesting transaction details and screenshots showing the behavior you’re experiencing, including the transactions on the financial institution's website and the duplicate transaction being created. This will help the team compare what Quicken is receiving with what is already in the register.
Since this information may contain personal financial details, I can send you a Direct Message with a secure file link where you can upload the requested information privately. I’ll then make sure it is transferred to the appropriate team for review. I look forward to your reply!
