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.
- Conference Management
- Features
- Review and reconciliation
Review and reconciliation
Trace event decisions and guarded operations to the source revision and evidence.
OverviewReceipts needing review×
Conference Management · Review and reconciliation
New
Receipts needing review
Operation receipts
| Operation key | Parent | Action | Expected revision | Result state | Failure reason | |
|---|---|---|---|---|---|---|
| OK-370 | EVN-34918 | ACT-250 | 160 | Needs review | Cut to length | |
| OK-688 | EVN-67033 | ACT-951 | 850 | Needs review | Weld frame | |
| OK-230 | EVN-50408 | ACT-815 | 850 | Needs review | Drill and tap | |
| OK-147 | EVN-74970 | ACT-667 | 630 | Needs review | Deburr | |
| OK-747 | EVN-66205 | ACT-562 | 840 | Needs review | Assemble |
6 of 6 records
OK-370Operation receipts · OR-82393
Needs reviewParentEVN-34918
ActionACT-250
Expected revision160
Failure reasonCut to length
Occurred at18 Oct
What you can do
Keep decisions close to their source
A review decision belongs to an event and names its reviewer. It records the source revision, decision, time, reason and operation key. Those details help the team distinguish an approval of the current event scope from a decision made before a venue or capacity change. Event Reviewer handles event approval; Registration Reviewer handles submitted registration scope. Both need a clear reason when returning or rejecting work.
An operation receipt also belongs to the event. It records the action, operation key, expected revision, result, time, optional external reference, effect references and failure reason. Finance Reviewer uses it to reconcile what the operation attempted with what the admission and provider evidence show. A pending receipt means the team still needs to inspect the result; a receipt needing review points to a discrepancy that should be named.
How the work is organized
- Human decision. A reviewer records an approval, rejection or return with a reason against a source revision.
- Operation attempt. A stable key and expected revision identify the attempted action and guard against retries.
- Evidence check. Local effects and any authoritative external reference determine whether the receipt is complete.
What to agree during setup
Agree who can decide event scope, who can decide registrations and how staff resolve a returned item. Decide which evidence types should be attached to the event and whether each file is internal or shared. Configure access so a preparer does not approve their own submitted work. The reviewer needs to see the source revision and supporting record, while the team keeps older decisions for explanation.
For reconciliation, specify the provider connection used to verify an external reference. Finance Reviewer should compare the expected effect with the linked admission and payment evidence before changing the receipt result. A failed or mismatched attempt is recorded with a concrete reason. Reconciliation reads what occurred; it should not repeat an external action.
Check the handoff on an actual case
Event Owner submits a conference after attaching its venue confirmation. Event Reviewer checks the selected event and records an approval for that revision. The owner opens registration. Later, a capacity correction changes the event revision. The earlier approval remains historically valid for its source, while the changed scope receives another decision before it is used.
For an interrupted admission operation, Finance Reviewer opens the receipt and compares its expected revision with the event, then follows its effect references to the admission line and verified provider capture. If both match, the receipt can be completed. If payment evidence is absent, the receipt needs review with a reason that tells the team exactly what is missing.
What your team sees
- Receipts needing review — Investigate mismatched local or provider effects without repeating execution.
- Review decisions — See decision, reviewer, source revision and reason for each event.
- Event attachments — Find shared supporting files under the right parent event.
Follow the work through
Read event approval for source decisions and event close for the final evidence check.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions recorded against a source revision.
- Operation receipts
- Idempotent receipts for guarded operations with expected revision and result state.
- Record attachments
- Uploaded evidence files linked to an event with visibility scope.
- Events
- Programs, events and sessions with capacity, lifecycle and revision.
- Admissions
- Reserved and admitted admission lines for an event.
- Payment evidence
- Provider payment authorizations, captures, refunds and voids.
- Registrations
- Participant registration records submitted for review and completion.
Who uses it
Permissions- Event Reviewer
- , Registration Reviewer, Finance Reviewer, Event Owner, Admin.
- Domain reviewers decide; Finance Reviewer reconciles; Admin maintains access.
Set up Conference Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.