Transaction Rule to trim template text from Payee Names (edited)

randy-sk
randy-sk Member ✭
edited December 2025 in Feature Requests

Hello,

A common case for receiving payee names includes a prefix which affects the ingestion. For example, "Purchase Non Pin Walmart" and "Purchase Non Pin Starbucks". There is a need to be able to configure a rule where if the exact text provided is found to trim it. To provide the best functionality, I would recommend a replacement versus trim. This would allow the user to perform either a trim if the replacement text is blank, or a specific text if there is a benefit to the user.

If {text} in original, then replace {text} with {replacement-text}

supporting {replacement-text} being blank, and of course blank space trimming either end after replacement.

Tagged:
5
Up Down
5 votes

Active · Last Updated

Comments

  • DryHeat
    DryHeat Superuser ✭✭✭✭✭

    Great idea!

    It would be nice if the replacement system could use typical wildcards, like ? for a single character and * for any number of characters. There are more complex schemes that would be helpful, but this should be the minimum.

    DryHeat
    -Quicken Classic (1990-2020), CountAbout (2021-2024), Simplifi (2025-…)

  • AndyM! AndyM!
    AndyM! AndyM! Member ✭

    A further refinement of this idea: if the payee contains xyz paid blob, just remove xyz paid.

    A practical example: many transactions for Venmo show up as "Andrew Mason Paid Sarah Risser Augustus Ii" which makes it hard to turn these into meaningful Payees for sorting and reporting. Can we add a step where if the payee contains "Andrew Mason Paid", remove it (i.e. trim left), leaving only the remainder: Sarah Risser Augustus Ii ??

Categories