Approval workflows should protect the decision
Compare two example purchases under a configured 50,000 IQD approval threshold. The same rule gives different outcomes for 36,000 and 60,000 IQD.
Below the threshold → held exception → dated approval
Compare two example purchases under a configured 50,000 IQD approval threshold. The same rule gives different outcomes for 36,000 and 60,000 IQD.
1 · 36,000 IQD proceeds
P00003: purchasing user 9 confirms six units at 6,000 IQD through the native record API. The order is confirmed; received and billed quantities remain zero. The screenshot is the manager view of the resulting record.
2 · 60,000 IQD waits for approval
P00004: the same non-manager purchaser confirms ten units. Native status is To Approve because the amount exceeds the configured threshold. The purchaser cannot approve; scoped manager user 7 can. The retained exception note names that reviewer and the next check.
3 · Native reviewer decision is retained
User 7 selects Approve Order in the native UI. The history retains the 3 October 05:38 transition to Purchase Order and the original purchaser note. Receipt and billing remain zero; no supplier email, physical receipt or payment was made.
