Payees - wildcards, grouping seem impossible (direly needed)

AchaarLonache
AchaarLonache Member ✭✭

I am evaluating Simplifi and want to confirm something.

There are a number of payees that most people deal with (especially when it comes to automated transfers that happen on a regular basis). The payees come up, as "Payee Somebodyorother XX890a70" where the characters at the end may change every time the automated transfer occurs.

Happens a lot with investment houses. Seems to happen a lot for people making regular crypto investments.

Anyway, it looks to me (and I just want to confirm this) that Simplifi actually lacks a way to group these payees under one rubric - under a single rule. You literally are making rules for every single variant payee name, for every new set of characters at the end (as in XX890a70 above).

Seems insane to me.

Question: Am I understanding the capabilities of the system correctly?? Or is this on me - because I don't understand how to use the product?

Tagged:

Comments

  • Seems like the only workaround is to create a renaming rule. This does what I want, but is unintuitive.

  • Philk
    Philk Member ✭✭✭

    -Phil-

    Former Quicken Desktop user 1984 -2023. Currently Testing Simplifi as its replacement.

  • I think you're right, @Philk, seems that renaming is the only way to handle a pattern match. You have to rename anything that contains a particular set of keywords (which itself is very dumb - no pattern matching there, either). Then you can create a series based on the renamed string.

    Kind of klunky and indirect - and clicky.

    But it works.

  • Philk
    Philk Member ✭✭✭

    @AchaarLonache I'm glad that information helped.

    You lost me with the statement of no pattern matching, My example below is a pattern of keywords, so I don't agree that it doesn't do pattern matching.

    I have on credit card that the payee comes in as: 2023-11-30: Payment - Thank You In

    This rule above worked for me for 4 other transactions.

    I'm curious to understand your issue as you do. Maybe talking it out in greater detail will help, maybe someone knows a less klunky workaround.

    -Phil-

    Former Quicken Desktop user 1984 -2023. Currently Testing Simplifi as its replacement.

  • My concern is that there's only one, fairly naive, way to pattern match, and that's with a sequence of strings that occur in the order specified.

    Renaming things is a complex affair and merits a reasonably powerful pattern matching language. Sure, maybe not all users should be using it, but it should be available. Regular expressions would make a lot of sense here. No need to reinvent the wheel. It would be an "advanced" thing.

  • UrsulaA
    UrsulaA Superuser ✭✭✭✭

    Check out this idea, it looks like it fits your request. Vote for it there.

    Simplifi User Since Nov 2023

    Minter 2014-2023

    Questionable Excel before 2014 to present

  • AchaarLonache
    AchaarLonache Member ✭✭

    Thank you! Heading off to upvote!

This discussion has been closed.