github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 03:32:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature] automatic rules for payees that embed variables #1820

New Issue
Closed
opened 2026-02-28 19:55:19 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 19:55:19 -06:00
Owner
Copy Link

Originally created by @porjo on GitHub (Feb 4, 2025).

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

I'm not sure if this is something unique to Australia, or just my bank but almost all my transactions have some variable embedded in the payee field. For example, the 'payee' field for my monthly bill to Apple looks like this

Apple.Com/Bill - Visa Purchase - Receipt 146315in Sydney Date 18 Jan 2025 Card xxxxxxxxxxxxxxxxxx

The receipt number & date changes each month. As a result, I have to manually categorise this as a bill each month as Actual doesn't detect that it's the same payee.

Describe your ideal solution to this problem

Could something like Levenshtein distance be implemented to determine that payees that share 90% of the same words are actually the same payee.

Teaching and learning

No response

Originally created by @porjo on GitHub (Feb 4, 2025). ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? I'm not sure if this is something unique to Australia, or just my bank but almost all my transactions have some variable embedded in the payee field. For example, the 'payee' field for my monthly bill to Apple looks like this ``` Apple.Com/Bill - Visa Purchase - Receipt 146315in Sydney Date 18 Jan 2025 Card xxxxxxxxxxxxxxxxxx ``` The receipt number & date changes each month. As a result, I have to manually categorise this as a bill each month as Actual doesn't detect that it's the same payee. ### Describe your ideal solution to this problem Could something like [Levenshtein distance](http://en.wikipedia.org/wiki/Levenshtein_distance) be implemented to determine that payees that share 90% of the same words are actually the same payee. ### Teaching and learning _No response_
GiteaMirror added the featureneeds votes labels 2026-02-28 19:55:19 -06:00
GiteaMirror commented 2026-02-28 19:55:20 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 4, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@github-actions[bot] commented on GitHub (Feb 4, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
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
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature needs votes
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#1820
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?