Page Comparison

Accounts Receivable of the customer associated with the event, or (in case of rewards) of the participant who will benefit from the awards.

Purchase Customer Event: ID Number of the event that the spend request is used to settle.

Performed By Unit: The unit that initiated the event. E.g., the store where the award was redeemed.

 Performed On (date/time)

Requested Spend Amount: The amount that should be spent.  Applicable and mandatory if it is enabled through the spend request rules of the active customer events definition.  In this case, the 'spend amount' defaults to the total purchase customer event amount and can be edited.

Classification: The classification of the customer event that can be evaluated through rewards to award a customer. Only customer event classifications associated with the specified customer event type can be selected.

Actual Spend Amount: The redeemed amount.  Applies only to automatic awards and not to the instant spending process.

Life Cycle State: 'Posted' or 'Cancelled'.

Reduction Method of requested amount (read-only). The reduction method depends on the 'Performed by Unit' of the purchase customer event for which the spent event is settlineg. If that unit is mapped to a rewards participating merchant, then the reduction method defined on the merchant is adopted.

• Front-End Reduction: Performed by the front-end system (e.g., a point of sale).

• Back-End Reduction: Performed by a back-end system (e.g., PayPal).
  
  

  Note
  'Reduction method' of spend request events which are not created through an instant spent or automatically (on the creation of a purchase customer event) it's always set to 'Front End'. Otherwise if created through an instant spend or automatically then the reduction method is set based on the 'Performed By Unit' of the associated purchase customer event.

  
  
  

Instant Spend (read-only, set by the system): Indicates whether the event was created as a result of an instant spend Reward Offer.

Automatic Spend (read-only): Indicates whether the event was created as part of the automatic awards spending process (as defined by the rewards merchants and participants)

External system (read-only): Defines the third-party system that generated the customer event, e.g., a point of sale or portal. It can only be set through the WEB APIs.

External System Reference Number (read-only): Provides a unique ID for the event (in the external system and CRM.COM).

Results from the spending of awards and can generate a transaction that debits the wallet of the participant. 

'Spend request customer event rules', which may apply when creating reward spend transactions, are configured in the customer event definition.