Setting Up an Integration to PeopleSoft Transaction Billing Processor

This chapter provides an overview of PeopleSoft Customer Relationship Management (PeopleSoft CRM) integration with PeopleSoft Transaction Billing Processor and discusses how to:

Set up integrations to PeopleSoft Transaction Billing Processor.
Work with on-demand billing.
Set up sales and use tax for third-party tax vendors.

Understanding PeopleSoft CRM Integration with PeopleSoft Transaction Billing Processor

This section discusses:

Billing and contracts functionality.
Agreements and entitlements.
PeopleSoft CRM transactions
Cost category definitions.
Pricing and invoicing.
Reason codes.
Tax calculations.
Workforce synchronization.
Item definition price types.
Service order report.
Accounting rules.
Financial profiles of customers.
Delivered enterprise integration points (EIPs).
Fields populated in PeopleSoft Transaction Billing Processor.
Contracts interface tables.

See Also

PeopleSoft Transaction Billing Processor 8.9 PeopleBook, “Getting Started with PeopleSoft Transaction Billing Processor”

PeopleSoft Transaction Billing Processor 8.9 PeopleBook, “Processing PeopleSoft Transaction Billing Processor Billing”

Billing and Contracts Functionality

PeopleSoft FieldService, PeopleSoft Order Capture, and PeopleSoft CRM call center applications can integrate with PeopleSoft Transaction Billing Processor or any third-party billing applications to:

Send agreement, service order, and case fees to PeopleSoft Transaction Billing Processor.
Send order capture service and product agreement information to PeopleSoft Transaction Billing Processor.
Generate invoices for services, cases and agreement fees.
Manage and book revenue to the appropriate general ledger accounts for recurring and one-time purchases of services and products.

Users can take advantage of the feature-rich billing functionality that is available through PeopleSoft Contracts, such as revenue recognition, billing cycle and schedule details, and accounting rules for applying revenue to the general ledger.

PeopleSoft also provides the ability to apply the appropriate surcharges and taxation to billable amounts and process the information using user-defined invoice formats.

Note. PeopleSoft CRM FieldService and Call Center do not calculate surcharges and taxes. These transactions are computed in PeopleSoft Transaction Billing Processor.

See Also

PeopleSoft Billing 8.8 PeopleBook, “Structuring Bills”

Agreements and Entitlements

Agreement information resides in PeopleSoft CRM. The system sends it to PeopleSoft Transaction Billing Processor for integration with PeopleSoft Billing and General Ledger. If you integrate PeopleSoft CRM with PeopleSoft Transaction Billing Processor, PeopleSoft CRM sends all agreement-based and on-demand transactions through to PeopleSoft Transaction Billing Processor. Entitlement discounts only on the additional discount or uplift amount in PeopleSoft CRM

PeopleSoft CRM sends transactions to PeopleSoft Transaction Billing Processor when they are ready to be billed, depending on the schedule.

In preparation for the integration to PeopleSoft Transaction Billing Processor, PeopleSoft CRM includes statuses and start and end dates on the agreement lines. To control the states that an agreement can move through during the agreement life cycle, PeopleSoft includes change control logic on the agreement status. PeopleSoft CRM uses the same status values that are used in PeopleSoft Transaction Billing Processor. The Pending Activation and Action Required statuses are, however, unique to PeopleSoft CRM

Note. The integration to PeopleSoft Transaction Billing Processor only works with PeopleSoft CRM release 8.9 and PeopleSoft Transaction Billing Processor 8.9.

Agreement Statuses

Here are the PeopleSoft FieldService and PeopleSoft Support agreement statuses:

Pending	Use this status when you create an agreement but you have not completed entering information into the agreement. This status enables you to save an agreement without initiating validation checking.
Pending Activation	An agreement is in the Pending Activation status when its data entry is complete and manager approval is obtained. Changing the status to the Pending Activation status triggers the message that is sent to PeopleSoft Transaction Billing Processor. From this status, the system attempts to create a contract. If no errors occur, the contract is created in the Active status. The agreement remains in Pending Activation status until the associated contract's billing and revenue plans are set to Ready status. When the contract line is ready for billing and revenue, PeopleSoft Transaction Billing Processor sends a message to PeopleSoft CRM and the system moves the agreement from Pending Activation to Active status automatically so that PeopleSoft CRM can send transactions to PeopleSoft Transaction Billing Processor for processing.
Action Required	An agreement is in a status of Action Required when there is a failure on the activation of an agreement in PeopleSoft CRM or a failure on the contract activation in PeopleSoft Transaction Billing Processor. If the error occurs in PeopleSoft Transaction Billing Processor, it sends an error message to PeopleSoft CRM indicating that the agreement will remain in a status of Action Required. It remains in this status until the status changes to Pending Activation after you add the correct information to the agreement. If the billing or revenue plan could not be set to Ready status, PeopleSoft Transaction Billing Processor sends an error message to PeopleSoft CRM indicating what information is missing or incorrect so that the appropriate areas can be corrected and another attempt can be made to put the billing plan or revenue plan in Ready status. In this case the system create a new contract. Once the billing and revenue plan are in Ready status, then the system sets the agreement and contract automatically to Active status. If there was any missing or incorrect information on the agreement, or if a server was down at the time of transmission, the agreement remains in Action Required status.
Active	If no errors exist for the agreement in the Pending Activation status, then the agreement is set to Active status. This occurs automatically after a contract is created and set to the Active status and a billing and revenue plan are created in the Ready status. The contract can now accept transactions from the agreement in PeopleSoft CRM.
Closed	A contract can be set to the Closed status when the agreement and agreement lines associated with the contract are in Closed status and all transactions associated with the agreement have been sent to billing and revenue. When the Bill Plan or Revenue Plan is attempted to be completed or canceled, the system checks that the agreement and agreement lines associated with the contract are closed and that there are no pending service orders or cases. If agreement lines are not closed or pending service orders and cases exist, the system displays an error message. Note. You cannot initiate the closure of a contract from the CRM side. The agreement becomes read-only when the status is set to Closed for the agreement. Note. A contract can no longer accept transactions from PeopleSoft CRM once it has been closed.

PeopleSoft CRM Transactions

These are all the transactions PeopleSoft CRM sends to PeopleSoft Transaction Billing Processor.

