Dynamics 365 Project Operations

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.

When creating a sales order from a Time & Material (T&M) project, the commission transaction is recorded with a settlement method of "On invoice", even though the Accounts receivable parameters are configured for "On payment". This behavior differs from what is observed when creating a standard (non-project) sales order.

Without it, users need to track the settlements of the invoices extra system, in order to pay commission to Agents.

The Consumed posting method in the Project accounting > Production parameters doesn't allow having a Costing sheet to be configured.

Therefore, there is no way to include surcharges such as Overhead as part of the cost for the item that is produced.

The alternative would be to configure Indirect cost components within the Project accounting module to add indirect cost when a specific type of transaction is posted.

However, Indirect cost components are not supported when direct Production order transactions are posted.

Suggestion: Add functionality that will create the Indirect cost amount in a posted Project transaction when the Production posting method is set to Consumed and the appropriate Cost category is posted within the Production order. If an Indirect cost is configured for that Cost category, it should create the indirect cost even though the Transaction origin is Production-consumed.