Receipt anomalies
Open Journal -> Advanced analytics -> Anomalies. This report compares each day's gross receipts with the average of preceding calendar days. It highlights changes for investigation, not their cause or a prediction of future receipts.
Filters
| Field | Purpose |
|---|---|
| Project | All available team projects or one project. |
| Game server | All servers of the selected project or one server. Select a project first. |
| Period | A calendar range, year or custom dates. |
| From (UTC) / Through (UTC) | First and last included dates. Today includes only the elapsed part of the day. |
| Baseline window, days | 1 to 90 preceding calendar days; default 7. The day being assessed is excluded. |
| Drop below, % of average | 1 to 99; default 50. Receipts must be strictly below this percentage of the average. |
| Spike above, % of average | 101 to 10,000; default 200. Receipts must be strictly above this percentage of the average. |
| Show days | All days or only spikes and drops. Summary cards still cover the entire selected period. |
| Payment currency | One currency and precision. Automatic selection uses the first code and scale in the known scoped history through the observation cutoff. |
| Rows per page | 1, 7, 14, 30, 50 or 100 days; default 30. |
Click refresh after changing filters. Reset restores the last 30 days and default thresholds. Settings remain in the page address; reopening starts from the first page.
Average and Thresholds
The baseline is the sum of receipts over the preceding window divided by its number of days. Days without receipts inside known history count as zero. The window can extend before the selected date range; it is not reduced to the visible days.
With an average of 100 and thresholds 50 / 200, receipts of 49 are a drop, 50 and 200 are within thresholds, and 201 is a spike. These are percentages of the average, not percentage changes: 150% means one and a half times the average. Classification uses exact amounts before display rounding.
A longer window reduces the influence of one day on the average. Thresholds closer to 100% flag more changes. Updating settings recalculates the selected period without changing payments.
Daily Results
| Result | Meaning |
|---|---|
| Within thresholds | The day has ended, the full window is known, its average is positive and receipts are within the limits. |
| Spike | Receipts for the finished day are strictly above the upper threshold. |
| Drop | Receipts for the finished day are strictly below the lower threshold. |
| Day in progress | Current receipts are shown, without a final daily classification. |
| Insufficient history | Fewer than the required number of days precede this day since the first known receipt. |
| Zero baseline | The complete window is known but totals zero. No percentage is calculated, even when the current day has receipts. |
The four cards show days, spikes, drops and days within thresholds. Below them are separate counts for unfinished days, insufficient history and zero baselines. These six outcomes do not overlap and together cover the selected period.
Table and Chart
| Column | Meaning |
|---|---|
| Date (UTC) | Calendar day of receipt, newest first. |
| Payments | Separate payments with receipts that day, including guests. Parts of one payment within the day count once. |
| Gross receipts | All qualifying receipts for the day in the selected currency. |
| Guest receipts | Amount received without a master account, already included in gross receipts. Not a count of guests. |
| Baseline average | Daily average for the preceding window. Unavailable for short history. |
| Baseline days | Known preceding calendar days compared with the required window size. |
| % of average | The day's receipts divided by the average, as a percentage. Unavailable for a zero baseline or short history. |
| Result | The day's classification under the selected rules. |
The average has additional decimal precision; the percentage is rounded to two places. Displayed rounding is not used to reclassify the day.
The chart shows the current page, oldest to newest. The solid line is receipts; the dashed line is the baseline average. Hover for amounts. An unavailable average is not drawn as zero. In flagged-only mode the chart also contains only flagged days.
Previous / Next changes pages. If data changes between pages, refresh from the first page. Changing filters resets navigation.
Projects, Servers and Currencies
Project and server filters apply to daily receipts, the baseline and the start of known history. The general selection includes payments without a server; choosing a specific server keeps only its receipts.
The report includes positive confirmed customer receipts, including guests. Test payments, bonus grants and administrative credits are excluded. Reprocessing a settlement does not increase receipts. When payment parts arrive on different days, each part belongs to its own day.
These are original gross receipts, not wallet balances, net profit or receipts after refunds. A later refund does not erase the original payment from this report. Use the payment journal for individual operations.
Currencies and different precision variants are not combined or converted. An explicitly selected missing currency is not replaced with another. The report does not display email addresses or personal payment details.
History and Availability
Select a year or custom range of available history starting from 1900. There is no rolling ten-year restriction. Longer periods remain accessible through daily pages.
The first known receipt marks the start of stored history in this currency and scope. It is not the project's launch date or proof that all receipts have arrived. Days before it and a short initial window are not labelled normal or drops.
Late-arriving data may change amounts and classifications for finished days. Today is marked as unfinished regardless of its current receipts.
An empty table means no matching history, or no deviations when using the flagged-only filter. A temporary failure replaces previous figures and the chart with a warning, not zeros. If a range is too large to calculate, narrow dates or select a project. The first page refreshes periodically while you are not editing filters.