xrg wrote:
cyberglobe wrote:
You still don't understand what I am saying.
3: If you input your ratecard, A2B will consider your ratecard as CAD and NOT as USD.
That's exactly how the system is supposed to behave!
Since you know that, you should have converted the ratecard (eg. with oocalc) to CAD *before* feeding it to the system. It is dead simple.
Keeping amounts in the database in anything else than base_currency is a bad idea, IMHO: Not only the db will have to do additional processing all the time, but a system it is bound (with a bug) to fail and result in messed up amounts. Keeping it simple (just one currency internally) is trivial and helps the programmers not do mistakes.
You still don't understand what I am saying.
By putting the currency in the Ratecard, it should, on a daily cron job, automatically adjust the currency of the call to reflect the current price per minute. I still want to work with one currency being my base currency but I want to have the cron job to "automatically adjust" the base currency rate of the rate card which I got from my provider in USD or EUR. Therefore, a daily converted rate field would be included with the current per minute rates there.
The system will spend 1 second ONCE in a day to compute the new daily rates of the ratecard from the existing exchange rate in A2B and therefore make the minor adjustments needed to ensure no loss in funds due to exchange rate swings.
Imagine in 1 month, your currency takes a swing of 50%. Your rates are only 20% from your month's base start. You would have to pay the remaining 30% of the funds from your pocket and you are at a negative income. If you had to handle 100,000 minutes in calls, at your cost of $0.15/min and you charge $0.18/min at the start of the month, and by the time you have to pay your provider it costs you $0.225/minute that would cost you $22,500 instead of $15,000. You only made $18,000 and now you are at a loss of $7,500. Yes, I am being dramatic here but in certain countries that can happen.
Just would like to see that 2 fields are added accordingly, Currency for ratecard and converted rate pricing. Also the cron job would update the converted rate pricing from the ratecard ONCE daily and therefore it would NOT do more than 10 seconds of additional processing time in a month.
I am following the Keep it simple path, By ensuring that it is simple and protects everyone from any potential increase/decrease in foreign exchange and ratecards. If you want to lose $75,000 and have no profit for a month, by all means do so. I would rather ENSURE that I am getting my daily cut from the provider without needing to run manual processes on my servers to adjust rates and cause errors in the system. The Base ratecard is the default price it would get the converted rate from.
The thing is that I only have USD ratecards available to me and no CAD ones from my providers. I have to convert it therefore I need it to follow the current currency exchange.
xrg wrote:
Money fluctuations and exchange rates .. Confused That is a complicated issue:
Consider *where* a2b gets its rates from. Is that the *exact* rate you are paying in? Do you pay the terminators every day or at the end of the month, on that instant rate?
Take an example: You are buying from a weird country, in WEIRD, say. You agreed to pay them in those rates. Today, rate is 0.50, so the customer does a 2.0 WEIRD call and you charge him $ 1. But, at the end of the month, you try to pay the terminator and the rate is 0.60, so you have to spend $1.20 to pay him. Doesn't it get very complicated already?
Exchange rates may be complicated for you, but in all honesty, it is easy for the rest of the world.
That is why by having the system manage via a daily cron to update the converted ratecard's per minute charge, I can manage this better and reduce my loses. Also, by offering my clients the lowest possible price, they know that they are getting the best pricing even though it fluctuates. Instead of paying a fixed high rate and not worry about the fluctuations. Today everyone looks at who is the cheapest. If you are not cheap in price, don't expect much business. This offers the best way to manage the lowest pricing with ensuring your clients pay you properly for the fluctuating currency exchange rates.
Basically, the simple way to fix this is:
1: When importing have a dropdown list field 'Ratecard Currency'.
2: After importing, it would run a script that will take the current exchange rate from the currency table and update the field 'converted per minute rate'
3: Have a cron daily job to simply convert all ratecards per minute charges to the 'converted per minute rate'
Not to hard to do, barely uses any CPU resources and you have a daily fluctuating per minute rate chart.
I found one provider who offers CAD rates however he charges a 50% premium in comparison to his USD rates. Why should I pay that premium and reduce my profits when I can have a system that can handle it with a simple inclusion.
A2B has the engine to do it, all they now need is to simply adjust it for the ratecards and presto, we don't need to worry about it anymore. International A2B owners would be happy to get more profits into their pockets.