Memo field Downloading Payee Info [Edited]

TDooley
TDooley Member ✭✭
The "Memo" field duplicates the "Payee" field on account updates with the new / updated Chase connection. Did anybody else notice this?

Best Answers

  • Quicken Anja
    Quicken Anja Moderator mod
    edited August 2022 Answer ✓
    Hello @TDooley & @Dan Miller,

    Thank you both for taking the time to visit the Community and report this issue, though I apologize that you are experiencing this.

    While you both are reporting different financial institutions, I went ahead and merged your threads together as I was able to replicate this issue in my own Quicken (with Key Bank).

    Since I was able to replicate the issue, I will also go ahead and submit a bug report for this to our Development and Product teams for further investigation and resolution.

    Unfortunately, we won't have an ETA on this. However, once a solution is created it will be made available as part of a future update release.

    Thank you for your patience and for bringing awareness to this issue!
    (CTP-4193)

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

  • Boatnmaniac
    Boatnmaniac SuperUser ✭✭✭✭✭
    edited August 2022 Answer ✓
    Until this issue gets resolved you might want to consider checking the box for "Don't update memo when downloading" on the Online Services tab of Account Details.  Perhaps that will stop the payee from being entered into the memo field.

    (Quicken Classic Premier Subscription: R54.16 on Windows 11)

  • Dan Miller
    Dan Miller Member ✭✭✭
    Answer ✓
    Thanks Anja for your prompt response and all of your help. Have a great day.

    Also thanks to boatnmaniac for your recommendation.

    Dan

