github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-12 01:52:09 -05:00
Code Issues 1.6k Packages Projects Releases 57 Wiki Activity

[GH-ISSUE #767] [Bug]: OFX with payee information in MEMO field not parsed correctly #26092

New Issue
Closed
opened 2026-04-18 02:03:33 -05:00 by GiteaMirror · 12 comments
GiteaMirror commented 2026-04-18 02:03:33 -05:00
Owner
Copy Link

Originally created by @damomato on GitHub (Mar 17, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/767

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

When importing an OFX file with credit card transactions the payees are remaining blank and no rules are created. Everything else seems to be working fine apart from that,

According to the docs:
"When importing transactions, by default it will create new payees based on the given name."

However this isn't happening. Apologies if I've misunderstood how this is supposed to work.

What error did you receive?

No response

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

Originally created by @damomato on GitHub (Mar 17, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/767 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? When importing an OFX file with credit card transactions the payees are remaining blank and no rules are created. Everything else seems to be working fine apart from that, According to the docs: "When importing transactions, by default it will create new payees based on the given name." However this isn't happening. Apologies if I've misunderstood how this is supposed to work. ### What error did you receive? _No response_ ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox ### Operating System Linux
GiteaMirror added the transaction importbug labels 2026-04-18 02:03:34 -05:00
GiteaMirror commented 2026-04-18 02:03:36 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Mar 17, 2023):

Can you upload an example OFX file (with any sensitive information redacted)? We may not be parsing it correctly.

<!-- gh-comment-id:1473759882 --> @j-f1 commented on GitHub (Mar 17, 2023): Can you upload an example OFX file (with any sensitive information redacted)? We may not be parsing it correctly.
GiteaMirror commented 2026-04-18 02:03:36 -05:00
Author
Owner
Copy Link

@damomato commented on GitHub (Mar 18, 2023):

Thanks for the quick response. The file type wasn't supported so I zipped the OFX file. Just a single day of data.

file removed due to sensitive data

This is how it looks in Actual after I import it. Payee is empty.
image

And these are the options for downloading the data from my bank. I've tried both MYOB and Quicken OFX files. It's an Australian bank if that makes any difference.
image

<!-- gh-comment-id:1474858508 --> @damomato commented on GitHub (Mar 18, 2023): Thanks for the quick response. The file type wasn't supported so I zipped the OFX file. Just a single day of data. *file removed due to sensitive data* This is how it looks in Actual after I import it. Payee is empty. ![image](https://user-images.githubusercontent.com/85538685/226110206-f06f4214-6cc1-4474-bc26-117738c58f42.png) And these are the options for downloading the data from my bank. I've tried both MYOB and Quicken OFX files. It's an Australian bank if that makes any difference. ![image](https://user-images.githubusercontent.com/85538685/226110258-c198fa1c-926d-44ee-a3e9-5b1056a02f45.png)
GiteaMirror commented 2026-04-18 02:03:37 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Mar 18, 2023):

Thanks for that! It looks like the difference is that we’re expecting the payee to be the NAME of the transaction but your data has it as the MEMO instead (which we put in the notes field). I’m not sure what we should do — maybe interpret the memo as the payee if the payee is missing?

<!-- gh-comment-id:1474860842 --> @j-f1 commented on GitHub (Mar 18, 2023): Thanks for that! It looks like the difference is that we’re expecting the payee to be the `NAME` of the transaction but your data has it as the `MEMO` instead (which we put in the notes field). I’m not sure what we should do — maybe interpret the memo as the payee if the payee is missing?
GiteaMirror commented 2026-04-18 02:03:37 -05:00
Author
Owner
Copy Link

@Jackenmen commented on GitHub (Mar 18, 2023):

If this happens for all transactions then generalizing the UI for CSV imports (with default columns prefilled) could make sense, perhaps?

But if it happens only for some transactions then I think that falling back to MEMO is currently the only option. The rules engine doesn't currently support templating so it isn't possible to use the value of Notes field in Payee. A suggestion for templating was recently made in the Discord server but it doesn't sound like something that would be easy to implement so adding a fallback would make most sense, at least for now.

<!-- gh-comment-id:1474866745 --> @Jackenmen commented on GitHub (Mar 18, 2023): If this happens for all transactions then generalizing the UI for CSV imports (with default columns prefilled) could make sense, perhaps? But if it happens only for some transactions then I think that falling back to `MEMO` is currently the only option. The rules engine doesn't currently support templating so it isn't possible to use the value of Notes field in Payee. A suggestion for templating was recently made in the Discord server but it doesn't sound like something that would be easy to implement so adding a fallback would make most sense, at least for now.
GiteaMirror commented 2026-04-18 02:03:38 -05:00
Author
Owner
Copy Link

@damomato commented on GitHub (Mar 18, 2023):

I would think it's happening on all transactions for this particular bank, when I have some time later I'll download transactions for another bank and see if it's the same.

Of course an Aussie bank does it different 😵

<!-- gh-comment-id:1475012139 --> @damomato commented on GitHub (Mar 18, 2023): I would think it's happening on all transactions for this particular bank, when I have some time later I'll download transactions for another bank and see if it's the same. Of course an Aussie bank does it different 😵
GiteaMirror commented 2026-04-18 02:03:38 -05:00
Author
Owner
Copy Link

@damomato commented on GitHub (Mar 19, 2023):

I tried another bank and it uses MEMO as well. Not only that, it doesn't even import any transactions. It sometimes shows zero transactions and sometimes shows an error. Should I open a new separate issue for that?

image

image

<!-- gh-comment-id:1475100452 --> @damomato commented on GitHub (Mar 19, 2023): I tried another bank and it uses MEMO as well. Not only that, it doesn't even import any transactions. It sometimes shows zero transactions and sometimes shows an error. Should I open a new separate issue for that? ![image](https://user-images.githubusercontent.com/85538685/226153793-eebdbfeb-bfb6-4d5e-bff3-cc1dd16f290b.png) ![image](https://user-images.githubusercontent.com/85538685/226153781-f33b288b-8faf-4758-8a2c-43d037fed64e.png)
GiteaMirror commented 2026-04-18 02:03:39 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Mar 19, 2023):

