Define what the report measures
Lexoh revenue reporting helps operators review the payment activity recorded for their sites. Before using a total, identify its currency, period, transaction states and treatment of taxes and refunds. A report label alone does not establish the calculation behind it.
Open the revenue view available in your installation. Confirm your site access, permissions and software version. The available charts, fields and export options depend on the deployed version and configuration. Keep the report settings with any saved result.
Check each summary measure
Period total
Check whether the amount includes taxes and whether refunds are deducted, shown separately or excluded. Confirm which transaction states and payment channels contribute to the total.
Current-day amount
Verify the time zone and day boundary. Check whether a current-day indicator follows the selected period or has its own fixed scope. Note the last received data before comparing it with another report.
Average transaction amount
Use the amount and transaction count defined for the same population. For example, CAD 240 across 12 included payments gives CAD 20 per payment. With no included transactions, the average is undefined. A displayed zero may be a presentation convention rather than a calculated average.
Compare equivalent time periods
Read the chart’s axis labels, currency and grouping interval. Determine whether each bar represents an hour, day or month and whether the first or last interval is incomplete. Use detailed values when a chart is difficult to read.
Compare equivalent operating periods and note closures, events, price changes and missing records. A larger total in a longer month does not by itself show stronger daily performance. A change following a promotion also does not establish that the promotion caused it.
Separate payment channels and refunds
A payment channel describes where a payment originated, such as a kiosk or online checkout. A payment method describes how it was paid. Keep these dimensions separate when comparing totals. Use the channel definitions shown in your installation.
Reconcile a breakdown only when its categories cover the same records without overlap. Check the sign and date assigned to refunds and whether the original payment is also present. Avoid subtracting a refund twice.
| Component | Amount (CAD) |
|---|---|
| Included payments | 300 |
| Included refunds | −40 |
| Payments less refunds | 260 |
What the example establishes
CAD 300 − CAD 40 = CAD 260 before any fees or other adjustments. These invented values demonstrate arithmetic, not a Lexoh installation’s results or a bank payout. Use the actual inclusion rules of your report.
Read payment-method distribution
Confirm whether a share represents the number of payments or their value. Ten small payments can have a larger transaction count and a smaller amount than one large payment. Include unclassified records when checking that the breakdown reconciles.
A payment brand appearing in a report is historical data, not proof that every site terminal currently accepts it. Confirm enabled methods with the terminal configuration and payment provider. Investigate a change using relevant transaction records, device status and processing results.
Verify amounts and tax fields
Identify the subtotal, each recorded tax amount and the total charged. Compare the report with the corresponding receipt or transaction detail, including any refund adjustments. Confirm rounding and which records are included before interpreting a difference.
Preserve the transaction’s original date and recorded tax details when investigating historical totals. Have the person responsible for accounting validate the configuration and reporting requirements. This guide does not establish tax rates, filing totals or a record-retention period.
Check company and tag attribution
When a report groups amounts by company or tag, verify how records are assigned. An unassigned record is missing an association; it does not automatically identify a consumer purchase or a particular customer type.
If a transaction can belong to several displayed groups, adding all group totals may count it more than once. Confirm whether the report uses exclusive categories, splits amounts or repeats them. Record the grouping rule before comparing companies, zones or campaigns.
Trace totals to transactions and payouts
Provider settlement reports and site activity reports can use different dates and populations. Stripe’s payout-reconciliation documentation, for example, describes matching bank payouts to batches containing payments, refunds, fees and other adjustments. Check the equivalent records for your own provider.
Reference: Stripe, Payout reconciliation report — docs.stripe.com/reports/payout-reconciliation. This example of provider documentation does not establish which payment provider your Lexoh installation uses.
- Match a sample of report rows to their transaction references, dates, currency and amounts.
- Check the exact status meaning in the deployed application and payment provider. A successful payment status alone does not confirm a bank deposit.
- Match refunds to the original payment and the provider’s refund reference. Verify full or partial amounts and the relevant dates.
- For a bank-payout difference, identify the settlement batch and compare its payments, refunds, fees and other adjustments with the provider statement.
- Record unresolved differences separately and assign a follow-up owner.
Make the reporting scope reproducible
- Record the site, currency, start and end timestamps, time zone and included transaction states.
- Check whether a preset means calendar dates or a rolling interval. A month is not necessarily 30 days.
- Confirm how period boundaries and refund dates are handled. Use the same definition in both reports.
- If an export is available, compare its row count and total with the filtered view. Check whether pagination or selection limits the exported records.
- Note missing data and the latest update. Recheck the same scope after delayed records arrive.
Keep a review and handover record
Choose review thresholds from the site’s documented operating baseline and agreed objectives. This guide does not set a universal payment-decline threshold, revenue-per-space benchmark or kiosk-investment rule.
Keep the report settings, checked references, calculation, explanation and follow-up owner together. Separate a confirmed discrepancy from an incomplete report or a timing difference. Share only the record details needed to investigate, using your organization’s approved process.
Before changing prices or equipment, consider visit mix, operating costs, service requirements and the underlying transaction evidence. A report helps identify questions; the total alone does not explain their cause.