- The customer tries to submit a workflow it reflects with the error message below:
Stopped (error): Accounting distribution validation failed. Please recall purchase order workflow and rectify accounting distributions. This action can only be completed after the line number 10 is fully distributed.
- While checking the lines we found all lines are distributed.
- Throw investigation we found a raised fix request related to that error, it will not be fix and there is a workaround had been provided
- Our customer tested the workaround that had been mentioned in the fix request, and it did not resolve the issue as expected, please find the feedback below:
if we Disable the Parameter Auto Calculate Totals and Accounting Distribution from Accounts Payable Parameters -> General -> Purchase Order Workflow, this will also affect all PO's with actual errors in distribution that we would like the system to stop. For example if a PO is missing a financial dimension as Department, we need the PO to stop in WF and give a warning to correct the PO before approval. If this stop/validation is skipped, we will have issues later in the process when trying to post PO against vendor invoice. The error we have reported now is a bug and should be taken care of.
- As a result for the above please advise with another workaround as the mentioned did not fit our customer gap.
Comments
This issue has a direct impact on the reliability of workflow validation in the purchase order process. Although all lines are properly distributed, the system returns an erroneous validation failure, preventing workflow submission.Our customer confirmed that the proposed workaround (disabling Auto Calculate Totals and Accounting Distribution) is not viable. It introduces a functional gap by bypassing critical distribution validation checks, which are essential to prevent downstream errors during invoice posting — such as missing financial dimensions.This behavior contradicts the intended integrity controls in D365FO and poses a significant risk to data quality and process control. The issue appears to be a regression or unresolved bug rather than a configuration gap and should therefore be prioritized for a permanent resolution in the standard product.We strongly urge Microsoft to reconsider and address this as a product defect, or at minimum provide an alternative workaround that preserves standard validation logic while allowing submission of POs that are in fact correctly distributed.
Category: Procurement and Sourcing