Xoxoday Loyalife distinguishes between pending and posted points, allowing only fully posted points to be redeemed while applying configurable compliance checks at every redemption event.
Understanding Posted Points
In any enterprise loyalty program, not every earned point is immediately available for use. Xoxoday Loyalife separates the lifecycle of a point into distinct states — pending, posted, and redeemed — so that administrators maintain full control over what members can actually spend. A posted point is a credit that has been fully confirmed, validated, and reflected in a member’s balance. Unlike pending points, which may still be subject to approval workflows or hold periods, posted points represent a settled transaction. Members see only their posted balance, which prevents confusion and eliminates the risk of over-redemption against unconfirmed credits.How Points Move from Pending to Posted
Points are typically earned through behaviors like completing a purchase, hitting a performance milestone, or participating in an engagement campaign. Xoxoday Loyalife holds these credits in a pending state until the configured posting rules are satisfied — for example, a 30-day return window for transactional rewards, or manager approval for peer recognition points. Once all conditions are met, the system automatically posts the points to the member’s active balance. Administrators can configure posting delays, bulk posting schedules, or event-triggered posting directly from the Loyalife admin console. This is especially useful for organizations running Loyalife alongside HR systems like Workday, SAP SuccessFactors, or Darwinbox, where reward events may originate from external triggers that need reconciliation before posting.Compliance at the Redemption Layer
Xoxoday Loyalife applies compliance controls at the moment of redemption, not after. When a member initiates a redemption, the platform checks the request against a set of configurable rules before the transaction is approved. These rules can include minimum point thresholds, category restrictions, geography-based eligibility, and tax reporting requirements. For enterprise customers operating across multiple jurisdictions, this compliance layer is critical. For example, if a member in a region with specific gift taxation rules attempts to redeem a high-value reward, Xoxoday Loyalife can automatically flag the transaction, apply the correct tax treatment, or route it for manual review — all without manual intervention from the rewards team. This architecture supports audit requirements under frameworks like ISO 27001 and SOC 2 Type II, since every redemption event generates an immutable log entry that captures the member, the point balance at the time of request, the compliance checks performed, and the outcome.What Admins Can Configure
Redemption compliance in Xoxoday Loyalife is not a black box. Program administrators can define rules at the tier level, the reward category level, or the individual member segment level. A common use case is restricting high-value catalog redemptions to members who have held a certain tier for a minimum number of days, ensuring that gaming or fraudulent point accumulation cannot immediately convert into tangible rewards. Notifications delivered through Slack or Microsoft Teams can also be configured to alert compliance or finance teams when redemptions exceed defined thresholds, keeping oversight seamless without requiring manual log reviews. Learn more: Xoxoday Loyalife Help Centre — GeneralHow do point expiry rules work in Loyalife?
Understand how Xoxoday Loyalife manages point expiry, grace periods, and member notifications across program tiers.
How does Loyalife handle reward catalog compliance?
Learn how Xoxoday Loyalife enforces eligibility rules, tax handling, and category restrictions across the reward catalog.