Excerpt

hidden	true

Understand the usage of Wallets within CRM.COM

What does this section cover?

Panel

name	blue

What

are Wallets

are Wallets?

A wallet Wallet is an a type of account which holds contains an amount of money that can be used to fund transactions within CRM.COM. A wallet is used It works as a mini-ledger that can easily be topped up by various payment events, or spent by CRM.COM functions such as a prepaid subscription. Wallets can be managed through wallet Prepaid Subscriptions or the Redemption of Awards.
Wallets are managed through Wallet-specific processes which can create, update or cancel wallets or generate wallet transactions Wallets manually or automatically, as well as generate Wallet Transactions that credit, debit or refund amounts in walletsrefund Wallets.

Optionally, Wallets can be configured so that the Transactions affecting their Balance automatically generate the respective Financial Transactions on the related Accounts Receivable.

Wallets Glossary

A debit wallet transaction is a type of wallet transaction which is used to credit (i.e., add an amount of money) into the wallet. The entity (i.e., specific product) and entity value (amount consumed by the specific product) can be optionally specified, in order to be validated against any allotment amount and therefore use that allotment amount.
If the Credit Transaction is to be created automatically then this will be defined in the Wallet Definitions - Crediting Causes

Terms

Descriptions

Wallet Balance

The amount of money which is available (credits less debits) in a wallet Wallet and can be used to carry out transactions within CRM.COM. In more technical terms, the balance is the credits less the debits

Wallet Identifier

A value that uniquely identifies the wallet. It can be a direct identifier like the wallet ID or wallet number or an indirect identifier like the related accounts receivable’s ID or number

Wallet Allotments

Wallet allotments are used to identify restrictions on how the wallet available amount, generated by wallet credit transactions, can be consumed

Wallet Credit Transaction

Wallet Transactions

Transactions which are used to debit or credit a Wallet.

Wallet Credit Transaction

A transaction that funds the Wallet. Credit Wallet Transaction amounts:

can be allotted to specific products
can be assigned specific days of the week or times of the day when they can be spent
can be appointed specific shops/departments where they can be spent.
can have a validity date set to designate the day, from which the amount can be spent

Credit Transactions created automatically are defined in the /wiki/spaces/WIP/pages/10008390.

Wallet Debit Transaction

A

debit wallet transaction is a type of wallet transaction which is used to debit (i.e., deduct an amount of money) from the wallet. The entity (i.e. specific product) and entity value (amount consumed by the specific product) can be optionally specified, in order to be validated against any allotment amount and therefore use that allotment amount
If the Debit Transaction is to be created automatically then this will be defined in the Wallet Definitions - Debiting Causes

transaction that deducts funds from the Wallet.

Debit Transactions created automatically are defined in the /wiki/spaces/WIP/pages/10008390

Wallet Reimburse Transaction

A reimburse wallet transaction is a type of wallet transaction which is used to debit (i.e. deduct an amount of money) the wallet, in order transaction that deducts funds from the Wallet to pay back an amount of money, or to . The Reimburse Transaction can also use that amount in any other processes (for example to convert the wallet remaining amount into a credit financial transaction which will be allocated against the Financial Account belonging to the wallet holder, which can either be paid back to the customer or not)
If the Reimburse Transaction is to be created automatically then this will be defined in the Wallet Definitions - Reimburse Causesfor processes other than payback. It can, for example, convert the amount remaining in the Wallet into a credit Financial Transaction and allocate it against the Wallet holder's Accounts Receivable.

Reimburse Transactions created automatically are defined in the /wiki/spaces/WIP/pages/10008390

Wallet Void Transaction

A

