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; } } }

AT&T renaming rule problem

Mike Harris

I tried to get help with this previously, but it's still not working. I only get a new bill every 6 months, so it's difficult to troubleshoot.

Problem: Downloaded transaction "ATT* BILL PAYMENT 800-331-0500 TX" does not match renaming rule: "If payee contains 'Att' rename to AT&T".

https://community.quicken.com/discussion/7960955/unable-to-add-att-and-att-to-same-renaming-rule

Find more posts tagged with

Windows

download transactions

Comments

Jim_Harman

I reviewed my comments from your previous post and I don't know why your rule is not working.

It appears that the downloaded Payee name starts with Att* Bill Payment, with a space after the *. Have you tried If payee contains Att*

Per my earlier analysis that should be the same as "If payee contains Att" but there have been changes to the renaming rules dialogs so maybe something has changed about the way the rules are interpreted.

Rocket J Squirrel

This is just a guess. It appears that QWin thinks it has already renamed the payee from upper case to mixed case. Perhaps this is superseding your actual renaming rule.

There are various setting scattered through Preferences which might affect this, such as

Capitalize payees & categories
Capitalize first letter only in downloaded payee names

Maybe playing with those might help. As I said, just a guess.

Mike Harris

https://community.quicken.com/discussion/comment/20507929#Comment_20507929

The mixed case is because I have checked the box for "Capitalize first letter only in downloaded payee names". It doesn't seem to negatively affect any other rules, though I have always suspected it could cause problems.

Mike Harris

https://community.quicken.com/discussion/comment/20507918#Comment_20507918

Looking through my previous post, I did verify that just "att" matched everything with a hand-crafted QFX file, but it's not working with my credit card download using Express Web Connect+. I've tried just "att*" in the past, and it didn't match all of the ones that it should - like in the example QFX file. However, I just created a new rule to match "att*" to see if that works. Before, I was trying to use the same rule with two matches, and it won't allow both att and att*, as it just ignores the last one added.

Rocket J Squirrel

I find it RIDICULOUS that there is no wildcard or substring matching capability

Try these:

https://community.quicken.com/api/v2/media/download-by-url?url=https%3A%2F%2Fus.v-cdn.net%2F6031128%2Fuploads%2FLOHUAH989E8Z%2Fquickenmatchcharacters.pdf