Exceptions and evidence

An operation receipt records the guarded action, its operation key, expected revision and result state. It can also carry external and effect references or a failure reason. The Reconciliation Analyst reads that receipt alongside the parent order, review decision and actual line or event effects. A Completed state is justified only when the expected effects match. A failed or review-needed receipt stays in the exception queue with its reason.

Suppose a batch release received supervisor approval, but the external delivery reference has not appeared. The analyst checks the submitted ticket revision, decision, local prepared scope and any fulfillment event before deciding whether the receipt can be completed. Reconciliation starts with a read of the evidence. It must not repeat external execution simply because a response arrived late.

• Guarded action. Keep one operation key and expected revision with the attempted transition.
• Decision trail. Link the reviewer, source revision, decision time and reason to the parent order.
• Effect evidence. Compare local portions, stock movements, provider receipts, fulfillment events and attachments with the intended result.

Agree which team can mark an operation reconciled and which evidence is required for a refund, void or delivery confirmation. Identify the provider event ID used to detect repeated payment evidence and the external event ID used for fulfillment. Make the visibility of attachments explicit so operational evidence is shared only with the intended readers. Keep failures legible to the supervisor and analyst instead of hiding them behind a favorable order status.

A correction after service needs more care than a draft edit. Read the current order revision, every affected line and the existing review and receipt history. Identify what was not prepared, what was prepared but not served and what was served. The Kitchen Supervisor reviews the proposed compensating action. The analyst verifies any provider issued refund or void before recording its effect. The original service and payment evidence remain intact.

Choose an item in Operation Exceptions. Open the parent order and compare the receipt’s expected revision with the order revision. Read the decision and attachments, then find the actual local effects. If a provider event reports a refund, compare its amount and event ID with the authorized scope. A repeated correction request with the same operation key should resolve to the prior result, not create another refund.

When the evidence agrees, complete the receipt and retain its references. When quantities, identity or revision differ, leave the result Failed or needs review with a clear reason and the next investigative action. This makes the exception queue a working record of unresolved outcomes rather than a collection of unexplained failures.

• Operation Exceptions — Investigate failed and review-needed guarded actions with their parent orders.
• Unverified Payment Evidence — Check provider events before relying on a refund or capture.
• Delivered Fulfillment Events — Match delivery events to the menu item and order they report.

Use correction and reconciliation for recovery and batch review for the originating decision.