What this page shows
Gaming Revenue is a timeline-style report that combines banking movement with optional gaming totals.
It groups the selected period by day, week, or month.
When to use it
- compare deposits and withdrawals over time
- inspect current balance alongside period movement
- review gaming totals on the same time axis when the enhanced data path is active
How to read it
The always-visible summary cards are:
Total Non-Promotional DepositsTotal Non-Promotional WithdrawalsCurrent Player Account Balance
The card labels say Non-Promotional, but the summary aggregation does not apply the same cash-only filter as every timeline row. Do not expect the two summary cards to reconcile exactly to a sum of the visible timeline without checking the source population.
When the enhanced data path is active, the page can also expose:
Total GGRTotal NGRTotal WageredActive Players
Important reading rule:
Net Revenueon this page is banking net flow for the period (deposits - withdrawals)- it is not the same thing as gaming
GGRorNGR - enhanced summary cards are shown only when
Use New Schemais active and gaming totals are available for the selected range
Ending Balance is the running cumulative balance over the generated time series, not a per-row wallet snapshot captured only on that date.
Filters that change the result
Start DateandEnd Datedefine a custom date range.Intervalswitches to preset ranges: Custom, Month to Date, Year to Date, or Life to Date.Group Bychanges the time bucket to daily, weekly, or monthly.Use New Schemarequests the enhanced version of the report with gaming totals.
For a custom range, End Date is sent at the start of the selected date. It is not expanded through the end of that calendar day. To include a full final day, use the next date as the end boundary and verify the resulting range.
Action and filter behavior
Refreshis the real apply action. It copies the currently edited date, interval, grouping, and schema-toggle controls into the active query state and then re-fetches the report.- Pressing
Enterin the filter controls applies the same staged values asRefresh. Reset Filtersrestores the default view: no date range,Group By = Daily, andUse New Schema = ON.Export CSVuses the active query snapshot, not the currently staged page values.- The date pickers stay visible until an interval selection has actually been applied. Choosing
MTD,YTD, orLTDon the page does not hide the custom date inputs untilRefreshupdates the active state. - Page changes and rows-per-page changes keep the active filters unchanged.
Why this page can differ from gaming-performance
This page is period-based and banking-led. It starts from deposits, withdrawals, and balance movement.
Gaming Performance is dimension-based and gameplay-led. It starts from grouped gaming behavior by game-facing dimensions.
Known caveats
- A custom range that starts and ends on today forces the legacy path even when
Use New Schemais enabled. - The visible
New SchemaorLegacy Schemachip mirrors the active toggle state; today-only custom ranges can still fall back to legacy behavior. - The report presents values in
EUR. - Legacy mode does not expose the enhanced gaming totals shown by the newer schema.
Current Player Account Balanceis a current-wallet snapshot and does not respect the report date range the same way period rows do.- Even in enhanced mode, the page renders only a subset of the available enhanced values. Extra values such as
Bonus Deposits,Total Won,Total Bets, andTotal Sessionscan appear in export or source data without being visible as standalone page columns. Life to Datedoes not use one identical lower boundary everywhere: the timeline starts from 2024-01-01, the count path starts from 2020-01-01, and summary totals are not constrained by the same lower bound.- Banking amounts use a stored transaction conversion rate. The exact rate provider, capture timestamp, rate basis, and rounding boundary are not exposed by this report.
- Missing stored rates can fall back to 1, which treats the original amount as already EUR and can distort totals.
Access and operating recommendation
The page requires GamingRevenueReport: R. Give access to finance, management, analytics, or senior operations users who understand the difference between banking net flow, GGR, and NGR.
Use the same date boundaries, grouping, schema path, and timezone assumptions when comparing this report with another source. Treat it as an operational analytics report, not an accounting P&L.