By default, you can set the billing day of the month (DOM) to any day between 1 and 28. If your customer signs up on the 29th, 30th, or 31st, the billing DOM is set to the 1st. This can result in a large number of customers being billed on the 1st of the month.

You can change this setting to support billing on all days of the month. For example, if you create a customer account on the 29th, the billing DOM is set to the 29th instead of the 1st.

If your customers' billing DOM is the 29th, 30th, or 31st, for the months that do not have these days, you can configure whether billing should be run on the last day for the same month (set to back option) or the first day of the next month (set to forward option). By default, the billing DOM is set forward to the 1st of the next month.

For example, when the DOM is set to 31 because April has 30 days:

• The set to forward option sets the billing date to May 1.

• The set to back option sets the billing date to April 30.

To use 31-day billing, you must either modify the init_objects.source file before loading it into the database or set the 31DayBilling business parameter using the pin_bus_params utility. After BRM is configured to allow 31-day billing, you can specify whether to use the back or forward option.

To disable the 31-day billing feature:

1. In the init_objects.source file, change the value of the PIN_FLD_MAXIMUM field from 31 to 28 in the /config/fld_validate object that has the Actg_cycle value in the PIN_FLD_NAME field as follows:

   # /config/fld_validate  - Actg_cycle validation
   <PCM_OP $PIN_OPNAME=$PIN_CONF_INIT_OPNAME; $PIN_OPFLAGS=$PIN_CONF_INIT_OPFLAGS>
   0 PIN_FLD_POID                 POID [0] $PIN_CONF_DB_NO /config/fld_validate 606 0
   0 PIN_FLD_DESCR                 STR [0] "Field Validation"
   0 PIN_FLD_HOSTNAME              STR [0] "-"
   0 PIN_FLD_NAME                  STR [0] "Actg_cycle"
   0 PIN_FLD_PROGRAM_NAME          STR [0] "-"
   0 PIN_FLD_VALIDATION      SUBSTRUCT [0]
   1 PIN_FLD_FIELD_TYPE            INT [0] 2
   1 PIN_FLD_MAXIMUM               NUM [0] 28
   1 PIN_FLD_MINIMUM               NUM [0] 31
   </PCM_OP> 

2. Go to BRM_home/sys/data/config.

3. Use the following command to create an editable XML file from the Billing instance of the /config/business_params object:

   pin_bus_params -r BusParamsBilling bus_params_billing.xml

   This command creates an XML file named bus_params_billing.xml.out in your current directory. Use care when updating parameters in the file.

4. In bus_params_billing.xml.out, set 31DayBilling to disabled:

   <31DayBilling>disabled</31DayBilling>

   Caution:

   BRM uses the XML in this file to overwrite the existing instance of the /config/business_params object. If you delete or modify any other parameters in the file, these changes affect the associated aspects of the BRM configuration.

5. Save and exit the file.

6. Rename the bus_params_billing.xml.out file to bus_params_billing.xml.

7. Use the following command to load your changes into the /config/business_params object:

   pin_bus_params bus_params_billing.xml

   You should run this command from the BRM_home/sys/data/config directory, which includes support files used by the utility. To run it from a different directory, see "pin_bus_params" in BRM Developer's Guide.

8. Read the object with the testnap utility or the Object Browser to verify that all fields are correct.

   For general instructions on using testnap, see "Using the testnap Utility to Test BRM" in BRM Developer's Guide. For information on how to use Object Browser, see "Reading Objects" in BRM Developer's Guide.

9. Stop and restart the Connection Manager (CM).

   For more information, see "Starting and Stopping the BRM System" in BRM System Administrator's Guide.

To set the forward and back billing options:

1. Go to BRM_home/sys/data/config.

2. Use the following command to create an editable XML file from the Billing instance of the /config/business_params object:

   pin_bus_params -r BusParamsBilling bus_params_billing.xml

   This command creates an XML file named bus_params_billing.xml.out in your current directory. If you do not want this file in your current directory, specify the path as part of the file name.

3. In bus_params_billing.xml.out, set the following entry:

   <MoveDayForward>value</MoveDayForward>

   where value is one of the following:

   • firstDay: Sets the billing date to the first day of the month. This is the default.

   • lastDay: Sets the billing date to the last day of the month.

   Caution:

   BRM uses the XML in this file to overwrite the existing instance of the /config/business_params object. Use care when updating parameters in the file.

4. Save and exit the file.

5. Rename the bus_params_billing.xml.out file to bus_params_billing.xml.

6. Use the following command to load your changes into the /config/business_params object:

   pin_bus_params bus_params_billing.xml

   You should run this command from the BRM_home/sys/data/config directory, which includes support files used by the utility. To run it from a different directory, see "pin_bus_params" in BRM Developer's Guide.

7. Read the object with the testnap utility or the Object Browser to verify that all fields are correct.

   For general instructions on using testnap, see "Using the testnap Utility to Test BRM" in BRM Developer's Guide. For information on how to use Object Browser, see "Reading Objects" in BRM Developer's Guide.

8. Stop and restart the Connection Manager (CM).

   For more information, see "Starting and Stopping the BRM System" in BRM System Administrator's Guide.