Processing General Ledger Information

General Ledger (GL) information is processed based on which GL processor you use. For MongoDB, use the gl_processor.jar utility. For PostgreSQL, use the GL REST APIs.

Supported revenue recognition types are:

Immediate
Per day
Consumption-based
Pending Activation
Pending Settlement

The following event types are processed by GL processing, regardless of which database you use, even though no Event GL Info is generated for them. These event types must be enabled in pricing configuration so that events are generated for GL processing to use:

Group Delete, Object Delete, and Subscription Delete — The remainder of any deferred revenue in the deleted wallet is recognized.
Payment Settlement — If deferred settlement is used when payment is authorized, the GL information in the purchase event with a revenue recognition type of pending_settlement is processed after the payment is settled.
PeriodEndTimeChange — The daily revenue recognition rate, if applicable, for an active cycle is recalculated if the end time of that cycle is changed.

Note: If you must rerun processing (either gl_processor.jar or an API) for a specific GL date, you must rerun it for all subsequent GL dates.

You must run processing once for each GL date; this applies to both the gl_processor.jar utility and the GL REST APIs. The processing uses information from the summary records of the previous GL date to create the summary records for the current GL date, so it must run daily and in chronological order.

If you must rerun processing for a specific GL date, you must rerun it for all subsequent GL dates.

The GL processor queries events in the Event Repository for each GL date. The GL information found in each event is used by the processor to determine how much revenue could be recognized in each GL date.

Event Type Processing

Event Type Processing describes how GL information for different event types in an Event Detail Record (EDR) is processed. For more information about recognizing revenue, see the discussion about recognizing revenue in MATRIXX Integration.

Note: If an EDR has an MtxBalanceStateUpdate array, the GL processor verifies the balances with updated validity times that are assets subject to deferred revenue recognition. If a balance is subject to deferred revenue recognition, the balance end time is updated in the GL summary records and rates are recalculated to recognize revenue.

