Importing project estimates on the project contract line details is calculated differently to the manual creation of project contract line details.

MS ticket raised for this idea.TrackingID#2404240050001707. Details as below.

Hello, Hieu.

I hope you are well!

Our Product team has advised that this is the current expected system behavior because from the screenshots, it appears that a day is 7.5 hours, so 2.75 days gives 20.625 hours, which is rounded to 20.63. In the two contract line details (CLD), we can see that the imported one is priced in hours and the manual one in days.

When assigning to tasks, it creates a resource assignment that has contours, or day-by-day pricing. If viewed in the estimates tab, we should see 7.5 hours for days one and two, then 5.63 for day three, so when we import, it imports as hours rather than days. Thus, the calculation for the manual one is £475 * 2.75 days = £1306.25, while the other is 7.5 hours * 2.75 days * £475 / 7.5 hours. While the two equations are functionally the same, we round 20.625 hours to 20.63 which then gives us the difference.

So, to sum up, this is a rounding issue which could likely be mitigated by adding additional decimal places. Our Product Team has begun doing this in other areas.

There is a fix coming, likely in a release which should be released by the end of June, that will key off the currency precision. However, this will not help in your case as it's the quantity field that is causing the rounding issue. It's currently set to a precision of 2 decimal places meaning even with the currency precision fixed, multiplying by the quantity will still be a problem.

They will add a suggestion/design change request to up the quantity precision to 4 decimal places for CLDs, QLDs, estimate lines, and possibly resource assignment contours (If it's also 2 decimal places, it will just get imported as that even if the CLD/QLD quantity is fixed).

Looking forward to hearing from you!

Kind Regards,

Kristian Hadzhiyski