github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-11-09 10:45:04 -06:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #5679] [Bug]: Filtering By Payee Contains/Matches/Does Not Contain Only Allows Selection of Registered Payees #9387

New Issue
Closed
opened 2026-04-10 19:39:43 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-10 19:39:43 -05:00
Owner
Copy Link
Copy Source

Originally created by @cculbertson81 on GitHub (Sep 4, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5679

Verified issue does not already exist?

  • I have searched and found no existing issue

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.

Image Image Image Image

How can we reproduce the issue?

  1. Go to any page that allows filtering.
  2. Add a filter for Payee, and choose the Contains, Matches, or Does Not Contain criteria.
  3. Attempt to add free text or regular expressions to the input text box.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 11

Originally created by @cculbertson81 on GitHub (Sep 4, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5679 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### 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. <img width="274" height="281" alt="Image" src="https://github.com/user-attachments/assets/eca871ff-cb0c-4f4e-9bbc-7a8208b13138" /> <img width="277" height="285" alt="Image" src="https://github.com/user-attachments/assets/1440dd17-a4b2-4838-a358-3b723854746c" /> <img width="281" height="265" alt="Image" src="https://github.com/user-attachments/assets/37e93649-9e15-4027-bc2c-338d03c795e5" /> <img width="1067" height="368" alt="Image" src="https://github.com/user-attachments/assets/f50a1122-ac17-40c4-a280-c3658c64192d" /> ### How can we reproduce the issue? 1. Go to any page that allows filtering. 2. Add a filter for Payee, and choose the Contains, Matches, or Does Not Contain criteria. 3. Attempt to add free text or regular expressions to the input text box. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 11
GiteaMirror added the bugtransactions✅ approved labels 2026-04-10 19:39:44 -05:00
GiteaMirror commented 2026-04-10 19:39:45 -05:00
Author
Owner
Copy Link
Copy Source

@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.

<!-- gh-comment-id:3258527987 --> @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.
GiteaMirror commented 2026-04-10 19:39:46 -05:00
Author
Owner
Copy Link
Copy Source

@cculbertson81 commented on GitHub (Sep 6, 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.

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.

<!-- gh-comment-id:3263231298 --> @cculbertson81 commented on GitHub (Sep 6, 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. 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.
GiteaMirror commented 2026-04-10 19:39:46 -05:00
Author
Owner
Copy Link
Copy Source

@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.

<!-- gh-comment-id:3374470427 --> @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.
GiteaMirror commented 2026-04-10 19:39:47 -05:00
Author
Owner
Copy Link
Copy Source

@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.

<!-- gh-comment-id:3501875746 --> @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.
GiteaMirror commented 2026-04-10 19:39:48 -05:00
Author
Owner
Copy Link
Copy Source

@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.

<!-- gh-comment-id:3538986946 --> @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.
GiteaMirror commented 2026-04-10 19:39:48 -05:00
Author
Owner
Copy Link
Copy Source

@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:

Bolt.Eu/C/1234567890 10134 Tallinn
Bolt.Eu/C/1212121212 10134 Tallinn
Bolt.Eu/C/1313131313 10134 Tallinn

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.

<!-- gh-comment-id:3691245925 --> @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: > Bolt.Eu/C/1234567890 10134 Tallinn > Bolt.Eu/C/1212121212 10134 Tallinn > Bolt.Eu/C/1313131313 10134 Tallinn 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.
GiteaMirror commented 2026-04-10 19:39:49 -05:00
Author
Owner
Copy Link
Copy Source

@MikesGlitch commented on GitHub (Jan 10, 2026):

Closed by #6594, will be in the next release

<!-- gh-comment-id:3732337664 --> @MikesGlitch commented on GitHub (Jan 10, 2026): Closed by #6594, will be in the next release
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No labels bug transactions ✅ approved
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#9387