You are here:
How Accrual Cancellations Are Processed
When an accrual transaction is canceled, the member’s balance must be debited with the points they accrued. So, accrual transactions are canceled only if there’s sufficient balance, including the negative point balance.
Considerations
- If you cancel an accrual transaction for a currency with synchronous tracing, the system automatically creates a debit ledger and creates related traceability associations in the Traceability Loyalty Ledger object.
- If you cancel an accrual transaction for a currency with asynchronous tracing, the system automatically creates pending trace records for any redemptions that consumed points from the canceled accrual.
- When only Point Tracing for Fixed Duration Currencies is enabled, accrual transactions can’t be canceled if points credited by at least the threshold number of associated ledgers haven’t expired. By default, the threshold is 1,500. So, you can cancel a transaction with 1,600 ledgers if points credited by 300 of those ledgers have expired. However, you can't cancel a transaction with 1,600 ledgers if points credited by only 50 of those ledgers have expired.
Adria Darby now wants to return the shoes. They received 100 Reward Points and 500 Bonus Points, and CL1 and CL2 were created for the purchase. The program creates a transaction journal containing two debit ledgers, DL3 and DL4, for 100 points and 500 points, respectively.
| Ledger ID | Type | TJ ID | Points | Loyalty Program Currency | Currency Subtype | Expiration Date |
|---|---|---|---|---|---|---|
| CL1 | Credit | TJ1 | 100 | Member Points | Reward Points | 1/1/2025 |
| CL2 | Credit | TJ1 | 500 | Member Points | Bonus Points | 1/1/2025 |
| CL3 | Credit | TJ2 | 2000 | Member Points | Partner Points | 1/1/2025 |
| DL1 | Debit | TJ3 | 500 | Member Points | ||
| DL2 | Debit | TJ4 | 300 | Member Points | ||
| DL3 | Debit | TJ5 | 100 | Member Points | ||
| DL4 | Debit | TJ5 | 500 | Member Points |
The original accrual ledgers for this transaction, CL1 and CL2, are associated with two debit ledgers, DL1 and DL2. The program must remove previous trace associations with these credit ledgers, and create a redemption logic with existing accruals. Here’s what happens in the Traceability Loyalty Ledger object.
- DL1 and DL2 are now associated with CL3 because it has a balance of 1800 points.
- Previously, DL1 was split between CL1 and CL2. Now, because CL3 has sufficient balance for DL1, only one DL1 association is created for 500 points.
- Two debit records for the accrual cancellation, DL3 and DL4, are created and associated with the original credit ledgers, CL1 and CL2. The Action Type for this record is updated to Credit Cancellation to indicate the type of association.
| Debit Ledger ID | Credit Ledger ID | Action Type | Points | Currency | Currency Subtype |
|---|---|---|---|---|---|
| DL1 | CL3 | Debit | 500 | Member Points | Partner Points |
| DL2 | CL3 | Debit | 100 | Member Points | Partner Points |
| DL2 | CL3 | Debit | 200 | Member Points | Partner Points |
| DL3 | CL1 | Credit Cancellation | 100 | Member Points | Partner Points |
| DL4 | CL2 | Credit Cancellation | 500 | Member Points | Partner Points |
Details of the member’s fixed-type non-qualifying points that are set to expire on a particular date are stored in the Loyalty Aggregated Point Expiration Ledger object. When an accrual is canceled, it reduces the number of points balance set to expire on the expiration date.
