-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: QFX Import Broken on new parser #2331
Comments
Please include a sample qfx. We cant do anything useful without it |
Had to change the extension to |
ping @joel-jeremy |
I'm also having problems importing OFX |
I have a fix for the error you ran into in #2342 But @matthewkdies it appears that the OFX file you are trying to import is for multiple bank accounts. (Though only 1 has transactions). Actuals current transaction importers are meant to be per-account. Does your bank let you download per-account qfx files? |
Unfortunately, no. PNC's QFX/OFX export is terrible IMO -- it doesn't let you filter by date selection for import, so I have to do that myself with a script I wrote/am writing. It also exports for all accounts, and PNC's vast majority of users have three: spend, savings, and reserve. Edit: FWIW, I believe that PNC exports the OFX file based on the selected account and adds the appropriate transactions. So when I am in "reserve" those transactions do appear. |
The parse error is fixed in master with #2342 |
Verified issue does not already exist?
Is this related to GoCardless, Simplefin or another bank-sync provider?
What happened?
When importing QFX files from my bank (PNC), the import fails with no logs. Previously, I would uncheck the "Use experimental parser" option in the settings to fix this, but this option has disappeared in the current release. I also tried downgrading to
24.1.0
, though the migration failed and the app wouldn't start.If desired, I can include the relevant QFX file (censored) in the comments.
What error did you receive?
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Firefox, Safari
Operating System
Mac OSX
The text was updated successfully, but these errors were encountered: