Implementation Defaults

Defaults for Offering Packages and Bundles to Customers

Table 2-1 lists the default settings for packages and bundles provided by BRM:

Table 2-1 BRM Default Settings

Business Decision	Default Behavior	How to Customize
Control which packages a customer can create an account with on the Web.	Customers can create accounts with packages in the default package list.	When implementing Web-based account creation, write a script that presents packages based on user input. See "Getting Data about Bundles, Charge Offers, Discount Offers, and Services" in BRM Opcode Guide. To customize the source code, see PCM_OP_CUST_POL_GET_PLANS.
Control which bundles are available to customers.	The customer can purchase all bundles.	When implementing Web-based account creation, write a script that presents bundles based on user input. See "Getting Data about Bundles, Charge Offers, Discount Offers, and Services" in BRM Opcode Guide. To customize the source code, see PCM_OP_CUST_POL_GET_DEALS.
Change the amount of time during which you can cancel a charge offer without charging a cancel fee.	Cancel fees are applied.	Change the cancel_tolerance entry in the Connection Manager (CM) configuration file. See "Canceling Charge Offers without Charging a Cancel Fee" in BRM Managing Customers.
Set a credit limit in a package.	Credit limits are set to 0.	Change the credit limit in PDC. See "Applying Credit Limits to Balances" in BRM Creating Product Offerings. To customize the source code, see PCM_OP_CUST_POL_PREP_LIMIT.

Defaults for Creating Customer Accounts

Table 2-2 lists the default settings for customer accounts:

Table 2-2 Default Settings for Customer Accounts

Business Decision	Default Behavior	How to Customize
Specify the default country, in case the customer doesn't enter a country name.	USA.	Change the country entry in the CM configuration file. To customize the source code, see PCM_OP_CUST_POL_PREP_NAMEINFO.
Specify how to assign the merchant to each account. See "Setting Up Merchant Accounts" in BRM Configuring and Collecting Payments.	Use the merchant name from the /config/ach object.	To use multiple merchant names, customize the PCM_OP_CUST_POL_PREP_BILLINFO source code.
Specify the numbering scheme for account numbers.	Account numbers are created by combining the database number with the object ID from the account POID, for example, 0.0.0.1-1482.	To change how account numbers are generated, customize the PCM_OP_CUST_POL_PREP_ACCTINFO source code.
Standardize data for account names. For example, to ensure consistent display and formatting of account names, you can capitalize the first and last name, regardless of how the customer entered the information.	The name is formatted exactly how the customer entered it.	Customize the PCM_OP_CUST_POL_PREP_NAMEINFO source code.

Defaults for Login Names and Passwords

Table 2-3 lists the default settings for login names and passwords.

Table 2-3 Default Settings for Login Names and Passwords

Business Decision	Default Behavior	How to Customize
Specify the characteristics of a valid login name and password.	At least 1 character but no more than 255 characters.	To specify login requirements, including a list of "naughty words", use the Field Validation Editor. To edit the source code, see PCM_OP_CUST_POL_VALID_LOGIN and PCM_OP_CUST_POL_VALID_PASSWD.
Specify how to encrypt passwords.	Passwords for broadband services are not encrypted. AES encryption is used for nonservice passwords.	Customize the PCM_OP_CUST_POL_ENCRYPT_PASSWD source code.
Specify requirements for email login names.	Customers must use all lowercase characters for email logins. The login name must include the domain name.	Customize the PCM_OP_CUST_POL_PREP_LOGIN source code.
Specify whether the customer or the system picks the password.	Customer must specify a password.	To supply an algorithm for generating passwords, customize the PCM_OP_CUST_POL_PREP_PASSWD source code.
Specify the number of days before a CSR password must be changed.	CSR passwords expire after 90 days.	Edit the passwd_age entry in the CM configuration file. See "Setting the Default Password Expiry Duration" in BRM System Administrator's Guide.

Defaults for Validating Customer Account Creation Information

Table 2-4 lists the default settings for validating customer account creation information:

Table 2-4 Default Settings for Customer Account Creation Validation

