Monia MENG Miss

Below description about prepayment is from D365 Finance Learn Document.

Multiple prepayments definitions on a purchase order aren't allowed. If you need to allow multiple prepayments on a purchase order, post the payments using the payment journal instead of a prepayment invoice.

But in our business process, doing multiple prepayments for 1 PO is a must. Anyone has a better solution for this kind of situation? Thanks all!

According to our internal business, we want one of the FD show less FD value for a specific main account type, but whole FD values for other main account type, in the same legal entity, at the same time.

For example, we have 1 account structures, including 2 FD. The 2nd FD should not show "000" FD value in the pull-down list, when the order/journal are using main account (type = P&L). At the same time, in the same legal entity, both 1st and 2nd FD should show all FD values, when the order/journal are using main account (type ≠ P&L).

How to achieve that?

Situation:

We create a new PO with budget checking. We set a deferral template, and this PO will apply it. When posting the PO Invoice, the invoice deferral tag is "Yes", and the deferral schedule will auto-generate for this PO invoice. However, the PO budget will be released at the same time. When we decide to recognize these deferral lines, the budget checking will be triggered again.

Error:

If we don't recognize the deferral schedule as soon as the PO invoiced, the released budget may be occupied by other procurement action. And we cannot see the records in budget control statistics table. It is unreasonable.

Requirements:

1. We hope budget control statistics table can have a column to show the budget used by "PO invoiced-deferral schedule-active".
2. Budget control statistics table should reserve the budget, do not allow it to be released for other procurement, after deferral generated.

Situation:

If the PR workflow has been rejected by any approver, the workflow will show [Submit] when back to the workflow requester. It is reasonable.

If the PO workflow has been rejected by any approver, the workflow will show [Resubmit] when back to the workflow requester. It is unreasonable, should be changed.

Error:

If the user clicks [Resubmit] in PO, the workflow will continue to the approver who rejected. It won't go from the very beginning, which means it may skip some conditions before.

Requirement:

1. The PO workflow should show [Submit] like PR.
2. The PO workflow should start from the very beginning.

Currently, only before we post PO invoice journal, we can see the deferral tag in the PO invoice draft. After the PO invoice posted, no tag in PO invoice can prove that it has been ever deferred.

Requirement:

PO invoice journal need some fields to show the deferral details, such as deferral schedule number.