-
Notifications
You must be signed in to change notification settings - Fork 20
N26
N26 is a german Startup based in Berlin. It offers bank accounts in some European countries. https://n26.com/
---
ynab:
access_token: # (required) ynab access token
budget_id: # (required) budget_id
cash_account_id: # (optional)
accounts:
- dumper: :n26
iban: # (required) iban of your bank account
ynab_id: # (required) account id in YNAB (last id in the URL)
username: # (required) email
password: # (required) password
skip_pending_transactions: (optional: default is false) see explanation
set_category: # (optional: default is false) see explanation
The values should be written in quotes. For example password: "!mySuperSecret%Password^374"
.
The momo field in YNAB will be populated with a combination of the reference text and the city of the transaction provided by N26.
Only import transactions that are processed. This option will prevent duplicates. For more information about why this configuration flag was introduced please check out PR #38. Please note that this will result in longer waiting times (a few days) until transactions show up. It won't be 'real-time' anymore.
Set the transaction category to the N26 category. Only makes sense if you have the N26 categories set up in your YNAB.
- It currently only fetches the last 100 transactions. Please open an issue or PR if you want to change this. For now I didn't see the use case for it.
- Some transactions might show up again a few days later. This is due to a problem on N26's side. The creation-timestamp if a pending and processed transaction changes sometimes which results in a duplicated transaction. But you will notice the duplication so you just need to reject the second transaction. To avoid duplicated transactions please set the config flag
skip_pending_transactions
totrue
.
Do you think something is missing or incorrect here? Please open an issue for it to be addressed.