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 #1567] [Feature] Allow child transactions in a split transaction to have different payees #7522

New Issue
Closed
opened 2026-04-10 17:23:19 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-04-10 17:23:19 -05:00
Owner
Copy Link

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

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?

When doing transfers/bill payments in fintech apps, there's usually fees associated with every transaction. It would be great if we could model these fees through split transactions. Right now, users will need to create a separate transaction for fees which can make it hard to track which parent transaction that fee is for.

Describe your ideal solution to this problem

Allow child transactions in a split transaction to have different payees

Teaching and learning

No response

Originally created by @joel-jeremy on GitHub (Aug 22, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1567 ### 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? When doing transfers/bill payments in fintech apps, there's usually fees associated with every transaction. It would be great if we could model these fees through split transactions. Right now, users will need to create a separate transaction for fees which can make it hard to track which parent transaction that fee is for. ### Describe your ideal solution to this problem Allow child transactions in a split transaction to have different payees ### Teaching and learning _No response_
GiteaMirror added the split transactionsfeature labels 2026-04-10 17:23:19 -05:00
GiteaMirror commented 2026-04-10 17:23:21 -05:00
Author
Owner
Copy Link

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

✨ 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 👍!

<!-- gh-comment-id:1689029661 --> @github-actions[bot] commented on GitHub (Aug 22, 2023): :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-04-10 17:23:22 -05:00
Author
Owner
Copy Link

@kyrias commented on GitHub (Aug 22, 2023):

Child transactions can already have different payees.

<!-- gh-comment-id:1689059962 --> @kyrias commented on GitHub (Aug 22, 2023): Child transactions _can_ already have different payees.
GiteaMirror commented 2026-04-10 17:23:22 -05:00
Author
Owner
Copy Link

@joel-jeremy commented on GitHub (Aug 22, 2023):

That is true for transfer payees but for regular payees, they do not show up on the payee selection.

<!-- gh-comment-id:1689072003 --> @joel-jeremy commented on GitHub (Aug 22, 2023): That is true for transfer payees but for regular payees, they do not show up on the payee selection.
GiteaMirror commented 2026-04-10 17:23:23 -05:00
Author
Owner
Copy Link

@kyrias commented on GitHub (Aug 23, 2023):

The UI is a bit wonky here, but if you click the yellow "Make Transfer" button you can select among all of them. For some reason showing only the transfer payees is the default on child transactions, though I don't understand why.

@MatissJanis Does the current default behavior make sense to you? Otherwise I think we should change it.

<!-- gh-comment-id:1689730988 --> @kyrias commented on GitHub (Aug 23, 2023): The UI is a bit wonky here, but if you click the yellow "Make Transfer" button you can select among all of them. For some reason showing only the transfer payees is the default on child transactions, though I don't understand why. @MatissJanis Does the current default behavior make sense to you? Otherwise I think we should change it.
GiteaMirror commented 2026-04-10 17:23:24 -05:00
Author
Owner
Copy Link

@joel-jeremy commented on GitHub (Aug 23, 2023):

I think we should show regular payees too in the payee selection for child transactions. This is useful for entering transaction fees.

<!-- gh-comment-id:1689988811 --> @joel-jeremy commented on GitHub (Aug 23, 2023): I think we should show regular payees too in the payee selection for child transactions. This is useful for entering transaction fees.
GiteaMirror commented 2026-04-10 17:23:25 -05:00
Author
Owner
Copy Link

@kyrias commented on GitHub (Aug 23, 2023):

My point is that we do, we just don't do it by default and I think we should change this default.

<!-- gh-comment-id:1689994125 --> @kyrias commented on GitHub (Aug 23, 2023): My point is that we _do_, we just don't do it _by default_ and I think we should change this default.
GiteaMirror commented 2026-04-10 17:23:26 -05:00
Author
Owner
Copy Link

@joel-jeremy commented on GitHub (Aug 23, 2023):

Sorry, yeah - I meant show them by default. I agree.

<!-- gh-comment-id:1690035573 --> @joel-jeremy commented on GitHub (Aug 23, 2023): Sorry, yeah - I meant show them by default. I agree.
GiteaMirror commented 2026-04-10 17:23:26 -05:00
Author
Owner
Copy Link

@joel-jeremy commented on GitHub (Aug 23, 2023):

There also seems to be a bug with the amounts. I split the transaction between an off-budget account and a payee and the whole transaction amount (100) was deposited to the off-budget account instead of the the child amount (50):

image
image

<!-- gh-comment-id:1690077018 --> @joel-jeremy commented on GitHub (Aug 23, 2023): There also seems to be a bug with the amounts. I split the transaction between an off-budget account and a payee and the whole transaction amount (100) was deposited to the off-budget account instead of the the child amount (50): ![image](https://github.com/actualbudget/actual/assets/20313680/7a9c91e0-a836-46c4-9115-1c0f2cb91403) ![image](https://github.com/actualbudget/actual/assets/20313680/90733dc8-4f57-4065-a6ec-4994c0b42e71)
GiteaMirror commented 2026-04-10 17:23:27 -05:00
Author
Owner
Copy Link

@kyrias commented on GitHub (Aug 23, 2023):

Ah, that's because the payee of the parent transaction is the transfer payee. The simple work-around would be to have the non-transfer payee as the payee of the parent transaction.

I have a feeling that this will be involved to fix, but please do file a bug issue about it.

<!-- gh-comment-id:1690084112 --> @kyrias commented on GitHub (Aug 23, 2023): Ah, that's because the payee of the parent transaction is the transfer payee. The simple work-around would be to have the non-transfer payee as the payee of the parent transaction. I have a feeling that this will be involved to fix, but please do file a bug issue about it.
GiteaMirror commented 2026-04-10 17:23:28 -05:00
Author
Owner
Copy Link

@joel-jeremy commented on GitHub (Aug 23, 2023):

Thank you! The workaround works. I have filed a separate bug report for this: https://github.com/actualbudget/actual/issues/1574

<!-- gh-comment-id:1690142477 --> @joel-jeremy commented on GitHub (Aug 23, 2023): Thank you! The workaround works. I have filed a separate bug report for this: https://github.com/actualbudget/actual/issues/1574
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 split transactions
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#7522
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?