Enhance OFX import
Currently the only usage for the OFX import is to import an archived acces with associated accounts/transactions. Upon import it creates a new access.
This is quite limited since some users:
- would like to import old transactions into an existing access/account (not shown on the bank's website but available as OFX for example)
- don't have a woob connector for their bank and would like to regularly import an OFX file, always in the same access/account (I know some of them plan to do that and then change the accountId in the database themselves, some others have to use a manual account and recreate the transactions)
We might solve this by having several features, which could be useful for other things.
-
Upon import, choose on which access (user should be able to select "new") to import the accounts (creating new accounts on this access). -
For a given access, allow to merge two accounts. see #267 (closed) -
If the account vendorId in the OFX matches one of the account vendorId in database for this access, automatically merge the accounts. This should be something that the user requires (as this might create duplicates)
That way, one could import old transactions on an account (1+3 ideally) or at least import the accounts in the access and then merge the accounts that need it (still quicker than recreating the transactions manually each month and easier than manually editing the database).
I did not speak about Kresus exports files because:
- they can have several accesses
- I don't expect people to import an old "backup" in a new running one (and wanting to merge accesses)
Edited by Nicolas Frandeboeuf