Add exclusion criteria to Transaction Rules (edited)

Options
Chris.Landry8011
edited June 19 in Feature Requests

Forgive me if this suggestion exists, I ran a few searches and didn't see anything like this.

Currently there are only 2 options for Rule filters: Contains, and Is Exactly. I really need to have at least one negative, except, or exclude option so that a rule can be created to match some specific criteria and ignore entries that match the negative criteria.

For instance, I purchase things on Amazon, and I subsrcibe to Audible, which is owned by Amazon. So, the Audible transactions all include the word "Amazon" and the word "Audible", but Amazon purchases can be as little as the last 4 of the credit card and "Amazon.com".

With the current rules, I can either make a rule to match every transaction that has "Amazon", or I can make a rule for the Audible transactions, but not both. To do that, I need an exception option.

For example, this is how I would solve the problem described above:
Rule 1: Match transactions that contain "Amazon", exclude entries that contain "Audible"
Rule 2: Match transactions that contain "Audible".

3 votes

Active · Last Updated

Comments

  • DryHeat
    DryHeat Superuser ✭✭✭✭

    @Chris.Landry8011

    I have had the same problem and I hope some general solution is found for it.

    But there may be another way this could be handled. Simplifi could allow users to specify the order in which Rules are applied. If that were possible (and assuming the first matching rule controls), your Amazon/Audible issue could be handled like this:

    • Rule 1: Match transactions that contain "Audible".
    • Rule 2: Match transactions that contain "Amazon".

    Your Audible transaction would match Rule 1 and be modified by that rule. Non-Audible Amazon transactions would "fall through" to Rule 2 and be matched and modified by it.

    @geekcred is doing some tests to see if rules are actually being applied in the order they appear in the Rules list (see discussion below). If they are, you could solve your immediate problem by adding Rule 2 first, then adding Rule 1 (so Rule 1 will be at the top of the list). That might be worth a try.

    I suggested that users be able to manually change the order of Rule application:

    DryHeat
    -Quicken (1990-2020)
    -Countabout (2021-2024)