Operation Reconciliation

An operation receipt identifies an action with an operation key, expected revision, result state and occurrence time. It belongs to an event. External reference, effect references and failure reason explain what the action attempted and what the team can verify afterward. A Completed result means the expected effects have been matched. Pending, Failed and needs review remain visible for investigation. The receipt provides a durable answer when someone retries a scan or capacity claim after a connection interruption.

Reconciliation starts by reading local records. The lead checks the event revision, admissions, ticket scans, review decisions and payment evidence connected to the operation. If an external reference exists, the configured authoritative source must also be checked. The lead marks the receipt Completed only when the expected effects match. If they do not, needs review records the discrepancy. Reconciliation should not repeat the original external execution.

• Identity. Match the operation key and expected revision to the selected event.
• Effects. Compare local admission and scan outcomes with the receipt’s effect references.
• Resolution. Check provider evidence and retain a concrete discrepancy when results differ.

Choose the stable key used for guarded operations and decide how long the team retains receipts. Assign a reconciliation lead who can inspect provider references and local effects without acting as the original approver. Agree which provider source is authoritative for capture, refund and void events. A local entry marked verified should be traceable to that source.

Practice a pending result before opening admissions. The operator should know how to find the earlier receipt instead of submitting a fresh claim. A failed receipt should keep its failure reason. A needs review receipt should say which expected effect is missing or conflicting, so the next reviewer can resolve it without guessing.

An operator submits a ticket scan while the venue connection drops. The screen does not show a final outcome. The reconciliation lead searches the operation key and finds a Pending receipt. They compare its expected revision with the event, then read the linked scan, admission line and provider capture. If the scan has completed, the admission was recorded once and the capture is verified, the lead can mark the receipt Completed. If the provider reference is absent or the admission count differs, the lead records needs review with the exact discrepancy. The operator does not run a second external action to find out what happened.

• Receipts needing review — Actions whose local or provider effects need investigation.
• Unverified payment evidence — Provider events that still need confirmation.
• Completed scans — Recorded check-ins to compare with receipt effects.

Use review and evidence for authority and event closure for the final event check.