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] Import nYNAB future/scheduled transactions as scheduled in Actual #2343

New Issue
Closed
opened 2026-02-28 20:11:23 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-02-28 20:11:23 -06:00
Owner
Copy Link

Originally created by @Backspaze on GitHub (Aug 2, 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 imported my nYNAB budget to Actual and noticed that future scheduled transactions were not imported. They're in the JSON export from nYNAB, so why not import them? This would improve the user experience when migrating from nYNAB, to cut down on the manual steps needed after migrating.

Describe your ideal solution to this problem

The import script should have the functionality to import and configure the scheduled transactions.

Teaching and learning

If this feature is not going to be supported, the documentation should point out under the cleanup section that future scheduled transactions are not automatically configured, and that they need to be reconfigured in Actual.

Originally created by @Backspaze on GitHub (Aug 2, 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 imported my nYNAB budget to Actual and noticed that future scheduled transactions were not imported. They're in the JSON export from nYNAB, so why not import them? This would improve the user experience when migrating from nYNAB, to cut down on the manual steps needed after migrating. ### Describe your ideal solution to this problem The import script should have the functionality to import and configure the scheduled transactions. ### Teaching and learning If this feature is not going to be supported, the documentation should point out under the [cleanup section](https://actualbudget.org/docs/migration/nynab/#cleanup) that future scheduled transactions are not automatically configured, and that they need to be reconfigured in Actual.
GiteaMirror added the feature label 2026-02-28 20:11:23 -06:00
GiteaMirror commented 2026-02-28 20:11:24 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 2, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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 (Aug 2, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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 20:11:24 -06:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Aug 2, 2025):

Are you able to provide a sample JSON to show how these appear in the export please?

@matt-fidd commented on GitHub (Aug 2, 2025): Are you able to provide a sample JSON to show how these appear in the export please?
GiteaMirror commented 2026-02-28 20:11:25 -06:00
Author
Owner
Copy Link

@Backspaze commented on GitHub (Aug 2, 2025):

Are you able to provide a sample JSON to show how these appear in the export please?

Yes, I threw together a blank budget with one account and a scheduled transaction for every of the 13 variants of scheduled transactions there is in nYNAB. I've added it as an attachment here. Below you'll find an example from the JSON, note the frequency value.

scheduled_export.json

"scheduled_transactions": [
        {
          "id": "1db8beb8-ef31-4a07-b9a5-0648b1e3071a",
          "date_first": "2025-08-05",
          "date_next": "2025-08-05",
          "frequency": "every4Weeks",
          "amount": -100000,
          "memo": "Scheduled - repeated every four weeks",
          "flag_color": null,
          "account_id": "a4c7e450-5aab-41b8-a229-c39f793b336e",
          "payee_id": "0f0899e3-242f-42e6-aae9-a751060d878e",
          "category_id": "419ae801-27c8-424b-8f39-9611825803db",
          "transfer_account_id": null,
          "deleted": false
        },
@Backspaze commented on GitHub (Aug 2, 2025): > Are you able to provide a sample JSON to show how these appear in the export please? Yes, I threw together a blank budget with one account and a scheduled transaction for every of the 13 variants of scheduled transactions there is in nYNAB. I've added it as an attachment here. Below you'll find an example from the JSON, note the `frequency` value. [scheduled_export.json](https://github.com/user-attachments/files/21562802/scheduled_export.json) ```json "scheduled_transactions": [ { "id": "1db8beb8-ef31-4a07-b9a5-0648b1e3071a", "date_first": "2025-08-05", "date_next": "2025-08-05", "frequency": "every4Weeks", "amount": -100000, "memo": "Scheduled - repeated every four weeks", "flag_color": null, "account_id": "a4c7e450-5aab-41b8-a229-c39f793b336e", "payee_id": "0f0899e3-242f-42e6-aae9-a751060d878e", "category_id": "419ae801-27c8-424b-8f39-9611825803db", "transfer_account_id": null, "deleted": false }, ```
GiteaMirror commented 2026-02-28 20:11:25 -06:00
Author
Owner
Copy Link

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

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

@github-actions[bot] commented on GitHub (Feb 4, 2026): :tada: This feature has been implemented in #6844 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#2343
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?