mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-15 14:43:36 -05:00
[GH-ISSUE #3208] [Feature] Support newer versions of OFX format #8245
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#8245
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 @faroguy on GitHub (Aug 6, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/3208
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
All of my banks lets me download my transactions in OFX format. However, earlier this year (April I think?) Actual budget started refusing to import anything from one bank in particular. Only today did I figure out that my bank is providing the information in the OFX V2 format, while other institutions are still providing the V1 format. The specification is laid out here: https://financialdataexchange.org/FDX/About/About-FDX.aspx?WebsiteKey=deae9d6d-1a7a-457b-a678-8a5517f8a474&hkey=dffb9a93-fc7d-4f65-840c-f2cfbe7fe8a6&a315d1c24e44=5#a315d1c24e44
Sorry for the long link.
As more banks move to the new format, it would benefit Actual to be able to import from those files.
Any thoughts?
Describe your ideal solution to this problem
Implementing the new format would be wonderful.
At least being able to recognize the file and provide a meaningful error would be a great start.
Teaching and learning
Implementing this feature, or at least providing an error, would help users understand that nothing is wrong with their file.
Adding some documentation about the new version would also help. Currently there is nothing.
@github-actions[bot] commented on GitHub (Aug 6, 2024):
✨ 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 👍!
@vinstaal0 commented on GitHub (Aug 7, 2024):
There are a shit ton of bank formats that are used, I see the use of MT940 and CAMT053 the most for my clients.
@faroguy commented on GitHub (Aug 11, 2024):
That is true and I'm not saying that every format needs to be supported. However, Actual supports one version of the OFX format and not another. In my case, this was a huge source of confusion for me as the file I downloaded used to work and then suddenly didn't. In the case of less technical users, they would not be able to understand the reason. For this reason alone, it would be worthwhile to give an error message saying this version of OFX is not yet supported and to import the transactions another way.