[GH-ISSUE #1007] [Bug]: OFX Importer fails to recognize transactions in file #26183

Closed
opened 2026-04-18 02:14:35 -05:00 by GiteaMirror · 8 comments
Owner

Originally created by @austempest on GitHub (May 7, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1007

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

A bug happened!

Imported OFX file (direct export from bank. Bank wwas ING Direct (Australia).

What error did you receive?

Import was successful, but please file a bug report and attach a redacted version of the file so we can fix our new algorithm.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox

Operating System

Windows 10

Originally created by @austempest on GitHub (May 7, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1007 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? A bug happened! Imported OFX file (direct export from bank. Bank wwas ING Direct (Australia). ### What error did you receive? Import was successful, but please [file a bug report](https://github.com/actualbudget/actual/issues/new?assignees=&labels=bug%2Cneeds+triage&template=bug-report.yml&title=%5BBug%5D%3A+New+OFX+Importer:+bad+new+parse:) and attach a redacted version of the file so we can fix our new algorithm. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox ### Operating System Windows 10
GiteaMirror added the transaction importbug labels 2026-04-18 02:14:35 -05:00
Author
Owner

@austempest commented on GitHub (May 7, 2023):

Transactions(redacted).zip

<!-- gh-comment-id:1537418006 --> @austempest commented on GitHub (May 7, 2023): [Transactions(redacted).zip](https://github.com/actualbudget/actual/files/11414857/Transactions.redacted.zip)
Author
Owner

@j-f1 commented on GitHub (May 7, 2023):

fyi @sinistersnare

<!-- gh-comment-id:1537463595 --> @j-f1 commented on GitHub (May 7, 2023): fyi @sinistersnare
Author
Owner

@j-f1 commented on GitHub (May 7, 2023):

Thank you for reporting!

<!-- gh-comment-id:1537463659 --> @j-f1 commented on GitHub (May 7, 2023): Thank you for reporting!
Author
Owner

@tjfinlinson commented on GitHub (May 9, 2023):

I noticed the same thing when importing my ofx files. I'm downloading from Zions Bank in Utah. I'll try and put a redacted file up here for use as well.

<!-- gh-comment-id:1541022787 --> @tjfinlinson commented on GitHub (May 9, 2023): I noticed the same thing when importing my ofx files. I'm downloading from Zions Bank in Utah. I'll try and put a redacted file up here for use as well.
Author
Owner

@sinistersnare commented on GitHub (May 10, 2023):

Looking at this, it seems the old importer produced an import with 0 entries, and the new with 2. Because there was no explicit error, but only a diff, the old results were used (to ensure compatibility with past imports), and a warning was shown.

If the new importer was used, it would have succeeded as you would want. As the old results are used, you get the results you see here.

<!-- gh-comment-id:1542212332 --> @sinistersnare commented on GitHub (May 10, 2023): Looking at this, it seems the old importer produced an import with 0 entries, and the new with 2. Because there was no explicit error, but only a diff, the old results were used (to ensure compatibility with past imports), and a warning was shown. If the new importer was used, it would have succeeded as you would want. As the old results are used, you get the results you see here.
Author
Owner

@tjfinlinson commented on GitHub (May 19, 2023):

Looking at this, it seems the old importer produced an import with 0 entries, and the new with 2. Because there was no explicit error, but only a diff, the old results were used (to ensure compatibility with past imports), and a warning was shown.

If the new importer was used, it would have succeeded as you would want. As the old results are used, you get the results you see here.

I'm not totally sure what this means, but are you saying that since the transactions are importing nothing is broken, just giving an error (or more of a notification) to say that Actual just sees the latest import as different previous ones? Will that message always show up, or will it eventually be removed?

That makes me think something didn't happen correctly and it might not have worked 100%.

Regardless, I'm attaching a redacted file in-case it helps in any way.

Account-OFX-Transactions-Download-Redacted.txt

<!-- gh-comment-id:1554802769 --> @tjfinlinson commented on GitHub (May 19, 2023): > Looking at this, it seems the old importer produced an import with 0 entries, and the new with 2. Because there was no explicit error, but only a diff, the old results were used (to ensure compatibility with past imports), and a warning was shown. > > If the new importer was used, it would have succeeded as you would want. As the old results are used, you get the results you see here. I'm not totally sure what this means, but are you saying that since the transactions are importing nothing is broken, just giving an error (or more of a notification) to say that Actual just sees the latest import as different previous ones? Will that message always show up, or will it eventually be removed? That makes me think something didn't happen correctly and it might not have worked 100%. Regardless, I'm attaching a redacted file in-case it helps in any way. [Account-OFX-Transactions-Download-Redacted.txt](https://github.com/actualbudget/actual/files/11518630/Account-OFX-Transactions-Download-Redacted.txt)
Author
Owner

@sinistersnare commented on GitHub (May 19, 2023):

Currently there are 2 OFX importers use, the 'old' and the 'new'. In case of different results, 'old' is always used. However, in the case of this issue, 'new' would have been better.

In the future, if we remove the old parser and just use the new, this would have worked better.

<!-- gh-comment-id:1555002029 --> @sinistersnare commented on GitHub (May 19, 2023): Currently there are 2 OFX importers use, the 'old' and the 'new'. In case of different results, 'old' is always used. However, in the case of this issue, 'new' would have been better. In the future, if we remove the old parser and just use the new, this would have worked better.
Author
Owner

@youngcw commented on GitHub (Nov 16, 2023):

closing this as outdated since we have moved to a new test importer.

<!-- gh-comment-id:1814838235 --> @youngcw commented on GitHub (Nov 16, 2023): closing this as outdated since we have moved to a new test importer.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#26183