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.
Comments
For my clients this also will solve most of additioanl manual work. Main functionality of projects sholud be budgeting in one currency (ex EUR) and invoicing is in local currency. Thats the most of cases how it works in markets outside Euro/USD zone, so contrants are in EUR, USD, GBP, but invocicin are in LCY.
Category: Project Management
I'd like to second the original idea and all other comments made here. I have just recently encountered all of the limitations outlined here while configuring a proof of concept solution for our customer. Simply put, we need to be able to specify the exchange rate and currency code for all Job Planning Lines so that resulting Sales Invoices and related Purchase Invoices calculate correctly.The Job Planning Line does have a "Currency Date" field but even this does not seem to accomplish one would expect (derive an exchange rate based on a date other than the posting/document date of the resulting invoice. Nor does it allow you to specify different rates for different Jobs (as mentioned in several comments above).
Category: Project Management
In my opinion problem is also that actual costs are always - whatever document/source currency (SCY) - converted using system currency rates to first local currency (LCY), and then second to project currency (PCY). In my view, we are lacking the option to see total cost values per job ledger entry in SCY. This is not just a job module issue, this has been the case always for Navision on eg. general ledger entries. Other smaller system keeps SCY value on entries, so why can't we. In other cases, you may need to be able to maintain LCY to PCY or SCY to PCY rates directly on a job, if requested by the customer that's billing to. I have a project now where this is case, and we maintain rates as dictated by an external part in a custom tables where rates are defined by job.
Category: Project Management
This will solve all of my clients problem when it comes to job invoicing. They have an agreed exchange rate with the customer and since the Currency Factor is un-editable, it makes it very hard for them to invoice the client. There will be more instances where jobs will be multi-currency because of how the global market is now working. Please consider this functionality for the next update.
Category: Project Management
I agree !
We have several clients with this exact requirement.
Category: Project Management
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
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
Business Central Team (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