These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Network Inventory Management
- Features
- Operation receipts
Operation receipts
Inspect recorded, verified and failed outcomes for work order actions.
OverviewFailed Operation Receipts×
Network Inventory Management · Operation receipts
New
Failed Operation Receipts
Operation receipts
| Receipt number | Parent | Action | Failure reason | Occurred at | Result state | |
|---|---|---|---|---|---|---|
| OR-84014 | WO-60373 | ACT-770 | Cut to length | 16 Oct | Failed | |
| OR-61157 | WO-54089 | ACT-946 | Weld frame | 11 Oct | Failed | |
| OR-97875 | WO-59542 | ACT-288 | Drill and tap | 24 Oct | Failed | |
| OR-79006 | WO-74649 | ACT-775 | Deburr | 13 Oct | Failed | |
| OR-21730 | WO-77949 | ACT-439 | Assemble | 21 Oct | Failed |
6 of 6 records
ACT-770Operation receipts · OR-84014
FailedParentWO-60373
Failure reasonCut to length
Occurred at16 Oct
What you can do
Read the result of an action
An operation receipt records what an action attempted on a work order and how it ended. It carries a receipt number, parent, owner, date, quantity, action and operation key. Its result is recorded, verified, failed or corrected. A failed receipt can include the reason, while a successful verification provides a dated completion check tied to the source job.
Failed Operation Receipts is the clerk’s and supervisor’s exception queue. The Operation Receipts Register places all result states together for audit. Operations Overview brings failed receipts beside late work and escalated decisions, which helps a supervisor decide whether a failure needs a new assignment, a correction or another review.
How the work is organized
- Action. Work order workflows create receipts when an operation is attempted.
- Result. The receipt records the result state and, on failure, the reason.
- Follow-up. The supervisor returns to the parent work order and its current revision before retrying.
A receipt is evidence of the action’s outcome, not a substitute for the parent record. A failed reconciliation receipt leaves the work order unchanged when posted evidence does not equal authorized quantity. The team can then inspect the evidence ledger and correct the cause. A repeated action with the same stable key returns the existing result instead of producing another receipt for the same request.
What to agree during setup
Decide who monitors failed receipts each day and how they notify the work order owner. Agree how action names will be used in reports so a supervisor can distinguish review, execution and reconciliation attempts. Set an expectation for recording the failure reason in language the owner can act on.
Keep external references in the receipt only when there is an actual outside event to identify. They should not replace the work order link. When the same job is reviewed again after a correction, use its current revision and a distinct authorized action. The old receipt remains visible as part of the job’s history.
Check the handoff on an actual case
Run an execution step for a work order with accepted evidence and inspect the recorded receipt. Confirm its parent, owner, quantity and action match the case. Then attempt reconciliation while the posted evidence total differs from authorized quantity. Failed Operation Receipts should show the reason, and the work order should retain its previous state.
Correct the underlying evidence or authorized scope through the appropriate review path. Reconcile again, then inspect the verified receipt and compare its parent with the earlier failed attempt. Ask an auditor to read the sequence from the Operation Receipts Register without relying on a private chat or spreadsheet.
What your team sees
- Failed Operation Receipts — Failed actions with reason, date and parent work order.
- Operation Receipts Register — Recorded, verified, failed and corrected outcomes together.
Follow the work through
See execute and verify and port review.
What it keeps track of
Data model- Operation receipts
- Recorded, verified, failed or corrected operation evidence.
- Work orders
- Planned and executed asset work; the parent record for evidence, port assignments, decisions and receipts.
- Work evidence
- Evidence ledger for a parent work order: occurrence, quantity, revision and review state.
- Review decisions
- Approved, rejected, returned or escalated decisions on source records.
- Team members
- Warehouse staff and reviewers linked to an organization and platform user.
Who uses it
Permissions- Inventory Supervisor
- Triages failures and verifies completion.
- Inventory Clerk
- Responds to execution exceptions.
- Auditor
- Reads the receipts and linked source records.
Set up Network Inventory Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.