"Matching" transaction no longer match existing entries

Jeff Kantner
Jeff Kantner Member ✭✭✭
edited 4:32PM in Download, Add/Update Accounts (Windows)

Q Classic-Windows. I record credit transaction as they occur, then download weekly to confirm I didn't miss or mis-enter something. For decades, the downloaded transactions matched as long as Payee and Amount were identical, and date "close". No longer. Now the download reads "match" but is enter as a new transaction when accepted; the download copy is 'cleared', original is not. Example att'd. Not matched: Category, Tag, Memo, Downloaded ID. Hasn't mattered before. How would credit agency know how the Category/Tag/Memo I used? How would I know the Download ID in advance? I first noticed this is in the last week or two. Is there now a way to configure Q which fields to consider when matching download vs. existing transactions?

image.png
Tagged:

Answers

  • NotACPA
    NotACPA Quicken Windows Subscription SuperUser ✭✭✭✭✭

    Making sure I understand. The lower 2 txn were manually input, and the top 2 were downloads. Correct?

    And I also input card txn when they happen … and I've not encountered your issue.

    SO, a bit more info is needed. What Q product are you running and what RELEASE of that product? This info is at HELP, About Quicken.

    Also, in the downloaded txn, the Memo field seems to be WAY too specific to have downloaded. Did you add that after the download?

    And Category and Memo don't impact the match, because neither your bank, not Intuit (who provides the download function for Q) can know/provide those.

    Q user since February, 1990. DOS Version 4
    Now running Quicken Windows Subscription, Business & Personal
    Retired "Certified Information Systems Auditor" & Bank Audit VP

  • Jeff Kantner
    Jeff Kantner Member ✭✭✭

    Quicken (Windows) Classic Premier, v R66.18, build 27.1.66.18
    Yes, should've mentioned: I sorted newest to top so I could get the transactions in question closer to the column labels for the screen-scrape.
    The transactions with more detail are those I entered manually (on the date shown). The transactions showing nothing but Payee, Date, amount, and Downloaded ID are those downloaded today. They showed "Match" in the register before I accept them (never auto-accept on download); when I accepted these they turned into new entries, as shown - matching Date, Payee, Amount. This is new behavior.
    (I hadn't heard of Downloaded ID - never display it - until today when I began to investigate why the downloads are misbehaving now.) Lemme know more questions.

  • Jeff Kantner
    Jeff Kantner Member ✭✭✭

    PS: should also mention, recently upgraded (over the top of W10) to Windows 11. That ended up breaking existing Q install (wouldn't load), so I uninstalled Q and reinstalled Q fresh (to same version, afaik), which did fix the load failure issue). Dunno if that's related to the matching issue at hand.

  • AgBrewer97
    AgBrewer97 Member ✭✭✭✭

    I see this as well. Using the latest version of W11 Quicken (R66.23) but I think this happened about a week ago with an earlier recent update.

    To reiterate, I see the same thing as OP. I manually input transactions AS I INCUR THEM. Then I do daily downloads (OSU) and normally about 2-3 days later, the would download and most would match properly based on payee, amt, and date. Now as @Jeff Kantner says, it creates a new entry, and not even one that shows as "unmatched", but one that shows up as a new, cleared entry. Whatever you did, it changed the near seamless auto matching AND seems to make new entries, NOT just show them as unmatched downloads. Please revert to the previous way.

  • jaws2
    jaws2 Member ✭✭✭✭

    I have been having the same problem as well for several weeks, maybe longer

    W11 Quicken (R66.23)

  • Dave493
    Dave493 Member ✭✭✭

    Same here

  • mrzookie
    mrzookie Member ✭✭✭✭
    edited March 12

    I oftentimes enter checking account transactions manually to keep things in synch or to enter splits etc. When the transactions download from BofA, they match to the manual entries. It's worked this way for years, but it's stopped. The downloaded transactions are in the register as well as the manual entries. The problem seems to have started 2-3 weeks ago when I updated from BofA - Quicken to the new BofA connection method, although I'm not 100% sure.

    Anyone else seeing this?

  • Loribeth Clark
    Loribeth Clark Member ✭✭

    I am having the same problem. I am still using W10 Pro. This started happening right after the lastest Quicken upgrade Version R66.23 HF3 (Mar. 2026). Quicken Classic.

  • RalphC
    RalphC Quicken Windows Subscription Member ✭✭✭✭

    I think you're confusing the Quicken software by using the Reference field for a credit card charge. A credit card charge would not be entered as an EFT (Electronic File Transfer). And, I'm not sure what MCC is. I enter my charges like you do and wait for them to match with subsequent transaction downloads as a confirmation. I don't use or display the Reference field in my credit card registers.

  • Sisyphus1967
    Sisyphus1967 Member ✭✭✭

    I'm on R66.23 on Windows 11 using Quicken Premier and I am experiencing the same issue. Started within the last two weeks for me.

  • Quicken Kristina
    Quicken Kristina Quicken Windows Subscription Moderator mod

    Hello All,

    Thank you for letting us know you're encountering this issue. To clarify, is the issue you're seeing the same as the issue discussed in this earlier thread:

    https://community.quicken.com/discussion/7971677/quicken-one-step-update-is-duplicating-transactions-version-r66-18-build-27-1-66-18

    I look forward to your replies!

    Quicken Kristina

    Make sure to sign up for the email digest to see a round up of your top posts.

  • mrzookie
    mrzookie Member ✭✭✭✭
    https://community.quicken.com/discussion/comment/20543135#Comment_20543135

    @Quicken Kristina

    What you've quoted sounds very similar to, but is not the exact same flavor of the issue I'm seeing. The OP, @jtomalley, said they see the problem when they enter transactions via the Calendar but when they enter transactions manually, they match fine. I never enter transactions via the calendar although I DO enter them via the Bill and Income Reminder list. Perhaps both methods are using the same code and that's wherein the problem lies?

    Note that I am only seeing this with my Bank of America checking account. All credit cards and brokerage accounts are (as of now) matching as they should be, but come to think of it, in none of those cases do I enter manual transactions via the Bills & Income Reminders list. I have a transaction that should download tomorrow. I'm going to key it in rather than enter it from the list. I will let you know what happens.

    I suspect the Bill & Income Reminders list/Calendar is the place to look for the source of the problem.

    FTR - I'm running R66.18, Build 27.1.66.18 on WIN 11 (fully updated)

Categories