Loyalty points redeemed do not always mean a discount was used

A customer can exchange points for a coupon without immediately using that coupon in a purchase. Finance therefore needs both the points activity and the resulting reward record. Record the customer reference, points removed, reward identifier, promised benefit and issue time. Then link any completed purchase that actually used the reward.

Smile documents separate reward states for generation and use, including pending, failed, issued, canceled and used. It also states that gift-card usage is not tracked through its used status. Inspect the relevant commerce or gift-card records when the reward type requires them; a loyalty-system label alone cannot establish every customer's remaining benefit.

Prepare a points rollforward from opening points through earnings, adjustments, redemptions and the actual program's other permitted changes. Separately reconcile rewards from opening unused rewards through new issues, confirmed uses, cancellations and remaining balances. The two schedules should connect through issue events, but they measure different things and should not be forced into the same unit.

In a hypothetical program, customers exchange points for 100 coupons worth $5 each. Seventy coupons appear on completed orders, 25 remain unused and five failed during generation. The issued-and-used history needs investigation if all 100 were reported as successful issues. The $350 applied to orders is a different measure from the $500 requested benefit and the $125 of valid unused coupons.

Resolve failed events with support and the application's actual behavior. Confirm whether points were restored, a replacement reward was issued or the first attempt later succeeded. Keep the failed event and its correction linked so the customer does not receive two valid rewards and finance does not count both as independent obligations.

When an order using a reward is returned, inspect the customer refund, points adjustment and coupon status separately. The program may restore points, replace a reward or leave the original benefit consumed under its terms. Verify the permitted outcome and what the systems actually did. A cash refund alone does not explain the remaining loyalty balance.

Keep manual customer-service grants distinguishable from purchase-earned benefits. Record the reason, approver and related order where appropriate. Repeated grants made to fix a technical failure should be investigated as a system issue, while a goodwill reward should retain its own business purpose. Combining those events obscures both program cost and customer support problems.

Provide the accountant with the program terms, reward types, earning conditions and reconciled outstanding balances. The appropriate accounting depends on the arrangement and reporting framework, including whether benefits relate to an earlier purchase. Do not treat points as a dollar liability using an arbitrary conversion or assume every issued coupon is an immediate expense.

For operating review, show rewards requested, successfully issued and used, with unresolved failures and aged unused benefits. Measure discounts applied to completed orders from actual checkout records. Keep program accounting estimates separate from that observed use measure, and document any estimate changes so a reported cost reduction is not mistaken for an improvement in customer behavior.