Back to Wallets Main Page

Wallet Transactions created by the system

Automatic Wallet Transactions are transactions created by the System (in contrast to Manual Wallet Transactions that are created by users).
Transactions that are created automatically must be explicitly defined in the Wallet Definitions. System processes that may create Automatic Wallet Transactions include:

• Posting of Financial Transactions
• Cancelling of Financial Transactions
• Prepaid Billing Runs
• Cancelling Wallets
• Changing a Prepaid Subscription Accounts Receivable
• Creation of Customer Events
• Creation and cancellation of Spend Reward Transactions
• Creation and cancellation of Award Reward Transactions
• Cancellation of Award Expiration Reward Transactions
• APPLICABLE UP TO CRM.COM R9.0.0 - Creation of Award Expiration Reward Transactions
• AVAILABLE FROM CRM.COM R10.0.0 - Wallet Balance Expiration Run

Discover below the available Wallet Definitions options for each transaction type along with the result of each automatic action.

Crediting Wallets

There are four cases that may be defined as a Cause for automatically creating a Credit Wallet Transaction:

• On a Prepaid Billing Run
  • A Credit Wallet Transaction is created when a Subscription service is credited by a Prepaid Billing Run.
  • The following log information is also entered:
    • Process name: Prepaid Billing Run
    • Entity name: Billing Run
    • Entity value: The Number of the Billing run
       
• On Payments posting:
  • A Credit Wallet Transaction of equal value is created when a Payment of the Payment Type included in the definition, is posted
  • If the Payment is related with a Voucher which includes Extra Added Value, then the Credit Wallet Transaction "Extra Added Amount" will be set and the Credit Wallet Transaction Amount will be the sum of the initial Payment and the extra amount. In case of a Voucher product an Allotment will be created for that product.
  • The following log information is also entered:
    • Process name: Payment Posting
    • Entity name: Payment
    • Entity value: The Number of the Payment
      
      
• On Credit Note posting:
  • A Credit Wallet Transaction of equal value is created when a Credit Note of the Credit Note Type included in the definition, is posted
  • The following log information is also entered:
    • Process name: Credit Note Posting
    • Entity name: Credit Note
    • Entity value: The Number of the Credit Note
      
      
• On Award Transactions:
  • A  Credit Wallet Transaction is created together with every Award Transaction.  The Spend Conditions defined in the Reward Offer which triggered the Award Transaction and transferred in the Allotment conditions of the Credit Wallet Transactions.
  • The following log information is also entered:
    • Process name: Create Award Reward Transaction
    • Entity name: Reward Award Transaction
    • Entity value: The Number of the Reward Award Transaction

Debiting Wallets

There are three cases that may be defined as a Cause for automatically creating a Debit Wallet Transaction:

• On a Prepaid Billing Run:
  • A Debit Wallet Transaction is created with the amount that was consumed by Subscription services, as calculated by the Prepaid Billing Run.
  • The following log information is also entered:
    • Process name: Prepaid Billing Run
    • Entity name: Rated Billing Item
    • Entity value: The Number of the Rated Billing Item
       
• On Spend Transaction:
  
  • A Debit Wallet Transaction is created together with every Spend Transaction.  The amount and product of the Spend Transaction is transferred on the Wallet Transaction's products.
  • The following log information is also entered:
    • Process name: Create Spend Reward Transaction
    • Entity name: Spend Award Transaction
    • Entity value: The Number of the Spend Award Transaction
      
      
• APPLICABLE UP TO CRM.COM R9.0.0 - On Award Expiration Reward Transaction:
  • A Debit Wallet Transaction is created together with every Award Expiration Reward Transaction. 
  • The following log information is also entered:
    • Process name: Create Award Expiration Reward Transaction
    • Entity name: Award Reward Transactions
    • Entity value: The Number of the Award Expiration Reward Transaction
       
• AVAILABLE FROM CRM.COM R10.0.0 - On Wallet Balance Expiration Run
  
  • A Debit Wallet Transaction is created for every Credit Wallet Transaction that is expired.
  • The following log information is also entered:
    • Process name: Wallet Balance Expiration Run
    • Entity name: Process Run Log
    • Entity value: The Number of the Process Run

Reimbursing Wallets

There are two cases that may be defined as Causes for automatically creating a Wallet Reimburse Transaction.

• On Cancelling a Wallet:
  • A Wallet Reimburse Transaction is created each time a Wallet is cancelled, for the total Balance (provided it is positive) including Extra Added Amounts.
  • Wallet Transaction Allotments are also set, for each product whose available consumption amount is greater than zero.
  • The following log information is also entered:
    • Process name: Wallet Cancellation
    • Entity name: Wallet
    • Entity value: The Number of the Wallet
      
      
• On Changing a Prepaid Subscription Accounts Receivable:
  • A Wallet Reimburse Transaction will be created each time a related Accounts Receivable with a Subscription is changed, for the total Balance (provided it is positive) including Extra Added Amounts.
  • Wallet Transaction Allotments are also set, for each product whose available consumption amount is greater than zero.
  • The following log information is also entered:
    • Process name: Change Subscriber Accounts
    • Entity name: Subscription Action
    • Entity value: The Number of the Subscription action

Voiding Wallets

There are four cases that may be defined as a Cause for automatically creating a Void Wallet Transaction:

• On Cancelling a Payment:
  • When a Payment that resulted in a Credit Wallet Transaction is cancelled and the Payment Cancellation Type is defined in the Cause Definition, the Credit Wallet Transaction is voided.
  • Wallet Transaction Allotments and Extra Added Amount are also set, if the Payment is related with a Voucher.
  • The following log information is also entered:
    • Process name: Payment Cancellation
    • Entity name: Payment Cancellation
    • Entity value: The Number of the Payment Cancellation
       
• On Cancelling a Reward Award Transaction:
  
  • When a Reward Award Transaction related to a Credit Wallet Transaction is cancelled, the related Credit Wallet Transaction is voided.
  • Wallet Transaction Allotments and Extra Added Amount are also set, if the Payment is related with a Voucher.
  • The following log information is also entered:
    • Process name: Payment Cancellation
    • Entity name: Payment Cancellation
    • Entity value: The Number of the Payment Cancellation
    
    
• On Cancelling a Reward Spend Transaction:
  • When a Reward Spend Transaction related to a Debit Wallet Transaction is cancelled, the related Debit Wallet Transaction is voided.
  • Wallet Transaction Allotments and Extra Added Amount are also set, if the Payment is related with a Voucher.
  • The following log information is also entered:
    • Process name: Payment Cancellation
    • Entity name: Payment Cancellation
    • Entity value: The Number of the Payment Cancellation
      
      
• On Cancelling an Award Expiration Reward Transaction
  • When an Award Expiration Reward Transaction that created a Credit Wallet Transaction is cancelled, the Wallet Transaction is voided.
    
  • The following log information is also entered:
    • Process name: Spend Reward Transaction Cancellation
    • Entity name: Spend Reward Transaction
    • Entity value: The Number of the Spend Reward Transaction