If a client requests us to switch their currency on their account, that all previous invoicing remain in the old currency and new invoices will be shown in the new currency. From an accounting purpose, this is a huge issue with the archived information not matching what currency they paid in, and this should be retained for perpetuity.
It would also be helpful if the client could set on a product level, not on a client level, what currency they wish to pay in.
Merged Ideas
currency per invoice - add field to database determine the payment currency type
Hello,We have customers that they pay sometimes with eur, sometimes with usd. To set the currency to the invoice, not to the customer will be best update and will finish the currency problemsThank you
72 Comments
Login to post a comment.
This is a *HUGE* mess.
Changing the currency for a client resulting in all past invoices (paid or not) going to that currency as well is ridiculous. It shouldn't work like that at all, and it is a bit strange for an accounting tool to have such a major bug inside of it.
If a client moves from USA to Europe for example, or vice versa, and now wants to pay in that currency: it should be possible! Without all the trouble.
It also causes issues for business owners within the EU as they will have to do a currency conversion for every payment not received in EUR by clients living within the eurozone and having to pay taxes...
This must be fixed.
As far as I know, this feature can be implemented if the PHP code checks for the value on invoices "Unpaid" and the issue is solved. WHMCS should only change them on this invoices and not others. All other invoices with a status which is not "Unpaid" should be skipped and its currency symbol untouched.
Another example is someone moving to another country. Lets say they move from Europe to the states and want now their current account in USD.
Said this, currently its a major accounting mess.
Changing the currency changes the currency symbol on past invoices which is a bug. Since if the customers paid 120$ in one invoice, and 12$ in another invoice, you changed his account to Euros and now it says he paid 120EUR and 12EUR.
This is a major bug. Paid invoices [u]should not have their symbol changed[/u] and problem solved. Open invoices would change to the current new EUR value in this example but PAID/CANCELED invoices should not be touched. It seems rather than a feature request this is a WHMCS bug. It changes the currency symbol on all the invoices for that customer.
How hard can it be to make a pre-check on the PHP code that runs this?All it needs to do is skip the invoices that have the status PAID/REFUNDED/CANCELLED.
Let's suppose that he pays from Italy an invoice of [u]1000 EUR[/u]. Now he moves to UK and the invoice becomes of 1000 GBP which is [u]1176 EUR[/u]. Next month he goes to Japan and his invoice becomes of 1000 YEN which is [u]8 EUR[/u], in China [u]124 EUR[/u], in Chile [u]2 EUR[/u], in Iran [u]0.06 EURO[/u].
It's absurde! A Japanese could order a service of 1000 YEN then download the invoice via proxy from Italy and voilà . Now he gets an invoice of 1000 EUR which is 992 EUR higher!
Let's suppose that i'm a client and that i place an order of 1.000 USD. As soon as i pay i get my invoice of 1.000 USD. Then i pay for another service 2.000 USD. Now i have 2 invoices with a total amount of 3.000 USD.
+++ Individual income tax return +++
I change the currency of my account to EUR so that WHMCS replace $ with € in all my invoices. Now i can report that i've spent 3.000 EUR instead of 3.000 USD. With the current change rate i'll report that i've spent 3.938 USD! I though that with Invoice Fix i would be able to fix this issue since in "mod_invoicedata.clientsdetails" i can see that you keep a track of currency ID but i was wrong. Why don't you use it?
This is a really dangerous problem because clients can fake their individual income tax return by editing our invoices and we can get serious problems. It's not acceptable that clients can freely change the amount paid on their existing invoices.
Do you have any workaround? When do you plan to fix this very big problem?