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

& symbol in statement name appears to cause rule to not work

dividebylife

I have some transactions from a place called Beverages & More, which is imported from the statement with a token of "beverages&more". I've created rules to automatically update the name and category, but they aren't applied.

On the next transaction that comes through, I try to create to another rule, and it tells me that the new rule conflicts with an existing rule… but new transactions from the same vendor do not get the rule applied.

Find more posts tagged with

Transaction Rules

Comments

DryHeat

Check out this thread about "AT&T" and see if anything in it helps you.

The OP had a problem with the "&" but was able to find a way around it.

https://community.simplifimoney.com/discussion/11752/cant-get-rules-to-work-new-to-simplifi

dividebylife

https://community.simplifimoney.com/discussion/comment/50109#Comment_50109

In my case, the rule was created directly from the transaction itself, so the problem isn't capitalization differences or missing/addition of ampersand or spaces.

DryHeat

@dividebylife "so the problem isn't capitalization differences or missing/addition of ampersand or spaces."

The solution in the thread I linked (about "At&t" problem) did not involve those issues. It was based on:

matching the statement name,
not including the "&" in the matching process, and
using the "Contains" operator.

As @barncrow put it, "the original/raw payee name is "ATT*BILL PAYMENT DALLAS TX", and "Contains" "att*bill" did the trick."

You will probably have to create a rule manually in the Rules section of Settings.

I don't know what the statement or Simplifi names are in your case, so I can't tell you what rule to create. But I suggest you delete any related current rules (that aren't working anyway) and try to manually create a "Contains" rule that uses only the non-"&" text from whichever name doesn't run afoul of "&" problems.**

**This may not work for you if you cannot find words in the selected name that don't contain, start, or end with an "&".