 |
little functional feature request
Hello CK,
I am entering a couple of vendor invoices denominated in USD whereas I keep
my accounting in EUR. When I edit a new vendor invoice, I would first enter
the corresponding exchange rate (jumping from box to box using the TAB),
then the lines corresponding to the vendor invoice. When I enter a new line
or refresh, the exchange rate that I had entered is replaced with the
default exchange rate stored in ck_currency.
Would it be easy for you to store the spot exchange rate in memory so that
it is not needed to enter it again when the "new line" or "refresh" button
is selected?
And in fact, unless I'm wrong, the ck_currency table is useful when you have
forward currency contracts. Then the accountant would do a journal entry
corresponding to the FX loss or gain based on the negotiated (default)
exchange rate. Because most people do only spot FX, this ability to keep a
value in the exchange rate while refreshing is a plus.
Keep up the good work.
Vince
Hi, Vince, Thank you for the enhancement request. It shouldn't be too difficult to
implement. However, just to clarify a bit,
The current design is that,
a) after initial entry to the invoice, po, so, quotation screen, or
b) if invoice, po, so, quotation currency had been changed (say EUR
to USD),
then the default exchange rate will be loaded from ck_currency.
Otherwise, the current exchange rate (default or manually entered) will
be retained after subsequent screen refresh.
I presume you are referring to case a) that after the initial entry to a
new screen, if an exchange rate had been manually entered, then that
exchange rate number should be retained after the next screen refresh.
This should be easy to add. However, for case b) (currency change), it
is easy to have the old (most likely wrong) exchange rate to slip
through if a fresh default exchange rate is not re-loaded from ck_currency.
Could you confirm if you are requiring only case a) modification.
Cheers,
CK
Vincent Cardon wrote: > Hello CK, > I am entering a couple of vendor invoices denominated in USD whereas I
> keep my accounting in EUR. When I edit a new vendor invoice, I would
> first enter the corresponding exchange rate (jumping from box to box
> using the TAB), then the lines corresponding to the vendor invoice.
> When I enter a new line or refresh, the exchange rate that I had
> entered is replaced with the default exchange rate stored in ck_currency.
> Would it be easy for you to store the spot exchange rate in memory so
> that it is not needed to enter it again when the "new line" or
> "refresh" button is selected?
> And in fact, unless I'm wrong, the ck_currency table is useful when
> you have forward currency contracts. Then the accountant would do a
> journal entry corresponding to the FX loss or gain based on the
> negotiated (default) exchange rate. Because most people do only spot
> FX, this ability to keep a value in the exchange rate while refreshing
> is a plus.
> Keep up the good work.
> Vince
Hello CK,
I believe that case (a) modification would be most useful for a majority of
cases (spot FX for online purchasing for exemple whereas you receive the
invoicein USD, look at your bank statement in EUR, take kcalc in KDE (i've
switched to XFCE on MDV2006 recently, a delight), take the ratio, and enter
it as the floating rate).
The feature whereas it tells you that you enter a widely different exchange
rate is useful. Thanks for the implementation.
Vince
On 9/20/06, C K Wu <c@cheerful.com> wrote:
> Hi, Vince,
> Thank you for the enhancement request. It shouldn't be too difficult to
> implement. However, just to clarify a bit,
> The current design is that,
> a) after initial entry to the invoice, po, so, quotation screen, or
> b) if invoice, po, so, quotation currency had been changed (say EUR
> to USD),
> then the default exchange rate will be loaded from ck_currency.
> Otherwise, the current exchange rate (default or manually entered) will
> be retained after subsequent screen refresh.
> I presume you are referring to case a) that after the initial entry to a
> new screen, if an exchange rate had been manually entered, then that
> exchange rate number should be retained after the next screen refresh.
> This should be easy to add. However, for case b) (currency change), it
> is easy to have the old (most likely wrong) exchange rate to slip
> through if a fresh default exchange rate is not re-loaded from
> ck_currency.
> Could you confirm if you are requiring only case a) modification.
> Cheers,
> CK
> Vincent Cardon wrote:
> > Hello CK,
> > I am entering a couple of vendor invoices denominated in USD whereas I
> > keep my accounting in EUR. When I edit a new vendor invoice, I would
> > first enter the corresponding exchange rate (jumping from box to box
> > using the TAB), then the lines corresponding to the vendor invoice.
> > When I enter a new line or refresh, the exchange rate that I had
> > entered is replaced with the default exchange rate stored in
> ck_currency.
> > Would it be easy for you to store the spot exchange rate in memory so
> > that it is not needed to enter it again when the "new line" or
> > "refresh" button is selected?
> > And in fact, unless I'm wrong, the ck_currency table is useful when
> > you have forward currency contracts. Then the accountant would do a
> > journal entry corresponding to the FX loss or gain based on the
> > negotiated (default) exchange rate. Because most people do only spot
> > FX, this ability to keep a value in the exchange rate while refreshing
> > is a plus.
> > Keep up the good work.
> > Vince
Hi, Vince, No problem. Will be added in the next release.
Cheers,
CK
Vincent Cardon wrote: > Hello CK, > I believe that case (a) modification would be most useful for a
> majority of cases (spot FX for online purchasing for exemple whereas
> you receive the invoicein USD, look at your bank statement in EUR,
> take kcalc in KDE (i've switched to XFCE on MDV2006 recently, a
> delight), take the ratio, and enter it as the floating rate).
> The feature whereas it tells you that you enter a widely different
> exchange rate is useful. Thanks for the implementation.
> Vince
|
 |
Add to del.icio.us |
Digg this |
Stumble it |
Powered by Megasolutions Inc
