35
For companies working internationally with purchase and sales in various currencies, the Jobs module way of handling currency is far to limiting.

The main problem is not being able to budget costs in LCY and enter Billing lines in another currency. Either you enter ALL planning lines in LCY and have the amount converted to Invoice Currency, or you enter ALL lines in FCY, thus being forced to convert your budgeted costs to FCY.

But it should be possible to enter planning lines in whatever currency you want - both billable and budget!

Example (LCY = DKK):
A project could encompass budgeted costs in GBP, EUR etc. (exchange rate unknown at creation time) , while invoicing the customer in USD. Now you cannot follow up on differences between expected and actual budgeted currency amounts in this case - you would have to keep a separate record somewhere else - not good!

Most fields and functions are available in the table but need to be reworked - especially in the transfer to invoice and invoice posting objects.
STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for your feedback. Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future. 

 

Sincerely, 

Jodi Christiansen 

PM, Microsoft 


Comments

A

I insist on this request. Actually it could even be considered as a bug the fact the job planning lines of the project must be managed with a single currency code when it is clear that purchases can be done with multiple currencies for a single project.

Another topic which is a bug for me as well, is the fact that the field "Invoice currency code" on the jobs table is only used when creating a new sales invoice and the amount on the job planning lines (for billable type) are managed in local currency and converted to foreign currency only when the invoice is created. Which means there is no way, upstream, to preview the unit and total price in foreign currency before actually generating the invoice...except if we change "Currency code" field in the job card but in these case it will apply to all budget and billable lines. Total nonsense. And finally, we can add the fact that all flowfields in job tasks are showing LCY values (FCY values only displayed in the jobs statistics which is clearly a shortcoming).

Anyway, a huge rework is stronly required on this module.

Category: Project Management

A

We have 2 clients with this exact requirement. We need to be able separate the Fx gain/loss from controllable gains and losses in the project and it's impossible to do that if we cannot plan in multiple currencies.

Category: Project Management