Business Decision	Default Behavior	How to Customize
Specify the minimal information a CSR or customer must enter to create an account.	Customer must enter: Last name Address City State ZIP code Country Service logins and passwords	To change which entries are required, use the Field Validation Editor. To customize the source code, see PCM_OP_CUST_POL_VALID_NAMEINFO.
Specify the formats a CSR or customer must use when entering state, phone number, and postal code.	State: two uppercase letters, for example, CA. Phone number: either a TAPI-compliant number or (xxx) xxx-xxxx Postal code: (USA only); 5 digits, or 5 digits followed by a hyphen and 4 digits.	To change the required format, use the Field Validation Editor. To customize the source code, see PCM_OP_CUST_POL_VALID_NAMEINFO.
Validate state and ZIP code for tax calculation.	Do not validate state and ZIP code.	Edit the tax_valid entry in the CM configuration file. See BRM Calculating Taxes. To customize the source code, see PCM_OP_CUST_POL_VALID_NAMEINFO.

Business Decision

Default Behavior

How to Customize

Specify the minimal information a CSR or customer must enter to create an account.

Customer must enter:

Last name
Address
City
State
ZIP code
Country
Service logins and passwords

To change which entries are required, use the Field Validation Editor.

To customize the source code, see PCM_OP_CUST_POL_VALID_NAMEINFO.

Specify the formats a CSR or customer must use when entering state, phone number, and postal code.

State: two uppercase letters, for example, CA.
Phone number: either a TAPI-compliant number or (xxx) xxx-xxxx
Postal code: (USA only); 5 digits, or 5 digits followed by a hyphen and 4 digits.

To change the required format, use the Field Validation Editor.

To customize the source code, see PCM_OP_CUST_POL_VALID_NAMEINFO.

Validate state and ZIP code for tax calculation.

Do not validate state and ZIP code.

Edit the tax_valid entry in the CM configuration file.

See BRM Calculating Taxes.

To customize the source code, see PCM_OP_CUST_POL_VALID_NAMEINFO.

Defaults for Validating Payment Information

Table 2-5 lists for validating payment information:

Table 2-5 Defaults to Validate Payment Information

Business Decision	Default Behavior	How to Customize
Specify what information to validate when creating an account.	BRM validates the credit card only. An error in the street address is allowed. The following errors are not allowed: Wrong postal code Bad credit card number Failed credit check	Customize the PCM_OP_PYMT_POL_VALIDATE source code.
Specify how to validate payment information, such as credit card type, expiration date, and debit account information.	For credit cards, verifies the type as: Amex Carte Blanche Diners Discover JBC Mastercard Optima VISA Validates that the credit card number has the required number of digits, and verifies the expiration date. For direct debit, validates the number of digits in bank, branch, and account numbers.	Customize the PCM_OP_CUST_POL_VALID_PAYINFO source code.
Specify whether to validate the customer's billing information during account creation.	Validates credit card information.	Change the cc_validate entry in the CM configuration file. See "Specifying How to Validate Customer Contact Information " in BRM Managing Customers. To customize the source code, see PCM_OP_PYMT_POL_SPEC_VALIDATE.
Specify whether to validate direct debit information during account creation.	Validates direct debit information.	Change the dd_validate entry in the CM configuration file. See "Enabling Paymentech Direct Debit Processing" in BRM Configuring and Collecting Payments.
Specify the time between validations of the same credit card. For example, you can allow two members of the same family to create an account for the same service without validating the credit card the second time.	Does not validate a credit card that has been validated within the last hour.	Edit the cc_revalidation_interval entry in the CM configuration file. See "Avoiding Credit Card Revalidation" in BRM Managing Customers. To customize the source code, see PCM_OP_PYMT_POL_SPEC_VALIDATE.
Specify the valid format for entering a credit card or debit number.	Strips spaces between groups of digits.	Customize the PCM_OP_CUST_POL_PREP_PAYINFO source code. See "Customizing Payment Method Data Preparation" in BRM Opcode Guide.
Specify the valid date format for credit card or debit card expiration.	BRM stores expiration dates as 4-character strings in the format MMYY. BRM is Y2K compliant, for example, 02 is the same as 2002. Valid formats are: MMYY MM/YY M/YY MM/YYYY All formats are converted to MMYY.	Customize the PCM_OP_CUST_POL_PREP_PAYINFO source code. See "Customizing Payment Method Data Preparation" in BRM Opcode Guide.
Run a checksum validation on the customer's credit card during validation.	Use a checksum to validate the credit card during account creation.	Change the checksum entry in the CM configuration file. See "Disabling the Credit Card Checksum" in BRM Opcode Guide.

