[Bug]: Transaction not synced with Gocardless, has no transactionId #2495
Comments
|
👋 First of all: thank you for providing all this data! It's much easier to help if all the necessary logs are provided.
Are you sure your friend has made the payment? Has it cleared? I find it strange that you can make a payment request to a 3rd party and that it would affect your ledger prior to actually receiving the funds (i.e. what happens if you make a 10m payment request from your friend? Does that temporarily make your balance go up by 10m?). After receiving the monies from your friend and the transaction clearing (in a few days from today I guess?) - does the -- Internally the problem is that We might need to add some logic here to trim the But this is dangerous as it is a breaking change that can impact other users of Actual. Would need to be careful. |
Thanks for the explanation. To answer your questions: the payment request is created in my bank app, and only shows up in the transactions once someone actually pays. The payments are always instantly (all Dutch banks support SEPA instant) received. So the transaction I tried to sync is the final transaction, there is no clearing involved as it's always instant and only shows up (becomes a transaction) when someone pays. |
|
What's the institution ID for this bank? We could create a custom bank mapper for it to trim the |
The institution ID is ASN_BANK_ASNBNL21. Thanks! |
|
👋 I was chatting with @kyrias and he noted that according to GoCardless documentation the Which leads us to believe the patch should actually be on GoCardless side. Could you reach out to their support and see if they can patch it on their side? Thanks |
|
👍 I've send in a ticket to support about this. I noticed that basically all the 'internal' transactions (paid payment requests, account fees, interest payments) have transaction ID " ". When I send in the ticket I saw this support article. Why does Actual not use the internalTransactionID? It seems that one is truly unique and already filtered by GoCardless for duplicates. |
|
Just got a response from GoCardless. They suggest to use the internalTransactionID;
|
|
Because it didn't exist when the GoCardless (or then Nordigen) support was added, and switching at this point would need to be done very carefully to not break existing users. The options I can think of are:
Also, I find it so annoying how GoCardless support responses to their API not working the way it's documented is always for you to implement random work-arounds rather than them cleaning up the data to correspond to their own documented schema. |
MatissJanis
added
help wanted
|
+1 to @kyrias Ideally we should push more on GoCardless here to either patch it on their end or update the documentation to reflect the reality ( I will also leave this issue open in case anyone wants to pick up the refactors to gracefully switch over to |
|
Just as an observation from my Nationwide account I sync via GoCardless, it doesn't look like internalTransactionId is populated until the transaction is booked. Pending {
"transactionId": "xxxx",
"bookingDate": "2024-04-19",
"bookingDateTime": "2024-04-29T12:31:29Z",
"transactionAmount": {
"amount": "-3.75",
"currency": "GBP"
},
"creditorName": "xxxx",
"remittanceInformationUnstructured": "xxxx"
}Booked {
"transactionId": "xxxx",
"bookingDate": "2024-04-18",
"bookingDateTime": "2024-04-18T00:00:00Z",
"transactionAmount": {
"amount": "-3.75",
"currency": "GBP"
},
"creditorName": "xxxx",
"remittanceInformationUnstructured": "xxxx",
"internalTransactionId": "xxxx"
},The GoCardless docs don't seem to mention this at all, and I'm unsure whether it's inconsistent between different banks.
|
Verified issue does not already exist?
Is this related to GoCardless, Simplefin or another bank-sync provider?
What happened?
After syncing bank transactions with Gocardless, I noticed that one transaction was missing due to the balance not adding up to my current balance when I check it in my bank app. I had this issue before when initially setting up Actual and syncing the past 3 months, but figured it had to do with historic data and corrected it manually.
What I noticed is that this particular transaction doesn't have a transactionId, it shows:
"transactionId":" "in the log, where all the other transactions have some value shown there. Seeing that the transaction shows up in the log (both browser and server) and the current balance also matches, it seems the data is complete, but not shown/processed in Actual. The transaction in question has entryReference 20240320-90950171.Server log:
Browser log;
The transaction in question is a 'Payment request'. You can send these using the bank app to other people with a link so they can pay you. In this case it was a friend paying me back for a concert ticket.
I run Actual v24.3.0 as a Home Assistant add-on.
What error did you receive?
None
Where are you hosting Actual?
Other
What browsers are you seeing the problem on?
Chrome
Operating System
Windows 11
The text was updated successfully, but these errors were encountered: