Integration Across Databases

The integration begins outside of the PeopleSoft Transaction Billing Processor application. Upon saving a transaction in PeopleSoft CRM or PeopleSoft Lease Administration, the system creates a corresponding contract and contract line in PeopleSoft Contracts through the PeopleSoft Transaction Billing Processor. Transactions are sent from PeopleSoft CRM and PeopleSoft Lease Administration to the PeopleSoft Transaction Billing Processor and stored in the PeopleSoft Contracts Interface tables. PeopleSoft Transaction Billing Processor utilizes the PeopleSoft Contracts rate-based functionality and bills charges on an as-incurred basis. The transaction information is then forwarded to PeopleSoft Billing as bill lines for invoice generation. The PeopleSoft Transaction Billing Processor manages the appropriate timing of sending these transactions to PeopleSoft Billing.

The following table provides the correlation between the PeopleSoft product that integrates with the PeopleSoft Transaction Billing Processor and the applicable transaction types for the product:

Product	Recurring	One-Time	On-Demand
PeopleSoft FieldService	X	X	X
PeopleSoft Support	X	X	X
PeopleSoft Order Capture	X	X
PeopleSoft Lease Administration			X

From PeopleSoft CRM and PeopleSoft Lease Administration transactions, the system creates contracts and contract lines in the PeopleSoft Transaction Billing Processor application. The contract lines are associated with revenue plans for revenue recognition. For one-time transactions, the revenue method is as-incurred. However, recurring and on-demand transactions do not utilize revenue plans for revenue recognition. PeopleSoft Billing manages revenue for those transactions.

The following table provides the correlation between transaction type, product that manages revenue, and the PeopleSoft Contracts revenue recognition method:

Transaction Type	Product Managing Revenue	Revenue Recognition Method
Recurring	PeopleSoft Billing	Billing Manages Revenue
One-time	PeopleSoft Contracts	As-Incurred
On-Demand	PeopleSoft Billing	Billing Manages Revenue

This section discusses the following transaction types:

• Recurring transactions

• One-time transactions

• On-demand transactions

Recurring Transactions

PeopleSoft CRM uses the PeopleSoft Transaction Billing Processor for the Billing Manages Revenue revenue recognition structure, billing cycle, schedule details, and accounting rules for their recurring transactions. Through this integration, PeopleSoft CRM can create invoices and recognize revenue to the general ledger. In addition, you can apply agreement-based uplifts or discounts as separate transactions, as well as taxes to the billable amount and process the transactions through user-defined invoice formats.

The system uses the information contained in the PeopleSoft CRM agreement or order as default values to create the contract header, contract line, billing plan, and revenue plan in the PeopleSoft Transaction Billing Processor.

Once created, the PeopleSoft Transaction Billing Processor sends the contract and contract line number back to PeopleSoft CRM to add this information to the PeopleSoft CRM agreement or order. In addition, the contract line stores the PeopleSoft CRM agreement and renewal numbers, if applicable, and uses this information for processing.

When PeopleSoft CRM sends recurring transactions to the PeopleSoft Transaction Billing Processor, the transactions are sent with an amount, start date, end date, and schedule. Based on this information, the PeopleSoft Transaction Billing Processor expands the transactions for each schedule. The schedules allow the user to book contract liability when the transaction is billed and later recognize the appropriate amount of revenue for each period.

For adjustments to transactions after billing has occurred or revenue has been recognized, the PeopleSoft Transaction Billing Processor creates reversal transactions for the original amounts, and creates new transactions for the adjusted amounts. Both the reversal and the new transactions will appear on the invoice. Therefore, the net amount on the invoice is the difference between what has already been billed and the adjustment that has been made.

For adjustments to transactions before billing has occurred or revenue has been recognized, the PeopleSoft Transaction Billing Processor replaces the original transactions with the new transactions for the adjusted amounts.

Note:

For recurring transactions, you must define a schedule on the Schedules page and select your revenue proration options on the Contracts Definition - Processing Options page for the PeopleSoft Transaction Billing Processor to process the transactions.

Note:

In the case of a PeopleSoft CRM renewal, the PeopleSoft Transaction Billing Processor adds a new contract line to the existing contract instead of creating a new contract and contract line.

Note:

Recurring transactions are applicable to PeopleSoft Field Service, Support, and Order Capture.

One-Time Transactions

PeopleSoft CRM uses the PeopleSoft Transaction Billing Processor for the As-Incurred revenue recognition structure, billing and accounting rules for their one-time transactions. Through this integration, PeopleSoft CRM can create invoices and recognize revenue to the general ledger. In addition, you can apply agreement-based uplifts or discounts as separate transactions, as well as taxes to the billable amount and process the transactions through user-defined invoice formats.

The functionality for one-time transactions is similar to that for recurring transactions. However, for one-time transactions, revenue is managed by PeopleSoft Contracts through the PeopleSoft Transaction Billing Processor instead of by PeopleSoft Billing. Managing revenue through PeopleSoft Contracts provides you with the option to recognize revenue before processing billing. For one-time transactions, you process billing and revenue through the Process As Incurred Billing and Process Project Accounting (as incurred revenue) run control pages respectively.

Note:

One-time transactions are applicable to PeopleSoft Field Service, Support, and Order Capture.

On-Demand Transactions

PeopleSoft FieldService, Support, and Lease Administration send on-demand-fee transactions to the PeopleSoft Transaction Billing Processor in order to utilize the PeopleSoft Contracts functionality to bill and book revenue. PeopleSoft Transaction Billing Processor initiates billing processing, sends the transactions to PeopleSoft Billing, and PeopleSoft Billing completes both revenue and billing processing for on-demand transactions. On-demand transactions are one-time transactions and are never associated with an agreement.

On-demand transactions use functionality similar to recurring and one-time transactions. The same messages and interface tables are used and much of the same setup is required. However, revenue recognition for all on-demand transactions is managed by PeopleSoft Billing through the Contracts Billing Interface (CA_BI_INTFC) process. In addition, contract liability is not applicable for on-demand transactions.

For on-demand transactions, the PeopleSoft Transaction Billing Processor launches the revenue and billing processes immediately after the on-demand transaction loads into the contract staging table (INTFC_CA) without any manual intervention.

Note:

On-demand billing is specific to PeopleSoft FieldService, Support, and Lease Administration.

Note:

On-demand transactions differ from other one-time transactions, because they are never tied to an agreement and the revenue is managed by PeopleSoft Billing instead of PeopleSoft Contracts. In addition, there is no visibility or access to on-demand contracts from within the PeopleSoft Contracts application.