Why an Experience order is not the same as a payment
Rezervem Experience records product orders and, for eligible fulfilment types, redemption activity. Rezervem Pay records supported online payment requests, successful collections and refunds. An order count is not a payment count, and an advance payment does not mean the guest has already received the service.
For a product with a prepayment percentage, the gross order value may exceed the amount collected online. An item added by staff for payment at the venue may not represent collected revenue at all. Reporting those values in one undifferentiated total can mislead both restaurant management and finance.
Reading a busy month's sales without double counting
Imagine that a restaurant has many special-menu orders. Some were paid in full, some required a deposit, some are payable at the venue and some were refunded. Start with order source and state; then identify the payment transaction and whether a service or redemption code was actually used.
Compare branches only after checking that the same metrics and currencies are being used. A code-free reservation-linked order should not be treated as an unused voucher, and a refund instruction should not be counted as a settled provider refund. Different transaction dates can also shift results between reporting periods.
Five controls for order and payment reporting
Check the real venue configuration and staff responsibilities before inviting guests to use this workflow.
- Group orders by source, product, variant and venue.
- Separate gross order value, collected prepayment and outstanding venue balance.
- Verify successful collections and actual refunds in the payment record.
- Review redeemed, valid, expired and cancelled rights only for code-based sales.
- Match currencies, dates and bank transactions before calculating totals.
How Experience and Pay support a reconciled picture
Experience can expose order details, source, items and relevant usage states. Pay supplies the financial payment and refund outcomes. These views complement one another, but the same sale must not be added twice merely because it appears in both product and payment reports.
If a specific product shows unusually frequent refunds, examine its description, conditions and service operations rather than assuming a software defect. If branch figures differ, check venue assignments and supported sales channels. Bank reconciliation remains the final check for cash movements.
FAQ: Do 100 orders mean 100 successful payments?
No. Orders may be pending, payable at the venue or otherwise not collected.
FAQ: Does every product have a redemption-code count?
No. Some orders fulfil through their booking rather than a code.
FAQ: Should Experience and Pay totals be added together?
No. Avoid treating the same order and its payment as separate revenue.
