I have made PocketSense scrubbers, and currently have some, with Fidelity being one FI that benefits. At some point I may get inspired to add payee consolidation to the incoming processing. I am throwing out thoughts, and I hope to get comments about what would be a good mix of easy-to-set-up and utility.
1. Simple for user setup. File of lines that have the starting points.
Aldi
Best Buy
Amazon M* (various forms that mean marketplace -- MKTPL MARK marketplace )
Amazon RET* (returns)
AmazonStores
AmznMktp
Amzn Mktp (already I can see that this and AmznMktp should combine)
Amazon* (those that did not match earlier string, would also match
amazon.com)
Amoco Oil
Costco
eBay
Interest Paid
Marathon
Membership Fee
Mobil Oil
Paypal
Sams club
Samsclub
Southwes*
State FARM
THE HOME DEPOT
TRANSFER FROM CHECKING
TRANSFER TO CHECKING
USPS
WALL MART
WALL-MART
WALLMART
WM SUPERCENTER
For "Walmart" for example, the search string would actually have a space appended. With the asterisk, that would not need an immediate space.
All matches would be not case-sensitive
1A... replacement string could have a suffix word such as combined or group, or replacement string could be the entry with no trailing space.
2. Full regex-- list has pairs... match string, and result. Very hard for user setup, but powerful for those proficient in Regex.
3. Hybrid: treat as 1 or 1A unless the lines match a different pattern that triggers parsing as regex. This could added later.
My current thought is to start with 1 or 1A, and expand if it turns out there is a significant unmet need.
So throwing out ideas for discussion.
A. Separate list per account, or global? All credit cards would logically share the same list, but the cash transactions for bank accounts and broker accounts also?
B. I can see appending the incoming payee string into the Memo.
C. This is only for new transactions.