Top summary
Direct answer: An ecommerce business should first decide whether loyalty points give customers a material right, then allocate revenue using supportable standalone values, recognize the deferred portion as rewards are redeemed or expire, and reconcile points to the contract liability.
- Points are not merely a marketing cost when they promise an incremental future benefit.
- The accounting population must separate earned points, promotional grants, cash-equivalent credits, and third-party rewards.
- A monthly roll-forward should prove both units of points and the related monetary liability.
Who is this for, and what decision must be completed?
This guide is for a founder, controller, or finance operator running a points-based ecommerce program and preparing monthly or year-end revenue. The decision is whether an award is a separate promise, how much transaction price belongs to it, and when that amount becomes revenue. The workflow is designed for company-operated programs in which customers earn a future discount or free product.
Representative results often explain the phrase “material right” or show one journal entry. They rarely distinguish promotional points from purchase-earned points, connect the customer points ledger to the general ledger, or show how changing redemption estimates affect allocation and breakage. Those are the operational gaps addressed here.
Which awards belong in the accounting population?
Start with contract terms, not the word “points.” Export points issued by reason code: purchase-earned, sign-up, service recovery, referral, manual adjustment, migration, and purchased points. Identify what each award can buy, its expiry, transferability, minimum threshold, and whether another party supplies the reward.
Purchase-earned points may give a customer an incremental option that the customer would not receive without the current purchase. Under ASC 606 and IFRS 15, that can be a material right and a separate performance obligation. A broadly available coupon may not be incremental. A cash refund or store credit created by a return is a different obligation and should not be forced into the loyalty model.
How does the award-classification decision tree work?
This is the first topic-specific original component.
- Was the award linked to a customer contract? If not, assess it as a promotion or other expense rather than automatically deferring current-sale revenue.
- Does it provide an incremental discount or benefit? Compare it with discounts available to similar customers without the purchase.
- Is the benefit substantive when points accumulate? Evaluate the whole program, not one small award in isolation.
- Who controls the future good or service? Principal-versus-agent and third-party arrangements can change measurement and presentation.
- Can standalone value and expected redemption be supported? If evidence is weak, use a conservative documented method and obtain accounting review.
The output is a signed classification memo for each award class. Reperform it when redemption rules, expiry, partners, tiers, or customer economics change.
How is transaction price allocated to qualifying points?
When points are a separate performance obligation, allocate transaction price between today’s goods and the points on a relative standalone-selling-price basis. A practical estimate for points begins with the value of the incremental discount, adjusted for the proportion expected to be redeemed. The exact method and updates depend on the reporting framework and facts.
Allocated amount to points = transaction price × points standalone value ÷ (current goods standalone price + points standalone value).
Do not simply record the retail cost of the future reward as the liability. Cost answers a margin question; revenue allocation measures the promise made to the customer. Also avoid multiplying every point by its headline redemption value without considering thresholds, eligible products, expected redemptions, and discounts customers could receive without points.
What should the monthly points-to-liability map contain?
The second original component is a two-layer reconciliation.
| Movement | Points ledger evidence | Accounting effect | Main control |
|---|---|---|---|
| Earned on purchases | Order, customer, rule version | Add allocated contract liability | No duplicate order awards |
| Promotional grants | Campaign and reason code | Separate assessment; not presumed deferred revenue | Approved campaign population |
| Redeemed | Redemption order and benefit | Recognize allocated revenue as obligation is satisfied | One redemption per point movement |
| Expired | Terms, expiry event, customer history | Recognize only under applicable breakage/expiry policy | No manual early expiry |
| Manual adjustment | Ticket, approver, reason | Depends on underlying cause | Privileged-user review |
| Closing balance | Customer-level outstanding points | Tie to contract-liability subledger | Units and dollars both reconcile |
Reconcile opening points plus issues minus redemptions, expiries, and net adjustments to closing points. Separately reconcile opening contract liability plus new allocations minus recognized revenue and approved true-ups to closing liability. A points tie without a dollar tie is incomplete.
Worked hypothetical example: points earned on a product order
Hypothetical example—not a customer result. Assume a customer pays $120 for goods with a standalone selling price of $120 and earns 1,200 points. The points can provide a $12 incremental discount. Based on a cohort analysis, management estimates 75% of the point value will be redeemed, producing a points standalone value of $9.
| Item | Standalone value | Allocation |
|---|---|---|
| Goods delivered now | $120 | $120 × $120/$129 = $111.63 |
| Loyalty points | $9 | $120 × $9/$129 = $8.37 |
| Total | $129 | $120.00 |
At sale, the example recognizes $111.63 of goods revenue and an $8.37 contract liability, with cash of $120. If half of the expected redeemable points are later redeemed and the obligation is satisfied proportionately, $4.19 of the allocated liability would be recognized, subject to rounding and policy. Interpretation: the liability is based on allocated transaction price, not the $12 headline discount or the future product’s cost.
Limits: this simplified example ignores taxes, tier status, partial redemptions, partner rewards, returns, and changes in estimates. A qualified accountant should approve the policy and treatment of estimate updates and breakage.
How should redemption estimates and breakage be governed?
Build cohorts by issue month, program version, tier, geography, and expiry where those factors materially affect behavior. Compare cumulative redemption curves only after enough time has elapsed. A newly launched program does not have mature internal history; external benchmarks may not reflect its rules or customers.
Breakage is not a plug used to reduce the liability. Recognition must follow the applicable standard and be constrained when a significant reversal is possible. Preserve the dataset, observation window, exclusions, model version, reviewer, sensitivity, and subsequent actuals. A change in estimate should be visible rather than silently overwritten.
Which anomalies should be investigated first?
- Negative customer balances or redemptions exceeding issued points.
- Large manual grants, backdated expiry, or privileged-user adjustments.
- Points issued on cancelled, refunded, fraudulent, or test orders.
- A monetary liability that moves without a corresponding points movement.
- Redemption assumptions that improve while actual cohorts deteriorate.
- Third-party rewards booked as though the business controlled the underlying benefit.
Prioritize by monetary exposure, control failure, and reversibility. A small interface delay is different from an unauthorized award or an unsupported breakage release.
What steps create a reviewable month-end close?
- Freeze order, returns, points, redemption, and rule-version exports for the same cutoff.
- Classify award types with approved accounting conclusions.
- Reconcile points movements by customer and reason code.
- Calculate new revenue allocations with controlled standalone-value assumptions.
- Match redemptions to fulfilled rewards and release the related liability.
- Run cohort and breakage analysis; document any estimate change.
- Post the journal and tie it to the contract-liability roll-forward.
- Retain exceptions, approvals, and subsequent-resolution evidence.
Definition of done: closing points tie to the customer system; the monetary roll-forward ties to the general ledger; classifications and assumptions are approved; and every material exception has an owner and disposition.
What common failures distort revenue?
Expensing only the expected reward cost can recognize too much revenue when points are a separate promise. Deferring points at face value can overstate the liability. Treating all unredeemed points as immediate breakage can accelerate revenue without evidence. Mixing return credits with loyalty points obscures both obligations. Failing to reverse points on cancelled orders creates orphan awards.
Tax treatment can differ from financial reporting. Indirect tax, unclaimed-property, consumer-protection, and expiry rules vary by jurisdiction. This guide does not determine legal enforceability or tax filing treatment.
When is specialist review necessary?
Obtain qualified accounting advice for material programs, audited reporting, complex tiers, partner-funded rewards, purchased points, cash redemption, indefinite expiry, acquisitions, migrations, or weak redemption history. Legal and tax advice may be needed for expiry, customer notices, unclaimed property, and indirect taxes.
Caigeek can take order-level sales, loyalty events, rule versions, redemption catalog data, refunds, and the general ledger to produce an award-classification register, cohort analysis, points-to-liability roll-forward, exception list, and journal support. Management and its advisers remain responsible for policy conclusions.
Self-check before sign-off
- Award classes and rule versions are complete.
- Material-right conclusions are documented.
- Standalone values use supportable incremental benefits.
- Points and dollars both roll forward.
- Refund and cancellation reversals are captured.
- Breakage is evidence-based and reviewed.
- Journal, subledger, and disclosure support agree.
Sources and last updated
Last checked: 19 August 2026.
- IFRS Foundation, IFRS 15 Revenue from Contracts with Customers
- IFRS Foundation, customer loyalty points discussion
- Deloitte DART, material rights and loyalty programs
- EY, Revenue from contracts with customers
- LegalClarity, loyalty-program accounting overview
FAQ
Are loyalty points always deferred revenue?
No. First assess whether the award provides a material right under the applicable revenue standard.
Should the liability equal points outstanding times face value?
Not automatically. Allocation generally uses relative standalone values and supportable redemption expectations.
When is loyalty-point revenue recognized?
Generally as the related reward obligation is satisfied, or under applicable expiry and breakage guidance.
What should be reconciled each month?
Reconcile issued, redeemed, expired, adjusted, and outstanding points to the liability roll-forward, revenue journal, and reward fulfillment.