Agreement Fee (including renewal and uplift/discount
Order Capture Service Product (including recurring, service product free, and one time except not on demand)
On Demand (including case fee, uplift/discount, service order fee, and service order fee uplift discount)
Agreement Based (including case fee, uplift/discount, service order fee, and service order uplift/discount)
Service Order (including labor fee, labor fee uplift/discount, material fee, material fee uplift/discount, expenses, expenses uplift/discount).

Note. The transactions with uplifts and discounts are sent to the customer on the same invoice as the fee. They appear as separate bill lines; therefore, they are considered separate transactions.

Cost Category Definitions

To retrieve the correct rate for a worker’s time, you must define cost category types using the Cost Category Definition page within the Service Level component. Cost category types are set based on the service level, which defines the service provider’s hours of operation.

The Service level setup page is used to configure a customer's hours of operation. For example a service provider might define their hours of operation to be:

Straight hours.

Monday through Friday 8:00 a.m. to 5 p.m.
Overtime hours.

Monday through Thursday 5:00 p.m. to 8:00 a.m.
Weekends.

Friday 5:00 p.m. to Monday 8:00 a.m.

Once you tie cost categories to the days and hours of operation, then the system can apply the correct rate to the provider group or provider group member. The Cost Category Definition page enables you to define the cost category for the service level hours of operation defined on the service level page. You can override begin and end times, select different cost categories, and enter multiple values for a given day.

In addition, you must define cost categories for workers to account for the cost of labor time to your company. You set up these cost categories by selecting Set Up CRM, Common Definitions, Employee Data, Cost Categories.

When technicians enter their hours in the time log based on that day and time, the system retrieves the correct rate from the member cost categories.

See Also

Defining Service Levels

Establishing Cost Categories for Workers

Pricing and Invoicing

To price cases for a call center agent’s time or to implement pricing based on a flat fee per case, which is based on the price defined on the agreement, PeopleSoft CRM uses pricing logic that automatically reduces the number of hours or partial hours upon saving a case.

You can also price and invoice prepaid services by time or the number of service orders or cases initiated through PeopleSoft FieldService and Support.

Additionally, PeopleSoft has incorporated pricing features within the Service Order component to enable pricing for the billable elements of a service (material, time, and expense fees) and to synchronize the service price of the materials from PeopleSoft SCM with the information that resides on the service order.

You can also apply a service fee to cases and services orders.

The system retrieves the correct price from the Item Definition page in PeopleSoft CRM when the technician records material used at the customer site on the service order. The sum of the material used is calculated and summed up with the total cost of labor, expense charges, and service fees.

The service manager or contracts administrator can increase or decrease the sum of labor, material, and expense charges and recalculate fees to generate new service order totals. Surcharges and taxation are not, however, included in this total. These fees are calculated by billing and included on the invoice to the customer. You don't, however, need an agreement to bill a flat fee for a case.

The integration begins with PeopleSoft Transaction Billing Processor when a user sets the status to Pending Activation for an agreement or service. The system creates a corresponding contract and contract line in PeopleSoft Contracts through PeopleSoft Transaction Billing Processor. Transactions such as service orders, service agreements, and case details are sent from PeopleSoft CRM to PeopleSoft Transaction Billing Processor and stored in the Contracts Interface tables. PeopleSoft Transaction Billing Processor utilizes 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. PeopleSoft Transaction Billing Processor manages the appropriate timing of sending these transactions to PeopleSoft Billing.

Managing Service Orders

Reason Codes

PeopleSoft CRM uses reason codes on the Agreement and Billing pages for service orders and cases to provide an informational reason as to why an adjustment was made to the fees.

The prompt values for the Reason field are from the Reason Code table (RB_REASON_CD). To facilitate the integration with PeopleSoft Transaction Billing Processor, PeopleSoft uses reason codes to further describe billing adjustments. When you set up reason codes, you also need to specify the correct reason type to make the reasons available within the transactions.

For service order billing, you can specify reason codes for service fees, material, time, expenses, and additional adjustments for the total cost of the service order. For agreement billing, you can specify reason codes for service fees, product fees, service and product fees, and additional adjustments to the agreement fee total. For cases, you can specify reason codes for case fees and time-based fees.

All reason code types enable the end user to choose predefined reason codes from the Reason Code table (PS_RB_REASON_CD). If the reason codes in the database are not adequate for the user to make a billing adjustment, end users can click the Other link and enter their own reason in the Detail field.

See Also

Setting Up Reason Codes

Tax Calculations

For PeopleSoft CRM transactions that require VAT, the system sends the ship from location along with the address associated with the customer or the location where the product was shipped to PeopleSoft Transaction Billing Processor.

PeopleSoft CRM derives the customer ship to location from the FSCM (PeopleSoft Financials and Supply Chain Management) database. If VAT is set up for the services or products, the system determines whether VAT is required and performs the tax calculations to include on the invoice.

The system applies taxes during billing invoice finalization for value-added taxes (VAT ) and sales and use taxes (SUT). Rarely are both applied at the same time; however, PeopleSoft provides the flexibility to handle both taxes for those countries where both taxes apply.

To add VAT and SUT functionality, use the VAT and SUT fields within the Agreement, Case and Service Order components and in the customer data model in PeopleSoft CRM. There are also links to the VAT setup pages in PeopleSoft SCM from the PeopleSoft CRM setup pages, where an administrator can move between applications easily to set up VAT.

Note. PeopleSoft Order Capture uses third-party tax calculation routines for Sales and Use tax as well as VAT tax calculations and does not use Simple Tax. Also, any taxes calculated by PeopleSoft Order Capture are recalculated in PeopleSoft Billing.

See Defining Tax Installation Options.

There are two methods that a service provider can use to determine sales and use taxes that can be applied to a case, service order, and agreement fee transactions:

Simple Tax (PeopleSoft tax)

If the customer is tax exempt, users can link to the Tax Parameters page from the Billing page on the service order, case, or agreement and then select the Tax Exempt check box. Customers should inform the service provider if they are exempt from taxes and provide their tax certificate number. If a user selects the Tax Exempt check box they must also enter the tax certificate number.

Since the exemption certificates are synced, the exemption certificate is prompted from the customer exemption table. However, it does not have to exist in the customer exemption table. PeopleSoft CRM does not perform a validation. If a user creates new addresses for a company, consumer, or site, the user can select a tax code from the prompt. When the company, consumer, or site is selected for an agreement fee, service order fee, or case fee transaction, the newly created address and tax code are be sent to PeopleSoft Transaction Billing Processor with the transaction.
Third-Party Tax (Vertex or Taxware).

See Setting Up Sales and Use Tax for Third-Party Tax Vendors.

When PeopleSoft Transaction Billing Processor sends the transaction to PeopleSoft Billing for invoicing, final taxes are calculated at the time of invoice finalization using either of these methods. For PeopleSoft Billing to calculate the taxes for service order transaction (including service fees, labor, materials, and expenses) or case transactions (case fee or labor fee), specific tax fields must be populated and sent along with the transaction.

The fields that need to be populated are dependent on the tax methodology used, either PeopleSoft Tax or Third-Party Tax. PeopleSoft Billing handles the information for PeopleSoft CRM services.

This table shows the combination of information passed to PeopleSoft Billing for VAT and sales tax determinations.

Field	Use	Defaults From
Ship To Customer ID	VAT Tax/ Sales/Use Tax	Customer
Ship To Address	VAT Tax/ Sales/Use Tax	Customer
Ship From Location	VAT Tax/ Sales/Use Tax	Contracts Business Unit
Tax Code	Sales/Use Tax	Customer
Tax Group	Sales/Use Tax	Product
Tax Transaction Type	Sales/Use Tax	Product
Tax Transaction Subtype	Sales/Use Tax	Product
Exemption Certificate (if applicable) and Certificate Number	Sales/Use Tax	Customer
Physical Location	VAT Tax	Product Note. Used only for PeopleSoft Order Capture.

Note. The source where PeopleSoft Billing derives this information is the contract line in PeopleSoft Contracts Also, you can override all fields listed in this table on the billing plan. PeopleSoft CRM also uses order acceptance location, order origin location, and storage location for third-party tax calculations.

If billable transactions for PeopleSoft FieldService and call center applications require VAT, use the links on these PeopleSoft CRM setup pages to access the VAT Treatment page in PeopleSoft SCM:

Service Types
Cost Category
Case Type
Item
Item Group

To add SUT information, access the Tax Parameters page in PeopleSoft CRM from the billing pages within the agreement, service order, or case. You can also access the Tax Parameters Definitions page in PeopleSoft CRM by selecting (Set Up CRM, Common Definitions, Tax Parameter Definitions).

See Also

PeopleSoft Working with Customers and Orders 8.8 PeopleBook, “Maintaining General Customer Information,” Setting Up Tax-Exempt Certificate Information

PeopleSoft Working with Customers and Orders 8.8 PeopleBook, “Maintaining General Customer Information,” Adding General Customer Information, Entering Customer VAT Information

PeopleSoft Financials, Enterprise Service Automation and Supply Chain Management Application Fundamentals 8.8 PeopleBook, “Defining Financials and Supply Chain Management Common Definitions,” Defining PeopleSoft Sales and Use Tax Authorities and Codes

PeopleSoft Global Options and Reports 8.8 PeopleBook, “Working with Value Added Taxes (VAT)”

Workforce Synchronization

To apply revenue to the correct general ledger accounts for the time an agent or field service technician spends on a case or service order, the Workforce EIP (WORKFORCE_SYNC) and the Business Unit HR Sync EIP (BUS_UNIT_HR_SYNC) from PeopleSoft Human Resources Management retrieves the human resources business unit and the general ledger business unit for every worker.

The system stores the general ledger business unit information within the person data structure. The Business Unit HR Sync EIP (BUS_UNIT_HR_SYNC) from PeopleSoft HCM maps the human resource business unit information to the general ledger business unit.

This links the general ledger business unit to the call center agent or field service technician. To accomplish this, PeopleSoft created two fields in the Worker component for the general ledger business unit and the human resources business unit.

See Also

Workforce Management

Item Definition Price Types

The Item Definition page contains two pricing fields: Service Price and Service Exchange Amount. The service price is what the field technician charges the customer for using an item, regardless of whether it is an install or repair. The service exchange amount is what the field technician charges when they replace an old part with a new one. This charge is deducted from the service price.

For example, a company has a service price of 10.00 USD for a new PC chip. The service exchange amount is set to 4.00 USD. When the field technician removes the part (item) from the installed product and replaces it with a new item, then the new chip costs 6.00 USD. In this case, the service exchange amount (4.00 USD) is subtracted from the service price (10 USD).

These fields map to the PeopleSoft Supply Chain Management pricing fields (created specifically for pricing items in PeopleSoft FieldService). When the item price is synchronized with the item master, the system checks the appropriate fields for item definitions. The price and currency code are exposed on the Item Definition page when there is integration with PeopleSoft SCM but they are not available for update. Therefore, the currency and price cannot be modified on the Item Definition page.

However, if the items are not synchronized with PeopleSoft SCM, the administrator may enter price information on the Item Definition page. To stay in sync with the Item Definition page in PeopleSoft Supply Chain Management, the same fields and labels are used in PeopleSoft CRM.

The system displays these fields on the Item Definition page in PeopleSoft CRM:

Currency Code

This field prompts on the Currency Code table (CURRENCY_CODE_TABLE). The administrator can select the currency code for each item, because items can have different currency codes. This field is not required.
Service Price

Enter an amount for the item. This field is not required.
Service Exchange Amount

Enter an amount for the item if it is being exchanged for a newer or working item. This field is not required.

Note. These prices are only used within the service order when calculating the pricing for materials.

See Also

PeopleSoft Managing Items 8.8 PeopleBook, “Defining Items”

Defining Items

Service Order Reports

PeopleSoft FieldService provides two reports that are used to detail the services that have to be performed for a service order and provide expense details to customers.

Here are descriptions of the reports:

Service Order Estimate Report

Once a technician enters time, material, and expense information in a service order, the contract administrator, service manager, or technician may generate a report to provide to the customer for services performed. This report is an estimate of the dollar amount that is planned for the job. It includes all activities with the planned start and stop dates and times, the status of each activity, the charge for performing the service, and any materials that are going to be used. There is a comments section that the technician can use to report actual material and labor if it is different than what was specified on the report. This report does not include taxes and surcharges and it is not a bill. To launch the report from the Service Order page the user clicks the Estimate Report button on the toolbar.
Service Order Detail Report

This report is used by technicians to list the work that they have to perform to fulfill the requirements of the service order. To launch the report from the Service Order or My Service Order page the user clicks the Detail Report button on the toolbar.

Accounting Rules

To define the various attributes of an agreement, service order, or case that should be sent to specific revenue accounts, set up accounting rules in PeopleSoft Transaction Billing Processor during implementation.

The integration to PeopleSoft Transaction Billing Processor enables users to manage and book their revenue by posting revenue accounting entries to their general ledger for agreement fees and services rendered, which are entered on service orders and cases.

For accounting purposes, these fields must be populated in the Contracts Interface table by PeopleSoft CRM:

Transaction Source	Indicates the origin of the transaction. For example, if the value is CRM, it tells the system that the transaction is from PeopleSoft CRM.
From GL Unit	This is the source general ledger business unit (GLBU). Enter the source PeopleSoft General Ledger business unit. With the exception of employee-related transactions (service orders), this value should always be the same as the value in the GL Business Unit field.
GLBU	The PeopleSoft General Ledger business unit defines where the accounting entry is booked. The system populates this field from various sources based on the type of transactions: Agreement Fee Transactions, Service Order Transactions, or Support Case Transactions.
Transaction Type and Transaction Subtype	These fields resides in PeopleSoft Transaction Billing Processor, they are system-defined codes to identify whether the transaction is an agreement, service order, or support case. This field is critical for Transaction Billing Processor to know the type of accounting. Accounting rules setup is different depending on this field.
Accounting Date	This is populated with the transaction date if no date is sent from PeopleSoft CRM.
Department	This field is optional. Wildcard this value in the accounting rules to use the department sent from PeopleSoft CRM in the revenue accounting entry.

See Also

PeopleSoft Transaction Billing Processor 8.9 PeopleBook “Working with the Transaction Billing Processor,” Setting Up PeopleSoft Transaction Billing Processor

PeopleSoft Contracts 8.8 PeopleBook, “Working with PeopleSoft Project Costing,” Setting Up Rules and Exceptions for Organizational Sharing

PeopleSoft Project Costing 8.8 PeopleBook, “Setting Up Accounting for Projects,” Defining Accounting Rules

Financial Profiles of Customers

The 360-degree view integration to PeopleSoft Accounts Receivable provides the ability to display financial profiles of the customer for agreement-based service fees and service order and case transactions.

Customer profile information that is applicable to the services integration to PeopleSoft Transaction Billing Processor includes: statement number, statement date, statement currency, statement total, bill to customer, outstanding balance, and past due balance.

For invoice data, PeopleSoft CRM sends a request application message to PeopleSoft Billing. PeopleSoft Billing sends a response application message to PeopleSoft CRM with the information that appears under the 360-Degree View tree. In addition, once invoices and payments appear on the 360-Degree View tree for a customer, you can click an invoice or payment to access PeopleSoft Billing where you can view more details on the invoice.

See Also

Setting Up the 360-Degree View Tree

Delivered Enterprise Integration Points (EIPs)

This table lists the EIPs that PeopleSoft CRM delivers to facilitate the integration of PeopleSoft CRM applications to PeopleSoft Financial Management Services (PeopleSoft FMS), PeopleSoft Enterprise Service Automation (PeopleSoft ESA), PeopleSoft Supply Chain Management (PeopleSoft SCM), and PeopleSoft Human Capital Management (PeopleSoft HCM).

Note. The database code for PeopleSoft Financials and Supply Chain Management is FSCM.

Channel Name	Description	Message Name	Directions of Integration	Technology
FO_SYNC	Sends tax code definitions from PeopleSoft FSCM to CRM.	TAX_HEADER_TBL_FULLSYNC	FSCM —> CRM	Application Message
HR_SETUP	Maps PeopleSoft HCM business units to general ledger business units.	BUS_UNIT_HR_SYNC BUS_UNIT_HR_FULLSYNC	HCM —> CRM	Application Message
CONTRACT	Synchronizes request and response messages from PeopleSoft CRM and Contracts for pending activities regarding agreements, transactions, invoicing, and contracts.	CONTRACT_REQUEST CONTRACT_RESPONSE CONTRACT_TXN PENDING_ACTIVITY	CRM —> ESA CRM <— ESA CRM —> ESA CRM <—> ESA	Application Message
SERVICE	Synchronizes messages from PeopleSoft CRM to Contracts for accounting definitions, VAT, and VAT drivers.	SERVICE_SYNC SERVICE_FULLSYNC SERVICE_TYPE_SYNC SERVICE_TYPE_FULLSYNC	CRM —> ESA	Application Message
COST_CATEGORY	Synchronizes cost categories (called labor type in PeopleSoft FSCM) from PeopleSoft CRM to Contracts for accounting definitions and VAT drivers.	COST_CATEGORY_SYNC COST_CATEGORY_FULLSYNC	CRM —> ESA	Application Message
CASE	Synchronizes case types and accounting definition information from PeopleSoft CRM to Contracts.	CASE_TYPE_SYNC CASE_TYPE_FULLSYNC SOURCE_SYNC SOURCE_FULLSYNC	CRM —> ESA	Application Message
ENTERPRISE_SETUP	Synchronizes schedule information from PeopleSoft Financials to CRM for agreement information and revenue recognition.	SCHEDULE_SYNC SCHEDULE_FULLSYNC	FMS —> CRM	Application Message
BI_SETUP	Synchronizes bill types and bill sources from PeopleSoft SCM to CRM for contract transactions.	BILL_TYPE_SYNC BILL_TYPE_FULLSYNC BILL_SOURCE_SYNC BILL_SOURCE_FULLSYNC	SCM —> CRM	Application Message
VAT_TRANSFER	Generates request and response messages from PeopleSoft CRM to global VAT to generate VAT defaults.	VAT_TRANSFER_REQ VAT_TRANSFER_RSP	SCM <—> CRM	Application Message
PAY_TERMS	Synchronizes messages from PeopleSoft FSCM to CRM for payment terms.	PAY_TERMS_SYNC PAY_TERMS_FULLSYNC	SCM —> CRM	Application Message
AGREEMENT	Generic message for synchronizing agreement information with third-party vendors.	AGREEMENT_SYNC	FieldService <—> External	Application Message
SERVICE_ORDER	Generic message for synchronizing service order billing information with third-party vendors.	SERVICE_ORDER_BILLING_SYNC	FieldService <—> External	Application Message

Fields Populated in PeopleSoft Transaction Billing Processor

This section discusses:

Contract header
Contract line
Billing plan
Revenue plan
Tax parameters

Note. PeopleSoft CRM sends fields to PeopleSoft Transaction Billing Processor to create the contract, contract line, and revenue and billing plans. Many of these fields can be changed manually on the contract. If you wish to change a field after contract activation has taken place, you must create an amendment using PeopleSoft Transaction Billing Processor amendment functionality.

Contract Header

These fields must be populated in the contract header. These values are sent from the PeopleSoft CRM agreement. This list contains fields that can be overridden on the contract header once they are populated from the CRM agreement.

Bill To Contact
Bill To Customer
Bill To Address
Purchase Order ID
Payment Terms
Sold To Customer

This list contains fields that cannot be overridden on the contract header:

Sold To Customer
CA Business Unit
Currency Code

Here are additional fields that are required on the contract header and the source from which the systems retrieves the value for the field:

PeopleSoft Contracts Field Name	Source
Bill Type Note. This is sent from PeopleSoft CRM.	PeopleSoft Contracts Business Unit
Legal Entity	PeopleSoft Contracts Business Unit
Contract Signed Date	The system populates this field with the current date. PeopleSoft CRM must send this date if they want to override the default contract signed date.
Contract Type	PeopleSoft Contracts Business Unit
Exchange Rate Type	PeopleSoft Contracts Business Unit

Contract Line

These fields that must be populated in the contract line. These values are sent from the PeopleSoft CRM agreement or on demand service order/case. The list contains fields that can be overridden on the contract line once they are populated from the CRM agreement.

Fields that can be overridden on the contract line:

Line Description
Ship From Location (source = PeopleSoft Contracts business unit)
Start Date
End Date

Note. These fields are not sent from PeopleSoft CRM, except Line Description.

The Currency Code field cannot be overridden on the contract line. The source for the currency code is the contract header.

Billing Plan

These fields that must be populated in the billing plan. These values are sent from the PeopleSoft CRM agreement or on demand service order/case. The list contains fields that can be overridden on the billing plan once they are populated from the CRM agreement.

Fields that can be overridden on the contract line:

Bill To Contact
Bill To Customer
Bill To Address
Schedule ID

These fields appear on the Billing Plan General page. The system populates the fields on this page upon contract creation. The table shows the source from which each field is populated, if the value can be changed in the billing plan in PeopleSoft Transaction Billing Processor, and if the field can be overridden by transactions sent from PeopleSoft CRM:

Billing Plan Field	PeopleSoft Contracts Source	Changeable?	Can be overwritten by CRM on transaction?
Billing Notes Note. You can create a note in PeopleSoft Transaction Billing Processor and attach that note to a billing plan. It can be sent to PeopleSoft Billing as part of the generated invoice.	Manual process	Yes	Yes
Contract Number	Contract header	No	No
Billing Plan Number	Billing plan	No	No
Billing Method	Contract line	No	No
Currency Code	Contract header	No	No
Bill Plan Description	Contract header	Yes	No

Other fields on the Billing Plan General page, such as the Billing Inquiry, Billing Specialist, Billing Authority, Cycle ID, Bill By ID, and Invoice Form can be added to the billing plan manually or left blank.

Revenue Plan

A contract line is linked to a revenue plan to recognize revenue. The required revenue plan fields populate automatically during contract creation and cannot be overwritten from the transaction data that is sent from PeopleSoft CRM. The revenue plan fields are managed entirely from the contract.

These fields are required for the Revenue Plan page. The table shows the source from which each field is populated. These fields cannot be overridden by transactions sent from PeopleSoft CRM:

Revenue Plan Field	PeopleSoft Contracts Source
Contract Number	Contract header
Sold To Customer	Contract header
Business Unit	Contract header
Revenue Method	Contract Line
Currency Code	Contract header
Revenue Plan Description	Contract header
Hold (flag)	Revenue Plan
Events	Contract header

Note. If there is a credit hold on a customer in PeopleSoft CRM, you must put the revenue plan for the contract on hold by selecting the Hold check box on the Revenue Plan page to prevent transactions from processing. If you select the Hold check box, then you must release the hold manually when you are ready to recognize revenue for the customer.

While every created contract line has a revenue plan, recurring fees do not utilize the revenue plan for revenue recognition. Revenue plans build a deferred revenue schedule associated with the billing transactions. In addition, on demand transactions do not need a revenue plan to recognize revenue. PeopleSoft Billing manages revenue for on demand transactions. PeopleSoft Billing manages the revenue method for all on demand and recurring transactions.

Tax Parameters

PeopleSoft CRM sends tax parameter information for agreements to PeopleSoft Transaction Billing Processor. PeopleSoft Transaction Billing Processor stores the CRM tax information in the Contract Interface tables (INTERFACE_CA) and passes this information onto PeopleSoft Billing for processing. The Billing Plan General -Tax Parameters tab is not available for CRM contracts.

Here are the tax fields passed from PeopleSoft CRM to the contract interface tables:

Ship From Location
Tax Code
Tax Group
Transaction Type
Transaction Sub Type
Exemption Certificate
Physical Nature
Order acceptance location.
Order origin location.
Storage location.

PeopleSoft CRM sends fields to PeopleSoft Transaction Billing Processor to create the contract, contract line, and revenue and billing plans. Many of these fields can be changed manually on the contract. In addition, PeopleSoft Transaction Billing Processor receives sales and use and VAT tax parameters if they are sent by PeopleSoft CRM.

Transaction Billing Processor Interface tables (INTFC_CA, INTFC_CA2, INTFC_CA_HDR, and INTFC_CA_NOTE) are duplicates of the Billing interface tables. However, the first two keys on the billing table, INTFC_ID and INFC_LINE_NUM, have been changed to the single key CA_TXN_ID on the Transaction Billing Processor tables.

See Also

PeopleSoft Contracts 8.8 PeopleBook, Processing PeopleSoft Contracts Billing

PeopleSoft Billing 8.8 PeopleBook, Entering Bills Online

Contracts Interface Tables

The Contracts Interface tables store the transactions from PeopleSoft CRM. The Transaction Billing Processor interface tables (INTFC_CA, INTFC_CA2, INTFC_CA_HDR, and INTFC_CA_NOTE) are duplicates of the Billing interface tables. However, the first two keys on the billing table, INTFC_ID and INFC_LINE_NUM, have been changed to the single key CA_TXN_ID on the Transaction Billing Processor tables.

PeopleSoft FieldService and Support

PeopleSoft CRM sends service order transaction information, case transaction information, and service agreement fees to be billed or accounted for to the Transaction Billing Processor interface tables.

PeopleSoft Order Capture

PeopleSoft Order Capture sends these fields to PeopleSoft Transaction Billing Processor for every transaction:

Sold to Customer
Sold To Contact
Sold To Address
Contract business unit

PeopleSoft Transaction Billing Processor sends these fields to PeopleSoft Order Capture as a response:

Contract Number
Contract Line Number
PeopleSoft Contracts Business Unit
Error Status
Error Message

Transactional Billing Plans

The system creates a billing plan with an As-incurred billing method for the service transactions sent from PeopleSoft CRM to PeopleSoft Contracts. Pricing occurs in PeopleSoft CRM for all services on the agreement such as service order transactions, service agreement fees, and cases. Contract lines within an agreement related contract are linked to the billing plan. Although these billing plans contain rules defined by default upon contract creation, you can manually override the system defaults.

This table contains fields on the billing plan, their source from within PeopleSoft Contracts, whether or not the field can be overridden on the billing plan manually, and whether or not the field can be overridden by the transaction message sent from PeopleSoft CRM.

Field	CA Source	Override on billing plan?	Override from CRM transaction?
Billing Notes	Manual Process	Yes	Yes
Contract #	Contract Header	No	No
Billing Plan #	Billing Plan	No	No
Billing Method	Contract Line	No	No
Currency Code	Contract Header	No	No
Bill Plan Description	Contract Header	Yes	No

You can link only CRM lines to a billing plan created from CRM transactions. You cannot mix lines with different transaction sources on the billing plan. For example, you cannot link a CRM contract line with a Project Costing contract line.

PeopleSoft FieldService, PeopleSoft Support and PeopleSoft Order Capture send credit card information to PeopleSoft Transaction Billing Processor. PeopleSoft Transaction Billing Processor does not validate the credit card numbers.

Common Elements Used in This Chapter

Agreement	A PeopleSoft CRM agreement is a list of obligations to which a service provider has agreed or committed to the customer. The agreement lines listed on the agreement include services and products covered by the agreement, information regarding who or what customer locations can request service, and the level of service that is provided, which includes restore time, response time, prime period of maintenance, and service coverage (time, material, and expense).
Agreement Pricing	Agreement pricing records define the fee paid for a specific service or support offering. The agreement price is paid when the agreement is issued to or signed by the customer. PeopleSoft CRM also allows you to initiate recurring charges where a customer might pay a fee on a monthly or quarterly basis.
Agreement Service Pricing	Agreement service pricing records define what the customer pays when the work associated with the service or support offering on the agreement is performed. This includes the price paid per transaction covered by the agreement line.
Billing Plan	When the system creates a contract it also generates a billing plan that is linked to a contract line. The billing plan determines how a transaction should be billed. It contains customer billing information, billing method (for example, as-incurred), and status of the billing plan.
Contract Amendment	A contract amendment is any change made to an active contract where you are altering the fundamental obligations and entitlements of the contract.
Deferred Revenue	Deferred revenue helps to create and send invoices for products or services that are to be delivered in the future or over a range of time. You may use deferred revenue to generate accounting entries that defer revenue recognition based on a revenue recognition date and proration method that you select.
General Ledger	General ledger is where all of the journal entries are posted. Journal Generator populates the general ledger with accounting entries (for example, accounts receivable and revenue entries).
Location	Select the location of the store where the order is to be purchased. This field is used for tax vendor exceptions and reporting
Order Acceptance Location	Select the location where the order is to be accepted. The system uses this field to determine tax jurisdiction.
Order Origin Location	Select the location where the order originated. The system uses this field to determine tax jurisdiction.
Rate based Contract Line	A rate-based contract line is a transaction-based offering (or an ad hoc offering) that PeopleSoft Transaction Billing Processor picks up and sends to PeopleSoft Billing.
Revenue Plan	When the system creates a contract, a revenue plan is also created and associated with a contract line. You can create revenue plans either automatically or manually. The contract line, however, must be linked to the revenue recognition plan to recognize revenue.
Revenue Recognition	Revenue recognition is when the system sends revenue information to the general ledger, and it is counted in the revenue projection for the accounting period.
Store Location	Enter the address of the store location. Note. If you are using a third-party tax vendor, the entry in this field should match the store location code in Vertex or Taxware.

Setting Up Integrations to PeopleSoft Transaction Billing Processor

To define agreement options, time types and tax parameters, use the Agreement Options (RF_AGR_OPTIONS), Time Type (RF_TIME_TYPE) and Tax Parameters (RF_TAX_PARAM) components.

This section discusses how to:

Establish billing and pricing options.
Map agreement setIDs with contracts and general ledger business units.
Set up time types for PeopleSoft FieldService.
Set up billing options for PeopleSoft FieldService.
Set up billing options for PeopleSoft Call Center.
Set up billing options for PeopleSoft Order Capture.

Note. It is necessary to activate the messages, message subscriptions, message channels, node transactions and relationships (from the EIP chart earlier) in to use the integration to PeopleSoft Transaction Billing Processor.

Pages Used to Set Up Integrations to PeopleSoft Transaction Billing Processor

Page Name	Object Name	Navigation	Usage
Billing and Pricing Options	RB_INTEGRATION	Set Up CRM, Install, Installation Options, Billing and Pricing Options	Turn on integration to PeopleSoft Transaction Billing Processor for PeopleSoft FieldService, Call Center, and Order Capture. Enable pricing for service order and cases.
Agreement Options	RF_AGR_OPTIONS	Set Up CRM, Common Definitions, Agreement Options, Agreement Options	Map the agreement setIDs with the business units for both PeopleSoft Transaction Billing Processor and PeopleSoft General Ledger.
Time Types	RF_TIME_TYPE	Set Up CRM, Product Related, FieldService, Time Type, Time Types	Establish the defaults for the types of time that are billable for the business units being set up under the selected setID.
Billing Options	RF_BU_BILL_OPTIONS	Set Up CRM, Business Unit Related, FieldService Definition, Billing Options.	Set up billing options for PeopleSoft FieldService.
Business Unit Billing Details	BUS_UNIT_RC_BI_SEC	Set Up CRM, Business Unit Related, Call Center Definition, Options. Select Bill for Cases and then click the Details link	Set up billing options for PeopleSoft Call Center applications.
Order Capture Definition - Internal	BUS_UNIT_RO1	Set Up CRM, Business Unit Related, Order Capture Definition, Internal.	Set up billing options for PeopleSoft Order Capture.
Tax Parameter Definitions	RF_TAX_PARAM	Set Up CRM, Common Definitions, Tax Parameter Definition, Tax Parameter Definition	Set up sales and use taxes for service, material, labor, expenses, and cases for third-party tax vendors.

Establishing Billing and Pricing Options

Access the Billing and Pricing Options page

Note. There are no installation options for third-party integration given that there is no way to determine what validation checking is required on the system to receive agreement, service order, or case data.

Send Billing Transactions to Contracts

Select this check box to send agreement fee billing date, service order billing data, case fees, and order information to PeopleSoft Transaction Billing Processor for billing and accounting.

The system sends agreement fees, case fees or service order fees to PeopleSoft Transaction Billing Processor when the case or service order is closed. For PeopleSoft Order Capture the system sends the information to PeopleSoft Transaction Billing Processor when you submit the order. These options are not available when delivered out-of-the-box.

Calculate Price on Service Orders

Select this check box if you want the system to price on-demand and agreement-based service orders.

Calculate Price on Case

Select this check box if you want the system to price agreement- and on-demand cases.

Mapping Agreement SetIDs with Contracts and General Ledger Business Units

Access the Agreement Options page.

Agreement Options Tab

Use the fields within this tab to map the agreement setIDs with the business units for both PeopleSoft Transaction Billing Processor and PeopleSoft General Ledger.

This mapping links the agreement to the corresponding contract. The system uses the existing business unit EIP to obtain all contracts and general ledger business units from the PeopleSoft FSCM database.

SetID	Enter the setID that you want to use with the agreements that you create for integration to PeopleSoft Transaction Billing Processor.
Contracts Business Unit	Enter the business unit that you want to use to create contracts in PeopleSoft Transaction Billing Processor. The PeopleSoft Transaction Billing Processor business unit must be tied to the agreement to facilitate the proper creation of a contract and to enable the appropriate default values to be selected when the contract is created.
GL Business Unit (general ledger business unit)	Enter the general ledger business unit that you want associated with the setID. The GL Business Unit field is required for contracts integration with PeopleSoft Global to send revenue to the appropriate general ledger account.
Location Code	The location code prompts from the Location table (LOCATION_TBL ) in PeopleSoft CRM and returns a location code. The system sends the country and state information to PeopleSoft Transaction Billing Processor with the agreement transaction. This information is needed to calculate VAT tax rates. The location table in PeopleSoft CRM is synced with the location table in the PeopleSoft FSCM database (two-way).
Schedule	Select the schedule by which you want to bill the customer.

Note. When the system creates the agreement it gets the setID, the contracts business unit, and the general ledger business unit from the Agreement Options page.

Billing Options Tab

Select the Billing Options tab.

Use the fields within this tab to map the agreement setID to the bill type and the bill source.

For example, suppose that the CRM01 setID identifies the bill type and bill source as a SERVICE, the system sends the information to PeopleSoft Transaction Billing Processor to override the Bill Source and Bill Type fields on the PeopleSoft Transaction Billing Processor billing plan.

Bill Type

Select the bill type that you want associated with the setID.

The bill type prompts on all bill type identifier codes that are synced from PeopleSoft Billing to PeopleSoft CRM. The bill type code is a user-defined value in PeopleSoft Billing.

Bill Source

Select the bill source that you want associated with the setID.

The bill source prompts on all bill source identifier codes that are synced from PeopleSoft Billing to PeopleSoft CRM. The bill source code is a user-defined value in PeopleSoft Billing.

Note. You can use both the Bill Type and Bill Source fields to define bill by identifiers in PeopleSoft Billing. If CRM overrides the Bill Type and Bill Source fields on the PeopleSoft Transaction Billing Processor billing plan with values defined in the CRM Billing Options page, then depending on the Bill By Identifier hierarchy in Billing, these values may be used to control the way that the invoices can be grouped.

On the Billing Options page, the Bill Type and Bill Source fields are optional. If they are not set in PeopleSoft CRM, the billing plan in PeopleSoft Transaction Billing Processor sets these fields based on the contracts business unit. PeopleSoft Billing still determines the bill by identifiers that are used based on its bill by identifier hierarchy.

Tax Options Tab

Select the Options tab.

Use the fields on this tab to indicate where the order originated, where it will be accepted, and where the store is located. This information is used for tax purposes.

Setting Up Time Types for PeopleSoft FieldService

Access the Time Types page.

Use this page to establish time types and indicate to the system which time types are billable. The system uses this information on the Billing Options page when you are setting up business units. If you enter one or more time types for a given setID, all PeopleSoft FieldService business units that use that setID as its default inherit the time types for the setID, including the billable flag.

For example, if you select the Billable check box for the Break time type, the system selects it as billable in the Time Type grid on the Billing Options page for the PeopleSoft FieldService business unit.

Time Type	Enter a number by which you want to order the time type that you are entering. The numbers that you enter determine the order in which the time types appear on the Billing Options page.
Short Description and Description	Enter the short and long description of the time type.
Billable	Select if you want to set the default to billable for the time type.

Note. If the installation option is not set to Calculate Price on Service Orders, then the system hides the Business Unit - Billing Option page, which contains the billable fields that you are entering on this page.

Setting Up Billing Options for PeopleSoft FieldService

Access the Billing Options page.

Billing Information

Use the fields within this group box to enter the information that is needed for PeopleSoft FieldService to integrate with PeopleSoft Transaction Billing Processor. To apply revenue to the correct general ledger account for service order fees, link the business units for PeopleSoft FieldService, Contracts, and General Ledger. This information is included in the contract transaction message that the system sends to PeopleSoft Transaction Billing Processor when the service order closes.

Note. You can link only one general ledger business unit to a service order. You cannot override the GL Business Unit field from the service order. The system does not display this field on the Service Order page in PeopleSoft FieldService.

Contracts Business Unit	Enter the contracts business unit that you want to use for billing.
GL Business Unit	Enter the general ledger business unit that you want to use for billing. The prompt values for this field include all business units for all product lines. Populating this field enables mapping between the general ledger business unit and the field service business unit. The Service Order page does not display the general ledger business unit or contracts business unit. When a service order closes, the system sends the general ledger business unit, contracts business unit, and contract ID to PeopleSoft Transaction Billing Processor with other transaction information.
Bill Type	Select the bill type that you want associated with the business unit. The prompt values for theBill Type field include all bill type identifier codes that are sent from PeopleSoft Billing to PeopleSoft CRM.
Bill Source	Enter the bill source that you want to associate with the business unit. The prompt values for the Bill Source field include all bill source identifier codes that are sent from PeopleSoft Billing to PeopleSoft CRM. Note. The system sends the Bill Type and Bill Source fields with every service order transaction if one or both have been set on the FieldService Business Unit - Billing Options page.
Material Billable and Expense Billable	Select the check boxes that you want to use for billing purposes on service orders for the business unit that you are defining. If you select the Send Billing Transaction to Contracts and Calculate Price on Service Orders check boxes on the Installation Options page, then the system automatically selects the Material Billable and Expense Billable check boxes The system administrator, however, can override these values by clearing the check boxes.
Time Type and Billable	Select the Billable check box to make the time type a billable item on the service order for the business unit. The defaulting of time types is based on the setup of the time types. If you enter one or more time types for a given setID, all PeopleSoft FieldService business units that use that setID as the default setID inherit the time types of the setID, including the billable option. You can, however, override time types for a business unit. For example, suppose that the time type for Break is not set to billable on Time Types page, then the system does not display it in the Time Type section on this page.

Tax Information

Use the fields on this tab to indicate where the order originated, where it will be accepted, and where the store is located. This information is used for tax purposes. The Order Origin Location, Order Acceptance Location, and Location fields prompt from the Location table (LOCATION_TBL), which is sent to PeopleSoft CRM through an EIP from PeopleSoft HCM and PeopleSoft FSCM.

Note. PeopleSoft Billing uses the fields in the Tax Information group box for integration to Vertex and Taxware, which are third-party tax vendors. Please refer to the setup for sales and use tax for third-party tax vendors for details on the function and behavior of each third-party tax field. These third-party tax fields are always blank when you first create a PeopleSoft FieldService business unit.

See Also

Defining FieldService Business Units

Setting Up Sales and Use Tax for Third-Party Tax Vendors

Setting Up Billing Options for PeopleSoft Call Center

Access the Business Unit Billing Details page.

Billing Information

Use the fields within this group box to enter the information that is needed for the integration to PeopleSoft Transaction Billing Processor.

On Demand Price By	Select either Hour or Case. This field provides the flexibility to price case transactions by hour or by case. For example, if you have a New York business unit and a California business unit, the New York unit could price a case by flat fee while the California unit could price the case by the total number of hours that an agent spends working on a case. This field is blank when you enter the page for the first time.
Currency Code	Enter the currency that you want to use for billing purposes for the business unit that you are defining.
Rate Type	Select the exchange rate type that is used to calculate monetary transaction amounts in alternate currencies.
Contracts Business Unit	Enter the contracts business unit that you want to use for billing.
GL Business Unit	Enter the general ledger business unit that you want to use for billing. The prompt values for this field include all business units for all product lines. Populating this field enables mapping between the general ledger business unit and the call center business unit. The Case page does not display the general ledger business unit. It does display the contracts business unit, which appears by default from the agreement. When a case closes, the system sends the general ledger business unit, contracts business unit, and contract ID to PeopleSoft Transaction Billing Processor with other transaction information.
Bill Type	Select the bill type that you want associated with the business unit. The prompt values for this field include all bill type identifier codes that are sent from PeopleSoft Billing to PeopleSoft CRM. The bill type code is a user-defined value in PeopleSoft Billing. Sample data includes SVC (Service), CASE, and CRM _ORDER..
Bill Source	Enter the bill source that you want associated with the business unit. The Bill Source field prompts on all bill source identifier codes that are sent from PeopleSoft Billing to PeopleSoft CRM. The bill source code is a user-defined value in PeopleSoft Billing. Sample data includes SERVICE, OES (Order Entry System), and GSO (General Service Orders). Note. The system sends the Bill Type and Bill Source fields with every transaction if one or both have been set up on the Business Unit Billing Details page.

See Defining Call Center Business Units.

Tax Information

Note. The fields in the Tax Information group box are used by PeopleSoft Billing for integration to Vertex and Taxware, which are third-party tax vendors. Please refer to the setup for sales and use tax for third-party tax vendors for details on the function and behavior of each third-party tax field. These third-party tax fields are always blank when you first create a business unit for a PeopleSoft call center application.

See Setting Up Sales and Use Tax for Third-Party Tax Vendors.

Setting Up Billing Options for PeopleSoft Order Capture

Access the Order Capture Definition - Internal page.

To set up billing options for PeopleSoft Order Capture, you must establish values for the Contracts, General Ledger, Bill Type, Bill Source, and Default Service Duration fields.

Contracts	Enter the contracts business unit that you want to use for billing.
General Ledger	Enter the general ledger business unit that you want to use for billing. The prompt values for this field include all business units for all product lines. Populating this field enables mapping between the general ledger business unit and the order capture business unit.
Bill Type	Select the bill type that you want associated with the business unit. The prompt values for this field include all bill type identifier codes that are sent from PeopleSoft Billing to PeopleSoft CRM. The bill type code is a user-defined value in PeopleSoft Billing. Sample data includes SVC (Service), CASE, and CRM _ORDER..
Bill Source	Enter the bill source that you want associated with the business unit. The Bill Source field prompts on all bill source identifier codes that are sent from PeopleSoft Billing to PeopleSoft CRM. The bill source code is a user-defined value in PeopleSoft Billing. Sample data includes SERVICE, OES (Order Entry System), and GSO (General Service Orders). Note. The system sends the Bill Type and Bill Source fields with every transaction if one or both have been set up on the Business Unit Billing Details page.
Default Service Duration	Enter the default duration for service products. This is used to calculate the service end date for service products ordered through order capture by adding the duration to the service start date. The duration specified in the order capture business unit is used when the duration on the product definition is blank.

For more information on setting up billing options, refer to the PeopleSoft Order Capture 8.9 PeopleBook.

Defining Tax Parameters

Access the Tax Parameter Definitions page.

Working with On Demand Billing

This section provides an overview of on demand billing and discusses how to set up PeopleSoft Transaction Billing Processor to process on demand billing transactions.

Understanding On Demand Billing

This section discusses:

Overview
Setup
Contract creation and processing
Integration points
Error handling

Note. On Demand billing is specific to PeopleSoft CRM FieldService and CRM Support.

Overview

On demand billing provides back office processing for one-time fee transactions for service orders and cases. These transactions are not linked to agreements. The fees are usually one-time fees that are billed to the customer. Through an integration with PeopleSoft Transaction Billing Processor, you can bill and book revenue for on demand service fees for cases and service orders.

Note. PeopleSoft CRM enables the system to bill on demand transactions through PeopleSoft Transaction Billing Processor. The same messages and interface tables are used. Revenue recognition for on demand transactions is managed by PeopleSoft Billing through the Contracts Billing Interface (CA_BI_INTFC) process.

Here is an overview of the on demand functionality:

Through PeopleSoft Contracts, On Demand cases and service orders are processed through PeopleSoft Transaction Billing Processor and General Ledger for billing and revenue.
PeopleSoft CRM identifies a transaction as on demand when passing the transaction from PeopleSoft CRM to PeopleSoft Transaction Billing Processor.
Closure of a service order or case in PeopleSoft CRM triggers the sending of transaction information from PeopleSoft CRM to PeopleSoft Transaction Billing Processor.

PeopleSoft CRM determines whether a new contract is created or if an existing contract is used based on the sold to customer. PeopleSoft CRM requests one on demand contract per sold to customer and PeopleSoft Contracts business unit mapping.
PeopleSoft Transaction Billing Processor launches the revenue and billing processes immediately after the on demand transaction loads into the contract staging table (INTERFACE_CA) without any manual intervention.
If a failure occurs during the creation of the contract or during processing of the on demand transaction, the system does not create the contract or process the transaction. The system sends an error message to PeopleSoft CRM with the failure reason. In this case you must resubmit the transaction.

Note. In PeopleSoft Transaction Billing Processor there is no visibility to on demand contract lines in any components, processes, or reports. Deferred revenue is not applicable for on demand transactions

Setup

To implement on demand transaction processing, you must set up:

PeopleSoft Contracts business units.
Contract statuses
Accounting definitions.
Accounting rules.
Billing plan detail template (optional).

Prior to creating on demand contracts, set up the contract business unit and contract status. Additionally, you must set up the accounting rules for on demand transactions to ensure that the system allows only one REV row per transaction. You must also select the Transaction Billing check box on the Installed Products page.

You have the option to create a billing plan detail template to populate or override the fields on the billing plan. Select the billing plan detail template on the Contract Definition - BU Options page. If you select a template on this page, the billing plan detail template populates or overrides the corresponding fields on the billing plan when the billing plan is created.

Contract Creation and Processing

PeopleSoft FieldService and Support send one-time fee transactions to PeopleSoft Transaction Billing Processor to utilize the contracts functionality to bill and book revenue. PeopleSoft Transaction Billing Processor initiates billing processing and completes both revenue and billing processing for on demand transactions.

Here are the steps that the system completes to create and process on demand transactions through PeopleSoft Transaction Billing Processor.

If the service order or case is not covered by an agreement, the system sends the transaction to PeopleSoft Transaction Billing Processor as an on demand transaction when a PeopleSoft CRM Support case or FieldService service order is closed.
The first time PeopleSoft CRM creates an on demand service order or case, the system searches for the sold to customer or PeopleSoft FieldService or Support business unit to map to the PeopleSoft Contracts business unit and contract number.

If the search does not find a mapping, PeopleSoft CRM sends a contract request message (CONTRACT_REQUEST) to PeopleSoft Transaction Billing Processor to create a new on demand contract. PeopleSoft CRM sends a contract request message only when the system needs to create a new contract. The request message from PeopleSoft CRM specifies the transaction type (service order or case).
PeopleSoft Transaction Billing Processor creates an on demand contract and sends a contract response message (CONTRACT_RESPONSE) to PeopleSoft CRM providing the contract business unit, contract number, contract line number, error status, and error message.

The system creates the contract and contract lines, including an As-incurred billing plan, using the CA_HDR_CI component interface. On success, PeopleSoft Transaction Billing Processor responds to PeopleSoft CRM with the new contract number.
On receipt of the contract response message, PeopleSoft CRM sends the transaction to PeopleSoft Transaction Billing Processor through a transaction message (CONTRACT_TXN) with all necessary data for the invoicing and booking revenue.

In the transaction message, the contract number identifies a particular contract. Each transaction is unique and is marked by its own transaction ID (CA_TXN_ID). For all future transactions for the same sold to customer, only the transaction (through the transaction message) is sent to PeopleSoft Transaction Billing Processor.
PeopleSoft Transaction Billing Processor retrieves the transaction data and loads the on demand transaction from PeopleSoft CRM into the contract staging tables (INTFC_CA).

Loading the contract staging tables triggers both the revenue process to apply the revenue to the appropriate account and billing process to generate the invoice to run. The transaction populates the contract interface tables, initiates the Billing Interface process (CA_BI_INTFC), and prepares the transaction for billing processing. Revenue recognition is handled by PeopleSoft Billing.

If there are errors during processing, the system sends a reply message to PeopleSoft CRM containing the contract business unit, contract number, contract line number, CRM identifier, and status indicating that the process failed.

If the transaction posts successfully to both PeopleSoft General Ledger and PeopleSoft Billing, the system sends a reply message to PeopleSoft CRM containing the contract business unit, contract number, contract line number, CRM identifier, and status indicating that the process succeeded. The response message is CONTRACT_RESPONSE for both request and transaction messages and it contains the appropriate success and failure codes and descriptions.
The CRM transaction changes the billing status from submitted to completed. This action marks the end of the PeopleSoft CRM processing.
PeopleSoft Billing runs the Billing Interface and Finalization processes.

Integration Points

These are the four major steps in the integration process between PeopleSoft CRM and PeopleSoft Contracts for on demand contracts:

Creating a billing plan.
Creating a contract.
Populating the Contracts interface tables.
Processing billing.

Creating a billing plan, creating a contract, and populating the interface table are the same steps that occur with agreement-based processing. These steps use the contract request (CONTRACT_REQUEST and CONTRACT_RESPONSE) and transaction (CONTRACT_TXN) messages. The last step, processing billing, differs from agreement-based transactions since billing for on demand contracts takes place immediately through PeopleSoft Billing.

With agreement-based billing, you have control over the billing plan in PeopleSoft Contracts and you can make changes to the contract before it goes to PeopleSoft Billing for processing. The on demand process uses the same integration points as agreement based transactions.

Error Handling

Errors can occur during the contract and billing plan creation process, when the system loads the staging table, or when the system runs the revenue and billing processes. PeopleSoft Transaction Billing Processor initiates billing processing and sends the transactions to PeopleSoft Billing. PeopleSoft Billing completes both the revenue and billing processing for on demand transactions.

Here is how the system handles errors:

If a failure occurs during contract creation, the system creates the contract in a cancelled status and a response is sent back to PeopleSoft CRM with a message stating the nature of the error.

Once you correct the error manually, you must resubmit the transaction.
If a contract was successfully created and is ready for billing, but the transaction fails to populate the contract interface tables, the transaction is not created and the response message sends an error message back to PeopleSoft CRM stating the cause of the error.

Once you correct the problem manually, you must resubmit the transaction. PeopleSoft CRM resubmits only the Contract Transaction message since the contract has already been created.
If there are errors triggered during the revenue or billing processes, both processes send a response message back to PeopleSoft CRM with the failure and message.

Once you correct the problem manually, you must resubmit the transaction. PeopleSoft CRM resubmits only the Contract Transaction message since the contract has already been created.

Setting Up On Demand Transactions

This section discusses how to set up on demand transactions in PeopleSoft Financials and Supply Chain Management.

Pages Used for Setting Up On Demand Transactions

Page Name	Object Name	Navigation	Usage
Installation Options - Installed Products	INSTALLATION_FS	Set Up Financials/Supply Chain, Install, Installation Options Click the Products link in the General Options group box.	Select the Contracts Transaction Billing check box to indicate that this product is installed on the system. See PeopleSoft Financials, Enterprise Service Automation and Supply Chain Management Application Fundamentals 8.8 PeopleBook, “Setting Installation Options for PeopleSoft Applications”
Contracts Definition - BU Definition	BUS_UNIT_TBL_CA	Set Up Financials/Supply Chain, Business Unit Related, Contracts, Contracts Definition, BU Definition	Create a new PeopleSoft Contracts business unit definition or manage an existing business unit. See PeopleSoft Contracts 8.8 PeopleBook, “Defining PeopleSoft Contracts Business Units”
Contracts Definition - BU Options	BUS_UNIT_OPT_CA	Set Up Financials/Supply Chain, Business Unit Related, Contracts, Contracts Definition, BU Options	Select a bill plan template ID to use to override the fields on the billing plan (optional). If you select a template on this page, when the billing plan is created, the billing plan detail template overrides the corresponding fields on the billing plan. See PeopleSoft Contracts 8.8 PeopleBook, “Defining PeopleSoft Contracts Business Units”
Contract Status	CA_STATUS_PNL	Set Up Financials/Supply Chain, Product Related, Contracts, General Options, Contract Status	Define contract statuses and map them to processing statuses. The system uses the contract status to control all processing that can occur against a contract. See PeopleSoft Contracts 8.8 PeopleBook, “Structuring Contracts”
CRM Accounting Rules	CA_ACCT_CRM	Customer Contracts, Create and Amend, CRM Acct Distribution	Define the accounting rules to apply to PeopleSoft CRM transactions. Set up the accounting rules for on demand transactions to ensure that the system allows only one REV row per transaction See PeopleSoft Transaction Billing Processor 8.9 PeopleBook, “Setting Up PeopleSoft Transaction Billing Processor”

Setting Up Sales and Use Tax for Third-Party Tax Vendors

This chapter provides an overview of the tax setup for third-party tax vendors and discusses how to set up sales and use tax for third-party tax vendors. To enter sales and use tax, use the Tax Parameters (RF_TAX_PARAM) component. To load data into the tables for this component, you can also use the RF_TAX_PARAM component interface.

Understanding Tax Setup for Third-Party Tax Vendors

Use the Tax Parameter Definitions page to integrate with third-party tax vendors, such as Taxware or Vertex. The system passes the values in the fields that appear on the page to PeopleSoft Transaction Billing Processor with every PeopleSoft CRM transaction and uses the values during invoice finalization when the taxes are calculated.

For Sales and Use Tax, there are two ways of calculating the taxes on PeopleSoft Billing side, either the third-party tax calculations or PeopleSoft internal tax calculation. Basically, the tax code and the address overrides are used for calculating taxes through PeopleSoft internal system.

The data required for internal tax calculations is sent through the integration with PeopleSoft Transaction Billing Processor. If the Billing business unit on the SCM side is configured for PeopleSoft internal tax calculation, it calculates the taxes. It is basically the tax code.

You can define fields for each type of transaction (agreement fees, service order fees, and case fees) independent of each other. Use the fields listed in the next section only if you have a third-party integration with either Taxware or Vertex.

See Also

PeopleSoft Integration Broker

PeopleSoft Integration Tools and Utilities

PeopleSoft Business Interlink Application Developer Guide

Common Elements Used in This Section

Product Tax Group

Use to identify special tax-related charge information associated with individual transaction lines. For example, suppose that you are selling computers, a computer for the hearing impaired might receive a better rate for a laptop than a computer that doesn't have a feature for the hearing impaired.

The values for this field come from the Product Group table. You may, however, enter free-form values. This is not a required field, so you may leave it blank.

See Product and Item Management.

Note. These values should match the values defined by either Taxware or Vertex. As the administrator, you must enter the values accurately, because there is no interface to verify that the tax group is a valid Taxware product code or Vertex product group.

Transaction Type

Determines how a vendor can calculate taxes. For example, the State of Illinois charges a six percent sales tax for purchases. This field includes these translate values: Rental, Sales, and Service. It is not a required and may be left blank.

Transactions Sub Type

Use for reporting purposes with the Vertex product only. This field is tied to the Transaction Type field and has predefined translate values that include Expense, Freight, Misc, None, Property, Rental, and Service. It is not required and may be left blank.

Page Used to Set Up Sales and Use Tax for Third-Party Tax Vendors

Page Name	Object Name	Navigation	Usage
Tax Parameter Definitions	RF_TAX_PARAM	Set Up CRM, Common Definitions, Tax Parameter Definition, Tax Parameter Definition	Set up sales and use taxes for service, material, labor, expenses, and cases for third-party tax vendors.

Setting Up Sales and Use Tax for Third-Party Tax Vendors

Access the Tax Parameter Definitions page.

Service Sales and Use Tax

Select the service type and service ID for which you want to enter tax information. To add additional rows of information, click the Add Service Sales and Use Tax button.

Material Sales and Use Tax

Select the item group and item ID for which you want to enter tax information. To add additional rows of information, click the Add Material Sales and Use Tax button.

Labor Sales and Use Tax

Select the cost category for which you want to enter tax information. To add additional rows of information, click the Add Labor Sales and Use Tax button.

Expense Sales and Use Tax

Select the expense type for which you want to enter tax information. To add additional rows of information, click the Add Expense Sales and Use Tax button.

Support Sales and Use Tax

Select the product and case type for which you want to enter tax information. To add additional rows of information, click the Add Support Sales and Use Tax button.