This chapter provides overviews of billing systems integration of the communications and energy industries and enterprise integration points (EIPs) used in the communications and energy industries, and discusses how to define configuration parameters to implement billing systems integration for the communications and energy industries.
Integration with billing systems facilitates seamless data flow between PeopleSoft Enterprise CRM and third-party billing applications in the following ways:
Billing-integration enables communication and energy service providers to provide superior customer service.
Through billing integration, industry solutions offer customer service representatives (CSRs) access to a complete, multidimensional view of all customer information (accounts, billings, installed services, and so on), in addition to account and billing application functionality.
PeopleSoft industry solutions deliver EIPs for the integration with billing systems.
Through the use of EIPs, which prompt and initiate actions in business processes to communicate with the billing system, the integration leverages application functionality provided in account, billing and service management (for example, update account information, view bill details, and change service features) to support the entire customer lifecycle, from acquisition through support.
PeopleSoft Integration Broker develops the integration between PeopleSoft industry solutions and external billing systems.
Integration Broker is an industry-standard tool that enables open flow of information between systems, which is extremely critical for system-to-system integration. It accomplishes true internet system integration by leveraging ubiquitous internet technologies such as XML and HTTP.
PeopleSoft industry solutions provide prebuilt integration messaging capability.
Request and reply messages prepared for all EIPs are stored in Integration Broker. Using configuration parameters, you can either turn on all prebuilt EIPs or just a subset.
Note. The discussion on integration in this chapter is primarily focused on the functional account and billing frameworks, workflow, and predefined inbound and outbound messages that are delivered with the application. It is assumed that some degree of configuration is required during the implementation project to tightly integrate specific industry solutions offered by PeopleSoft with third-party or legacy billing applications.
An EIP is an instance of enterprise integration between a PeopleSoft application and an external system or application: a seamless connection between the two products to accomplish a specific business purpose. PeopleSoft industry solutions implement EIPs to integrate with billing systems.
PeopleSoft delivers EIPs. While most billing EIPs are initiated by a customer-facing event that occurs in a particular industry solution (for example, new service order, service change order, view accounts, change account information, view bills, and dispute bills), some are driven by business projects (for example, account creation through the order management process). Several EIPs are built into components themselves (for example, account view or bill view).
The following are account-related EIPs:
Create account.
View account balance and usage.
Change payment details.
Change billing address.
The following are bill-related EIPs:
Get Bill List EIP.
View Bill Items EIP.
View Bill Events EIP.
Create Disputes and Adjustments EIP.
PeopleSoft CRM industry solutions enable CSRs to get all bills that are associated with an account over a period of time. Billing data are retrieved from the billing system and viewable by CSRs as well as customers (using the self-service application).
To mitigate the dependencies on billing systems to access bill-related information, you can replicate bills on a monthly basis and force CRM industry solutions to access the local data store. The CRM system does not replicate billing information automatically.
The diagram shows the Get Bill List process flow:
Category |
Description |
EIP |
Get Bill List |
Request Message |
RBT_GETBILL_REQ_MSG |
Message Type |
Outbound Synchronous |
Message Called From |
Account Component |
Reply Message |
RBT_GETBILLS_RPLY_MSG |
Channel Name |
RBT_BILL_CHNL |
Configuration Parameter Used |
RBTBILL, RBTBILLCYCLES |
A customer can contact a CSR and inquire about bill items associated with an account.
The following diagram shows the View Bill Items process flow:
Category |
Description |
EIP |
View Bill Items |
Request Message |
RBT_GETBILLITEMS_REQ_MSG |
Message Type |
Outbound Synchronous |
Message Called From |
Account Component |
Reply Message |
RBT_GETBILLITEMS_RPLY_MSG |
Channel Name |
RBT_BILL_CHNL |
Configuration Parameter Used |
RBTBILLITEM |
A customer can contact a CSR and inquire about bill events (within bill items) associated with an account.
Category |
Description |
EIP |
View Bill Events |
Request Message |
RBT_GETBILLEVENTS_REQ_MSG |
Message Type |
Outbound Synchronous |
Message Called From |
Billing Component |
Reply Message |
RBT_GETBILLEVENTS_RPLY_MSG |
Channel Name |
RBT_BILL_CHNL |
Configuration Parameter Used |
RBTBILLEVENT |
Create Disputes and Adjustments EIP
As a bill dispute gets saved in the CRM system, it needs to be reflected in the billing system accordingly so that proper adjustments can be made to customers’ accounts in a timely fashion. Customers can create bill disputes through CSRs, or by themselves using the self-service application.
Disputes can be raised against:
Bill items (for example, if the wrong rate plan is used to calculate long distance charges).
Bill events (for example, dropped calls).
Account balance and usage (for example, an account is not credited accurately).
Category |
Description |
EIP |
Create Dispute |
Request Message |
RBT_BILL_DISP_MSG |
Message Type |
Outbound Asynchronous |
Message Called From |
Case Component |
Channel Name |
RBT_BILLDISP_CHNL |
Configuration Parameters |
RBTMAXDISP, RBTMAXITEMUSD (bill item dispute), RBTMAXEVENTUSD (bill event dispute)/RBTMAXEVENTMIN (bill event dispute), RBTMAXBALUSD (account balance dispute), RBTMAXUSAGEMINS (account usage dispute) |
See Also
PeopleSoft Enterprise CRM 8.9 Process Integration Packs PeopleBook
This section provides overviews of configuration parameters and the Billing Account component and discusses how to:
Define configuration parameters for integration.
Set up the Billing Account component.
You need to complete two setups for the integration with billing systems to run properly:
Set up for Integration Broker.
Set up integration gateway properties.
Set up local and remote nodes.
Define integration messages and corresponding channels.
Set up for PeopleSoft Enterprise CRM.
You can turn messaging for EIPs on or off and define threshold values for application rules (to handle disputes. The configuration options are the same for customers in the communications industry and the energy industry. The financial industry and the insurance industry share the same configuration parameters.
Customers want complaints addressed and settled quickly. While some issues take time to resolve, you can take care of those that do not by setting up parameters in the CRM system to make instantaneous adjustments to disputes with insignificant disputing values, for example, less than 1.0 USD in a bill dispute or one minute in a usage dispute.
For instance, a customer in the communications industry files a bill event dispute on a long-distance call he did not make. According to the configuration of the above table, if this dispute is not the sixth one (or more) in this billing cycle and the dispute amount is less than (or equal to) 1.0 USD, the CRM system makes the adjustment automatically. The customer’s account is credited with the amount in dispute, and a message is sent to the system for an account update; the case is then closed.
Page Name |
Object Name |
Navigation |
Usage |
Communications Setup |
RBT_CONFIG_PG |
|
Define billing integration parameters for the communications industry and the energy industry. |
Access the Communications Setup page.
The following table lists configuration parameters that are used to integrate with billing systems. These parameters can be used to turn integration functionality on or off and to enable or disable integration messaging, at the message level, for each EIP.
Parameter |
Description |
INTEGRATBILL |
Turns integration on or off. If this variable is turned off, no messages are published. If this is turned on, messaging for individual EIP can be turned on or off by setting corresponding configuration parameter. |
RBTACCOUNT |
Enables the CRM system to send a message to the billing system asking for new account creation. Set the parameter to 1 to turn it on, 0 to turn it off. |
RBTACTIVATION |
Enables the CRM system to send a message to the billing system asking for service activation. Set the parameter to 1 to turn it on, 0 to turn it off. |
RBTADDR |
Enables the CRM system to publish address changes to the billing system. This message is published only changes are made in the Account component. Set the parameter to 1 to turn it on, 0 to turn it off. |
RBTBALANCE |
Enables the CRM system to send a message to the billing system asking for account balance information. Set the parameter to 1 to turn it on, 0 to turn it off. If this parameter is off, data is read from local tables. |
RBTBILL |
Enables the CRM system to send a message to the billing system asking for bill summary of an account. Set the parameter to 1 to turn it on, 0 to turn it off. If this parameter is off, data is read from local tables. |
RBTBILLCYCLES |
Defines the number of billing cycles for which bills have to be fetched from the billing system. |
RBTBILLITEM |
Enables the CRM system to send a message to the billing system asking for bill item information.Set the parameter to 1 to turn it on, 0 to turn it off. If this parameter is off, data is read from local tables. |
RBTBILLEVENT |
Enables the CRM system to send a message to the billing system asking for bill event information. Set the parameter to 1 to turn it on, 0 to turn it off. If this parameter is off, data is read from local tables. |
RBTDISPUTE |
Enables the CRM system to send a message to the billing system regarding a bill dispute. Set the parameter to 1 to turn it on, 0 to turn it off. |
RBTMAXBALUSD |
Defines the maximum disputable amount (account balance) allowed for automatic adjustment. |
RBTMAXDISP |
Defines the maximum number of disputable cases allowed for an account per billing cycle. |
RBTMAXEVENTMIN |
Defines the maximum number of disputable minutes (bill event dispute) allowed for automatic adjustment. The monetary parameter, RBTMAXEVENTUSD is the default value. |
RBTMAXEVENTUSD |
Defines the maximum disputable amount (bill event dispute) allowed for automatic adjustment. |
RBTMAXITEMUSD |
Defines the maximum disputable amount (bill item dispute) allowed for automatic adjustment. |
RBTMAXUSAGEMINS |
Defines the maximum number of disputable minutes (account usage dispute) allowed for automatic adjustment. |
RBTPAYMENT |
Enables the CRM system to send a message to the billing system effecting a change in payment information. Set the parameter to 1 to turn it on, 0 to turn it off. |
RBTSERVICE |
Enables publication of service-management-related messaging (for example, change, new, suspend, resume, or disconnect service) to the billing system. Set the parameter to 1 to turn it on, 0 to turn it off. |
RBTUSAGE |
Use this parameter to allow the CRM system to send a message to the billing system asking for account usage information. Set the parameter to 1 to turn it ON, 0 to turn it OFF. If this parameter is OFF, data is read from local tables. |
RBTUSEMINS |
Enables the creation of disputes to be based on usage (in minutes). The monetary parameter is the default value. |
RBTACTUSGRESTYP |
Sets the default account usage resource type to be used for self-service disputes. |