github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 15:14:02 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #1467] [Feature] Custom mapping Gocardless fields #114923

New Issue
Closed
opened 2026-06-11 05:15:07 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-06-11 05:15:07 -05:00
Owner
Copy Link

Originally created by @CharlieMK on GitHub (Aug 5, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1467

Verified feature request does not already exist?

  • I have searched and found no existing issue
    This feature request is related to https://github.com/actualbudget/actual/issues/1466 . However, 1466 is about a static mapping from the 'additionalInformation' field to the 'notes' field in Actual. This feature request on the other hand is about being able to make all mappings between Gocardless and Actual configurable.

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

Not all banks expose the same fields via their apis (see https://developer.gocardless.com/bank-account-data/transactions).
Some banks (mine for example) use the additionalinformation payload for adding quite some information in json formatted objects. Other banks may use different (sub)fields. We cannot expect the devs to keep up with all these bank specific information, while this information may be very valuable to the users of Actual.

Describe your ideal solution to this problem

We could solve this by adding two enhancements:

  1. [optional] allow users to create fields
  2. allow users to create mappings between the gocardless API fields and the fields in Actual

Enhancement 1 is optional as the mapping feature would already be useful using the current fields (the notes field for example). However, it would probably be more valuable as otherwise users have a limited set of fields to map to.

Enhancement 2 would for allow users to configure custom mappings. For example, for a bank with institution ID 'FINTRO_BE_GEBABEBB' I have the following transaction list:

{
                "entryReference": "2023080520230805134410******",
                "bookingDate": "2023-08-05",
                "valueDate": "2023-08-04",
                "transactionAmount": {
                    "amount": "-75",
                    "currency": "EUR"
                },
                "creditorName": "NAME****",
                "additionalInformation": "atmPosName: NAME****, cardNumber: ******XXXXXX****, narrative: ['BETALING MET DEBETKAART', 'NUMMER ****', 'NAME ***', 'COUNTRY', '04/08/2023', 'VISA DEBIT - CONTACTLOOS', 'BANKREFERENTIE : 230805*****', 'VALUTADATUM : 04/08/2023']",
                "bankTransactionCode": "PMNT-CCRD-****",
                "internalTransactionId": "2eedbc23f037aa516c47***
            },
            {
                "entryReference": "20230805202308050315205*****",
                "bookingDate": "2023-08-05",
                "valueDate": "2023-08-01",
                "transactionAmount": {
                    "amount": "-3.5",
                    "currency": "EUR"
                },
                "additionalInformation": "narrative: ['MAANDELIJKSE BIJDRAGE', 'FINTRO BLUE', 'BANKREFERENTIE : *****', 'VALUTADATUM : 01/08/2023']",
                "bankTransactionCode": "ACMT-MDOP-****",
                "internalTransactionId": "bf414d977b1fbaed1ee75***"
            },

It would be great if I could manually configure that 'additionalInformation.narrative' should be mapped to the 'notes' field in Actual. Potentially, inspiration could be gotten from Homeassistant where it is possible to parse any value as if it is a json object: https://www.home-assistant.io/docs/configuration/templating/#processing-incoming-data. In my above example, the home-assistant way of doing it would then be:
value_json['additionalInformation']['narrative'] => notes

Teaching and learning

No response

Originally created by @CharlieMK on GitHub (Aug 5, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1467 ### Verified feature request does not already exist? - [X] I have searched and found no existing issue _This feature request is related to https://github.com/actualbudget/actual/issues/1466 . However, 1466 is about a static mapping from the 'additionalInformation' field to the 'notes' field in Actual. This feature request on the other hand is about being able to make all mappings between Gocardless and Actual configurable._ ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? Not all banks expose the same fields via their apis (see https://developer.gocardless.com/bank-account-data/transactions). Some banks (mine for example) use the additionalinformation payload for adding quite some information in json formatted objects. Other banks may use different (sub)fields. We cannot expect the devs to keep up with all these bank specific information, while this information may be very valuable to the users of Actual. ### Describe your ideal solution to this problem We could solve this by adding two enhancements: 1. [optional] allow users to create fields 2. allow users to create mappings between the gocardless API fields and the fields in Actual Enhancement 1 is optional as the mapping feature would already be useful using the current fields (the notes field for example). However, it would probably be more valuable as otherwise users have a limited set of fields to map to. Enhancement 2 would for allow users to configure custom mappings. For example, for a bank with institution ID 'FINTRO_BE_GEBABEBB' I have the following transaction list: ``` { "entryReference": "2023080520230805134410******", "bookingDate": "2023-08-05", "valueDate": "2023-08-04", "transactionAmount": { "amount": "-75", "currency": "EUR" }, "creditorName": "NAME****", "additionalInformation": "atmPosName: NAME****, cardNumber: ******XXXXXX****, narrative: ['BETALING MET DEBETKAART', 'NUMMER ****', 'NAME ***', 'COUNTRY', '04/08/2023', 'VISA DEBIT - CONTACTLOOS', 'BANKREFERENTIE : 230805*****', 'VALUTADATUM : 04/08/2023']", "bankTransactionCode": "PMNT-CCRD-****", "internalTransactionId": "2eedbc23f037aa516c47*** }, { "entryReference": "20230805202308050315205*****", "bookingDate": "2023-08-05", "valueDate": "2023-08-01", "transactionAmount": { "amount": "-3.5", "currency": "EUR" }, "additionalInformation": "narrative: ['MAANDELIJKSE BIJDRAGE', 'FINTRO BLUE', 'BANKREFERENTIE : *****', 'VALUTADATUM : 01/08/2023']", "bankTransactionCode": "ACMT-MDOP-****", "internalTransactionId": "bf414d977b1fbaed1ee75***" }, ``` It would be great if I could manually configure that 'additionalInformation.narrative' should be mapped to the 'notes' field in Actual. Potentially, inspiration could be gotten from Homeassistant where it is possible to parse any value as if it is a json object: https://www.home-assistant.io/docs/configuration/templating/#processing-incoming-data. In my above example, the home-assistant way of doing it would then be: value_json['additionalInformation']['narrative'] => notes ### Teaching and learning _No response_
GiteaMirror added the feature label 2026-06-11 05:15:07 -05:00
GiteaMirror commented 2026-06-11 05:15:10 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 5, 2023):

✨ 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:1666555990 --> @github-actions[bot] commented on GitHub (Aug 5, 2023): :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 -->
GiteaMirror commented 2026-06-11 05:15:12 -05:00
Author
Owner
Copy Link

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

🎉 This feature has been implemented in #4253 and will be released in the next version. Thanks for sharing your idea! 🎉

<!-- gh-comment-id:2659404426 --> @github-actions[bot] commented on GitHub (Feb 14, 2025): :tada: This feature has been implemented in #4253 and will be released in the next version. Thanks for sharing your idea! :tada: <!-- feature-implemented-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
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature
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#114923
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?