void wallet transaction is a type of wallet transaction which is used to cancel (reverse) a wallet transaction of any type (

transaction that cancels or reverses any type of Wallet Transaction (credit, debit, reimburse)

and make it non-visible to the wallet holder. A wallet void transaction

by voiding it. A Wallet Void Transaction is always related to the

wallet transaction

Wallet Transaction that it

voids.
If the Void Transaction is to be created automatically then this will be defined in the Wallet Definitions - Void Causes

Wallet Transfer Transaction

Status

colour	Red
title	Available from CRM.COM R9.0.0

A wallet transfer transaction is a type of wallet transaction

cancelled

Wallet Transactions can either be voided by the System or manually. Events causing the voiding of Transactions by the System are defined in the /wiki/spaces/WIP/pages/10008390

Wallet Transfer Transaction

A transaction which is used to transfer money from one wallet Wallet to another. The Wallet Transfer transaction Transaction refers to two wallets; the wallet Wallets, the (debit) Wallet from which money will b transferred from (i.e. the wallet being debited) and the wallet to which money will be transferred to (i.e. the wallet being credited).

Wallets Key

is transferred and the (credit) Wallet to which money is transferred.

Wallet Allotments

Restrictions on how the amount available in the Wallet can be spent. For example, from a Balance of €20, there can be an Allotment of €15 to be spent exclusively on Product A.
Allotments on Debit Transactions provide information on how the Balance was spent.

Credit Wallet Allotments: Wallet Allotments that credit the Wallet, which can be created by Credit Wallet Transactions, Voided Debit Transactions or Voided Reimburse Transactions.
Debit Wallet Allotments: Wallet Allotments that debit the Wallet, which can be created by Debit Wallet Transactions, Reimburse Wallet Transactions or Voided Credit Wallet Transactions.

Validity Consumption Date

The date from which allotment funds are available for spending. Before this date, the funds are not considered in the calculation of the Wallet Balance.

Wallet Transaction Expiration Date

Status

colour	Green
title	Available from CRM.COM R10.0.0

A date available on Credit Transactions (Credit Wallet Transactions, Transfer Wallet Transactions) that indicates the expiration of the credit amount.

Note
Used by the System Allocation Process to allocate debit transactions on credit transactions, and by Wallet Balance Expiration Runs to expire Wallet Amount that has not been spent and is expired.

Wallets Key Processes and Concepts

Balance Calculations

Wallets have their own balance as with accounts. In the case of wallets there are 2 fields providing information related to balance.

Note:Wallet Transactions with classification Transfer are not taken into account during wallet balance calculation.
This is because transfer transactions are related to a debit and a credit wallet transaction which in turn are considered during balance calculation.Estimated Consumption valuesAvailable from CRM.COM R9.0.0be retrieved.

Processes / Concept Description

Transfer Money between Wallets Money can be transferred between Wallets belonging to different owners. Transferring money triggers the creation of two new Wallet Transactions, a debit for the current Wallet from which money is transferred and a credit for the new Wallet to which the money is transferred. The transfer function can be accessed from the Wallets Data Entry or the Wallets Transactions Data Entry pages.

Expiration of Wallet Balance

Status

colour	Green
title	Available from CRM.COM R10.0.0

The Wallet Balance Expiration process is available and is used to identify the Wallet Amount that has not been spent and has expired.
The process identifies the amount to expire, based on the Expiration Date found in Credit Transactions and the amount that is already spent. The unspent amount is then debited from the Wallet.

The resulting debit reflecting the expired amount is directly allocated against the expired credit amount.
View Using Wallet Balance Expiration Run Definitions for more information on expiring Wallet Balance.

Note
If the expired amount is created by Reward Award Transactions, then the respective Award Expiration Transactions will be created.

Anchor

	allocation
	allocation

Allocation for Wallet Transaction Allotments

Status

colour	Green
title	Available from CRM.COM R10.0.0

Funds spent from the Wallet (e.g. Debit Wallet Transactions) are allocated against funds available in the Wallet (money from Credit Wallet Transactions).
The System first allocates the debit to the credit with the oldest Expiration Date. In case a Credit Transactions with an expiration Date is not present, then the FIFO principle is applied, i.e. the Debit Transactions are allocated against the Credit Transactions with the earliest Created Date.

Note
The allocation takes place within the same allotment group, and the Validity Consumption Date is also taken into consideration.

Wallet Balance Calculations

A positive Wallet Balance indicates how much money is available in the Wallet to be spent, while a negative Wallet Balance indicates how much money is owed.

Note
The balance logic of a Wallet is opposite to that of the Accounts Receivable, where a positive amount indicates money owed to the company and a negative amount indicates money owed to the customer by the company.

Two fields provide information related to Wallet balance:

Wallet Balance
Balance = (credit WT amounts + voided debit WT amounts + voided reimburse WT amounts) - ( debit WT amounts + reimburse WT amounts + voided credit WT amounts)
Product Balance
Balance = (credit WTA amounts + voided debit WTA amounts + voided reimburse WTA amounts) - ( debit WTA amounts +

reimburse WTAamounts

reimburse WTA amounts + voided credit WTA amounts)

WTA = Wallet Transaction Allotment (related to a specific product)

Note
Transfer Wallet Transactions are not taken into account during the calculation of the Wallet Balance calculations, as they are derived from already accounted debit and credit Wallet transactions.

Estimated Consumption Values

Wallets are used by prepaid Prepaid Subscriptions for to handle billing and payments. Via Wallets you can check display the date by on which a Prepaid Subscription expires (based on its products and the price plan rates) will be disconnected.

Consumption Amount Calculation for long periods

If the remaining consumption amount covers is more than the next 6 six months, then the estimation may not be as precise.
If the remaining consumption amount covers is more than the next 3 three years, then the estimation no results will not be able to retrieve any results

Info

Status

colour Red

title

Note
The maximum estimated time is

now configurable through Configuring Prepaid Billing Run Definitions. The default value is 1 year

one year by default, but

it

can be configured

to be more. The system will estimate up to the value that is configured. i.e. you can configure the Maximum estimation to be up to 10 years.( You no longer have the maximum 3 year threshold)Calculations of remaining balance and consumption days is done

for more through /wiki/spaces/WIP/pages/10008771. The 3-year limit on the maximum estimation period no longer applies.

The calculations below are performed by the Prepaid Billing Run:

Once BR Once a BR (Billing Run) is executed the remaining amount on the Wallet, and the remaining product allotted amount is are calculated.
The cost of the product is then calculated per day using according to the price provided on the respective Price Plan.
- If more than one products exist then, the sum of all the products will be is calculated. For example:
  - Product Allotted = Cost per Product per day
  - Wallet = Sum of (Cost per Product per day)
Remaining consumption days (Wallet) = Remaining Balance / Sum of (Cost per Product per Day)
Remaining consumption days (Product) = Remaining Allotted Amount / Cost per Product per Day

Note

If Unless the UOT (Unit of Time) of a product in the Price Plans is not /wiki/spaces/WIP/pages/10008533 is set to 'Daily', then according to the month the calculation is made and of the daily rate will vary . See according to the number of days in each month, as in the example below.:

	January (31 Days)	February (28 Days)	April (30 days)
Monthly Product Rate	31	31	31
Daily Rate Estimation	31/31 = 1	31/28 = 1.11	31/30 = 1.03

Voiding Wallet Transactions

Wallet Transactions are voided (reversed) instead of cancelled. All types of Wallet Transactions can be voided except Transfer Wallet Transactions. When a Wallet Transaction is voided, the System creates a Void Wallet Transaction which is an exact opposite of the initial transaction.

If you void a (-) Debit Wallet Transaction, then a (+) Void Wallet Transaction is created.
If you void a (-) Reimburse Wallet Transaction, then a (+) Void Wallet Transaction is created.
If you void a (+) Credit Wallet Transaction, then a (-) Void Wallet Transaction is created.

Automatic Generation of Wallet Transactions

Wallet Transactions can be manually created via the Wallet Transactions Data Entry page.

Provided it is configured to do so (via the active Wallets Definition), CRM.COM can automatically generate Wallet Transactions of any type through various System processes.

CRM.COM processes that can be configured to automatically generate Wallet Transactions are the following:

Creating Financial Transactions
Cancelling Financial Transactions
Executing Prepaid Billing Runs
Cancelling Wallets
Creation of Customer Events
Creation and cancellation of Spend Reward Transactions
Creation and cancellation of Award Reward Transactions
Creation and cancellation of Award Expiration Reward Transactions
Status
colour Red

Wallets Network Characteristics

title Applicable up to CRM.COM R9.0.0

Wallets Viewing & Access Controls

Business Network Characteristics define the level of access for each record. i.e., whether it will be available for selection, viewing , or editing etc.

Entity	Network Characteristics	Description
Wallets	Implicit Viewing Access Entities Accounts Receivable based Entities	Implicit Viewing Entities: Wallet records can be accessed, viewed and modified by users that belong to the Group defined at the Owned By Group of the related Accounts Receivable, or that belong to a group that collaborates with the specified group, or by Super Users. Accounts Receivable based Entities: Wallets cannot be created unless an Accounts Receivable is selected.
Wallet TransactionsTransaction Types	Controlled Selection Entities	A Wallet Transaction Typecan be added on a Wallet, provided the user adding the Wallet Transaction Typebelongs to one of the Allowed Organisational units defined in the Wallet Transaction Type, or a collaboration exists between the user's unit and the Allowed Organisational Unit of the Wallet Transaction Type, or if the user is a Super User.

Wallets Related Related Modules

Wallets

Interaction Entity	How Wallets interact with Entity
Accounts Receivable	Wallets are owned by Accounts receivableAn Accounts Receivable must be selected to create a Wallet. The System can be configured as such that transactions affecting the Wallet also affect the Accounts Receivable (and vice versa). For example, when a Payment is made to the Accounts Receivable, a Credit Wallet Transaction credits the Wallet, and an Invoice debits the Accounts Receivable.
Wallet Transactions	Wallet Transactions allocated against Walletsare created to debit or credit Wallets.
Rewards Participants	All rewards Rewards Participants own a wallet which holds wallet transactions created via reward award transaction and reward spend transactionsWallet which contains Wallet Transactions created via Reward Award Transactions and Reward Spend Transactions.
Prepaid Subscription	Prepaid Subscriptions billing and paying is handled via wallets
Vouchers	Voucher payments will create Credit wallet transactions. If vouchers have specified products then wallet allotments are also created
Rewards	Rewards Run will create spend and award reward transactions that will debit and credit the wallet accordingly

Billing affect subscribers' Wallets, rather than their Accounts Receivable. When Prepaid Billing is executed, the Wallet is debited accordingly and its Balance evaluated to determine whether a Subscription should stay activated.
Vouchers	Vouchers can be used as a payment to Top Up a Wallet by triggering Credit Wallet Transactions. If specific products are defined on the Vouchers, then Wallet Allotments are created, restricting the use of the available amount to these products.
Rewards	Customers participating in Rewards schemes can access their awards and spend funds via their Wallets.

Wallets - Business Examples

The following section provides business examples to help you understand of how the CRM.COM Wallets module is used.

Calculation of

wallet

Wallet estimated consumption for

prepaid subscriptions

Prepaid Subscriptions

Panel

name	blue
title	Calculation of wallet estimated consumption for prepaid subscriptions

Business Requirement

Company ZX provides offers Prepaid Subscriptions to its customers with .

In Prepaid Subscriptions

. This means that the

, customers pay

up front

upfront for the services

that

they

would like

chose to use.

Once the amount they have to pay for their services is insufficient then the services

The credited amount can be allotted to specific products on their Subscription.
When the customer's balance is insufficient to cover all the chosen services they are automatically disconnected.

The credited amount can be allotted on specific products that they have on their subscription. Customers often call in order to find out

Customers can call, to inquire on how much money is left in their

account

Wallet and when their

subscription

Subscription will be disconnected.

Case 1

Customer The customer has paid 300 Euros €300 and he has 2 products on his subscription. two products, Sports HD and Kids HD, on their Subscription. Customer has subscribed to the normal Price Plan with the following rates:

Kids HD: 20 Euros €20 per month

Sports HD: 30 Euros €30 per month

CRM.COM Solution

Customers with Prepaid Subscriptions have both an Accounts Receivable as well as and a Wallet. The wallet holds Wallet contains the amount of money that the customer has paid upfront in order to use it for his prepaid subscription.

Once the background process

for use on their Prepaid Subscription. Once the Prepaid Billing Run is executed the following information will be

populated

entered in the Wallet:

Current Date: 01.06
Wallet
- Estimated Consumption Days:6 months183 days
- Estimated Consumption Date: 01.12
- Estimated Consumption As of Date: 01.06
- Balance: 300€300
Per Product
- Sports HD
  - Estimated Consumption Days: 183 days
  - Estimated Consumption Date: 01.12
  - Estimated Consumption As of Date: 01.06
- Kids HD
  - Estimated Consumption Days: 183 days
  - Estimated Consumption Date: 01.12
  - Estimated Consumption As of Date: 01.06
Next Day: 02.06
Wallet
- Estimated Consumption Days:182 days
- Estimated Consumption Date: 01.12
- Estimated Consumption As of Date: 02.06
- Balance: €298.33
Per Product
- Sports HD
  - Estimated Consumption Days: 182 days
  - Estimated Consumption Date: 01.12
  - Estimated Consumption As of Date: 02.06
- Kids HD
  - Estimated Consumption Days: 182 days
  - Estimated Consumption Date: 01.12
  - Estimated Consumption As of Date: 02.06

Allocation of Wallet Transactions -
Status
colour Green
title Available from CRM.COM R10.0.0

Panel

name	blue
title	Allocation of Wallet Transactions

The following process demonstrates how funds spent from the consumer's Wallet are allocated against Credit Transactions (funds already available in the Wallet) based on the aforementioned allocation logic.

Table 1 lists a number of Debit and Credit Transactions reported into the System.

Note
Green and Pink Cells indicate Credit and Debit Transactions respectively. Some Credit Transactions have an Expiration or Consumption Validity Date. Some have both or none. Two Allotment Condition Groups are available indicating that allocation occurs within each Group.

Table 1 - Wallet Transactions Table

Order of creation	Created Date	Number	Wallet Transaction Type	Amount	Allotment Condition Group	Consumption Validity Date	Expiration Date
1	01/10/2016	WT0001	Credit	€10	Group 1	N/A	N/A
2	01

.06

/10/2016	WT0002	Credit	€10	Group 1	N/A	01/11/2016
3	02/10/2016	WT0003	Credit	€10	Group 1	N/A	15/10/2016
4	02/10/2016	WT0004	Credit	€10	Group 1	05/10/2016	10/10/2016
5	02/10/2016	WT0005	Credit	€10	Group 2	N/A	09/10/2016
6	03/10/2016	WT0006	Debit	€-8	Group 1	N/A	N/A
7	05/10/2016	WT0007	Debit	€-15	Group 1	N/A	N/A
8	05/10/2016	WT0008	Debit	€-10	Group 2	N/A	N/A
9	06/10/2016	WT0009	Credit	€10	Group 1	N/A	20/10/2016
10	07/10/2016	WT0010	Debit	€-15	Group 1	N/A	N/A
11	08/10/2016	WT0011	Credit	€10	Group 1	N/A	N/A
12	09/10/2016	WT0012	Debit	€-12	Group 1	N/A	N/A
13	10/10/2016	WT0013	Debit	€-10	Group 1	N/A	N/A

Table 2 - Allocations Table

Table 2 shows the allocation and the order in which it occurs in the System, taking into consideration the:

Allotment Condition Group
- The Credit Transactions that belong to the same Allotment Condition Group as the Debit Transaction and are not fully allocated.
Expiration Date & Created Date
- Credit Transactions with the earliest Expiration and Created Date are sorted by Expiration and Created Date from earliest to latest (if no Expiration Date exists then the sorting is done based on the Created Date only).
Consumption Validity Date
- Credit Transactions whose Consumption Validity Date is before the current date.

Order of Allocation	Credit Allotment	Debit Allotment	Allocated Amount	Allocation Date	Unallocated Amount
1	WT0003	WT0006	€8	03/10/2016	€2
2	WT0004	WT0007	€10	05/10/2016	€0
3	WT0003	WT0007	€2	05/10/2016	€0
4	WT0002	WT0007	€3	05/10/2016	€7
5	WT0005	WT0008	€10	05/10/2016	€0
6	WT0009	WT0010	€10	07/10/2016	€0
7	WT0002	WT0010	€5	07/10/2016	€2
8	WT0002	WT0012	€2	09/10/2016	€0
9	WT0001	WT0012	€10	09/10/2016	€0
10	WT0011	WT0013	€10	10/10/2016	€0

Panel

name	grey

Related Areas

Filter by label (Content by label)

showLabels	false
spaces	V4Manual
showSpace	false

excerpt

true

labels	wallets-basics-r7,wallets-advanced-r7,wallets-admin-r7

Panel

name	grey

Popular Labels

Popular LabelsspaceKeyV4Manualstyleheatmap

Versions Compared

Old Version 10

New Version 11

Key

Table of Contents

What

are Wallets?

Wallets Glossary

Wallets Key Processes and Concepts

Wallets Network Characteristics

Wallets Viewing & Access Controls

Wallets Related Related Modules

Wallets - Business Examples

Calculation of

Wallet estimated consumption for

Prepaid Subscriptions

Allocation of Wallet Transactions -
Status
colour Green
title Available from CRM.COM R10.0.0

Related Areas

Popular Labels

Page Comparison

Versions Compared

Old Version 10

New Version 11

Key

Table of Contents

What

are Wallets?

Wallets Glossary

Wallets Key Processes and Concepts

Wallets Network Characteristics

Wallets Viewing & Access Controls

Wallets Related Related Modules

Wallets - Business Examples

Calculation of

Wallet estimated consumption for

Prepaid Subscriptions

Allocation of Wallet Transactions - StatuscolourGreentitleAvailable from CRM.COM R10.0.0

Related Areas

Popular Labels

Allocation of Wallet Transactions -
Status
colour Green
title Available from CRM.COM R10.0.0