Execution and verification answer different operating questions. The clerk needs to know whether the approved action changed the lot balance. The supervisor needs to know whether the posted movement total matches the request's authorized quantity. Keep the operation evidence for both questions.
Inventory Clerk confirms the request's item, lot context and authorized quantity with the physical evidence. Agree the meaning of the signed effect before execution; a load state cannot substitute for this stock check.
Inventory Clerk runs the receive-or-move workflow. It posts stock movements, adds signed quantity to the lot's quantity on hand, marks the request Executed and writes a Recorded operation receipt. Source effect key derives from the request identity so repeated execution does not post the same effect again.
Inventory Supervisor runs reconciliation against the request's posted movements. Matching authorized and posted quantity produces verification evidence. A mismatch writes a Failed receipt and leaves the request unchanged; verification does not manufacture the missing movement.
Inventory Supervisor traces the request, decision and movements to choose supported correction or reversal work. Auditor reads the original and follow-up evidence. Repeat verification using the documented stable operation key behavior and inspect the returned result.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.