The requirement is to classify different types of accrual transactions, such as 'Enrollment Bonus' or 'Flight Purchase'. In the Salesforce Loyalty Management data model, the Transaction Journal object records each individual transaction. This object includes standard lookup fields to Journal Type and Journal Subtype.

The Journal Type is used for high-level categorization (e.g., Accrual, Redemption, Reversal). All the transactions listed in the scenario are of the 'Accrual' type. The Journal Subtype object is specifically designed to provide a more granular classification within a Journal Type. Therefore, the administrator should create a Journal Subtype for each specific case like 'Enrollment Bonus' and 'Member Referral' to properly classify these accrual transactions.

A. Create a custom field on transaction journal object

This is incorrect because it bypasses the standard, built-in functionality of the Journal Subtype object, which is designed specifically for this purpose, leading to a non-standard implementation.

B. Create a custom field on Loyalty Ledger object

This is incorrect because the Loyalty Ledger object tracks a member's aggregate point balance, not individual transactions. Classification must occur at the transaction journal level.

C. Create a Journal Type for each case.

This is incorrect because Journal Type is for broad categories like 'Accrual' or 'Redemption'. Creating a new Journal Type for each accrual reason misuses the data model.

1. Salesforce Help Documentation, Loyalty Management Objects:

Journal Subtype: "Represents the subtype of a transaction journal, such as referral bonus or welcome bonus." This directly aligns with the examples in the question ('Enrollment Bonus', 'Member Referral').

Journal Type: "Represents the type of a transaction journal, such as accrual or redemption." This confirms its use for high-level categories, not the specific reasons mentioned in the scenario.

Transaction Journal: The documentation shows that the Transaction Journal object has standard fields for JournalTypeId and JournalSubtypeId, indicating these are the intended objects for classification.

2. Salesforce Developer Guide, Object Reference for Salesforce and Lightning Platform:

JournalSubtype: The API documentation for the JournalSubtype object describes its purpose as providing a sub-classification for a JournalType. For a JournalType of 'Accrual', JournalSubtype could be 'Product Purchase' or 'Welcome Bonus', which directly supports the correct answer. (Section: Standard Objects > JournalSubtype).