Defaults for Displaying and Sending Introductory Messages

Table 2-6 lists the default settings used to display and send introductory messages:

Table 2-6 Default Settings for Introductory Messages

Business Decision	Default Behavior	How to Customize
Specify whether to display an HTML introductory message to customers during account creation.	The introductory message is disabled by default.	Customize the default introductory message and configure your Web-based account creation to display it. See "Customizing the Introductory Message" in BRM Opcode Guide. To enable the introductory message, customize the PCM_OP_CUST_POL_GET_INTRO_MSG source code.
Specify whether to send a welcome email message to customers after they create an account.	The welcome email message is enabled by default.	Customize the welcome message. See "Setting up Welcome Messages to Customers" in BRM Managing Customers. To customize the source code, see PCM_OP_CUST_POL_POST_COMMIT.

Business Decision

Default Behavior

How to Customize

Specify whether to display an HTML introductory message to customers during account creation.

The introductory message is disabled by default.

Customize the default introductory message and configure your Web-based account creation to display it. See "Customizing the Introductory Message" in BRM Opcode Guide.

To enable the introductory message, customize the PCM_OP_CUST_POL_GET_INTRO_MSG source code.

Specify whether to send a welcome email message to customers after they create an account.

The welcome email message is enabled by default.

Customize the welcome message. See "Setting up Welcome Messages to Customers" in BRM Managing Customers. To customize the source code, see PCM_OP_CUST_POL_POST_COMMIT.

Defaults for Billing

Table 2-7 lists the default settings for billing.

Table 2-7 Billing Defaults

Business Decision	Default Behavior	How to Customize
Set the default accounting type to open item accounting or balance forward accounting.	Balance forward accounting.	Change the actg_type entry in the CM configuration file. See "Setting the Default Accounting Type" in BRM Configuring and Running Billing. To customize the source code, see PCM_OP_CUST_POL_PREP_BILLINFO.
For open item accounting, set whether to include or exclude the previous total (PIN_FLD_PREVIOUS_TOTAL) of the bill from the pending amount due (PENDING_RECV) of the current bill unit (/billinfo object).	The previous total is not included.	Change the open_item_actg_include_prev_total entry in the CM configuration file.
Set the default accounting day to a specific day of the month, or to the day that the account was created.	The day that the account was created. For example, if a customer creates an account on the 15th, the accounting for that customer is done on the 15th. By default, if the account was created on day 29 - 31, the accounting day is the 1st of the next month. You can change this to be able to use any day of the month.	To set the default accounting day of month, change the actg_dom entry in the CM configuration file. See "Setting the Default Accounting Day of Month" in BRM Configuring and Running Billing. To customize the source code, see PCM_OP_CUST_POL_PREP_BILLINFO. To use 31-day billing, see "About Using 31-Day Billing" in BRM Configuring and Running Billing.
Set the default number of accounting cycles in a billing cycle. The billing cycle must be a whole-number multiple of accounting cycles. See "About Accounting and Billing Cycles" in BRM Concepts.	Monthly billing (one accounting cycle per billing cycle).	Change the bill_when entry in the CM configuration file. See "Setting the Default Billing-Cycle Length" in BRM Configuring and Running Billing. To edit the source code, see PCM_OP_CUST_POL_PREP_BILLINFO.
Specify the system currency.	US dollars.	You must set the system currency when you install BRM. See "Setting the System Currency" in BRM Managing Customers.
Specify the default account currency for new accounts.	US dollars.	Change the currency entry in the CM configuration file. See "Setting the Default Account Currency" in BRM Managing Customers. To edit the source code, see PCM_OP_CUST_POL_PREP_BILLINFO.
Specify whether to create a long cycle or a short cycle when creating an account or changing the billing date. See "Specifying How to Handle Partial Accounting Cycles" in BRM Configuring and Running Billing.	If the short accounting cycle is 15 days or greater, create a short cycle. If the short accounting cycle is less than 15 days, create a long cycle.	Customize the PCM_OP_CUST_POL_PREP_BILLINFO source code.
Specify a numbering scheme for bills.	Creates the bill number B-sequence number, for example, "B-81".	Customize the PCM_OP_BILL_POL_SPEC_BILLNO source code.
Change the cutoff time for billing, accounting, and promotion start times. For example, if your cutoff time is 10:00:00 a.m., any events that occur after 10:00:00 a.m. on that date are included in the next billing run.	The cutoff time is midnight.	Change the BillingCycleOffset business parameter. See "Configuring the Billing Cutoff Time" in BRM Configuring and Running Billing.
Bill sponsor group member accounts.	Sponsor group member accounts are not billed.	Change the BillingFlowSponsorship and BillingFlowDiscount business parameters. See "Setting Up Billing for Charge and Discount Sharing Groups" in BRM Configuring and Running Billing.
Change the number of days to delay billing.	Billing is not delayed.	Change the ConfigBillingDelay business parameter. See "Configuring Delayed Billing" in BRM Configuring and Running Billing.
Change how proration is calculated: The number of days in the cycle. The number of days in the month.	Number of days in the cycle.	Change the use_number_of_days_in_month entry in the CM configuration file. See "Calculating Prorated Cycle Fees" in BRM Configuring and Running Billing.
Apply cycle fees in parallel for multiple services in an account.	Cycle fees is applied sequentially for each of the services in an account.	Change the StagedBillingFeeProcessing business parameter. See "Applying Cycle Forward Fees in Parallel" in BRM PDC Creating Product Offerings.
Align the purchase, cycle, and usage start and end times with the accounting cycle if you set up charge offers with delayed fees.	Start and end times are not aligned.	Change the cycle_delay_align entry in the CM configuration file. See "Aligning Account and Cycle Start and End Times" in BRM Configuring and Running Billing.

