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

[GH-ISSUE #1835] [Bug]: NYNAB import - importing transaction with a transfer as a split payment causes transfer to get treated as uncategorised payment #49817

New Issue
Closed
opened 2026-04-30 11:33:34 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-30 11:33:34 -05:00
Owner
Copy Link

Originally created by @Marethyu1 on GitHub (Oct 28, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1835

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Consider the following transaction:
image

It is payment to the store, but it also contains a transaction split which is a transfer of $50 to the savings account.
If you try to import a transaction like this, the sub transaction gets treated as an uncategorised payment instead:
Screenshot 2023-10-29 at 12 42 25 PM

I have attached a modified demo budget which you can use to reproduce the behaviour.
ynab5-demo-budget.json
ynab5-demo-budget-working.json

Expected behaviour: imported transaction contains a sub transaction which is a transfer to the savings account
Actual behaviour: imported transaction contains a sub transaction which is an uncategorised payment.

👋 also hello this is my first issue - let me know if I need to add anything else - thanks

What error did you receive?

It doesn't result in an error it just doesn't work as expected.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome, Safari

Operating System

Mac OSX

Originally created by @Marethyu1 on GitHub (Oct 28, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1835 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? Consider the following transaction: <img width="1269" alt="image" src="https://github.com/actualbudget/actual/assets/17978203/c56c1cb3-446a-4d61-8d72-920be07a9985"> It is payment to the store, but it also contains a transaction split which is a transfer of $50 to the savings account. If you try to import a transaction like this, the sub transaction gets treated as an uncategorised payment instead: <img width="1271" alt="Screenshot 2023-10-29 at 12 42 25 PM" src="https://github.com/actualbudget/actual/assets/17978203/2022e65f-6622-4466-9947-74b94fb7a993"> I have attached a modified demo budget which you can use to reproduce the behaviour. ~~[ynab5-demo-budget.json](https://github.com/actualbudget/actual/files/13196930/ynab5-demo-budget.json)~~ [ynab5-demo-budget-working.json](https://github.com/actualbudget/actual/files/13257671/ynab5-demo-budget.json) Expected behaviour: imported transaction contains a sub transaction which is a transfer to the savings account Actual behaviour: imported transaction contains a sub transaction which is an uncategorised payment. 👋 also hello this is my first issue - let me know if I need to add anything else - thanks ### What error did you receive? It doesn't result in an error it just doesn't work as expected. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome, Safari ### Operating System Mac OSX
GiteaMirror added the bug label 2026-04-30 11:33:34 -05:00
GiteaMirror commented 2026-04-30 11:33:38 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Nov 7, 2023):

@Marethyu1 Is this fully fixed now that your PR was merged?

<!-- gh-comment-id:1799553615 --> @youngcw commented on GitHub (Nov 7, 2023): @Marethyu1 Is this fully fixed now that your PR was merged?
GiteaMirror commented 2026-04-30 11:33:41 -05:00
Author
Owner
Copy Link

@Marethyu1 commented on GitHub (Nov 7, 2023):

Hey @youngcw it works for me in master. Im not sure what the process is for closing these issues off. Not sure if it is best to wait until the issue has been included in a full release or if I should be fine to close it now.

<!-- gh-comment-id:1799777635 --> @Marethyu1 commented on GitHub (Nov 7, 2023): Hey @youngcw it works for me in master. Im not sure what the process is for closing these issues off. Not sure if it is best to wait until the issue has been included in a full release or if I should be fine to close it now.
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 bug
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#49817
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?