Payee names truncated in ledger
Payee names are not displaying correctly in the transaction ledger. Starting around Nov 17, most Payees are truncated to just one word. For example, "Trader Joe's" is listed as "Trader" and "Manhattan Pizza" is listed as "Pizza" (see screenshot). I would prefer not to create new payee rules for something that appears to be a bug. Can this be fixed retroactively?
Comments
-
I noticed the same thing yesterday. Whole Green Cafe was shortened to Cafe and CVS Pharmacy was shortened to Pharmacy. This behavior is new starting with version 4.35.0.
Simplifi User Since Nov 2023
Minter 2014-2023
Questionable Excel before 2014 to present
0 -
Thanks for chiming in, I'm glad it's not just me.
Also, it may be worth noting that sometimes the payee is missing the first word(s) as in your examples, other times it shows only the first word (see "Trader" in my post).
1 -
I haven't noticed this yet. Are these Payee names for ones that you haven't set up Renaming Rules for; they are just what Simplifi happens to download them as? Based on your original post, I'd assume that this isn't a case where Simplifi is actually ignoring your renaming rules altogether. Have you noticed the problem with any Payee with a Renaming Rule?
Unfortunately, I'm guessing that they wouldn't be able to fix it retroactively although you could easily…
- Filter for just "Pizza" transactions.
- Select the ones that are problems and select the Edit option.
- Change them to the correct Payee name.
Chris
Spreadsheet user since forever.
Quicken Desktop user since 2014.
Quicken Simplifi user since 2021.1 -
I saw something similar with my Comcast internet payment. Weirdly, it named the payee as 1. It did not get recognized as a recurring bill.
0 -
Good question about payee renaming rules. It looks like all occurrences of this problem are with payees that do not have renaming rules.
I appreciate your thoughts on how to easily fix; however most of the payees affected have only one transaction at this point so I would have to edit each one individually. If the problem is resolved quickly, that would be annoying but manageable. If it goes on for a while, your method would help with any payee that has multiple transactions.
I also realize that I could create renaming rules for all the payees affected but I'd rather the issue be fixed in the product.
0 -
I've noticed this bug, too. It has caused errors in linking recurring transactions to the wrong transaction. Hope it gets fixed soon.
0 -
I'm also seeing this bug, in some cases the payee has been truncated to a single letter.
0 -
I'm experiencing this issue as well. All sorts of transactions are being given bizarre payee names. One example is "REI.COM 800-426-4840 - 5490" showing up as simply "4".
0 -
I'm seeing the same behavior…
IN this example "Kindle Unltd 888-802-3080" becomes "888" for the Payee field. I've seen this in several transactions lately.
Danny
Simplifi user since 01/22
”Budget: a mathematical confirmation of your suspicions.” ~A.A. Latimer0 -
I'd be hesitant to start creating renaming rules before there is some response from one of our coaches about a resolution to this bug.
@Coach Jon or @Coach Natalie will be able to escalate this issue since it appears to be affecting a number of accounts.
Danny
Simplifi user since 01/22
”Budget: a mathematical confirmation of your suspicions.” ~A.A. Latimer1 -
I completely agree about not making any payee rules. That's what I was trying to say, sorry if I wasn't clear.
1 -
same issue for me since about Nov 17th payees are coming in as random names and numbers.
0 -
Funniest rename- Quicken Inc Simplifi MenloPark, CA subscription shows up as Park.. and gets categorized as home improvement..! Ha ha
0 -
FWIW, I'm also seeing this with Quickbooks (Intuit) downloads which makes look like the aggregation service may be the culprit.
0 -
I'm seeing the same bug. Several payees renamed to "1" or "2", etc., and improperly categorized.
0 -
+1 - i.e GRUBHUB is being renamed to Rub Hub and categorized as Doctor 🤣
1 -
Looks like we can have a separate thread to capture all the funny renames..!
0 -
This is the funniest rename now..! 😜😜
0 -
I just noticed this issue as well. It's really bad! I hope this change is reverted soon. It happens for regular transactions that have not been renamed.
Not only that but it has started auto-guessing the wrong category for simple things like Dunkin Donuts or Starbucks. Dunkin Donuts is now just Dunkin and it assigns it as Dining and Drinks instead of Coffee Shops. There was a transaction at my local diner, and it just had the payee name as D.
My Factor meals are now showing up as Payee 2.
This is not manageable and hopefully it changes back to the old way. I would really hate to have to find a new budgeting system since I finally have this all setup.
0 -
Hey everyone, thanks for making us aware of this issue!
It looks like the truncated or incorrect Payee Names have already been escalated internally. We have an Alert that you all can follow for updates:
We appreciate everyone's patience as we work to resolve this matter!
-Coach Natalie
-Coach Natalie
2 -
Thank you @Coach Natalie !
Since there is currently no ETA for a fix, do you know whether the fix will be retroactive? Or do you recommend we fix all transactions affected so far?
Thanks for your help!
0 -
@lindsayla18, absolutely — I'm glad we're already aware of and working on this!
As for the fix being retroactive, I'm not sure. As soon as we learn any new information, we'll be sure to post it to the Alert. However, in my experience, online banking fixes are usually only applied to transactions that take place after the fix. Regardless, I'd say that manually fixing them wouldn't be a bad idea just so you have correct data.
Thanks!
-Coach Natalie
-Coach Natalie
2 -
I am also having this issue. I chatted with support yesterday and they were not helpful. He said it was an issue in the way I had my Payee Rules setup, and it is definitely not that. I also have some transactions with payee updated as "1" or "2". Others are truncated to just a single word. None of these pertain to anything in my Payee rules, so it's definitely a backend Simplifi problem. Please get this fixed, this is a frustrating problem.
0 -
Please see @Coach Natalie’s post, above. This is clearly a widespread issue based on all the comments on this thread. Simplifi has acknowledged the problem and are taking steps to resolve the issue, although this may not have been communicated to support before you contacted them. I suggest you follow the Alert that Natalie shared with us, as that is how they plan to keep us informed.
0 -
I didn't see any misnamed payees this morning and then @Coach Natalie posted this…
[RESOLVED] 11/25/24: Multiple FI's - Payee Names Are Truncated or Incorrect — Simplifi
Danny
Simplifi user since 01/22
”Budget: a mathematical confirmation of your suspicions.” ~A.A. Latimer0 -
@Coach Natalie I'm glad this is fixed, but I hope there is some attention paid to the egregious testing slipup that allowed this very obvious bug to go through. I am going to have to spend a bunch of time laboriously fixing these transactions – since it's not apparent what the correct payee is, you have to go into the details for each one to even know what to change it to. This would be a pretty bad screwup even for free software, which this is not.
0 -
@Coach Natalie I'm still seeing some incomplete original descriptions. Maybe my remaining issues are still related to the post linked below (see my other examples and comments ~11/24 on this post)? I'm attaching one payee example. This shows that I was getting the full description during my initial import in late October, and these have since started truncating to one word.
I just had another thought as to what may be affecting this particular payee - I have a rule for this payee based on the Simplifi name. The "rename payee" is not changed with the rule, only the Category, but now I wonder if I removed this rule if I'd see the original tran description for this payee.
I don't have time today to look for other examples, but I will look for other examples soon and let you know if there is a correlation here. Or maybe there is already some other known issues related to my examples?
"Appears on your [...] statement as" Text Download Length — Simplifi
0
