FAQ

Are recurring transactions handled or matched?

Unfortunately, the official YNAB API currently can't create those kind of transactions and there is no way to match them.

Current solution: You can always reject imported transactions if you notice that it already exists.

I entered my transactions manual until now, will the script create duplicates if I use it for the first time?

Yes it will. This is because we don't fetch your entered YNAB transactions. What we do is to generate a hash which we send to the API. If that hash is the same then the transaction won't be imported again. But your manual entered transactions don't have this hash in the YNAB database which means that the first time you run the script you will have to do some cleanup.

Recommended approach: When you imported the transactions they won't be cleared. That means that you can reject the ones that you already entered manually and approve the ones you don't have yet.

How far in the past will the script import my transactions?

This depends on the Dumper. For N26 only the last 100 transactions will be imported. For the other dumpers it will take the transactions from the last 30 days.

Note: The idea here is that the script is ran on a regular bases so you don't miss any transactions. The limit is set to not accidentally mess up your entire budget in case something goes wrong (even through we don't expect anything to go wrong). Would be pretty bad if you would have to fix all your transactions from the last 3 years, no? That's why we decided to only take the last 30 days or last 100 transactions.

How do I find out the fints_endpoint for the FinTS / HBIC dumper?

You can find out more about that on the FinTS / HBIC documentation.