nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Transactions matching to older transactions 100% of the time.

mfullmer

Just over the past 3 or 4 months my downloaded transactions always match to an older, sometimes much older, similar transaction. Looking at the criteria for matching I know that it first looks at the transaction id, if there is one, then date, payee, & amount. Well 100% of the time, it matches to items that are 2-6 weeks past, sometimes a totally different payee, always the same amount. I've already done the file validation and super validation several times. I'm on the latest update. I wouldn't know how far back to go for a backup. The criteria for matching just seems to be broken in the current (and recent) updates. Help!

Find more posts tagged with

Comments

UKR

When downloading new transactions from the bank, does a new supposedly matching transaction already exist in your register or has it yet to be recorded?

If there's a scheduled reminder waiting in the wings and already past due or becoming due in the next few days, it should have been recorded before downloading transactions.

Are you automatically accepting downloaded transactions into your registers?
I would try switching to manually reviewing and accepting each downloaded transaction, to ensure it correctly matches to the desired register transaction. If it doesn't, unmatch or match manually to achieve the desired result.

Chris_QPW

You are a bit mistaken by how the matching works in regard to the Downloaded ID.

Each time you download a transaction Quicken records the Downloaded ID in that register's list of Downloaded IDs.

When it downloads transactions, it checks that list, and if a transaction has the same Downloaded ID as one on the list, it will skip it. It will not be involved in matching or any other process that flows into the register.

So, basically it should be impossible to match an existing transaction that already has a Downloaded ID. If this is happening it suggests that there is a problem with the list of Downloaded IDs for that account. Running Validate and Repair might help.

Past that the actual matching really has very little to go on, and mostly matches on the amount. And from what I have seen it seems to pick the older transactions first if there is more than one transaction that has the same amount.

And people can get themselves into trouble if they start deleting transactions that "match" but are for the "wrong one", because the transaction in the register never gets matched with a downloaded one and therefore never gets a Downloaded ID.

mfullmer

https://community.quicken.com/discussion/comment/20446351#Comment_20446351

No, to all of your questions.

mfullmer

I was going off something I read, about the transaction ID. For what it's worth, I have no transactions with "Downloaded ID" in most of my accounts. I think one of AmEx credit cards brings it in. That is not the problem. Something has definitely changed. I've been paying my housekeeper the exact same amount, through Venmo, every two weeks for nearly 10 years and it only started matching past transactions in the past few months. I saw one answer that said to un connect the downloading accounts and reconnect. That did not help.