github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-07 04:18:51 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[Feature] Import multiple accounts at once #2626

New Issue
Closed
opened 2026-02-28 20:22:12 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 20:22:12 -06:00
Owner
Copy Link

Originally created by @DenizUgur on GitHub (Nov 15, 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?

OFX format can contain multiple accounts as identified via CCACCTFROM.ACCTID or BANKACCTFROM.ACCTID. These fields can be used to import multiple accounts at once. Same field can be used to ensure when importing OFX to an account it is indeed the correct OFX file.

Right now, there is no validation or support for multiple account import.

Describe your ideal solution to this problem

My recommended solution is to store this account id internally for each account. When the user imports via OFX, then populate this field.

Expose the "Import" button on "All transactions" page only if there's an account with account id populated. When user clicks on the import button on this page, open the Import transactions (OFX) window for each account. That's it.

Teaching and learning

We could make this grayed out or configurable via the settings page

Originally created by @DenizUgur on GitHub (Nov 15, 2025). ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [x] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? OFX format can contain multiple accounts as identified via `CCACCTFROM.ACCTID` or `BANKACCTFROM.ACCTID`. These fields can be used to import multiple accounts at once. Same field can be used to ensure when importing OFX to an account it is indeed the correct OFX file. Right now, there is no validation or support for multiple account import. ### Describe your ideal solution to this problem My recommended solution is to store this account id internally for each account. When the user imports via OFX, then populate this field. Expose the "Import" button on "All transactions" page only if there's an account with account id populated. When user clicks on the import button on this page, open the `Import transactions (OFX)` window for each account. That's it. ### Teaching and learning We could make this grayed out or configurable via the settings page
GiteaMirror added the needs votesfeature labels 2026-02-28 20:22:12 -06:00
GiteaMirror commented 2026-02-28 20:22:13 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 15, 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 (Nov 15, 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:22:14 -06:00
Author
Owner
Copy Link

@db-src commented on GitHub (Nov 18, 2025):

Dupe of https://github.com/actualbudget/actual/issues/525

@db-src commented on GitHub (Nov 18, 2025): Dupe of https://github.com/actualbudget/actual/issues/525
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 needs votes
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#2626
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?