Bonus Report — Operations Log

Bonus Report — Operations Log

The Operations tab in the Bonus Report is a complete, row-level transaction journal for every change to customer bonus balances over a selected period. It records every accrual — whether from a top-up bonus rule, a promo code, or a manual staff correction — and every deduction, including bonus payments for sessions, bar orders, and expired-bonus burn-offs. The log answers the operational question that both club owners and accountants need: “exactly what happened to the club’s bonus liability during this period, and why.”

Unlike the aggregate figures in the Bonus Report Metrics tab, the Operations tab gives you one row per transaction with a labeled source. That distinction matters: a metric that says “1,400 bonuses accrued this week” tells you the total; the Operations log tells you that 800 came from the top-up ladder’s anchor tier, 350 from birthday greetings, and 250 from manual staff corrections. Without this breakdown you cannot manage a loyalty program — you cannot tell which rule is driving costs or whether staff are abusing manual adjustments.

Navigate to Analytics → Bonus Report → Operations. Data can be filtered by period, operation type, source (automation rule, manual correction, promo code), and individual customer.

What the log shows

Each row represents one transaction on a bonus balance. Every row always contains:

Field	What it means
Date and time	When the operation occurred (club’s local time zone)
Customer	Player name or identifier
Type	Accrual (+) or deduction (−)
Amount	Size of the operation in bonus units
Source	What triggered it: automation rule, promo code, manual correction, or expiry
Staff member	Who performed it (for manual ops) or “System” (for automatic ones)

The log is sorted newest-first. Records are immutable: if a wrong accrual needs to be reversed, a separate correcting transaction is created — which also appears in the log, preserving the full audit trail.

Operation types

Accruals

An accrual is bonuses added to a customer’s balance. It appears with a ”+” sign and one of the following sources:

• Automation — a rule in the bonus engine fired: a top-up bonus, session bonus, bar order bonus, birthday reward, or first-visit welcome.
• Promo code — a customer redeemed a promo code that included a bonus grant.
• Manual correction — an admin or owner accrued bonuses directly from the customer card.

For automation-triggered accruals, the specific rule name is always shown — for example, “Top-up ladder: Anchor tier.” This lets you see exactly how many bonuses each ladder tier issued in a period without writing a separate report.

Deductions

A deduction is bonuses leaving a customer’s balance. It appears with a ”−” sign and one of the following sources:

• Session payment — the customer paid for part or all of a session using bonuses (within the limit defined in the tariff settings).
• Bar order payment — bonuses were spent on items from the bar menu.
• Expiry — bonuses reached the end of their validity window set in the automation rule and were burned off. These rows are labeled separately and do not reduce real cash revenue.

Separating expired bonuses from redeemed ones is important: expiry represents a club liability that never materialized into an actual purchase, so it carries no cash impact. A high expiry share in the log signals that customers are not returning frequently enough to spend what they earn.

How to use the filters

An unfiltered monthly log in an active club can run to thousands of rows. The key filters:

Period — always set this first. Starting with a one-week window gives a representative picture and stays small enough to review without exporting.

Operation type — “Accruals only” or “Deductions only.” To assess the cost of your loyalty program, look at accruals. To check that customers are actually spending bonuses rather than hoarding them, look at deductions.

Source — select a specific automation rule. This is the essential filter for auditing a single top-up tier or a specific campaign. For example, filtering on “Birthday rule” shows exactly how many birthday bonuses went out and to whom.

Customer — search by name or phone number. When handling a complaint (“my bonus wasn’t credited”), this filter pulls up the full transaction history for that customer with dates, amounts, and sources — turning a subjective dispute into a factual audit.

Business meaning for club owners

Loyalty program cost control

The Operations log is financial control, not just history. The sum of all accruals in a period is the bonus liability the club has taken on. It is not equal to actual cash lost — bonuses are redeemed at marginal cost and some expire — but it is manageable.

If total accruals spike compared to the prior week, drill into Source: find out whether a rule has an erroneously high percentage, or whether manual corrections are running unusually high.

Auditing manual corrections

Manual corrections are the main risk area. A staff member can — accidentally or deliberately — accrue bonuses without a legitimate trigger. Filtering by Source: Manual correction and then by Staff member shows every manual operation that person performed in the period. This is the standard check when you suspect misuse. For a deeper view of anomalies, see Suspicious Balance Operations.

Verifying a new rule after launch

After launching a new top-up tier or promotion, open Operations 3–5 days later, filter by the new rule, and check:

• How many distinct customers triggered it (unique names in the result)
• Average accrual per operation
• Whether any single accrual is anomalously large (signals an error in the rule conditions)

This is faster than waiting for the weekly Metrics summary to refresh.

Export and accounting reconciliation

The export button (top right) downloads the current filtered view as CSV. The file includes the same columns as the UI plus an internal transaction ID. This ID is useful for reconciling bonus data with an external accounting system or for building dashboards in Google Sheets.

One important distinction for reconciliation: the Operations log shows bonus transactions, not cash transactions. Accruing bonuses is not a cash expense at the moment of accrual. The actual revenue impact occurs when a customer redeems bonuses to pay for a session — at that moment the club forgoes revenue equal to the redeemed amount. For the full financial picture, cross-reference Operations with the Transaction History report, which tracks cash-denominated movements.

Parametric benchmarks

Absolute figures depend on your club size, period length, and program configuration. Focus on ratios:

Metric	What to watch
Accruals vs. deductions	If accruals are several times higher than deductions, bonuses are accumulating faster than they are being spent — either visit cycle is short (customers spend at the next visit, outside your period) or spend motivation is too weak
Expiry share of deductions	Above 30% means bonuses are expiring before use — validity window too long or return frequency too low. Below 5% means customers reliably spend before expiry
Manual corrections share of accruals	Above 10–15% warrants investigation: either automation rules are mis-configured or staff correction practices need review

Related sections

• Bonus Report Metrics — summary figures: total accrued, average check, ARPU, behavioral trends
• Bonus Report Tags — segmenting operations by custom tags
• Top-Up Bonus: Setup and Analytics — how the top-up ladder works and how to measure its effect
• IZI Bonus Engine — reference for rules, events, and conditions
• Suspicious Balance Operations — tool for auditing manual corrections and detecting anomalies
• Customer Transaction History — cash (not bonus) transactions tied to individual customers