Skip to main content
Xoxoday Loyalife surfaces rebate details directly within a member’s transaction history, presenting the originating purchase, the rebate percentage applied, and the net reward credited — all in a single, auditable record.

What a Rebate Entry Looks Like in Practice

When a qualifying transaction triggers a rebate, Xoxoday Loyalife appends a structured rebate row immediately beneath the parent transaction. This keeps the full earning event together in one view rather than scattering it across separate reports. A typical rebate entry in the transaction history includes the following fields:
  • Transaction ID — a unique reference linking the rebate to the originating purchase
  • Transaction Date — timestamp of when the purchase was processed
  • Purchase Amount — the gross spend that qualified for the rebate
  • Rebate Rate — the percentage configured in the active loyalty program rule (for example, 2% cashback on all invoice payments above ₹10,000)
  • Rebate Amount — the calculated reward value credited to the member’s account
  • Status — whether the rebate is Pending, Approved, or Settled

A Concrete Example

Consider a distributor who processes a ₹50,000 invoice through a channel loyalty program. The configured rebate rule is 1.5% on all B2B purchases. The transaction history would display:
FieldValue
Transaction IDTXN-20240610-00417
Purchase Amount₹50,000
Rebate Rate1.5%
Rebate Credited₹750
StatusApproved
This entry is visible to both the member and program administrators, creating a shared audit trail without requiring separate reconciliation reports.

Transparency Across Roles

Xoxoday Loyalife makes the rebate record accessible at every level. Members see the credit in their personal transaction history. Program managers can filter, export, and audit rebate activity from the admin console. If the program integrates with an ERP such as SAP SuccessFactors or a finance tool connected via API, the same rebate data flows downstream to keep accounting aligned. Rebate statuses update in real time as approvals move through the configured workflow. A rebate marked Pending becomes Approved once the validation rule is satisfied — for example, after the purchase is confirmed by the brand or the cooling-off period expires. Members receive a notification at each status change, so there is no ambiguity about when their reward is accessible.

Configuring Rebate Display Rules

Program administrators control which fields are exposed to members versus kept internal. Xoxoday Loyalife supports role-based visibility, so a channel partner sees the rebate amount and status while the underlying rule logic and margin data remain hidden. This balance between transparency and confidentiality is set at the program tier level, not on individual transactions. Learn more: Xoxoday Loyalife Help Centre — General

How are rebate rules configured in Loyalife?

Learn how program administrators define rebate percentages, qualifying transaction types, and approval workflows in the Loyalife rules engine.

How does points earning appear in transaction history?

Understand how Xoxoday Loyalife records points accrual events alongside purchases, conversions, and expiry in a unified transaction log.