Vivienne Le

Reapproval rule for purchase orders does not working as expected.

• If any changes are made that affect the Total Amount—such as tax, quantity, etc—the workflow is reassigned to another user.
• If changes are made to other fields that do not impact the Total Amount, the workflow proceeds with auto-approval.

Based on our documentation and logical expectations, the Reapproval Purchase Order Rule in Purchasing Policies should function as follows:

• If a field listed in the “Selected” panel is modified, the workflow should trigger reapproval.
• If a field in the “Available” panel is changed, the workflow should proceed with auto-approval.

Our Expected Behavior:

• Any changes that impact the Total Amount (e.g., tax, quantity) should cause the workflow to be reassigned for reapproval.
• Changes to other fields that do not affect the Total Amount should allow the workflow to auto-approve.

To align with this logic, we have included the following fields in the “Selected” panel:

• Accounting Distributions.Changed
• Purchase order lines.Net amount
• Purchase orders.Currency
• Purchase orders.Requester

All other fields remain in the “Available” panel.

The Product Group has suggested removing the Accounting Distributions.Changed field from the “Selected” section.

But this recommendation may not be acceptable for our customer. Removing this field could allow users to add additional charges without triggering reapproval, potentially leading to unauthorized approvals and payments—posing a risk of misuse.

Please kindly fix this issue in a future update to ensure the reapproval logic works as intended and maintains necessary financial controls.