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

[GH-ISSUE #1466] [Feature] Map Gocardless 'additionalInformation' field to notes. #7484

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

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

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/1467. However, 1467 is about a customizable mapping from any Gocardless field to any field in Actual. This feature request on the other hand is about a static mapping between the 'additionalInformation' field in Gocardless to the 'notes' field in Actual.

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

I have an integration with bank FINTRO_BE_GEBABEBB using Gocardless. Two example transactions where no (un)structured information was added to the transaction look like this (I masked some information):

            {
                "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***"
            },

A third one where the (un)structured info field was not empty is the following:

            {
                "entryReference": "2023080820230808080******",
                "bookingDate": "2023-08-08",
                "valueDate": "2023-08-08",
                "transactionAmount": {
                    "amount": "300",
                    "currency": "EUR"
                },
                "debtorName": "NAME****",
                "debtorAccount": {
                    "iban": "**********"
                },
                "remittanceInformationUnstructuredArray": [
                    "TEST ****"
                ],
                "additionalInformation": "endToEndReference: NOTPROVIDED, narrative: ['INSTANTOVERSCHRIJVING IN EURO', '****', 'MEDEDELING :', 'TEST ****', 'BANKREFERENTIE : *****', 'VALUTADATUM : 08/08/2023']",
                "bankTransactionCode": "PMNT-RRCT-****",
                "internalTransactionId": "33bcdc207b1f9960574034c****"
            },

The information of the 'remittanceInformationUnstructured(Array)' is mapped to the notes field, but the info in the 'additionalInformation' field is not. However, the additionalInformation field contains valuable information needed to categorize spendings in case the (un)structured field is empty.

Describe your ideal solution to this problem

I would like the notes field to contain the following:

trans.remittanceInformationUnstructured ||
((trans.remittanceInformationUnstructuredArray || []).join(', ')) ||
((trans.additionalNotes || []).join(', '))

From https://docs.google.com/spreadsheets/d/1ogpzydzotOltbssrc3IQ8rhBLlIZbQgm5QCiiNJrkyA/edit?pli=1#gid=489769432 I understand almost all other banks also use the additionalInformation field, though not necessarily the 'narrative' subfield.

The different items from the narrative subfield can be joined together with any delimiter. My preferred delimiter would be a semicolon. The value of the notes field from the first transaction in the example above would then become:
BETALING MET DEBETKAART; NUMMER ****; NAME ***; COUNTRY; 04/08/2023; VISA DEBIT - CONTACTLOOS; BANKREFERENTIE : 230805*****; VALUTADATUM : 04/08/2023

Note: I would be fine if simply the 'additionalInformation' field instead of the 'additionalInformation.narrative' field was mapped to the notes field in Actual. This is probably more useful to other users, whereas the subfield 'narrative' is potentially only useful to Fintro bank clients.

Teaching and learning

No response

Originally created by @CharlieMK on GitHub (Aug 5, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1466 ### 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/1467. However, 1467 is about a customizable mapping from any Gocardless field to any field in Actual. This feature request on the other hand is about a static mapping between the 'additionalInformation' field in Gocardless to the 'notes' field in Actual._ ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? I have an integration with bank FINTRO_BE_GEBABEBB using Gocardless. Two example transactions where no (un)structured information was added to the transaction look like this (I masked some information): ``` { "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***" }, ``` A third one where the (un)structured info field was not empty is the following: ``` { "entryReference": "2023080820230808080******", "bookingDate": "2023-08-08", "valueDate": "2023-08-08", "transactionAmount": { "amount": "300", "currency": "EUR" }, "debtorName": "NAME****", "debtorAccount": { "iban": "**********" }, "remittanceInformationUnstructuredArray": [ "TEST ****" ], "additionalInformation": "endToEndReference: NOTPROVIDED, narrative: ['INSTANTOVERSCHRIJVING IN EURO', '****', 'MEDEDELING :', 'TEST ****', 'BANKREFERENTIE : *****', 'VALUTADATUM : 08/08/2023']", "bankTransactionCode": "PMNT-RRCT-****", "internalTransactionId": "33bcdc207b1f9960574034c****" }, ``` The information of the 'remittanceInformationUnstructured(Array)' [is mapped](https://github.com/actualbudget/actual/blob/master/packages/loot-core/src/server/accounts/sync.ts#L376) to the notes field, but the info in the 'additionalInformation' field is not. However, the additionalInformation field contains valuable information needed to categorize spendings in case the (un)structured field is empty. ### Describe your ideal solution to this problem I would like the notes field to contain the following: ``` trans.remittanceInformationUnstructured || ((trans.remittanceInformationUnstructuredArray || []).join(', ')) || ((trans.additionalNotes || []).join(', ')) ``` From https://docs.google.com/spreadsheets/d/1ogpzydzotOltbssrc3IQ8rhBLlIZbQgm5QCiiNJrkyA/edit?pli=1#gid=489769432 I understand almost all other banks also use the additionalInformation field, though not necessarily the 'narrative' subfield. The different items from the narrative subfield can be joined together with any delimiter. My preferred delimiter would be a semicolon. The value of the notes field from the first transaction in the example above would then become: `BETALING MET DEBETKAART; NUMMER ****; NAME ***; COUNTRY; 04/08/2023; VISA DEBIT - CONTACTLOOS; BANKREFERENTIE : 230805*****; VALUTADATUM : 04/08/2023` Note: I would be fine if simply the 'additionalInformation' field instead of the 'additionalInformation.narrative' field was mapped to the notes field in Actual. This is probably more useful to other users, whereas the subfield 'narrative' is potentially only useful to Fintro bank clients. ### Teaching and learning _No response_
GiteaMirror added the feature label 2026-04-10 17:20:17 -05:00
GiteaMirror commented 2026-04-10 17:20:19 -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:1666553580 --> @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 -->
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
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#7484
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?