Accept All incorrectly matches transaction to an existing transaction in another account

Misterbill
Misterbill Member ✭✭✭
When I do an "Accept All", Quicken is attaching some transactions to what it thinks is a matching transaction in another account.  Below is one that just happened today. I had a $20 deposit posted in my PayPal account, and I had a $20 charge on my credit card. I had already accepted the PayPal transaction and when I did an "Accept All" on my credit card, it incorrectly set the category to the PayPal account, making the incorrect assumption that it was a matching item, even though it did not show "Match" prior to doing the accept.

The good news is that an "Undo Accept All" option was added a while back, which has saved me the major hassle of having to restore from a backup to fix this mess when a large number of transactions are incorrectly matched. But it is still a bug. When I accept transactions individually, it never suggests matching the transaction the way it automatically does when I accept all transactions.

How do I get this reported as a bug, so it can be fixed?

Also, in the time it took me to get the screenshot and post this here, the "Undo Accept All" option has disappeared. Another hassle.





Comments

  • Sherlock
    Sherlock SuperUser ✭✭✭✭✭
    edited September 2021
    I suggest you disable automatic Transfer Detectionhttps://help.quicken.com/display/WIN/Transfer+Detection+preferences

    To report a problem to Quicken, I suggest you select Help > Report a problem...
  • Misterbill
    Misterbill Member ✭✭✭
    Sherlock said:
    I suggest you disable automatic Transfer Detectionhttps://help.quicken.com/display/WIN/Transfer+Detection+preferences

    To report a problem to Quicken, I suggest you select Help > Report a problem...

    Thanks, but the issue here is that it isn't reporting or showing it as a transfer when the download is done, but assumes it when I do the mass accept all. That feature generally works fine when there is a real transfer.
  • UKR
    UKR SuperUser ✭✭✭✭✭
    May I suggest that you review all downloaded transactions before "Accept All", to individually review, change and accept transactions where Quicken could make an error. Transfer transactions, for one. Others, where you had problems with in prior downloads, to ensure they are now generated correctly. Accept those one by one, then "Accept all" the rest. This may take an extra minute or two, but it'll save you the hassle of having to fix bad transactions afterwards.
    You should also review your Memorized Payee List and fix or delete any entries which could cause the creation of bad transactions. Quicken thinks, if it's in MPL it must be OK to use ...
  • Chris_QPW
    Chris_QPW Member ✭✭✭✭
    Sherlock said:
    I suggest you disable automatic Transfer Detectionhttps://help.quicken.com/display/WIN/Transfer+Detection+preferences

    To report a problem to Quicken, I suggest you select Help > Report a problem...

    Thanks, but the issue here is that it isn't reporting or showing it as a transfer when the download is done, but assumes it when I do the mass accept all. That feature generally works fine when there is a real transfer.
    Automatic transfer detection is done after all the transactions have been accepted into the register.  It isn't done as part of the initial Download into the Downloaded Transactions tab.  And it is purely a guess based on the amount and approximately the date.  If automatic transfer mode is on, it should at least be set to confirm to avoid these exact kinds of problems.
    Signature:
    (I'm always using the latest Quicken Windows Premier subscription version)
    This is my website: http://www.quicknperlwiz.com/
This discussion has been closed.