Comment 10 for bug 514305

Well, I am not up to changing or extending account.journal objects, in any way. This is because, if somebody would correct some bug or adds functionality in methods... This will render us into big trouble.

I see functionality of account_bankning starting and stopping right with account.journal, bankning should interact with accounting module, but nor replace it. If we make step into accounting, then we will have to make another step, and another step...

I see no big problems with the way we are now finding the journals. Only thing have to be that if we search on journals that serve default currency, they should be searched for, by both - explicitly set currency and False...
If we search for journals that serve other currencies we have to search only those with explicitly set currencies. It is simple as it looks like.

I see, that we are now close to operational module, we just need to make it workable.

The next step would be, making it understand other specific transaction types, like direct debit etc. This would be for nearest future. For bigger plans, we can consider building interface for directly connecting banking systems, for sending and receiving transaction requests. This would be interesting for companies that will want to work synchronously with their customers, like distributors etc.