github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[Feature] Append MEMO to NAME when importing QFX files. #1338

New Issue
Closed
opened 2026-02-28 19:40:50 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 19:40:50 -06:00
Owner
Copy Link

Originally created by @daybreak7022 on GitHub (Aug 15, 2024).

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

My bank split long Payees between the NAME and MEMO field in the .qfx export file.
When I import my QFX file into Actual, only half of the actual Payee is imported.

I would like the ability to append the MEMO field to the NAME field as Actual Budget imports the Payee. Meaning, I would like Actual to combine the NAME and MEMO fields before importing that value into the Payee field in Actual.

Describe your ideal solution to this problem

Another open source budget application called HomeBank allows the user additional control over how the NAME and MEMO fields in the file are imported.

Below is a list of what the options are regarding how to handle the NAME and MEMO fields:
OFX/QFX Options

OFX Name
Ignore
Memo
Payee
Number

OFX Memo
Ignore
Append to Memo
Append to Payee
Append to Number

You can see from the example above that HomeBank allows the user to specify what to do with the NAME and MEMO fields.

This functionality could help compensate for the different ways banks will create their QFX files.

HomeBank specifies these options at a global application level. I think it would be better if/when Actual implements this feature that it's done at the account level. If a user has multiple financial institutions, the QFX formatting for NAME and MEMO might be different. If setting these options is done at the account level, the user wouldn't need to change settings before doing each import. Also, the user wouldn't have to remember each time which bank uses which settings.

Another option would be the ability to have a template in the Import section which the user could select.

Teaching and learning

By exposing this feature on the Import screen, users would become aware of its presence.
Additionally, adding this functionality to the documentation would educate users.

Originally created by @daybreak7022 on GitHub (Aug 15, 2024). ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? My bank split long Payees between the NAME and MEMO field in the .qfx export file. When I import my QFX file into Actual, only half of the actual Payee is imported. I would like the ability to append the MEMO field to the NAME field as Actual Budget imports the Payee. Meaning, I would like Actual to combine the NAME and MEMO fields before importing that value into the Payee field in Actual. ### Describe your ideal solution to this problem Another open source budget application called HomeBank allows the user additional control over how the NAME and MEMO fields in the file are imported. Below is a list of what the options are regarding how to handle the NAME and MEMO fields: OFX/QFX Options OFX Name Ignore Memo Payee Number OFX Memo Ignore Append to Memo Append to Payee Append to Number You can see from the example above that HomeBank allows the user to specify what to do with the NAME and MEMO fields. This functionality could help compensate for the different ways banks will create their QFX files. HomeBank specifies these options at a global application level. I think it would be better if/when Actual implements this feature that it's done at the account level. If a user has multiple financial institutions, the QFX formatting for NAME and MEMO might be different. If setting these options is done at the account level, the user wouldn't need to change settings before doing each import. Also, the user wouldn't have to remember each time which bank uses which settings. Another option would be the ability to have a template in the Import section which the user could select. ### Teaching and learning By exposing this feature on the Import screen, users would become aware of its presence. Additionally, adding this functionality to the documentation would educate users.
GiteaMirror added the featureneeds votes labels 2026-02-28 19:40:50 -06:00
GiteaMirror commented 2026-02-28 19:40:51 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 15, 2024):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@github-actions[bot] commented on GitHub (Aug 15, 2024): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
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 feature needs votes
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#1338
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?