-
-
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]: OFX transactions offset by 1 day #1731
Comments
@bverkron Do you have the experimental OFX parser enabled? |
@joel-jeremy I don't believe so. I imagine it would show here in the settings? Or it it set elsewhere? |
Hmm yeah looks like it should be in that section according to PR #1600 and it was release in 23.5.0 according to the release notes. Any idea why I'm not seeing it? |
There is a new experimental OFX parser in that page but is only available in edge at the moment. Would you be able to test your import on the edge version and the experimental OFX parser enabled? |
That seems to work! From my institution... In the import dialog (after import the dates matched as well)... Side note, is there an open request to have the sort date of the import dialog be in reverse chronological order instead of the current chronological order or allow it to be sortable? I think the default for the accounts is reverse chronological (or at least that's how I have it and most people seem to use it) and same with banking institution usually. Would be nice if it would match in the import dialog. If not I can open a request :) |
Can this be closed? Looks like the new parser doesn't have the same issue. |
I'm good to close it yes. Thanks! |
Verified issue does not already exist?
What happened?
Same issue as #1053, was not resolved via the fix.
Dates are offset by -1 day when importing files such as the following. Other files from other institutions work fine.
statement.6.qfx (1).zip
Still happening in the latest 23.9.0 version
What error did you receive?
No error dates are just off.
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Chrome, Safari
Operating System
Mac OSX
The text was updated successfully, but these errors were encountered: