mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-15 22:54:03 -05:00
[GH-ISSUE #7799] [Feedback]: Enable Banking bank sync provider #100619
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#100619
Reference in New Issue
Block a user
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?
Originally created by @matt-fidd on GitHub (May 11, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7799
Implemented in https://github.com/actualbudget/actual/pull/7345
cc @AurelDemiri
@ProtoxiDe22 commented on GitHub (May 11, 2026):
Hello, i'm testing the flow, i have found a couple minor problems with it.
initially i tried setting up the integration with a non-complete setup on enable banking (the eb application was not activated), however, actual didn't report any errors in the frontend, and when trying to link accounts, nothing would just show up when trying to select the bank.
The logs (understandably) contained this
actual_server-1 | 2026-05-11T17:37:52.729Z actual:enable-banking:errors Enable Banking API error: status=403 body={"code":403,"message":"Application is not active"} actual_server-1 | 2026-05-11T17:37:52.730Z info: POST 200 /enablebanking/aspspsresetting the enable bank credentials from the bank sync page, the frontend throws an error, but in reality the request went through just fine and the credentials were reset. I couldn't find anything relevant in the js logs, and the server logs just reported the successful request
actual_server-1 | 2026-05-11T17:39:15.157Z actual:secrets-db setting secret 'enablebanking_applicationId' to 'null' actual_server-1 | 2026-05-11T17:39:15.164Z info: POST 200 /secretOn the last step of linking the account, the frontend (correctly) preselects an account to link. However, the confirm button of the modal is disabled, and only enables if i click "remove bank sync" and then "set up bank sync" on the same account
after re-selecting the account in actual, the button is enabled correctly and the flow terminates just fine.
I use this occasion to thank the author for their work, and the maintainers for (finally :) ) merging this.
@daneov commented on GitHub (May 12, 2026):
What happened?
I was trying to set up banking using the
sha-e479c84-alpineimage when going through theSet up bankingflow with Enable Banking credentials. I selectedEnable Banking -> Set upand provided the Application IDsome_uuidtogether withsome_uuid.pemreturned by Enable Banking.Expected: the banking setup flow completes successfully and linked accounts are available.
Actual: the flow fails during authentication/setup on Firefox, but works on Chromium even though the application details are set exactly the same.
Error message:
As far as I can see from the code, this would only happen if something is going wrong with the
userTokenfrom session storage. This seems to be browser specific, maybe some API needs to be called just a bit differently?How can we reproduce the issue?
Enable Bankingin the feature flagsBank sync<uuid.pem>file, as provided by Enable BankingUsing the same steps in Chromium works, potentially (but unverified) pointing to using a webkit-specific API? Unsure.
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Firefox
Operating System
Linux
@emiltb commented on GitHub (May 12, 2026):
I was able to connect to Enable Banking and link it to my account.
A minor detail, that I noticed, is that the list of banks to select from is not sorted - that would be a nice touch and make it slightly faster to find the bank you need.
Even though my account was linked and during linking it showed the right balance, I was not able to succesfully sync it and got a network-error.
When trying to sync to an existing account in Actual:
When trying to sync to a newly created account in Actual:
I'm in doubt about how this works in terms of my network setup and the callback-url. Does that need to be accessible from outside the network for this to work? I host my edge test-instance locally, and the URL is only available internally. I tried briefly opening my test instance up to outside access, but that made no difference.
Edit: I just tried linking accounts over again, but to no avail. I noticed this time, that it actually also gives an error, so it never successfully links the account, with basically the same network-failure as above.
Browser: Tried both Firefox and Chromium
OS: Linux
Environment:
edge-alpineas of 2026-05-12 (I'm not completely sure of the exact version) image in docker, through caddy reverse proxy@geekuality commented on GitHub (May 12, 2026):
Works fine for me, using Firefox 150.0.1 on a Mac to access Actual on a Linux server over https. Actual installed from NPM
@actual-app/sync-server@26.6.0-nightly.20260512.@geekuality commented on GitHub (May 12, 2026):
But now what I came here to do, actual feedback: There is something funny happening with confirmed future payments (on an account) and holds (on a card), the upcoming charge amount is put into "deposit" and screws up things. I don't know yet what happens when the upcoming payment is turned into a real statement entry or a hold matures into an actual charge.
Here is an example of an account that has two upcoming charges from it (turned running balance on to highlight the effect):
My current enviroment is listed in the post above.
@Tatcher00 commented on GitHub (May 13, 2026):
It worked without any problems for me. I’m using a Linux server running 26.6.0-nightly.20260512.
Tested with Chromium. The connection via Enable Banking worked without any error messages once I’d linked my bank.
All transactions were synchronised correctly (German bank DKB)
Thanks for your work
@oskardotglobal commented on GitHub (May 14, 2026):
Runs perfectly with one of my banks (German DKB) as reported by @Tatcher00, but my other bank Berliner Sparkasse refuses to sync:
(Linking works though)
@matt-fidd commented on GitHub (May 14, 2026):
Out of interest, are there any logs in your server logs?
@oskardotglobal commented on GitHub (May 14, 2026):
No, unless I have to enable debug logging or something?
@tylerlinquata commented on GitHub (May 14, 2026):
The "start date" when creating a new, linked account seems to be ignored. I selected 5/13/2026, but it appears that the entire transaction history of the account synced (371 uncategorized transactions).
@geekuality commented on GitHub (May 14, 2026):
I'm now getting errors with one bank (S-Pankki, Finland), but only for two of several accounts there.
EDIT: It is also a bank holiday today in Finland, if that would matter - can't figure out how it could.
@geekuality commented on GitHub (May 14, 2026):
You do. Set env
DEBUG=actual:enable-banking:appto activate debug only for this plugin.@emiltb commented on GitHub (May 14, 2026):
Where to add that? I tried adding it as en var to my compose.yml and redeployed my edge-server, but saw no difference in the log output.
@emarforio commented on GitHub (May 15, 2026):
Tried out the bank sync and have to say that I love it! This is the first integration that I have gotten to work with EU banks. I have tried out the web interface as well as the JavaScript API and no issues at all using my Swedish bank. Great job!
@Calychas commented on GitHub (May 16, 2026):
Hey! Thanks a lot for the feature!
I had no problems linking 5 accounts with Erste Bank Poland (former Santander Bank Poland), both personal and business accounts, and Revolut as well
@insomniacslk commented on GitHub (May 18, 2026):
Worked just fine with N26 and Revolut. When adding Fineco Italy, a traditional bank, I get an empty list of accounts after successful authorization of the main account, as per screenshot
@alcroito commented on GitHub (May 19, 2026):
Tried the new integration with N26 production account.
Noticed the following.
When syncing multiple accounts from the same bank, and setting up sync for all of them, transfer transactions between accounts are not properly set up.
Instead a new Payee gets created.
The one transfer at the bottom was manually created before syncing.
@riley211 commented on GitHub (May 19, 2026):
Unfortunately this only supports very limited banks in the UK - could we investigate using something like TrueLayer?
@filiptrplan commented on GitHub (May 19, 2026):
Same with OTP Banka in Slovenia.
@matt-fidd commented on GitHub (May 19, 2026):
I'd suggest that a first port of call on some of these issues would be to contact Enable Banking and see if they can provide any insight.
@mnogueron commented on GitHub (May 20, 2026):
You can check on EB console all the requests made by the integration. If you have errors, you can check EB's error, plus the bank layer error.
On my side, the initial pull worked flawlessly, now if I try to sync it fails and EB and my bank report an invalid
dateFromwith aWRONG_TRANSACTIONS_PERIODon EB's side.@geekuality commented on GitHub (May 20, 2026):
@matt-fidd @mnogueron Good pointers, I did find irregularities from EB request logs - did submit a support ticket there. 😌
@filiptrplan commented on GitHub (May 21, 2026):
Nevermind, it was a stupid mistake. I have a restricted production app and forgot to link the account in the EB dashboard first.
@insomniacslk commented on GitHub (May 21, 2026):
...I did the same mistake, thanks for catching that. Feedback for the developers: if there's an error message from EB, it could be bubbled up? Alternatively there could still be a warning from Actual that this could be caused by an account that hasn't been linked on EB
May 21, 2026 20:05:32 Filip Trplan @.***>:
@alanwflood commented on GitHub (May 22, 2026):
I've spotted on issue where Bank of Ireland will only allow you to log in as a business user, it gives no option to log in with a personal account.
@mnil commented on GitHub (May 22, 2026):
@mnogueron Do you know if this a problem with actualserver/EB integration or EB itself? I am getting the same problem, initial link and sync works, but the day after I get an error with
WRONG_TRANSACTIONS_PERIOD.@mnogueron commented on GitHub (May 22, 2026):
@mnil It seems EB obfuscate any query params which makes debugging impossible.
The initial calls shows the same call to a
/transactionendpoint to my bank withdateFrom=0000-00-00&dateTo=0000-00-00which works fine, but the next ones have the same params and fails.I have a strong feeling that these zeros are fillers.
Although, I also see that my app is flagged as restricted and I can ask to make it unrestricted. This is very blurry as to what it's supposed to do. Are you in the same situation?
@geekuality commented on GitHub (May 23, 2026):
I got a reply from EB regrding that
WRONG_TRANSACTIONS_PERIODerror:@mnil commented on GitHub (May 23, 2026):
thanks for this, I think it's likely it's and off-by-one error in the date handling so created a PR: https://github.com/actualbudget/actual/pull/7930
Not sure how to test it in production env though.
@mnogueron commented on GitHub (May 23, 2026):
I was about with my dev instance but now I'm having an
Invalid status PSU-IP-Addresson my dev instance.I'll create a ticket on EB's side.
@stevenhansel commented on GitHub (May 24, 2026):
I'm using Commerzbank, and there is a problem in the
"pending"transactions that all the dates object are empty.The Enable Banking API was successful and everything from the API side is working, only from the client side worker is failing, due to the empty dates.
I was able to resolve this temporarily by going to Bank Sync > Edit the Enable Banking Bank Sync Settings > Uncheck the Import Pending Transactions Checkbox.
The Pending Logs from the Enable Banking API:
Console errors from the Browser:
@mnil commented on GitHub (May 25, 2026):
@matt-fidd or @MatissJanis I have now tested this on my local instance and it fixes the problems I was having. Would be nice with a review before you cut the 2026.6 release.
@DmitriiGoi commented on GitHub (May 25, 2026):
i was using the feature from branch for one month, and found out no bugs, thx for the development, happy to have this feature in release version
@nickmansrob commented on GitHub (May 26, 2026):
Very happy to see this implemented! Found one small bug: when going to the bank sync page and clicking 'Link account' on an already existing, manual account and then following the linking process, I cannot click 'Link accounts' in the Link Accounts modal. The Actual Budget account was already prefilled since I use the 'Link account' button. When clicking on the account and selecting it again, the 'Link accounts' button became clickable.
@chrismin13 commented on GitHub (May 26, 2026):
+1 on this, plus we need some more docs before this goes in a production build, as it isn't clear that:
a) you can only find this via the browser for the server, not the app or locally
b) you need https working
c) you need to FIRST connect the app from Enable, then through Actual
And one more bug: the verification for the Application ID field isn't very strict, I had a
)at the end of my UUID and it was just accepted, leading to an empty list of banks after selecting my country, which took me a sec to figure out. Not a big deal, just something that could be easily solved and improve the experience for everyone.Thanks for your efforts!
@matt-fidd commented on GitHub (May 26, 2026):
If anyone feels like writing up some docs before this is released at the start of next month, that would be really useful!
@mnil commented on GitHub (May 26, 2026):
I wrote up something here: https://github.com/actualbudget/actual/pull/7961/changes#diff-b1eec69c3d5896824cacc6c465d172a5fbb2756894eb9c887c663d1bda4ec059
I don't consider them complete but not sure what else is needed, so please add feedback.