Kapta · 15/09/2026
Use shared references to connect events while retaining the meaning of each measure. Bookings sold, payments received, authorisations and confirmed passages answer different questions and can happen on different days.
Why can sales totals differ from admissions?
A booking can be purchased on Monday and used on Saturday. A group may enter partially, a customer may not arrive or a sale may be refunded. Reports should let staff choose the relevant date and explain differences through concrete cases, rather than forcing every total to match.
Which identifiers should accompany each record?
Define references for the booking, participant or admission entitlement, payment and access event. Where invoicing is involved, retain the document reference. Systems may use different units: one booking can contain several participants and multiple payments.
Does the scan count show how many people are inside?
Not by itself. One person may make several attempts, and an authorisation may not result in passage. Estimating occupancy requires defined entry and exit events and exception handling. Label totals as scans or authorisations when those are the events actually available.
How can differences become an actionable work list?
Create useful exception groups: paid bookings with no admission, admissions without a reconciled reference, refunds after use and manual corrections. Assign an owner to each group and define the operational day, including its time zone. Kapta can help map this workflow during the integration assessment using anonymised report examples.
