Dynamics 365 Project Operations

If Sales prices for hours are invoiced without a full currency amount (e.g. 120,50) and no full hours (e.g. quarter hours and three-quarter hours), D365 rounds the decimal places at line level.

This can lead to differences in cents adding up in the total and an incorrect invoice amount being issued in relation to the sales price per hour.

Example: One hour has a sales price of $127.50. The service is invoiced with three items of 0.25 hours, 0.75 hours and 1 hour. The total of 2 hours is $255, but the individual lines are rounded up and the invoice amount is $255.01.

The more positions with 3 or more decimal places, the more the difference is added up. A manual change is not possible.

In connection with eInvoicing, which will be mandatory from 2025 in Germany for B2B-transactions, the check leads to the invoices not being accepted and rejected. It is not possible to change this logic with the rounding settings in the system.

The rounding rules must be adjusted in order to comply with legal requirements.

In the Estimates tab of the project table, output the unit cost price and unit sales price by member and task to Export.

This feature is not currently implemented.

The addition of this feature will improve the experience for users.

We cannot use in France the Expense management Addin for OCR if we are in the French LCS.

We must be in the Europe LCS.

Can we have the possibility to have it available in the French lifecycle services.

When customer retention is set to decimals, the calculation fails somewhere. The project invoice total amount becomes a penny different than the revenue in calculated tax.

For example,

with customer retention 7,5% on a project invoice

Header

Invoice amount: 6,805,505.96

Gross margin: 5,444,404.77

Invoice proposal transaction summaries

Invoice line amount: 5,885,843.00

Retention: 7,5%

Customer retained amount: 441,438.23 (actually 441,438.225)

Amount less retention 5,444,404.78

Posted sales tax

Amount origin: 5,444,404.78

tax: 25%

Calculated sales tax amount: 1,361,101.19 (actually 1,361,101.195)

amount origin + calculated sales tax amount = 6,805,505.97

The problem is that this causes problems in in xml validation tools, which fails with the following error message:

Document not a valid Electronic invoice, failed in validation for document type. 

The error message is due to amount + calculated sales tax is not equal invoice total amount.

To sort this out today, you need to 1) send to external provider for validation, 2) receive the error message, 3)re-invoice and manually adjust retained amount so the penny difference no longer appears, and 4) resend.

Alternatively, the XML-file can be adjusted manually, causing penny difference between actually invoiced and stated in Dynamics.

The cost of this issue for one of our clients is at least 10.000USD per year, due to increased validation and resending of invoices. This does not include the labour cost for adjusting manually the xml files and re-uploading a new file.

This was reported to Microsoft as an issue, but it was declined - as they deem it too complex to fix and they believed it is an uncommon issue. However, it happens every month for our client.

Introducing a feature in Project Operations that sends automated email notifications to team members when a task is assigned to them. This enhancement will improve task management and ensure team members are promptly informed about their responsibilities

Scenario: In our organization, we frequently deal with multi-year tasks where both cost and sales rates are updated on an annual basis. To improve our operational efficiency and maintain better traceability of changes, we propose the following enhancements to the Price List management and recalculation features within Quote lines and Project Contract Lines:

• Currently, if we have a Project Task spanning across two Fiscal years (for example November 2023 to February 2024), and we have two Price Lists, Price List A(2023) with effective dates 1/1/2023 to 31/12/2023 and Price List B(2024) with effective dates 1/1/2024 to 31/12/2024 the Project estimates calculated on the Project Master record are correct.
• The Project Estimates are calculated as follows:
• November and December 2023 estimation is calculated with the rates specified in Price list A(2023)
• January and February 2024 estimation is calculated with the rates specified in Price list B(2024)
• The Total Estimation is accurate.
• However, when we import the Project Estimates to a Quote/ Project Contract line, the Estimation is calculated using only Price list A(2023), meaning that:

1. Project Estimation is not aligned with Quote/ Project Contract Estimation
2. If we do an Uplift of the rates in 2024, our estimates in the Quote/Project Contract are underestimated as Project Operations only calculates the estimate based on Price List A(2023)

• Our proposal is for the Quote/Contract line to support the use of multiple Project Price lists for each line, where the estimation is calculated according to the Effective periods of each Price list, which is similar to the Pricing Engine already used for the Project Estimations.

An error messages (Unable to find a unique worker record corresponding to the entered values) occurs when carrying out a project adjustment if a project validation is used in Project Parameter and setup for category/resources validation lookup.

The option is available to be use in the system and support our business processes. such scenario shouldn't pose any error message in the system.

The issue needs to be address and fixed.

We would suggest that the system would be able to process project hour journals in the "Project management and accounting" module in D365 F&O as efficiently as possible. If a journal of +5000 lines would be processed more efficiently if split in 15 journals, and run in batch, we would recommend the system would process the job in that way. Hence, when a user initiates the posting of a journal, the size of the journal should have a minimal impact on performance.

Add possibility to create a new batch order (process manufacturing) out of project.

User would like to have a method of passing reallocation journal for project materials because the current method for adjustments is treating the adjustment as a return to stores and re-issue. 

They need a workable solution that does not change the price of the items that were already issued as these would be historical transaction.