To understand unused loyalty rewards, ask for a dated opening balance, every point movement during the period, and a dated closing balance. Then request enough detail to trace those totals to individual accounts and transactions. Include earned, redeemed, expired, adjusted, and outstanding points, with the source and date for each figure.
That gives you an operational picture of what guests still hold. It does not, by itself, tell you the amount to record as a financial liability. An accountant should assess the financial treatment using your program terms and applicable rules.
Start with the records behind the balance
Choose a review period and specify its start and end times, including the time zone. Ask the vendor for both a summary report and the underlying transaction detail for the same period. A total on a dashboard is useful for a quick check, but it is hard to audit if you cannot see what changed it.
Request these items:
- Opening and closing balances: Total outstanding points at each cutoff, with account-level balances if available.
- Points earned: The units added, transaction date, account identifier, and associated order or reason.
- Points redeemed: The units deducted, redemption date, and reward or transaction reference.
- Points expired: The units removed, effective date, and policy or rule applied.
- Adjustments and reversals: Manual changes, refunds, canceled orders, corrections, and the reason and staff identifier where recorded.
- Program rules: Reward thresholds, eligible rewards, expiration terms, and any rule changes effective during the period.
For each field, ask where it comes from: a loyalty ledger, the restaurant POS system, an online order record, or a manual entry. Confirm whether the report covers every location and order channel you intend to include. If one channel is missing, label that gap rather than treating its activity as zero.
Keep observed data separate from assumptions. A recorded deduction of 200 points is an observation. Assuming every remaining point will eventually be redeemed is a scenario. Assuming a point has a particular dollar value is also a scenario, not a fact established by the point balance.
Reconcile the balance before estimating value
Use this basic check: opening points plus earned points, minus redeemed points, minus expired points, plus or minus documented adjustments, should equal closing points. Investigate differences before using the closing number for planning.
The following worksheet is hypothetical. Both outcomes use the same opening balance, earnings, and redemptions. The only difference is the number of points that actually expired under the assumed program rules. There are no adjustments in either outcome.
| Point movement | Outcome A | Outcome B | What to check |
|---|---|---|---|
| Opening balance | 1,200 | 1,200 | Prior period closing report |
| Earned | +800 | +800 | Eligible order records |
| Redeemed | −500 | −500 | Completed reward transactions |
| Expired | −100 | −300 | Effective dates and account detail |
| Adjustments | 0 | 0 | Refunds and manual changes |
| Closing balance | 1,400 | 1,200 | Account balances at the cutoff |
In outcome A, 1,200 + 800 − 500 − 100 = 1,400 outstanding points. In outcome B, 1,200 + 800 − 500 − 300 = 1,200. Both calculations balance, but the difference matters: the owner needs evidence that supports the expiration count, not just a report that adds up.
For this example, choose a workflow that can show the 200-point difference by account and effective date. A summary that produces either closing number without that detail is not sufficient for the review. If the vendor can only provide a total, ask how corrections will be identified and documented before accepting it as the regular source.
The closing points also do not reveal how many rewards guests can redeem. Suppose a reward requires 500 points. A combined balance of 1,400 points is an arithmetic equivalent of 2.8 such rewards, but guests cannot necessarily redeem 2.8 rewards. If those points are spread across accounts below the threshold, none may currently qualify. Request account-level balances and the applicable reward rules to count actually redeemable rewards.
Separate point counts from financial estimates
Once the units reconcile, ask your accountant what additional information is needed to evaluate recognition and local rules. Provide program terms, transaction records, reward options, and any changes in policy. Do not convert the closing point balance into a liability simply by multiplying it by a guessed point value.
For operational planning, you can model what a possible set of redemptions might cost the restaurant. Keep that model separate from accounting treatment. State the reward assumed, the number of redemptions, the cost basis, and which costs are included.
For example, assume three guests each redeem a qualifying reward for an item with a $4 direct ingredient cost. The estimated ingredient cost is 3 × $4, or $12. This scenario includes that variable ingredient cost only. It excludes fixed costs, other variable costs such as packaging or labor, and exception costs such as replacements or corrections. It is not a sales total, processing fee, or financial liability.
Ask the vendor whether its reports distinguish points from reward counts and whether an export includes the reward type. If a report displays a dollar estimate, ask how it calculates that figure, which costs it includes, and whether you can inspect or change the assumptions. The loyalty reward cost guide can help frame the operating-cost questions; your accountant should handle the financial classification.
Find the failure before it reaches the report
A balanced-looking report can still be wrong. For example, an order may earn points and then be refunded, while the points remain on the account. The closing total may match the ledger, but the ledger may not reflect the program rule for that refund.
Assign the shift manager or another named loyalty administrator to review exceptions. That person should compare a sample of refunded or canceled orders with the associated point movements, record any mismatch, and route the correction to whoever has permission to make it. Keep the original entry, correction, reason, date, and approver visible where the system permits. If the system cannot retain that history, agree on a separate controlled exception log.
Also check timing. An order placed before the cutoff may be refunded afterward. Decide which period each event belongs to in the operational report and make sure the vendor can show the event dates. Do not silently change a prior report without documenting the revision.
Other useful checks include duplicate accounts, manual point grants, and a reward redemption reversed after an order cancellation. Ask how each appears in the export and whether the closing balance can be recreated from the movements. The restaurant loyalty program guide covers the broader program workflow; here the priority is a reliable record of what remains outstanding.
Set a pass-or-fail vendor demonstration
Before committing, give each vendor the same fictional transactions and request a demonstration in a sandbox or other isolated practice environment. No real card payment, guest message, or courier dispatch should occur. Confirm those safeguards before the exercise starts. A simulated check is not a live service pilot; if you later run a live pilot, agree on its scope and controls separately.
- Set an opening balance, add points for a fictional eligible order, redeem some, and apply an expiration. Ask the vendor to show the closing balance and the individual movements.
- Simulate a refunded order and show the point treatment required by the fictional program rules. Ask the vendor to identify any mismatch and demonstrate the correction or explain the manual process.
- Export or otherwise provide the summary and detail for the same cutoff. Check that identifiers, dates, movement types, and units allow the reviewer to trace the result.
- Ask the vendor to distinguish a reward equivalent from rewards currently redeemable by individual accounts, and to explain any displayed dollar estimate.
Pass: The closing balance reconciles to the movements; the refund exception is visible and handled according to the stated test rule; and the reviewer can trace the result to account-level detail without unexplained changes. A documented manual step can be acceptable if the owner is willing to perform it and the audit trail remains usable.
Fail: A movement is missing, the balance cannot be reconciled, the refund mismatch is hidden, or the vendor cannot explain the data behind the result. Assign the loyalty administrator to record each exception and its resolution. Have the accountant review the eventual financial treatment separately.
Next, take your required fields and demonstration checklist to Fleksa's marketing tools. Compare your requirements with the available loyalty workflow and confirm current reporting and export support before choosing it.
Frequently asked questions
Are outstanding points the same as a liability?
No. Outstanding points are an operational unit count. An accountant should assess whether and how the program creates a financial liability under its terms and applicable rules.
Can I divide total points by a reward threshold to count redeemable rewards?
That gives an arithmetic equivalent, not necessarily the number guests can redeem. Check individual account balances and the rules for each reward.
What if the vendor cannot provide transaction-level detail?
Ask for an alternative traceable record and a documented correction process. If neither supports your reconciliation and exception checks, treat the demonstration as a fail for this requirement.