Yes, please open a separate issue for that and attach the files that can’t be imported.

<!-- gh-comment-id:1475252237 --> @j-f1 commented on GitHub (Mar 19, 2023): Yes, please open a separate issue for that and attach the files that can’t be imported.
GiteaMirror commented 2026-04-18 02:03:40 -05:00
Author
Owner
Copy Link

@damomato commented on GitHub (Mar 20, 2023):

Thanks, I've added it now. I also removed the OFX file from this issue as I realised there was sensitive data I forgot to remove. Let me know if you need it again and I'll clean it up and upload.

<!-- gh-comment-id:1475735048 --> @damomato commented on GitHub (Mar 20, 2023): Thanks, I've added it now. I also removed the OFX file from this issue as I realised there was sensitive data I forgot to remove. Let me know if you need it again and I'll clean it up and upload.
GiteaMirror commented 2026-04-18 02:03:40 -05:00
Author
Owner
Copy Link

@damomato commented on GitHub (May 5, 2023):

I just installed the new release (v23.5.0) but am still having the same issue, Payee remains blank

I'm using the normal 'Import' button in the account. Is there a different import method as part of this release? I do get the error message pop-up now when I try to import though.

<!-- gh-comment-id:1535639105 --> @damomato commented on GitHub (May 5, 2023): I just installed the new release (v23.5.0) but am still having the same issue, Payee remains blank I'm using the normal 'Import' button in the account. Is there a different import method as part of this release? I do get the error message pop-up now when I try to import though.
GiteaMirror commented 2026-04-18 02:03:41 -05:00
Author
Owner
Copy Link

@rafacla commented on GitHub (Jun 25, 2023):

Here aswell, other apps have the option to disable/enable payee/memo swap, looks like it's a standarlization problem across the globe

<!-- gh-comment-id:1606264460 --> @rafacla commented on GitHub (Jun 25, 2023): Here aswell, other apps have the option to disable/enable payee/memo swap, looks like it's a standarlization problem across the globe
GiteaMirror commented 2026-04-18 02:03:42 -05:00
Author
Owner
Copy Link

@Shazib commented on GitHub (Jul 6, 2023):

@damomato @rafacla can you try this after the latest fix? then we can close this off

<!-- gh-comment-id:1624449789 --> @Shazib commented on GitHub (Jul 6, 2023): @damomato @rafacla can you try this after the latest fix? then we can close this off
GiteaMirror commented 2026-04-18 02:03:43 -05:00
Author
Owner
Copy Link

@damomato commented on GitHub (Jul 7, 2023):

I can confirm that this issue is now fixed in v23.7.1, thanks for the great work guys!

However issue #794 is still not fixed, same error with the "no transactions found" message.

If Nordigen/GoCardless supported Australian banks I would probably just set that up instead of importing OFX files. Hopefully they will eventually.

<!-- gh-comment-id:1624487476 --> @damomato commented on GitHub (Jul 7, 2023): I can confirm that this issue is now fixed in v23.7.1, thanks for the great work guys! However issue #794 is still not fixed, same error with the "no transactions found" message. If Nordigen/GoCardless supported Australian banks I would probably just set that up instead of importing OFX files. Hopefully they will eventually.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug transaction import
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#26092
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?