1. Inventory Allocation Engine
  2. Features
  3. Evidence and reconciliation
Feature · Evidence and reconciliation

Evidence and reconciliation

Explain failed operations and verify that posted stock effects match authorized demand.

OverviewFailed Operation Receipts
Inventory Allocation Engine · Evidence and reconciliation

Failed Operation Receipts

Operation receipts

New
Receipt numberSource recordEventQuantityRecorded atOperation key
OR-50359SR-15689EVN-38582002 OctOK-353
OR-73924SR-55150EVN-89396001 OctOK-713
OR-84970SR-61289EVN-69360011 OctOK-178
OR-75538SR-89650EVN-85543005 OctOK-418
OR-95896SR-35433EVN-79315002 OctOK-432
6 of 6 records
EVN-385Operation receipts · OR-50359
Failed
Source recordSR-15689
Quantity820
Recorded at02 Oct
Operation keyOK-353
Failure reasonCut to length
Example screen with sample data

What you can do

Explain the operation before closing the case

Operation Receipts Register brings receipt number, event, source request and quantity together with recorded date, operation key and failure reason. Status distinguishes Recorded, Verified, Failed and Corrected. Operations Overview also highlights failed operation receipts beside stock and pending review decisions, helping Inventory Supervisor find the allocation that needs investigation.

A Recorded receipt establishes that an operation recorded a result; it does not replace completion verification. The reconciliation workflow compares a request’s posted movement total with its authorized quantity. If they do not match, it writes a Failed receipt and leaves the request unchanged. A supervisor must resolve the underlying stock work before treating the case as complete.

How the work is organized

Inventory Supervisor follows the receipt to its source request and inspects the linked stock movements. The review decision supplies the deciding person’s rationale and the revision considered. Attach a photo or document when it helps explain the physical case, retaining its upload date and link so Auditor can inspect the same evidence.

  • Operation identity. Operation key explains which action result is being retried or reconciled and helps prevent duplicate effects.
  • Decision identity. Source request and revision connect the approval outcome to the request scope that was actually reviewed.
  • Verification basis. Compare authorized quantity with effective posted quantities, keeping reversal references visible instead of hiding the earlier movement.

What to agree during setup

Agree how the supervisor distinguishes an insufficient-stock failure from a stale review or a completion mismatch. The event and failure reason should make the cause understandable. Assign the follow-up to a named person and decide how the clerk learns the next permitted action. Review the unresolved cases together during the pilot.

Define the reconciliation treatment for signed effects and compensation with representative requests. Inspect which posted movements belong to the case before reading Request Completion Comparison. The supervisor should be able to explain the authorized quantity, the movement total and the receipt outcome. Ask Auditor to reproduce that explanation from the retained records.

Check the handoff on an actual case

An approved request authorizes 50 units, but its posted movement total is 40. Inventory Supervisor runs completion verification. The receipt must be Failed, the request must remain unchanged and the discrepancy must remain available for investigation. A successful transport response or a loaded handling unit cannot make the difference disappear.

Inspect the decision, authorized quantity and movements to find the cause. Resolve it through the supported execution, authorized correction or reversal path as appropriate to the physical evidence. Run verification again using the documented operation identity behavior and inspect its result. Retain the earlier failed evidence alongside the later outcome. Auditor then checks that the explanation accounts for the real movement history and does not depend on rewriting a previous result.

What your team sees

  • Operation Receipts Register — The main evidence view for recorded actions and verification outcomes.
  • Failed Operation Receipts — Failed operations showing their reason and the request needing follow-up.
  • Returned and Escalated Decisions — Recorded decisions and their source requests needing more evidence or further review.

Follow the work through

Follow posting and verification or correction and reversal. Use reports to agree the questions that the evidence should answer.

What it keeps track of

Data model
Operation receipts
Recorded, verified, failed or corrected operation evidence.
Review decisions
Approved, rejected, returned or escalated decisions on source records.
Record attachments
Documents and links attached to operational records.
Stock requests
Requests to receive, move, reserve or issue stock.
Stock movements
Posted signed-quantity movements that change on-hand inventory.

Who uses it

Permissions
Inventory Supervisor
, Auditor, Inventory Clerk.
Inventory Supervisor
Owns reconciliation; Auditor reads the evidence; Inventory Clerk supplies the operational facts needed to resolve the case.

Set up Inventory Allocation Engine your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started