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

[Feature] Automatic contract identification #932

New Issue
Closed
opened 2026-02-28 19:25:36 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 19:25:36 -06:00
Owner
Copy Link

Originally created by @M123-dev on GitHub (Feb 17, 2024).

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?, would love to help, but that's a big one

Pitch: what problem are you trying to solve?

With many transactions, it is difficult to keep track of recurring contracts.
Phone, energy, car, gym membership, Netflix, you get the point

Describe your ideal solution to this problem

I'm currently using FinanzGuru, a German mobile app with a good overview of contracts. It scans all transactions and looks for patterns, same amount coming from or going to the same destination account, every month, quarter, or year and marks it as a contract.

The app uses this information to:

  1. display this in a separate tab (monthly fixed income compared to fixed expenses)
  2. track changes (Attention, "GYM xyz" has increased by 33%/month, is that right? - The "Montly income" is already 4 days late!)
  3. show predictions for the future (the network graph can be extended into the future, of course only considering the contracts)

In addition, category rules can be created automatically for all transactions from a contract

Teaching and learning

It must be ensured that incorrectly recognized contracts can be deleted and that unrecognized contracts can be marked manually.

Originally created by @M123-dev on GitHub (Feb 17, 2024). ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature?, would love to help, but that's a big one ### Pitch: what problem are you trying to solve? With many transactions, it is difficult to keep track of recurring contracts. Phone, energy, car, gym membership, Netflix, you get the point ### Describe your ideal solution to this problem I'm currently using FinanzGuru, a German mobile app with a good overview of contracts. It scans all transactions and looks for patterns, same amount coming from or going to the same destination account, every month, quarter, or year and marks it as a contract. The app uses this information to: 1. display this in a separate tab (monthly fixed income compared to fixed expenses) 2. track changes (Attention, "GYM xyz" has increased by 33%/month, is that right? - The "Montly income" is already 4 days late!) 3. show predictions for the future (the network graph can be extended into the future, of course only considering the contracts) In addition, category rules can be created automatically for all transactions from a contract ### Teaching and learning It must be ensured that incorrectly recognized contracts can be deleted and that unrecognized contracts can be marked manually.
GiteaMirror added the feature label 2026-02-28 19:25:36 -06:00
GiteaMirror commented 2026-02-28 19:25:37 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 17, 2024):

✨ 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 17, 2024): :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 -->
GiteaMirror commented 2026-02-28 19:25:37 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Feb 18, 2024):

This is partially doable as is. Actual can find some reoccurring bills via the find schedules option. These can be budgeted automatically using the schedule goal template.

@youngcw commented on GitHub (Feb 18, 2024): This is partially doable as is. Actual can find some reoccurring bills via the find schedules option. These can be budgeted automatically using the schedule goal template.
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
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#932
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?