Comment 14 for bug 514297

Ad 1) Generally speaking: yes, but there are limitations, as coercion is required.

Ad 2) This is exactly what should be altered in scenario 1 from comment #12.

Ad 3) I don't understand. A bank statement is nothing but a message envelope for transactions done in a certain time period, possibly even from a number of accounts sharing the same holder. When you import these in digital form, you can't prevent multiple currencies to appear in a single bank statement, unless the import scheme uses a 1:1 mapping between bank statement and bank transaction, which narrows the reporting window to the time frame of a single transaction, as MT940 does. So, what are you trying to tell?

Ad 4) Possibly. An alternate approach would be the split up of bank accounts into multiple currency accounts. Using the defaults as modeled now, you should be able to map journals to currency accounts. No need for searching then. These are both just implementation choices.

Ad 5) I do not agree. OpenERP is fit for multiple currencies in a one time coercion scenario, but not for the parallel multiple currency aka non-coercion scenario. This kind of dynamic / external coercion would take a major system overhaul. Ignoring this would create all sorts of real life problems. For starters: Suppose you imported a transaction done in EUR and let OpenERP convert it to LVT using the current exchange rate. In reality nothing was coerced, you only let OpenERP suppose you did. When you later actually convert the two currencies, using a different exchange rate (the current rate on that date/time), where do you leave the differences?

Ad 6) This is only acceptable when coercion takes place based on the currency of the transaction. Right now, that is not the case. It suspects all transactions to be in a single predefined currency, but doesn't check. This is a major accountancy leak.