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.
- Exhibition / Trade Show
- Features
- Payments and reconciliation
Payments and reconciliation
Keep provider evidence and operation receipts beside the work they support.
OverviewReceipts needing investigation×
Exhibition / Trade Show · Payments and reconciliation
New
Receipts needing investigation
Operation receipts
| Id | Parent | Operation key | Action | Expected revision | Result state | |
|---|---|---|---|---|---|---|
| IDD-416 | EVN-93295 | OK-508 | ACT-665 | 590 | Needs review | |
| IDD-470 | EVN-58098 | OK-138 | ACT-249 | 270 | Needs review | |
| IDD-901 | EVN-49886 | OK-983 | ACT-679 | 360 | Needs review | |
| IDD-907 | EVN-73591 | OK-365 | ACT-249 | 120 | Needs review | |
| IDD-164 | EVN-26767 | OK-333 | ACT-456 | 440 | Needs review |
6 of 6 records
IDD-416Operation receipts · OR-77719
Needs reviewParentEVN-93295
Operation keyOK-508
ActionACT-665
Expected revision590
Failure reasonCut to length
What you can do
Separate provider facts from local actions
Payment evidence records a provider event identifier, type, amount, time, verification flag and provider reference under the parent event. An authorization, capture, refund or void is a distinct kind of evidence. Finance Reviewer checks the provider reference and verification before treating a capture as support for a completed paid reservation or booth assignment. A local record of a planned refund is not the same as confirmed money movement; review the provider’s authoritative result.
Each guarded action can have an operation receipt. The receipt records its stable key, action, expected revision, result state, time, linked effects and any external reference or failure reason. This gives the team a place to inspect an uncertain outcome without repeating an external action. A pending receipt can move to completed only when its local linked effects and authoritative external result agree. A discrepancy belongs in needs review with a concrete reason.
How the work is organized
- Check the source. Finance Reviewer identifies the provider event and confirms its type, amount, reference and verified state.
- Match the effect. The reviewer compares the payment evidence with the admission or booth work under the same event.
- Resolve uncertainty. The reviewer opens receipts needing investigation and checks linked effects before closing the operation outcome.
What to agree during setup
Choose the authoritative payment provider and how provider events will be imported or checked. Define the stable event identifier and how duplicate deliveries are recognized. Decide who verifies evidence and what proof is required for a capture, refund or void. Agree how external references are matched to an operation receipt and how a provider timeout is investigated. Keep provider access separate from ordinary event planning permissions.
Check the handoff on an actual case
A visitor reserves paid admission and receives a provider receipt. The provider later reports a capture with its event identifier and reference. Finance Reviewer checks that the evidence is verified and belongs to the same event before admission scope is treated as completed. If the action times out, the operation receipt remains pending while the reviewer checks linked effects and the provider’s authoritative source. When both agree, the receipt can be marked completed. If the provider shows no capture, the receipt moves to needs review with the discrepancy. Retrying the same request must not create a second capture or a second admission. The same discipline applies before a paid booth assignment is marked completed.
What your team sees
- Receipts needing investigation — Guarded actions with unresolved outcomes and failure reasons.
- Verified payment evidence — Provider facts grouped by event and payment type.
- Admission ledger — Admission lines with the linked provider receipt and entry time.
Follow the work through
What it keeps track of
Data model- Payment evidence
- Provider payment authorizations, captures, refunds and voids.
- Operation receipts
- Idempotent receipts for guarded operations with expected revision and result state.
- Admissions
- Reserved and admitted admission lines for an event.
- Booth assignments
- Exhibitor booth assignment records submitted for review and completion.
- Events
- Programs, events and sessions with capacity, lifecycle and revision.
Who uses it
Permissions- Finance Reviewer
- Verifies payment evidence and reconciles receipts.
- Admissions Coordinator
- And Booth Coordinator inspect the resulting scope.
- Event Reviewer
- Decides on compensating corrections.
- Admin
- Governs access.
Set up Exhibition / Trade Show your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.