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.
- Award / Competition Mgmt
- Features
- Payments
Payments
Keep provider payment evidence next to event admissions.
OverviewProvider captures×
Award / Competition Mgmt · Payments
New
Provider captures
Payment evidence
| Provider event ID | Parent | Amount USD | Occurred at | Verified | Provider reference | |
|---|---|---|---|---|---|---|
| PEI-909 | EVN-20377 | 20 | 12 Oct | Yes | PR-251 | |
| PEI-923 | EVN-10023 | 250 | 13 Oct | No | PR-103 | |
| PEI-442 | EVN-12230 | 840 | 22 Oct | Yes | PR-541 | |
| PEI-943 | EVN-28872 | 430 | 12 Oct | No | PR-475 | |
| PEI-179 | EVN-37946 | 850 | 07 Oct | Yes | PR-878 |
6 of 6 records
PEI-909Payment evidence · PE-20112
YesParentEVN-20377
Amount USD20
Occurred at12 Oct
Provider referencePR-251
What you can do
Review money movement through evidence
Payment evidence is linked to an event. Each record has a provider event ID and reference, a type, an amount in USD, an occurrence time and a verification state. Authorization, Capture, Refund and Void are distinct types. A capture is the relevant evidence for a paid reservation; an authorization is an earlier provider event and should not be counted as collected money.
The Finance Reviewer uses provider references to connect the recorded evidence with the payment source. A refund or void entry should reflect its own provider event, not an assumption made from an event cancellation. Keeping the types separate lets the team explain what the provider confirmed when an attendee asks about a charge or a cancellation.
How the work is organized
- Provider trail. The provider event ID and reference identify the external event behind the local record.
- Verification. The verification state distinguishes reviewed evidence from a record still awaiting confirmation.
- Event context. Admissions and the event status explain why a capture, refund or void matters to operations.
What to agree during setup
Name the provider source used for each operating organization and decide how its events reach the payment evidence record. Agree who verifies a provider event and how duplicate provider IDs are handled. Set a reconciliation routine that compares verified captures with reserved and admitted quantities under the same event. Decide what the team does when a refund has been prepared but the provider has not confirmed it. Keep the provider’s actual outcome separate from a local staff request to correct or cancel a booking.
Check the handoff on an actual case
A guest reserves two places for an award event. The registration is approved and the admission line records two reserved places. Finance Reviewer sees a provider authorization followed by a capture. Only the verified capture supports treating the paid reservation as settled. If the event is cancelled, staff retain the original admission history and review the refund evidence when the payment provider reports a separate refund event. A local note saying a refund is expected cannot replace that provider event. The reviewer compares provider references and amounts before closing the financial exception.
What your team sees
- Provider captures — Review captured amounts and verification state by parent event.
- Receipts needing review — Investigate actions whose recorded effects remain uncertain.
- Admission register — Compare the payment trail with reserved and admitted quantities.
Follow the work through
Use payment reconciliation to examine provider results and event closeout to reconcile the final event. See integrations for the provider connection.
What it keeps track of
Data model- Payment evidence
- Provider payment authorizations, captures, refunds and voids.
- Events
- Programs, events and sessions with capacity, lifecycle and revision.
- Admissions
- Reserved and admitted admission lines for an event.
- Registrations
- Registration records for award and competition events: parent event, registered-at, quantity, status, check-in and decision timestamps.
- Operation receipts
- Idempotent receipts for guarded operations with expected revision and result state.
Who uses it
Permissions- Finance Reviewer
- , Admission Lead, Event Owner, Admin
Set up Award / Competition Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.