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

[GH-ISSUE #4281] [Feature] payee bank account details #43469

New Issue
Closed
opened 2026-04-26 03:55:10 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-26 03:55:10 -05:00
Owner
Copy Link

Originally created by @DanielHabenicht on GitHub (Feb 2, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4281

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?

While importing data from finanzguru I noticed that actual does not ask for the payee account number which I find crucial to lookup historical transactions or find out if one already payed to a specific account.

Use Cases:

  • Look up if one has already paid an amount X to DE00 0000 1234 5678 1012 12
  • Find out to which account an amount was actually sent
  • better rules (e.g. a provider might use the same iban for each transaction but different transaction or payee details)

Describe your ideal solution to this problem

I don't know what would be the best option but I think adding a payee_reference field for each transaction would be sufficient. It could be filled with either IBAN, account number, or whatever is needed.

Teaching and learning

This field should be optional and added automatically when syncing with a bank accounts or adding transactions via import.
In the accounts table, it could be either shown by default or hidden from the view in the side menu.

One could discover the different account numbers by hovering over the payee or in the payee overview section where all account numbers for a payee could be viewed.

Originally created by @DanielHabenicht on GitHub (Feb 2, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4281 ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [x] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? While importing data from finanzguru I noticed that actual does not ask for the payee account number which I find crucial to lookup historical transactions or find out if one already payed to a specific account. Use Cases: - Look up if one has already paid an amount X to `DE00 0000 1234 5678 1012 12` - Find out to which account an amount was actually sent - better rules (e.g. a provider might use the same iban for each transaction but different transaction or payee details) ### Describe your ideal solution to this problem I don't know what would be the best option but I think adding a `payee_reference` field for each transaction would be sufficient. It could be filled with either IBAN, account number, or whatever is needed. ### Teaching and learning This field should be optional and added automatically when syncing with a bank accounts or adding transactions via import. In the accounts table, it could be either shown by default or hidden from the view in the side menu. One could discover the different account numbers by hovering over the payee or in the payee overview section where all account numbers for a payee could be viewed.
GiteaMirror added the needs votesfeature labels 2026-04-26 03:55:11 -05:00
GiteaMirror commented 2026-04-26 03:55:14 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 2, 2025):

✨ 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 👍!

<!-- gh-comment-id:2629410099 --> @github-actions[bot] commented on GitHub (Feb 2, 2025): :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#43469
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?