Evidence and reconciliation

A request marked executed still needs a check against its posted movements. The Inventory Supervisor runs reconciliation against the request’s authorized quantity. A matching posted movement total writes a verified operation receipt. A mismatch writes a failed receipt and leaves the request unchanged. The receipt identifies the source request, quantity, event and operation key, giving the team a specific result to investigate.

The receipt register includes recorded, verified, failed and corrected evidence. Failed receipts belong in an active follow-up queue. The supervisor can inspect the linked request, posted movement ledger and any reversal to find the difference. A replay of reconciliation uses the same stable operation key and returns the existing result rather than manufacturing a second verification. This is especially useful after a page timeout or an API retry.

Review decisions and record attachments give context to the quantity result. The reviewer rationale explains why the accepted units and disposition were authorized. A photo or document can show what inspection found. The Auditor can follow the request from return grade to decision, movement and receipt without relying on a verbal explanation. The evidence trail also distinguishes a posted stock effect from a grade that was approved but never executed.

• Decision evidence. Keep reviewer rationale and relevant attachments with the source request.
• Quantity check. Compare posted signed movements with the authorized request amount.
• Failure follow-up. Use the failed receipt to find the cause and check the authorized next action.

Agree which supervisor owns reconciliation and when it should run after execution. Decide how failed receipts are reviewed each day and what explanation is recorded for a compensating movement. Set a practical attachment convention so a condition photo can be found from the request rather than stored in a separate inbox. Give auditors read access to the registers while keeping stock actions and corrections with operational roles.

A return was approved for eight units, but the posted movement trail nets to seven after a correction. Reconciliation writes a failed receipt and does not change the request. The supervisor reviews the ledger and decides whether another stock correction or a change to authorized scope is needed. After correcting the source of the difference, the supervisor checks the movement trail and receipt before deciding the next authorized action. The failed result remains useful history; it explains why the first check did not verify completion.

• Failed Operation Receipts — Find mismatches and rejected actions that need investigation.
• Operation Receipts Register — Read the recorded and verified results beside the earlier failures.
• Review Decisions Register — Confirm who decided the request scope and why.

Read reconcile and correct and release and execute.