Table 1. Event Type Processing
Event Type	Impacted Balance is Currency	Impacted Balance is Liability Asset
Auto Renew	Revenue is recognized according to the revenue recognition type specified in the GL information.	No GL information is generated.
Balance Adjust	Revenue is recognized according to the revenue recognition type specified in the GL information. The supported revenue recognition types are immediate, per day, consumption-based, and pending.	A credit adjustment is treated like a purchase with zero charge. The GL account names and transaction type specified in the GL information in the event override those specified in the GL information from purchase events. A debit adjustment is treated like usage asset consumption. The GL account names and transaction type specified in the GL information in the event override those specified in the GL information from purchase events.
Balance Rollover	Nothing is done.	Nothing is done.
Balance Top-Up	Revenue is recognized according to the revenue recognition type specified in the GL information. The supported revenue recognition types are immediate, per day, consumption-based, and pending.	A credit adjustment is treated like a purchase with zero charge. GL account names and transaction type specified in GL Information do not override those specified in the GL Information from the original purchase event.
Balance Transfer	Revenue is recognized according to the revenue recognition type specified in the GL information. The supported revenue recognition types are immediate, per day, consumption-based, and pending.	An asset and its deferred revenue amount is transferred from the source wallet to the target wallet using the Transfer_From and Transfer_To balance impact types. Revenue is recognized later when the transferred asset is consumed. The GL account names and transaction type specified in the GL information in the event override those specified in the GL information from purchase events.
Balance Threshold	Revenue is recognized according to the revenue recognition type specified in the GL information.	No GL information is generated. The grant is treated like the purchase of a liability asset with a zero charge.
Cancel	Revenue is recognized according to the revenue recognition type specified in the GL information. The supported revenue recognition types are immediate, per day, consumption-based, and pending. In addition, the remaining deferred revenue using the straight-line method is recognized if an offer is canceled immediately.	A cancel forfeiture is treated like usage. Deferred revenue for the forfeited asset amount is recognized. The GL account names and transaction type specified in the GL information in the event override those specified in the GL information from purchase events.
Contract Finance	Revenue is recognized according to the revenue recognition type specified in the GL information. The GL Accounts and TxnType defined for purchase charge and activation charge must be the same. If not, a warning message is logged and the GL Accounts and TxnType defined for activation charge are used to recognize the deferred revenue.	No GL information is generated.
Contract Debit Payment	Revenue is recognized according to the revenue recognition type specified in the GL information. The GL Accounts and TxnType defined for purchase charge and activation charge must be the same. If not, a warning message is logged and the GL Accounts and TxnType defined for activation charge are used to recognize the deferred revenue.	No GL information is generated.
Contract Late Charge	Revenue is recognized according to the revenue recognition type specified in the GL information. The GL Accounts and TxnType defined for purchase charge and activation charge must be the same. If not, a warning message is logged and the GL Accounts and TxnType defined for activation charge are used to recognize the deferred revenue.	No GL information is generated.
Finance Contract Principal Payment	Revenue is recognized according to the revenue recognition type specified in the GL information. The GL Accounts and TxnType defined for purchase charge and activation charge must be the same. If not, a warning message is logged and the GL Accounts and TxnType defined for activation charge are used to recognize the deferred revenue.	No GL information is generated.
First Usage	Revenue is recognized according to the revenue recognition type specified in the GL information. The supported revenue recognition types are immediate, per day, consumption-based, and pending. If GL processing is configured with the `blendUnrecognizedRevenue` property equal to `yes`, multiple grants to the same asset with the same GL treatment are consolidated and the revenue recognition rate is recalculated after each grant.	No GL information is generated.
Forfeiture	Revenue is recognized according to the revenue recognition type specified in the GL information.	Deferred revenue for forfeited asset amount is recognized. The GL account names and transaction type specified in the GL information in the event override those specified in the GL information from purchase events.
Missed Contract Charge	Revenue is recognized according to the revenue recognition type specified in the GL information. The GL Accounts and TxnType defined for purchase charge and activation charge must be the same. If not, a warning message is logged and the GL Accounts and TxnType defined for activation charge are used to recognize the deferred revenue.	No GL information is generated.
Payment	Revenue is recognized according to the revenue recognition type specified in the GL information.	No GL information is generated.
Period Termination	Revenue is recognized according to the revenue recognition type specified in the GL information. The supported revenue recognition types are immediate, per day, consumption-based, and pending. In addition, the remaining deferred revenue under the straight-line method is recognized upon period termination. If deferred revenues have been blended, then accelerated recognition of deferred revenues cannot be performed.	Cancel Forfeiture is treated like usage. Deferred revenue for the forfeited asset amount is recognized. The GL account names and transaction type specified in the GL information in the event override those specified in the GL information from purchase events.
Period Write Off	Revenue is recognized according to the revenue recognition type specified in the GL information.	No GL information is generated.
Purchase	Revenue is recognized according to the revenue recognition type specified in the GL information. The supported revenue recognition types are immediate, per day, consumption-based, and pending. If GL processing is configured with the `blendUnrecognizedRevenue` property equal to `yes`, multiple grants to the same asset with the same GL treatment are consolidated and the revenue recognition rate is recalculated after each grant.	No GL information is generated.
Purchased Item Activation	Revenue is recognized according to the revenue recognition type specified in the GL information. The GL Accounts and TxnType defined for purchase charge and activation charge must be the same. If not, a warning message is logged and the GL Accounts and TxnType defined for activation charge are used to recognize the deferred revenue.	No GL information is generated.
Recharge	Revenue is recognized according to the revenue recognition type specified in the GL information.	No GL information is generated.
Recurring	Revenue is recognized according to the revenue recognition type specified in the GL information. The supported revenue recognition types are immediate, per day, consumption-based, and pending. If GL processing is configured with the `blendUnrecognizedRevenue` property equal to `yes`, multiple grants to the same asset with the same GL treatment are consolidated and the revenue recognition rate is recalculated after each grant.	No GL information is generated.
Refund	Revenue is recognized according to the revenue recognition type specified in the GL information.	No GL information is generated.
Resume	Revenue is recognized according to the revenue recognition type specified in the GL information. The supported revenue recognition types are immediate, per day, consumption-based, and pending. If resuming from Pause mode, the daily revenue recognition rate is recalculated.	No GL information is generated.
Rollover Balance Adjust	Revenue is recognized according to the revenue recognition type specified in the GL information. The supported revenue recognition types are immediate, per day, consumption-based, and pending.	A credit adjustment is treated like a purchase with zero charge while debit adjustment is treated like usage, asset consumption. The GL account names and transaction type specified in the GL information in the event override those specified in the GL information from purchase events.
Suspend	Revenue is recognized according to the revenue recognition type specified in the GL information. The supported revenue recognition types are immediate, per day, consumption-based, and pending. In addition, the remaining deferred revenue under the straight-line method is recognized if the offer is not suspended in Pause mode. If suspending the offer in Pause mode, recognition of deferred revenue under the straight-line method is put on hold.	No GL information is generated.
Transfer to Billed AR	Revenue is recognized according to the revenue recognition type specified in the GL information.	No GL information is generated.
Usage	Revenue is recognized according to the revenue recognition type specified in the GL information. The supported revenue recognition types are immediate, per day, consumption-based, and pending.	Deferred revenue for the consumed asset amount is recognized. The GL account names and transaction type specified in the GL information in the event override those specified in the GL information from purchase events.
Usage Refund	Revenue is recognized according to the revenue recognition type specified in the GL information. The supported revenue recognition types are immediate, per day, consumption-based, and pending.	A credit adjustment is treated like a purchase with zero charge. GL account names and transaction type specified in GL Information do not override those specified in the GL Information from the original purchase event.