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 #80638
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#80638
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.