Regex support
under review
Log In
J
Jeremy Elbourn
I would also love some more power in rule matching. Even something as simple as specifying multiple "contains" clauses would be nice, but regex would be perfect.
An example is that my payroll comes in as something like:
"Deposit Ach company_name, -Osv Type: Payroll789 Id: 1234567 Co: company_name, -Osv"
I want to be able to create a rule that matches on "company_name"
and
"payroll" (since I also receive e.g. reimbursement payments for travel, which I categorize differently).W
Willy Robertus Leonardo
This would be great
A
Anderson Imes
Another discord thread that details the context. Virtually every one of the transactions I do is with Google Pay and the payee comes in as hot garbage that I have to parse with my meat fingers or create a rule for every single one. It makes me sad. https://discord.com/channels/842337014556262411/1323202082605367388
M
Michael Bianco
Some more context (https://discord.com/channels/842337014556262411/1134593641776685178/1302629515654070312) about why this would be useful.
Jen from Lunch Money
Merged in a post:
Custom text "cleaning" rules
D
Daniel Coolidge
Is there a way to make a rule that cleans a transaction name dynamically? Every single one of my credit card transactions leads with "Credit Card Ln Adv" before the payee info (thanks bank :disappointed: ) and i'd like to auto remove that for every txn regardless of payee.
Ideally, this could be triggered as a top priority rule then the cleaned name if fed through my normal categorization rules
H
Holly & Helios
While I support and advocate for the need to be able to apply rules based on patterns, I'm concerned that asking non-technical users to write RegEx may be too cumbersome to make the feature useful for them. Could we consider overlaying a more user-friendly interface that can translate what needs done into RegEx behind-the-scenes? Maybe an AI tool to generate? Just thinking out loud...
Michael Menanno
Holly & Helios: I feel like some features are meant for power users, regex is likely one of them. That being said if regex was supported you could totally give chatgpt or similar tools some string examples and tell it to generate regex that would match them
Jen from Lunch Money
marked this post as
under review
Jen from Lunch Money
Merged in a post:
Support operators like AND, OR, NOT in rules
Jen from Lunch Money
Tangential to regex in rules (which can be a power user feature)
B
Bjørn Stabell
Allow regexp named groups to be used as properties to set other properties - e.g.,
ACH Paypal to <recipient> <extra>
when matched would make
recipient
and extra
available for "then" clauses to use to set fields, e.g.,Tag = "paypal"
Payee = <recipient>
Notes += <extra>
N
Nolan
I would love to be able to use regex for this purpose as well!
Jen from Lunch Money
Merged in a post:
Create rules matching multiple payee names
J
Jonathan Samines
My bank for whatever reason can create the same transaction (say an ATM withdrawal) with several distinct names, depending of how the transaction was processed. Right now I clasify those transactions using multiple rules, but over times it gets hard to keep track of them. It would be awesome to get either:
- A way to create "rules groups", the same way categories groups can be created
or
- Allow a single rule to match several possible payee names or of any other criteria
Load More
→