Salesforce Loyalty Management: point expiration date, redemption window, and Expiration Transaction Journal date in the Aggregate Ledger

Use these answers and steps to handle point expiration timing in the aggregate ledger:

1. Determine the redemption window. Members can redeem their points on and until the expiration date itself (for example, on and until 31 March 2026), as long as the point expiration job has not yet run for that day. The [ExpirationDate] field on the [LoyaltyAggrPointExprLedger] object marks the date the points are set to expire, and members retain availability throughout that full day. Members do NOT lose access before the expiration date.

2. Confirm that availability is controlled by job timing, not the date value alone. The points remain redeemable until the point expiration Data Processing Engine (DPE) job runs and creates the expiration journal. If you schedule the job to run during the day of the expiration date, members lose access at that runtime; if you schedule it after business hours or the next day, they keep access through the full expiration day.

3. Set the correct date for the Expiration Transaction Journal. Create the Expiration Transaction Journal on the day AFTER the expiration date (for example, 1 April 2026 when points expire 31 March 2026). This follows the standard DPE logic for point expiration, which expires balances after the expiration date has passed.

4. As an alternative to step 3, schedule your automated batch job to run at the very end of the expiration day (after business hours on 31 March 2026). Running at end-of-day preserves the full redemption window for that date and still reduces the point currency balance correctly.

5. Configure the schedule for the expiration DPE job: go to Setup > scheduled jobs for your loyalty point expiration Data Processing Engine definition and set the run time to either the next day or late evening of the expiration day, consistent with the redemption policy you confirmed in step 1.

6. Verify the expiration is processed correctly: after the job runs, open the affected member's loyalty ledger and confirm an Expiration-type transaction journal exists with the post-expiration date and that the point currency balance is reduced by the expired amount.

Note: This expiration timing applies to currencies configured with the Fixed expiration model. A single Loyalty Program Currency uses one Expiration Model (either Fixed or Activity) and cannot behave as Fixed for some transactions and Activity for others.

Confirm the issue is resolved by setting a test member's points to expire on a chosen date, scheduling the expiration DPE job for the following day, redeeming points on the expiration date itself (which must succeed), and confirming the balance is reduced only after the job runs.