github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-05 22:52:20 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #1168] [Feature] Split transactions in schedules #26240

New Issue
Closed
opened 2026-04-18 02:19:52 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-18 02:19:52 -05:00
Owner
Copy Link

Originally created by @joel-jeremy on GitHub (Jun 22, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1168

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?

Can we allow schedules to post split transactions? This will make it easier for users to track what's included in a transaction. An example of where this could be useful is if a user has multiple installments that are charged to an account on the same statement date, users will be able to identify which portion of the transaction is for which purchase.

Describe your ideal solution to this problem

Allow schedules to post split transactions

Teaching and learning

No response

Originally created by @joel-jeremy on GitHub (Jun 22, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1168 ### 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? Can we allow schedules to post split transactions? This will make it easier for users to track what's included in a transaction. An example of where this could be useful is if a user has multiple installments that are charged to an account on the same statement date, users will be able to identify which portion of the transaction is for which purchase. ### Describe your ideal solution to this problem Allow schedules to post split transactions ### Teaching and learning _No response_
GiteaMirror added the feature label 2026-04-18 02:19:52 -05:00
GiteaMirror commented 2026-04-18 02:19:54 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 22, 2023):

✨ Thanks for sharing your idea! ✨

This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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 👍!

<!-- gh-comment-id:1603437685 --> @github-actions[bot] commented on GitHub (Jun 22, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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-04-18 02:19:54 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Jun 24, 2023):

This is a good idea. I think it would require a new design for the schedule editor (which does need some improvements anyway). I’m not sure what that would look like, but feel free to pitch something if you want!

<!-- gh-comment-id:1605723816 --> @j-f1 commented on GitHub (Jun 24, 2023): This is a good idea. I think it would require a new design for the schedule editor (which does need some improvements anyway). I’m not sure what that would look like, but feel free to pitch something if you want!
GiteaMirror commented 2026-04-18 02:19:55 -05:00
Author
Owner
Copy Link

@ElDubsNZ commented on GitHub (Nov 29, 2023):

I too would appreciate this feature.

In the rule it should have a rule to say "split transaction", then a set of rule actions for each child transaction.

<!-- gh-comment-id:1831178839 --> @ElDubsNZ commented on GitHub (Nov 29, 2023): I too would appreciate this feature. In the rule it should have a rule to say "split transaction", then a set of rule actions for each child transaction.
GiteaMirror commented 2026-04-18 02:19:55 -05:00
Author
Owner
Copy Link

@jfdoming commented on GitHub (Nov 29, 2023):

I too would appreciate this feature.

In the rule it should have a rule to say "split transaction", then a set of rule actions for each child transaction.

Yep, that's exactly the implementation I'm working on!

<!-- gh-comment-id:1831998377 --> @jfdoming commented on GitHub (Nov 29, 2023): > I too would appreciate this feature. > > In the rule it should have a rule to say "split transaction", then a set of rule actions for each child transaction. Yep, that's exactly the implementation I'm working on!
GiteaMirror commented 2026-04-18 02:19:56 -05:00
Author
Owner
Copy Link

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

🎉 This feature has been implemented in #2059 and will be released in the next version. Thanks for sharing your idea! 🎉

<!-- gh-comment-id:1934293859 --> @github-actions[bot] commented on GitHub (Feb 8, 2024): :tada: This feature has been implemented in #2059 and will be released in the next version. Thanks for sharing your idea! :tada: <!-- feature-implemented-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
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#26240
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?