Understanding why purchase orders get stuck — and how to manage the approval cycle right.
The Problem: A Workflow That Doesn’t Loop Back
In a recent test run of purchase order change management
in Dynamics 365 Supply Chain Management, something strange happened.
Change management was turned on. A proper PO workflow was in
place. The order was approved successfully.
Then a vendor response arrived — with updated quantities and
delivery dates. But when trying to accept that response, an error
appeared:
"Changes to the document are only allowed in state
Draft, because change management is activated."
The catch? The PO was approved, and there was no way
to bring it back to Draft. It couldn’t be recalled. It couldn’t be
edited. It couldn’t be updated. You’re stuck — and so is your procurement flow.
Why Can’t a PO Go Back to Draft?
Dynamics 365 is behaving exactly as designed — but not in a
way that’s always obvious.
When change management is active, edits after
approval require the PO to be returned to Draft so it can re-enter
the workflow. That’s how the system preserves approval integrity.
But here’s the twist: Not all changes actually trigger a
return to Draft, unless your organizational policy says so.
This is where the “Re-approval rules for purchase order
changes” come in.
The Missing Piece: Purchase Order Reapproval Policies
Navigate to: Procurement and sourcing > Setup >
Procurement and sourcing parameters >Purchasing Policies> Re-approval
rules for PO changes
Here, you define:
- Which fields
require re-approval when changed (quantity, delivery date, line amount,
etc.)
- Whether
the PO should return to Draft
- Whether
certain changes are allowed without workflow retriggering
If your policies don’t flag these changes to return the PO
to Draft, you won’t be able to edit anything — even from vendor responses. The
system is protecting the approval process, but it feels like a dead-end
to the user.
Reapproval Rule Purchasing Policy D365
Vendor Collaboration + Change Management = Locked Orders
Now layer in vendor collaboration.
When a vendor responds to a PO with an update (via the
portal), the system expects:
- You’ll
review that change
- The
system will update the PO accordingly
- Any
required reapproval will happen automatically
But with change management on — and no reapproval policy
for that change — the PO is approved and frozen.
This creates the frustrating loop:
- Approved
PO
- Change
comes in
- No
Draft status
- No
edit allowed
- No
recall
- Workflow
blocked
Own the Approval Loop with Policy, Not Panic
If you want flexibility and control:
- Review
the reapproval rule setup – flag the fields that should retrigger
Draft
- Decide
if vendor-submitted changes should push the PO back to workflow
- Train
your teams to recognize when a PO must re-enter the approval path,
not bypass it
By managing this through organizational policy, you:
- Preserve
compliance and audit integrity
- Avoid
confusion during vendor collaboration
- Streamline
corrections without breaking process discipline
It’s Not a Bug
What seems like a system error is actually a gap in
policy design.
If you’re stuck in the “approved-but-locked” PO loop,
the answer isn’t a workaround — it’s a setting. One that lets you decide what
counts as a major change, and who gets to approve it.
Set it once, train your team, and break the loop — before it
breaks your procurement rhythm.
Views expressed in this blog are personal and do not
represent Microsoft or any affiliated organizations.
