How orders, payments, invoices, and tickets fit together

Use this when an order looks paid but not booked, booked but unpaid, missing tickets, waiting for a refund, or blocked from sending a payment link.

KORONA Event keeps operational state and financial state separate. Check both before you resend documents, issue tickets, cancel, refund, or tell a customer the order is complete.

The four state groups

Order states

Order states

Order state describes the operational progress of an order; read payment and invoice state separately.

Option	What it does	When to use it	Watch out for
New	Marks an order that is still open or has not progressed to a customer-facing result.	Use it while an order is being created or reviewed before request, reservation, or booking.	Check before sending payment links or documents.
Requested	Records a customer request that is waiting for review or a later staff action.	Use it when the booking must not be confirmed automatically.	Do not treat it as a final booking.
Reserved	Holds capacity until a reservation deadline or another action progresses the order.	Use it for temporary holds and pay-later workflows.	The reservation can expire and release capacity.
Expired	Marks a request or reservation that passed its allowed deadline without progressing.	Use it to identify orders that no longer hold their previous place in the workflow.	Check whether the customer completed a replacement order later.
Booked	Confirms the order operationally.	Use it when the selected offers are accepted as a booking.	Booked does not prove that payment or ticket generation completed.
Canceled	Ends the operational order and prevents it from being treated as active.	Use it after an approved cancellation workflow.	Payment, refund, invoice, capacity, and customer communication may still need separate action.

Order payment states

Order payment states

Order payment state summarizes whether money is still due, settled, or requires refund work.

Option	What it does	When to use it	Watch out for
Open payment	Shows that the order still has an amount that needs to be paid.	Use it to find orders that need payment follow-up or an available payment action.	Check invoice state and open items before sending a payment link.
Needs refund	Shows that money should be returned or refund follow-up is still required.	Use it to route the order into the team’s refund process.	It does not prove that the customer has received the money.
Action needed	Shows that the order contains both an amount to collect and an amount to refund.	Use it to identify mixed financial corrections that need deliberate review.	Review invoice details instead of assuming the two amounts cancel each other out.
Settled	Shows that the order has no remaining payment or refund difference at order level.	Use it as the order-level financial completion signal.	Still check individual invoices and provider settlement when finance detail matters.

Invoice payment states

Invoice payment states

Invoice payment state describes what payment or refund work remains for one invoice.

Option	What it does	When to use it	Watch out for
Requires payment	Shows that the invoice still needs payment.	Use it when collecting an open invoice through an available payment action.	A payment link exists only when the invoice and provider support it.
Requires refund	Shows that the invoice needs a refund or refund follow-up.	Use it to identify invoices that must enter the refund process.	The provider transaction can still be pending or require manual handling.
Refunded	Marks the invoice as refunded.	Use it after the approved refund workflow records completion.	Confirm provider and customer receipt when investigating a disputed refund.
Paid	Records payment for the invoice.	Use it when the invoice amount has been paid or deliberately marked paid.	Paid does not prove that the order is booked or tickets were generated.

Ticket states

Ticket states

Ticket state describes whether a ticket is ready, usable, consumed, restricted, or no longer valid.

Option	What it does	When to use it	Watch out for
Pending	Shows that ticket activation or final state is not complete yet.	Use it while waiting for ticket generation or synchronization to finish.	Do not promise entry until the ticket becomes active or its source confirms validity.
Active	Shows that the ticket is currently valid for its configured entitlement.	Use it as the normal ready-for-entry state.	Date, time, entitlement, and duplicate-scan rules can still affect admission.
Used	Shows that the ticket’s usable entitlement has already been consumed.	Use it to investigate a repeat or duplicate entry attempt.	Check scan history before overriding an admission decision.
Expired	Shows that the ticket is outside its valid period.	Use it when the configured validity has ended.	Confirm the selected event or admission date before rejecting the customer.
Locked	Prevents the ticket from being used while a restriction is active.	Use it when an operational or external-system rule deliberately blocks entry.	Review the lock reason and owning system before changing it.
Cancelled	Shows that the ticket was canceled and is no longer valid for entry.	Use it after the related order item or ticket has been canceled.	Check whether a replacement ticket was issued.
Unknown	Shows that KORONA Event cannot determine a reliable ticket state.	Use it as a signal to inspect ticket source, synchronization, and scan history.	Do not infer validity without checking the source system.

How to read a common order

1. Start with the order state on the order overview.
2. Check whether the order has Open items.
3. Open Documents when financial state matters.
4. Check whether payment actions such as Initiate payment, Copy payment link, or Send payment link email are available.
5. Open Attendees or the document downloads when entry, tickets, vouchers, or personalization matter.
6. Open History when you need to see how the order reached its current state.

State combinations that need care

Rules of thumb

• Do not treat Booked as proof of payment.
• Do not treat Paid as proof that tickets were generated.
• Do not resend an email until you confirm the order has the expected documents.
• Do not create a manual payment link when the payment link action is unavailable.
• Do not edit paid services or quantities until you understand the refund and invoice result.

Related articles

• Orders and invoices
• Payment setup overview
• Send or copy a payment link
• Test the customer checkout