Adrian Blake

We have suppliers that request a prepayment before the PO is shipped to us. We have been following the process of:

1. raising and posting a supplier payment journal for the prepayment
2. on the PO, settling the payment journal to the PO
3. the goods are received and the purchase invoice is received from the supplier
4. we create a pending invoice journal in D365 and match this up to the PO/GRN
5. when posted, if the pending invoice is manually created, the invoice will settle automatically against the payment journal
6. If the pending invoice is created via standard D365 DMF, using Vendor Invoice Header and Vendor Invoice Line data entities, then the automatic settlement to the payment journal

We have raised this as a bug in the standard D365 software, but have been requested to raise this as an idea. As the majority of our supplier invoices are created in D365 using DMF we would sorely like this fixed as there is a risk of double paying suppliers £10Ks by mistake. Also, I suspect, any supplier invoices created using the new Automation process may suffer the same problem.

We have a requirement where the Project Manager/Purchasing Team will purchase stock for a specific project to utilise during its life. We would like to be able to raise a PO for a project, receive the stock in and have the stock reserved for the project solely to use in the future via Project Works Orders, Project Sales Orders, or Project Item Journals.

In D365 Project Management & Accounting you can raise Project PO's for stock and non-stock items. When receipting a Project PO for stock items the system (when the PMA parameter Create Item Requirement is set to Yes and Item Consumption is set to No) asks the user if they wish to consume the stock immediately - No creates an Item Requirement Journal which hard reserves the stock and then consumes the stock on Invoicing. There is currently no good method in D365 of: reserving stock for a project for later use by the project.

We would prefer the following design:

• Have a new stock tracking dimension called Project
• For a Project PO for stocked items, when receipting the stock in populate the Project stock tracking dimension with the Project ID
• When receipting the stock do not create the item requirement journal
• In the Stock Reservation forms - warn or prevent users from reserving stock where the Project stock tracking dimension value is different to the Project WO, SO, Item Journal that the reservation is for
• A further enhancement would be to have the ability on Project PO line to state that the stock is being purchased for multiple projects with an initial allocation quantity for each project
• Stock can easily be transferred from 1 project to another by using a Stock Transfer Journal to move from Project A to Project B

Happy to discuss this at any time or hear other people's opinion on this approach.

We have a requirement where a boxed item is received in to the warehouse with components that need to be stored in a variety of temperatures. The box and its components need to be linked together so they can be putaway in different storage temperatures but on picking of a Sales Order or Works Order they can be effectively bundled together. It is effectively undoing a bundle on receipt and then on picking re-bundling it back together.

It would be good if D365:

1. Had the ability to state a released product is an "Unbundled item"
2. On receipt could unbundle the box in to its components (using say the BOM to hold the components for a box) and create/attach the same batch/serial ID to each stock item.
3. On sales orders extend the existing bundling functionality to make sure the same batch/serial IDs is picked
4. On works orders extend the picking and reservation functionality to make sure all the same batch/serial IDs for a unbundled item are picked/reserved

Happy to discuss this concept in more detail

Kind regards

Adrian

On our projects, we know the milestones up front as these are generally agreed upon, but who pays for each milestone changes during the life of the project. For example, initially Customer A may pay for the 1st 5 milestones, but then they transfer ownership over to Customer B to complete the project.

In D365 PMA, the system supports the creation of the Funding Sources and when the Milestones are created they take the Funding Source that applies at that point in time. If the Funding Source changes from Customer A to Customer B then the Milestone will keep its original Funding Source. Currently when a project changes its Funding Source we have to delete all the open milestones and recreate them against the new Funding Source.

We would like a PMA Parameter or Project Contract parameter for "Calculate Funding Source on Invoice Proposal". This would mean when running the Project Invoice Proposal it will look at the current Funding Source and Rules on the Project Contract when deciding who to invoice rather than the historic Funding Source and Rules held on the Milestones when they were 1st created.

Any queries on this please let me know

Kind regards

Adrian