Operations Evidence

Operation receipts record an action, its expected revision, outcome, time and any failure reason. They belong to an event, where the team can compare them with admissions, payment evidence and review decisions. Reconciliation Lead uses that trail to distinguish a completed action from one that failed or needs review.

Payment evidence records the provider event and reference, transaction type, US dollar amount, time and verification state. Attachments carry evidence type, visibility, uploader and upload time. Together these records help the team answer why an attendee was admitted, why a payment figure was counted, or why a release action remained unresolved.

• Inspect the action. Use the operation key and expected revision to identify the exact guarded request and its result.
• Check the source. Compare linked admissions and verified payment evidence with the event before treating a receipt as complete.
• Keep the file trail. Add supporting attachments with a clear title, evidence type and visibility for the event team.

For a busy event, one payment item might remain unverified while admissions continue. The Reconciliation Lead can open the unverified payment item, check its provider reference and compare it with an operation receipt. A mismatch belongs in the exception queue for investigation before event close.

Agree which provider supplies payment confirmation, how duplicate provider events are recognized and who may mark evidence verified. Define when a receipt marked failed or needing review blocks completion. Decide which attachments may be shared and which remain internal. The uploader should choose the visibility deliberately, particularly for consent and delivery evidence linked to an event.

Choose a retention and correction practice for provider references and files. If a provider later reverses or voids a transaction, record the new evidence type rather than treating the earlier capture as if it never happened. Keep enough context on the parent event to explain the change during reconciliation.

Use one event with a reserved attendee, admitted attendance, a verified payment item and an operation receipt. Compare quantities and references, then inspect the completed result. Add another receipt with a mismatched effect and confirm it is flagged for review with a reason. Try the same operation key twice and confirm the team sees one accepted effect. Add an internal attachment and a shared attachment, then check the intended visibility with each role. Close the event only after the Reconciliation Lead can explain the remaining exceptions.

• Failed and Needs Review Operations — Actions that need an owner, failure reason and event context.
• Unverified Payment Evidence — Provider events awaiting a verification decision.
• Operations Overview — A cross-event picture of attendance, review decisions and the exception queue.

Follow event completion for the close decision and scope correction for changes to accepted work.