Answers

  • Dan Miller
    Dan Miller Member ✭✭✭
    Yesterday One step Update started showing the Payeen Name in the Memo field of the register. Why is this happening? Is it an issue with the latest update R42.21?
    Thank you,
    Dan
  • Quicken Anja
    Quicken Anja Moderator mod
    Hello @Dan Miller,

    Thank you for reaching out to the Community and telling us about your issue, though I apologize that you are experiencing this.

    Which financial institution are you experiencing this issue with, or are you experiencing this with downloading from multiple financial institutions?

    Check back and let us know! Thank you.

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

  • Dan Miller
    Dan Miller Member ✭✭✭
    Hi Anja,
    It's happening with Capital One banking and all my credit cards
    Dan
  • Quicken Anja
    Quicken Anja Moderator mod
    edited August 2022 Answer ✓
    Hello @TDooley & @Dan Miller,

    Thank you both for taking the time to visit the Community and report this issue, though I apologize that you are experiencing this.

    While you both are reporting different financial institutions, I went ahead and merged your threads together as I was able to replicate this issue in my own Quicken (with Key Bank).

    Since I was able to replicate the issue, I will also go ahead and submit a bug report for this to our Development and Product teams for further investigation and resolution.

    Unfortunately, we won't have an ETA on this. However, once a solution is created it will be made available as part of a future update release.

    Thank you for your patience and for bringing awareness to this issue!
    (CTP-4193)

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

  • Boatnmaniac
    Boatnmaniac SuperUser ✭✭✭✭✭
    edited August 2022 Answer ✓
    Until this issue gets resolved you might want to consider checking the box for "Don't update memo when downloading" on the Online Services tab of Account Details.  Perhaps that will stop the payee from being entered into the memo field.

    (Quicken Classic Premier Subscription: R54.16 on Windows 11)

  • TDooley
    TDooley Member ✭✭
    Thanks for the tip
  • Dan Miller
    Dan Miller Member ✭✭✭
    Answer ✓
    Thanks Anja for your prompt response and all of your help. Have a great day.

    Also thanks to boatnmaniac for your recommendation.

    Dan
  • gambit.xmn
    gambit.xmn Member ✭✭
    "Until this issue gets resolved you might want to consider checking the box for "Don't update memo when downloading" on the Online Services tab of Account Details. Perhaps that will stop the payee from being entered into the memo field." -- Boatnmaniac

    Negative. This does not work. To be clear - duplication happens on various accounts from various banks.
  • Chris_QPW
    Chris_QPW Member ✭✭✭✭
    In my test file for this, this is what happened.
    The memo isn't coming from the download!

    Signature:
    This is my website: http://www.quicknperlwiz.com/
  • John Patriarca
    John Patriarca Member ✭✭✭
    Just sent to "Report a Problem": Recently, downloaded transactions from bank/credit card accounts have the Payee duplicated in the Memo field. The transactions are shown as "Nike / Nike" after download and then Nike is shown in the Payee and Memo Fields. I don't need/want duplication. I've been using Q for over 30 years, never seen this. In addition, 1 of the the recent updates mentioned an improved matching system for downloaded transactions. Not working, in fact it is worse. These issues persist across the 5 separate Q accounts I manage.
  • ameat
    ameat Member ✭✭
    edited September 2022
    As someone above said, it has nothing to do with EWC, which is why the "Don't update memo when downloading" option setting makes no difference. I don't see the issue with any of my American Express card accounts, but do see it with Citi, Chase, and Ally Bank. It is some kind of information that is inserted via the cloud sync process, regardless of whether cloud sync is actually enabled. I tried using cloud sync once years ago and hated it because it kept automatically renaming payees and doing other things automatically even though I had all those options disabled. So I turned off cloud sync right away after that, and it has been off for years since then. Despite cloud sync being disabled, I see all kinds of transaction information being exchanged in the cloud sync log. Below are three transactions from the cloud sync log, where it is clear that the "memo" field is being populated with the "inferredPayee" field, even though I never wanted or asked Quicken to infer anything:

    {"id":"341322370488530433","createdAt":"2022-08-23T16:13:06Z","modifiedAt":"2022-08-23T16:13:06Z","source":"QCS_REFRESH","accountId":"339860922229426433","postedOn":"2022-08-19","payee":"VENTRA MOBILE CHICAGO IL","coa":{"type":"UNCATEGORIZED","id":"0"},"amount":-5.0000,"state":"CLEARED","matchState":"NOT_MATCHED","knownCategoryId":"1000500000","cpData":{"id":"77692351-22fe-11ed-bd87-dad3f8bce15a","postedOn":"2022-08-19","txnOn":"2022-08-19","payee":"VENTRA MOBILE CHICAGO IL","memo":"VENTRA MOBILE CHICAGO IL","amount":-5.0000,"inferredPayee":"VENTRA MOBILE CHICAGO IL","inferredCoa":{"type":"UNCATEGORIZED","id":"0"},"cpCategoryId":"1406"},"mlKnownCategoryId":1000500000,"mlInferredPayee":"ventra mobile chicago il","type":"CASH_FLOW"},{"id":"341322370365360385","createdAt":"2022-08-23T16:13:06Z","modifiedAt":"2022-08-23T16:13:06Z","source":"QCS_REFRESH_BANK_PENDING","accountId":"339860922262980865","postedOn":"2022-08-22","payee":"7-ELEVEN 33781 CHICAGO IL","coa":{"type":"UNCATEGORIZED","id":"0"},"amount":-2.0300,"state":"PENDING","matchState":"NOT_MATCHED","knownCategoryId":"2250600000","cpData":{"id":"QUICKEN0ff4b08d0ae666417ebef46395386a2768529df4d05bfb51f4d30e6b2a470e47","cpPendingId":"QUICKEN0ff4b08d0ae666417ebef46395386a2768529df4d05bfb51f4d30e6b2a470e47","postedOn":"2022-08-22","txnOn":"2022-08-22","payee":"7-ELEVEN 33781 CHICAGO IL","memo":"7-Eleven","amount":-2.0300,"inferredPayee":"7-Eleven","inferredCoa":{"type":"UNCATEGORIZED","id":"0"},"cpCategoryId":"706"},"mlKnownCategoryId":2250600000,"mlInferredPayee":"7-eleven","type":"CASH_FLOW"},{"id":"341322294888319491","createdAt":"2022-08-23T16:12:21Z","modifiedAt":"2022-08-23T16:12:21Z","source":"QCS_REFRESH","accountId":"339860921826773249","postedOn":"2022-08-23","payee":"POSHMARK INC Poshmark~ Future Amount: 35.2 ~ Tran: DDIR","coa":{"type":"UNCATEGORIZED","id":"0"},"amount":35.2000,"state":"CLEARED","matchState":"NOT_MATCHED","knownCategoryId":"5750000000","cpData":{"id":"AeINw7WQfRzXivysXBqAPCRBLNFIimrjN9WRmzsgHCg","postedOn":"2022-08-23","txnOn":"2022-08-23","payee":"POSHMARK INC Poshmark~ Future Amount: 35.2 ~ Tran: DDIR","memo":"Poshmark Poshmark Future","amount":35.2000,"inferredPayee":"Poshmark Poshmark Future","inferredCoa":{"type":"UNCATEGORIZED","id":"0"},"cpCategoryId":"30"},"mlKnownCategoryId":5750000000,"mlInferredPayee":"poshmark poshmark future","type":"CASH_FLOW"}
This discussion has been closed.