Siebel Communications Guide > Profiles in Siebel Communications >

About Billing Profiles in Siebel Communications

End users create a billing profile to invoice the customer for products and services. A billing profile contains such information as billing frequency, payment type, bill media, bill type, and the customer's email address for sending a bill electronically. This information can be submitted to a back-office application for bill processing.

A billing profile is generally associated with a billing account and can represent the legally binding agreement between the customer and the service provider. A billing profile might contain information synchronized from an external billing application.

End users can associate more than one billing profile with an account, but they must choose one billing profile as the primary billing profile.

When Siebel Communications is integrated with a third-party billing application through Oracle Application Integration Architecture, a billing profile record is successfully passed to the billing application if the contact and address fields for the record contain data and if the payment method field for the record is Credit Card, Automatic Debit, or Bill Me. Additionally, if the payment method is Credit Card, the billing profile record is successfully passed to the billing application only if the Name, Credit Card #, and Exp fields in the Credit Card Payment form contain data. If the payment method is Automatic Debit, the billing profile record is successfully passed to the billing application only if the Account # and Routing # fields in the Automatic Debit form contain data.

After billing profiles are created, end users can select any billing profile for the account that is associated with a quote, a quote line item, an order, or an order line item (and, through an order line item, with an asset). For more information about Oracle Application Integration Architecture, see About Prebuilt Integration with Siebel Communications.