Dynamics 365 Project Operations

I have requirements to financially post discounts to a different GL on projects. The discounts would be coming from item requirement sales orders. I would like to see the Category Groups and Project Category Groups extended to be able to specify a GL account for discounts, similar to what is currently available for item group setup for sales orders.

Adding financial tags to the expense report experience (similar to Accounts Payable) would allow us to post valuable data to the General Ledger that is not possible today.

When a Task on a Project is deleted, the operation initially seems successful as there is no user feedback and the Project is saved however after some time if we return to the Project, we get an error that says the task cannot be deleted. This should be improved with better user feedback so that the user is aware if a Project Task cannot be successfully deleted and for what reason this has failed immediately rather than after some time has passed.

In Project Operations for Manufacturing environments (Previously Project management and accounting module in D365 for Finance & Operations). there is a function for Vendor Retention. You can assign retention terms to a project. Then, when Project purchase orders are created for that project and an invoice is generated, the retention amount is automatically calculated. When this happens, the cost associated to the project is the full amount of the invoice MINUS the vendor retention amount. Then the rest of the invoice (The retained amount) is part of the project cost once the retention invoice is posted.

This seems incorrect. The project cost amount should be the full amount of the invoice. It would seem that just because an amount is being retained from the vendor doesn't mean that it is not due and still part of the project cost. The offset, after all, is a payable (just split up between retention and accounts payable). And when the retention invoice is posted, the posting just moves the amount from retention payable to accounts payable. This entry does not seem to correlate to adding the cost to the project at this point.

This is not to mention that this causes issues in being able to reconcile your project balance against the associated ledger balance for project costs until the final retention invoice is posted.

I would suggest that the project transaction amount on the initial invoice with retention should match the full invoice amount. Then when the retention invoice is posted it should have no effect on the project cost.

In standard project intercompany expense and hour process, the system creates a pending vendor invoice in the project legal entity. On the pending invoice line we can see the intercompany resource being populated and we can post the invoice.

However, when the user wants to code an expense invoice via the pending vendor invoice form manually, the project resource field shows only local resources. In a situation where the expense is related to an intercompany resource (such as flight tickets paid in the project entity) we would need to link the expense to the resource from another entity.

Expected result: Intercompany resources are available for selection on the pending invoice line when coding project costs manually.

When intercompany time writing is activated between two entities, the intercompany resources are visible in the project resources list. However, we cannot select the intercompany resources on a project contract funding rule.

This means that we can define resource specific funding rules for local resources, but the same logic is unavailable for people writing time via an intercompany timesheet.

Expected result: Intercompany resource can be selected on project project contract funding rule.

When we create a project invoice proposals with billing rules we will pass the constant start date, end date and invoice date.

When running this in recurrence batch mode on daily basis the system checks for the same dates which we supplied on the parameters for all days.

if we try to use (DayRange(-30,0)) in query range against Project date but it is not getting filtered out.

if we try to pass future date in start date and end date field it is throwing an error “End date cannot be later than current date of legal entity's time zone.”

as per the limitation of our product we cannot run this in recurrence batch mode.

The idea is to provide a feasibility to supply dynamic values for start date, end date and invoice date so that invoice and other dates will get updated regularly if it was running in recurrence batch mode.

A project resource is available in both the legal entities USSI and GBSI. Assigned with required Project and categories.

While creating intercompany timesheet in USSI, categories should show in the dropdown list if the Category/Resource validation is set to Mandatory under PMA parameter in intercompany(GBSI).

In Finance, all grid views are able to be filterable with ability to SUM/AVERAGE/MAXIMUM/MINIMUM.

In Proj Ops, grid views are not able to be filterable with a subtotal ability.

Idea: to align with Finance and allow grid views subtotals.