mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-10 22:22:40 -05:00
[GH-ISSUE #1524] [Bug]: OFX Import "Notes" & "Payee" Fields Switched #114947
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#114947
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 @themadman0980 on GitHub (Aug 14, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1524
Verified issue does not already exist?
What happened?
I have been happily using Actual for the last 8 months, and the OFX import tool has worked beautifully until now (first attempt in the last 3-4 weeks, so I'm assuming it's the new OFX importer).
Basically, the "Notes" and "Payee" fields have all been swapped, which is immensely painful and makes the import tool basically unusable. Below is an example of what I am seeing now, with all the purchase details in the payee field instead of notes. This means that every new transaction imported has a new payee, as every payment description is unique.
#521 seems like a related problem but I'm unsure what ended up happening.
FWIW I attempted to re-import some old OFX files that worked beautifully several months ago, and they're all exhibiting the same behaviour. This leads me to believe its not an issue with my bank's OFX export tool.
I'm currently running 23.8.1 using Docker and Google Chrome.
What error did you receive?
No response
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Chrome
Operating System
Mac OSX
@MatissJanis commented on GitHub (Aug 14, 2023):
👋 Would you mind providing a redacted version of your OFX export? We really need a way to reproduce the issue in order to fix it.
@themadman0980 commented on GitHub (Aug 14, 2023):
Here's a sample file I've exported from my bank that I've confirmed has the issue on my current setup.
OFXData-Sample.zip
I can't see any personal info here, but please let me know if there's any issues.
@joel-jeremy commented on GitHub (Aug 15, 2023):
The way the ofx importer is implemented right now is that is checks first if the ofx transaction has a
NAMEfield and use that as the payee. Otherwise, it will use theMEMOas the payee.Banks do not generate the ofx file the same. Some banks populate the
NAMEfield with the name of the payee but others just use theMEMOfield with the transaction details. In your case, it is the latter.I think one possible solution is just put the
MEMOin the Notes field and provide a way to easily create a rule inside the import modal so that users can easily create a rule to populate the Payee based on the Notes e.g.@themadman0980 commented on GitHub (Aug 15, 2023):
Yeah, that sounds like exactly what used to happen tbh. Thanks for following up!
@themadman0980 commented on GitHub (Aug 23, 2023):
This issue seems to be derived from the outcome of #1268.
@Shazib commented on GitHub (Aug 24, 2023):
In this case the memo field seems to be some hybrid of the payee and some other notes. I guess we need a flag/option for the user to be able to use memo as payee optionally. @themadman0980
I will look this weekend if I can implement this - alternatively we could unwind #1268 as a regression in the interim @MatissJanis?
@MatissJanis commented on GitHub (Aug 25, 2023):
I would prefer not to rollback. If we did that, then another group of people would start reporting bug reports about the inverse problem. Lets just try to patch this issue for the next release. If you don't have time this weekend, then I'll try to take a look at it next week.
@MatissJanis commented on GitHub (Sep 1, 2023):
Fix: https://github.com/actualbudget/actual/pull/1631
Would appreciate some testing from you @themadman0980