This program converts the Dutch rabo csv file for non-business customers to the financial records of OFX for GnuCash or for HomeBank. The csv file is available for download for each customer.
I release this software under Copyright and with the user license of GPL version 3 of which the text accompanies the software.
Open a terminal in the directory where you downloaded the csv file.
Then use the program on that file. It will create an OFX formatted file
in a subdirectory with the same filename and extension of csv replaced by
ofx. The directory can be explicitly specified through the argument -d or --directory
or it has ofx as default. For HomeBank it has ofx_hb as default.
Example (GnuCash):
Output to ofx (GnuCash version)
TRANSACTIONS: 248
IN: 2018-008-transactions-30-12-to-26-09.csv
OUT: 2018-008-transactions-30-12-to-26-09.ofx
accountnumber processed skip sum
NL01RABO0123456789 1 16 17
NL02RABO9876543210 231 0 231
-
The output file is an OFX compliant xml file that GnuCash or HomeBank can process.
HomeBank needs all transactions, including the "internal transfers". It then concludes which transactions are internal transfers.
GnuCash will not automatically recognize internal transfers and these transactions will be included into the system twice. As this is undesirable, for GnuCash the system automatically skips transactions for the subordinate accounts to or from the main accounts.
Remark: only for GnuCash
Since version 2.10 the program uses a config file denoting accounts to be downloaded. An example file is available. Be sure to register your accounts in the config.
The files you download will have transactions for both accounts. Where a transfer from config.account1 to config.account2 is present, there will be 2 transactions:
- One from the perspective of config.account1
- One from the perspective of config.account2
Without measures, these transactions will be registered in your ofx file twice, as different transactions, causing havoc in your bookkeeping systems.
To prevent double transactions, for all transfers between config.account1 and config.account2, the program will only translate the transactions from the viewpoint of the first account in config. This is indepedent of whether they are in the same download or not.
It means that transfers between config.account1 and config.account2 will only show up if and when config.account1 is downloaded (config.account1 precedes config.account2 in the config file). In a file with only config.account2, the transfers will be skipped, i.e. not transferred to the ofx file.
Be sure to create a config file. An example file is present in the distribution. Remember: order is important.
Remark: only for GnuCash
For accounts not in config, if they are in the same download file, transfers will only produce one of two transfer transactions. These unknown accounts will never transfer to a known config account. For multiple unknown accounts, transfers between the unknown acounts will register only the first account processed.
This is a risk, and thus the program warns if an account is in the download file, that was not in the config file. Please make sure to always have the accounts you download in the config file.
-
The program was developed for a checking account.
-
The program can process multiple accounts per file. If processing gets slow, you could choose to download only one account per file. It reads the input once per account. But beware of transfers.
-
The FITID up until 2018 is a construction of transaction data (amount, date etc). From 2018 the Rabobank starts using a serialnumber that is unique per account.
-
The file assumes each account is a checking account. This may not be true for all your accounts, but the program has no way of knowing this.
-
The default directory is ofx. You can specify a different directory in the argument '-d'. The default for HomeBank is
ofx_hb. -
Some of the OFX entered data is fake, like signon-data and at the end of each account balance amount or balance date. There is no question of any logon session going on, but the OFX file needs the info.
The Rabo has decided to present non-business users with an unusual and unnecessary problem. For business users the field "datum" (date) is filled with "boekdatum" (the bookingdate). This is what one expects. However, for non-business users the Rabo fills "datum" (date) with "verwerkingsdatum" (the date the Rabo processed the transaction). These dates often differ and is not what one expects or would want for a bookkeeping system.
There is no rational explanation for this difference, but there are consequences for users with a non-business account. The first consequence is that selection is no longer based on the bookingdate, but on the processing date. For end of year payments, the processingdate is usually the next year. So selecting payments for a strict period (month, quarter, year), no longer works as expected.
The second consequence is that your bookkeeping will show the wrong date had I used 'datum' instead of 'rentedatum' (interestdate). Again, think of end of year payments. The bookkeeping program would attribute them to the wrong year.
For that reason I use interestdate in stead of date. It is not what I want and it does not make sense, but the Rabo forces this anomaly. I have contacted them through email april 2018. I have saved the email correspondence to date as a pdf file but have had no further response, neither a correction of the csv-file contents. I don't expect the Rabo bank to care enough to change anything unless more people complain or the problem becomes public. Public image sometimes can sway corporations where customers can not.
If anyone has remarks, please create an issue on the github repository gbonnema/rabo2ofx. If anyone feels like improving the code, please fork the repo and issue a pull request.
I usually just copy the python script rabo2ofx.py to /usr/local/bin and the man page in the man
subdirectory rabo2ofx.1 to /usr/local/man/man1 and then I am done with it.
There is no need to compile or build anything as python is a script interpreter.
I have no idea whether this program will run on ms windows. It should, but I haven't tested it. Also, I guess the man page is irrelevant to ms-windows.
If you are running linux on ms-windows, in theory you should be able to use the linux instruction.
Sept 2019, Guus Bonnema.