← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 591961] Re: historical currency rate support

 

Hello Samuel I. (Toradex),
          I have gone through the issue but could not face the error. I describe the steps followed by me:
             I have company currency set with EUR.
              1)  I setup foreign currency Rs (INR) with 2 different dates and rates:
                 a) 2010/11/24    -  50.0000
                 b) 2010/01/01   -   59.9739
              2) I create an invoice with date 2010/11/24 and with currency Rs and confirm it.
              3) I check in the Journal Entries menu, and the entries show the debit and credit amount calculated as 2 EUR which is on the basis of the latest exchange rate for this currency. It seems to work in a normal way.
              4) Then, I create an invoice with date 2010/01/05 with currency Rs and confirm it.
              5) Now, the journal entries show the debit and credit amount calculated as 1.67 EUR which is on the basis of the exchange rate as on 2010/01/01. This also seems to work in a normal way.

Thanks




** Changed in: openobject-addons
       Status: In Progress => Invalid

-- 
historical currency rate support
https://bugs.launchpad.net/bugs/591961
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Addons Modules: Invalid

Bug description:
It looks like OpenERP can not manage to choose the correct historical currency exchange rate. If we create a booking entry por a past date, the system will always use the latest exchange rate for this currency instead of using the currency rate for this period. 
This is not acceptable.

Background:
We have a multi-currency setup of OpenERP with two foreign currencies. We are updating the exchange rate every month so we have a clean currency history. There are cases when we have to enter bookings for a past date/period using the historical exchange rates in the system. This simply does not work.
 
Please confirm this bug.