That may be, but there are valid reasons to use multiple journals per bank account. So I wouldn't count on it.
I suggest to increase the traceability instead of assuming manual conformity. Statements already have a link to the imported file, so by adding a link to the settings when creating an import file, one could check the bank account itself, which seems a much cleaner approach to me. One could even generate warnings about different import parsers used beforehand.
If you can wait, I'll fix this in a week or two. Otherwise, you can try it yourself and propose a fix here.
That may be, but there are valid reasons to use multiple journals per bank account. So I wouldn't count on it.
I suggest to increase the traceability instead of assuming manual conformity. Statements already have a link to the imported file, so by adding a link to the settings when creating an import file, one could check the bank account itself, which seems a much cleaner approach to me. One could even generate warnings about different import parsers used beforehand.
If you can wait, I'll fix this in a week or two. Otherwise, you can try it yourself and propose a fix here.
Thanks for reporting.