Defaults for Tax Calculation

Table 2-8 lists the default settings for tax calculations:

Table 2-8 Tax Calculation Settings

Business Decision	Default Behavior	How to Customize
Enable or disable tax calculation.	Both real-time and deferred taxation are enabled.	Change the taxation_switch entry in the CM configuration file. See BRM Calculating Taxes.
Specify whether deferred taxes are calculated separately for a paying parent bill unit and its nonpaying child bill units or consolidated into a single tax item for both the parent and child bill units.	Taxes are calculated separately.	Change the cycle_tax_interval entry in the CM configuration file. See BRM Calculating Taxes.
Change the default ship-from locale for tax calculation.	No default: must be set, or disabled.	Change the provider_loc entry in the CM configuration file. See BRM Calculating Taxes.
Defer tax calculation for all adjustments that occur at account level until the end of the billing cycle.	Tax calculation is deferred.	Change the tax_now entry in the CM configuration file. See "Configuring the Default Tax Method for Account Adjustments" in BRM Calculating Taxes.
Perform tax reversals for adjustments, disputes, and settlements that occur at the bill and account level.	Taxes are not reversed.	Change the tax_reversal_with_tax entry in the CM configuration file. This entry is used if the opcode does not explicitly specify the tax behavior. See "Configuring the Default Tax Method for Account Adjustments" in BRM Calculating Taxes.
Report zero tax amounts.	Zero tax amounts are not reported.	Change the include_zero_tax entry in the CM configuration file. See BRM Calculating Taxes.
Summarize or itemize taxes by jurisdiction.	Summarize taxes by jurisdiction.	Change the tax_return_juris entry in the CM configuration file. See BRM Calculating Taxes.

Defaults for Payments and A/R

Table 2-9 lists the default settings for payments and A/R.

Table 2-9 Payment and A/R Defaults

