Improve Matching Downloaded Transactions [edited] (9 Legacy Votes)

Using Quicken Deluxe 2018 R10.11 Build 27.1.10.11
I have weekly transactions in checking and credit card accounts that are for the same payee and same amount, within each of those accounts, each week. When Quicken matches the downloaded transactions to the entered transactions, it ignores the date such that if there are two or more to be approved, it matches the most recent downloaded transaction with the older or oldest recorded transaction, and vice-versa. I have to manually match each transaction. Even once a transaction is correctly matched together, when I go to the next transaction, it will match a new transaction with an  older or different date that has already been matched. It seems all it looks at is the payee and the amount. It should look at the date also.
0
0 votes

No Status · Last Updated

Comments

  • PerryPerry Member
    edited August 13
     create or restore a mechanism that allows users to remove transactions from the Manual Match dialog list
  • mariettamarietta Member
    edited January 8
    Requesting that Quicken returns a way to remove transactions from the Manual Match dialog
  • QPWQPW Member ✭✭✭✭
    edited October 2018
    Yes, and make it a "visible" way not something hidden by some Ctrl+Shift click this and then that.
  • PerryPerry Member
    edited January 10
    Please consider providing 2 options on the manual match window to eliminate any transactions which have been previously cleared or have been reconciled.    
  • QPWQPW Member ✭✭✭✭
    edited September 4
    [removed]

    I agree that the matching could be better if the date was taking into consideration.  Note it can't be a "fixed rule" as in it being an exact date because the user/reminder might not be exactly, but I think if they pick the "closest date" it might be a lot better.
  • Bill MartzBill Martz Member ✭✭
    edited September 4
    [removed]

    You are right, QPW, closest date. 
  • SherlockSherlock SuperUser ✭✭✭✭✭
    edited September 4
    In my opinion, when the amount and payee match, the oldest downloaded transaction should match the oldest available entered transaction but we should have the ability to indicate the entered transaction is not available to be matched.  [removed]
    Quicken user since 1997 
    Premier on Windows 10 
  • QPWQPW Member ✭✭✭✭
    edited October 2018
    BTW for what it is worth the payee can only be used as a "hint".  Since you can put in any payee you like when manually entering the transaction there is no guarantee it is "the same" as the one downloaded.  Quicken mostly matches by the amounts.  As such downloading frequently might help.

    Personally I download everyday and I seldom have transactions that have the same amount, so I don't running into this kind of problem very frequently.

    Totally agree that there should be a way to tell Quicken to not match certain transactions, but if this is done all in the same download and all of the transactions are "active" then that wouldn't help in that case.
  • Bill MartzBill Martz Member ✭✭
    edited October 2018
    In my case, the original transaction is entered using a reminder. After name substitution on download, the names on the transactions in the downloaded list match exactly, at least it appears that way. Maybe it is not within the mechanics of Quicken. The fact that Quicken consistently mismatches the transactions in the same way indicates to me that it is in the programming. It seems to match exactly backward to what would be desired.
  • QPWQPW Member ✭✭✭✭
    edited September 2018

    In my case, the original transaction is entered using a reminder. After name substitution on download, the names on the transactions in the downloaded list match exactly, at least it appears that way. Maybe it is not within the mechanics of Quicken. The fact that Quicken consistently mismatches the transactions in the same way indicates to me that it is in the programming. It seems to match exactly backward to what would be desired.

    Let me be clear.  I said it is used as a "hint".  As in it is used, but isn't "100%" relied on.

    As Quicken will match transactions even if the payee is completely different.

    As for the matching of the older transactions first.  That is definitely programmed into Quicken.  And as Sherlock pointed out, something that a lot of people would desire.

    So there isn't a "clear winner" if "oldest" or "closest" should "win".

    But I have had some pretty ridiculous matches in the past.
    Like it trying to match a transaction in 2000 when there is a transaction with the exact date, payee, and amount in the register.

    I do notice though in the recent versions of Quicken that it has some kind of "window" maybe about 2 months, so that it doesn't match really old transactions any more.
  • Bill MartzBill Martz Member ✭✭
    edited September 2018

    In my case, the original transaction is entered using a reminder. After name substitution on download, the names on the transactions in the downloaded list match exactly, at least it appears that way. Maybe it is not within the mechanics of Quicken. The fact that Quicken consistently mismatches the transactions in the same way indicates to me that it is in the programming. It seems to match exactly backward to what would be desired.

    If I have two downloaded transactions, one a week newer than the other, it matches the newest transaction to the oldest entered one and vice-versa. 
  • QPWQPW Member ✭✭✭✭
    edited September 2018

    In my case, the original transaction is entered using a reminder. After name substitution on download, the names on the transactions in the downloaded list match exactly, at least it appears that way. Maybe it is not within the mechanics of Quicken. The fact that Quicken consistently mismatches the transactions in the same way indicates to me that it is in the programming. It seems to match exactly backward to what would be desired.

    Yeah That sounds "familiar".  And frankly if both transactions are in the download, then I certainly consider it a bug that it matches newer to older, and older to newer.

    EDIT:

    Note that the developers might not consider it a bug, because it was "designed" that way, and as such this would be a feature request, but AS A USER, I certainly consider it a bug.
  • smayer97smayer97 SuperUser ✭✭✭✭✭
    edited September 2018

    In my case, the original transaction is entered using a reminder. After name substitution on download, the names on the transactions in the downloaded list match exactly, at least it appears that way. Maybe it is not within the mechanics of Quicken. The fact that Quicken consistently mismatches the transactions in the same way indicates to me that it is in the programming. It seems to match exactly backward to what would be desired.

    BTW, I still experience this kind of reverse matching in QM2007. So this is nothing new. And the window thing I have seen many times also....sometimes it appears a window is being applied then other times no, matching really old transactions. 

    Unfortunately, it is just a black box and Quicken is just revealing the inner workings. But I do not think there is anything new going on, IMHO.

    If you find this reply helpful, please be sure to click "Like", so others will know, thanks.

    (Canadian  user since '92, STILL using QM2007)

    Have Questions? Check out these FAQs:
  • PerryPerry Member
    edited January 10
    Updated to to R15.16 - Today.   i was once again disappointed that the Manual Match Transaction List issue was not fixed.  

    Quicken please give us the option to filter out transactions which have been previously reconciled and or cleared from appearing in this window.    Thank you 
  • edited January 8
    Is there any update to this request?
  • JellieJellie Member
    edited January 10
    Perry said:

    Updated to to R15.16 - Today.   i was once again disappointed that the Manual Match Transaction List issue was not fixed.  

    Quicken please give us the option to filter out transactions which have been previously reconciled and or cleared from appearing in this window.    Thank you 

    Agree! This is annoying that previously reconciled transactions show up in the manual match window.  Also, I don't like when Quicken matches new transactions to a reconciled registry item that has nothing in common with the downloaded item - not the same amount, not the same date, not the same payee.  Nothing matches, but Quicken pairs it.
  • JediSQLJediSQL Member
    I have a checking account that I use only for scheduled transactions, so I don't need to download transactions and reconcile on a regular basis. When I get around to downloading transactions, there can be more than a dozen, e.g., $15.01 weekly transfers to my savings account. The primary matching matches only on the amount without looking at the date, so they are all mismatched. Thus, I need to go into manual matching to get them properly matched. However, in the "Manually Match Transactions" dialog box, it shows all unmatched transactions, not just the ones that match on amount. So, I have to do a lot of scrolling (on a very sensitive scroll bar) to find the correct date/amount. My satisfaction with the usage of Quicken would be greatly improved by one or both of these suggestions:
    1) When Quicken first downloads transactions and attempts matching to my Quicken register, it should note if there are multiple transactions for the same amount and factor in the dates when trying to make matches. The dates can be off a few days (you know how banks love to "float" our money), but it should be able to at least put them in the correct order.
    2) In the "Manually Match Transactions" dialog box, it would be helpful to have a checkbox something like "Show only register transactions with matching amount." That would save me a lot of scrolling.

Sign In or Register to comment.