mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-15 22:54:03 -05:00
[GH-ISSUE #525] [Feature] Support importing transactions over multiple accounts at once #77630
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#77630
Reference in New Issue
Block a user
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?
Originally created by @rich-howell on GitHub (Jan 22, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/525
Discussed in https://github.com/actualbudget/actual/discussions/158
Originally posted by winklevos August 6, 2022
In import UI select specific account or use a column of the data to define the related account
@MatissJanis commented on GitHub (Feb 10, 2023):
@winklevos could you please elaborate on your idea?
Thanks
@lanmaster53 commented on GitHub (Feb 19, 2023):
I'll provide some context. When I export an OFX file from my bank, it includes transactions for 4 different accounts. When I import that OFX into YNAB or other budgeting software, they allow me to select which local account is associated with each account listed in the OFX file, then imports the transactions accordingly. When I try to import the same OFX in Actual, whichever account I am in when I import receives all of the transactions.
I think the OP was referring to a way to do this with CSV files by having all transactions in a single CSV file, with a column that indicates which account each transaction should be imported into. Same thing I'm after, but a different file type.
Does that help?
@j-f1 commented on GitHub (Feb 19, 2023):
Can you share an example of one of these files (with any identifying details you’re not sharing redacted)? It will be a fairly significant undertaking to add an account field to the import dialog since the current import logic is fairly tightly designed around importing to a single transaction, but the underlying parser does seem to support pulling out the account name. Opened https://github.com/actualbudget/actual/pull/670 but I don’t plan on working on this too much more in the near future.
@lanmaster53 commented on GitHub (Feb 20, 2023):
Just a standard OFX file. You can find them on the internet, but see a simple one attached. I had to change the extension to txt for Github, but should be ofx.
sample.txt
@lanmaster53 commented on GitHub (Feb 20, 2023):
Also, this isn't nearly as urgent as the other issue I posted about transaction merging. I can make do with individual account importing, but I can't use Actual without manual transaction merging. Thanks for what you're doing. As a fellow open source developer, I know the thankless work you put in.
@github-actions[bot] commented on GitHub (May 1, 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 👍!
@djcurley89 commented on GitHub (Feb 22, 2026):
Multiple Account Transaction Example - Piere.csv
Here's an example of a CSV with transactions from multiple accounts that I get from Piere. Would really love if this could be integrated into AB as a way of importing regularly.