Business Decision	Default Behavior	How to Customize
Specify the minimum due amount that the pin_collect utility searches for when collecting online payments.	2.00 (expressed in the account currency).	Change the minimum entry in the configuration file (BRM_home/apps/pin_billd/pin.conf). See "Specifying the Minimum Payment to Collect" in BRM Configuring and Running Billing.
Specify the minimum due amount that custom billing utilities search for.	2.00 (expressed in the account currency).	Change the minimum_payment entry in the CM configuration file.
Specify the minimum credit card charge.	2.00 (expressed in the account currency).	Edit the PCM_OP_PYMT_POL_PRE_COLLECT source code.
Specify the minimum refund amount.	2.00 (expressed in the account currency).	Change the minimum_refund entry in the CM configuration file.
Use CVV fraud protection for Paymentech transactions. See "Requiring Additional Protection against Credit Card Fraud" in BRM Configuring and Collecting Payments.	Disabled.	Change the cvv2_required entry in the CM configuration file.
Use card identification data (CID), a method of fraud prevention for American Express card transactions. See "Requiring Additional Protection against Credit Card Fraud" in BRM Configuring and Collecting Payments.	Disabled.	Change the cid_required entry in the CM configuration file.
Specify whether to collect cycle forward and purchase fees when the customer creates an account.	Collects cycle-forward and purchase fees on account creation only for credit card customers.	Change the cc_collect entry in the CM configuration file. See "Charging Customers at Account Creation" in BRM Managing Customers. To customize the source code, see PCM_OP_PYMT_POL_SPEC_COLLECT.
Specify the payment methods your customers can use. If you use a payment method that is not included in the defaults, you must create a new payment method.	Accepts these payment methods: Credit card Invoice Nonpaying child Undefined Prepaid Debit card Direct debit Smart card Beta	To create a new payment method, customize the PCM_OP_CUST_POL_PREP_PAYINFO source code. To validate payment methods, use the Field Validation Editor.
Set the payment due date for invoice payments.	30 days.	Customize the PCM_OP_CUST_POL_PREP_PAYINFO source code.
Set the default invoice type to summary invoice.	Detailed invoices are generated.	Change the value of the PIN_FLD_INV_TYPE field in the /payinfo object to 1. When creating a customer account, pass it in the input flist of PCM_OP_CUST_COMMIT_CUSTOMER. When adding or changing a payment method, pass it in the input flist of PCM_OP_CUST_SET_PAYINFO.
Specify how to handle underpayments. See "Processing Overpayments and Underpayments" in BRM Configuring and Collecting Payments.	For balance forward accounting, BRM applies the payment to the oldest items first. If the remainder doesn't match the amount due for any one item, BRM requires that the remainder must be allocated manually. For open item accounting, BRM requires that the payment must be allocated manually.	Customize the PCM_OP_PYMT_POL_UNDER_PAYMENT source code.
Specify how to handle overpayments. See "Processing Overpayments and Underpayments" in BRM Configuring and Collecting Payments.	For balance forward accounting, BRM closes all open items and applies the overpayment as a credit balance. By default, you must allocate the resulting credit balance to future open items manually. For open item accounting, BRM requires that the payment must be allocated manually.	Customize the PCM_OP_PYMT_POL_OVER_PAYMENT source code.
Specify what to do if a credit card customer doesn't pay. See "Processing Late or Missed Payments" in BRM Configuring and Collecting Payments.	Inactivates the account if the account has an item more than 30 days past due and a credit card transaction receives one of these failures: Soft decline Wrong address Wrong ZIP code No connection Inactivates the account immediately if a credit card transaction receives one of these failures: Bad card Hard decline	Customize the PCM_OP_PYMT_POL_COLLECT source code.
Change the euro conversion error tolerance.	When the conversion result is less than the amount due: Apply tolerance values only if the amount applied to the item is in secondary currency. When the conversion result is more than the amount due: Do not apply tolerance values defined for balance elements.	Change the overdue_tolerance and underdue_tolerance entries in the CM configuration file. See "Handling Euro Conversion Rounding Errors" in BRM Managing Customers.
Collect the current direct debit balance of each account during account creation.	Collect the balance.	Change the dd_collect entry in the CM configuration file. See "Enabling Paymentech Direct Debit Processing" in BRM Configuring and Collecting Payments.
Specify how to handle write-off reversals.	Apply write-off reversals at the account level.	Edit the AutoWriteOffReversal business parameter. See "Enabling Automatic Write-Off Reversals during Payment Collection" in BRM Managing Accounts Receivable. You can also modify the PCM_OP_AR_POL_REVERSE_WRITEOFF opcode. See BRM Opcode Guide.

Defaults for Maintaining an Audit Trail of BRM Activity

Table 2-10 lists the defaults for maintaining an audit trail of BRM activity.

Table 2-10 Maintaining Audit Trail of BRM Activity

Business Decision	Default Behavior	How to Customize
Specify the BRM activity for which you want to keep an audit trail.	Keeps an audit trail of changes to customer credit card numbers and credit card expiration dates, and changes to BRM pricing components. See "Fields Marked for Auditing by Default".	Enable or disable BRM object fields for auditing by using BRM Storable Class Editor. See "Enabling Auditing for a Field".