mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 07:04:23 -05:00
[Bug]: Filtering By Payee Contains/Matches/Does Not Contain Only Allows Selection of Registered Payees #2448
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#2448
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cculbertson81 on GitHub (Sep 4, 2025).
Verified issue does not already exist?
What happened?
When attempting to filter transactions by Payee using the Contains, Matches, or Does Not Contain criteria, the Suggested Payees selection is shown, rather than allowing free-text input. This occurs when filtering in the All Transactions view, individual account view, and Reports.
How can we reproduce the issue?
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Chrome
Operating System
Windows 11
@youngcw commented on GitHub (Sep 5, 2025):
To be honest, the payee filter probably shouldn't have any of those 3 options with how the payees are currently handled. In the rules, the payee only can be searched by is/is not filters. I would think that the filter and the rules options should match.
@cculbertson81 commented on GitHub (Sep 6, 2025):
I respectfully disagree. I find it extremely useful to be able to do partial matching on payees when making bulk updates, especially in the context of importing transaction history. It essentially provides a more powerful way to search for and merge/rename payees.
If keeping filter options consistent between transactions and rules is the goal, I'd be open to moving the ability to filter by regular expression to the Payees page, but I'd consider it a pain point if the ability went away altogether.
@JamesMHenderson commented on GitHub (Oct 6, 2025):
I've come across this issue when trying to create a report, I have a naming convention for payees so filtering on contains or matches will be extremely useful.
@YagiOoda commented on GitHub (Nov 7, 2025):
It would be great if this could be returned. It used to work this way since I still have some filters that still use "contains" with a key word.
An example would be if I am making a report for income. Instead of having to manually go in and select the payee for paycheck across all jobs across the years, I can just make a contains filter with the key word "Paycheck". Then, it will automatically update without having to manually add in all the past payees or have to update everything if a job is switched.
@xWorldSerpent commented on GitHub (Nov 16, 2025):
I noticed multi-select is no longer populating when creating an "imported payee" Rule using the condition types "one of" or "not one of". Could this be a related bug? I still have a couple of older rules working with that configuration, but I only recent attempted to create a new rule and discovered the issue. I believe my older working rules were created prior to the September release.
@embermann commented on GitHub (Dec 25, 2025):
I agree that this is useful. I would like to see contains/not contains for payee also when creating rules. Because i have a lot of companies in my country that use a bit different names for their bank accounts for every retail shop or service provider. For example:
Also my bank have very limited options for data export about my transactions, so it would be nice if this app could have a bit more customization.
@MikesGlitch commented on GitHub (Jan 10, 2026):
Closed by #6594, will be in the next release