github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-21 06:31:58 -05:00
Code Issues 2.1k Packages Projects Releases 57 Wiki Activity

[Feature] Swap payee and memo when importing QFX #1461

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

Originally created by @colin-strong on GitHub (Oct 2, 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?

QFX exports from my bank have the payee and memo fields reversed. The <MEMO> field contains the specific payee, while the <NAME> field contains the generic transaction type (for example, "Point of sale"). I would like to be able to swap these values when importing QFX files.

I found a somewhat related issue (#767) in which @rafacla points out that other apps support this feature, and that it's a common standardization problem.

Here is an example QFX file:

example-statement.qfx.txt

(Remove the .txt suffix; I added it so that I could attach the file instead of copy-pasting the contents here.)

Describe your ideal solution to this problem

Implement a "Swap payee and memo" checkbox in the import dialogue.

This feature is supported in nYNAB:

https://github.com/user-attachments/assets/f5042195-972c-4a1a-a777-c65f7c2d56af

A workaround would be to export as CSV, and set the payee/memo columns appropriately.

Teaching and learning

No response

Originally created by @colin-strong on GitHub (Oct 2, 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? QFX exports from my bank have the payee and memo fields reversed. The `<MEMO>` field contains the specific payee, while the `<NAME>` field contains the generic transaction type (for example, "Point of sale"). I would like to be able to swap these values when importing QFX files. I found a somewhat related issue (#767) in which @rafacla [points out](https://github.com/actualbudget/actual/issues/767#issuecomment-1606264460) that other apps support this feature, and that it's a common standardization problem. Here is an example QFX file: [example-statement.qfx.txt](https://github.com/user-attachments/files/17235545/example-statement.qfx.txt) (Remove the `.txt` suffix; I added it so that I could attach the file instead of copy-pasting the contents here.) ### Describe your ideal solution to this problem Implement a "Swap payee and memo" checkbox in the import dialogue. This feature is supported in nYNAB: https://github.com/user-attachments/assets/f5042195-972c-4a1a-a777-c65f7c2d56af A workaround would be to export as CSV, and set the payee/memo columns appropriately. ### Teaching and learning _No response_
GiteaMirror added the featureneeds votes labels 2026-02-28 19:44:10 -06:00
GiteaMirror commented 2026-02-28 19:44:11 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 2, 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 (Oct 2, 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#1461
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?