![]() |
BillMax Billing Solutions 877.245.5629 sales@billmax.com |
Table of Contents
A Virtual Company may be used to segregate Accounts. Reasons for segregating Accounts may include:
Accounts are managed by different business rules.
Accounts are managed as if they belong to different business entities.
![]() |
Tip |
|---|---|
The values specified for each Virtual Company are available for use in the Email Template Files. |
There are two web pages that are used to configure a Virtual Company. These are "Company Info" and "Company Options".
Click on the Settings link on the Navigation Bar. Click on the "COMPANY INFO" button. The "Company Info" page will be displayed:
This page is used to specify contact information for the Virtual Company.
| (1) |
Clicking |
| (2) |
Clicking |
| (3) |
The "
|
| (4) | Billing Contact email address. This email address is used as the "From:" address when BillMax sends emails to customers. This address receives daily processing emails. A value for this field is required. |
| (5) | Administrative Contact email address. This email address is used as the "To:" for daily processing emails. A value for this field is required. |
The Company Options page specifies business rules.
![]() |
Warning |
|---|---|
Many of the following settings act as defaults for Accounts when creating a new Accounts. Changing theses values will affect new Accounts only, and not existing Accounts. |
Click on the Settings link on the Navigation Bar. Click on the "COMPANY OPTIONS" button. The "Company Options" page will be displayed. This page is composed of the following:
| (1) |
If a partial service term is billed a prorated amount, the setting of billnextterm determines whether an additional complete service term is billed in addition to the partial term.
|
| (2) |
Defines tax status of postal and fax surcharges.
|
| (3) | Default domain used when creating an email address for a User or Account. If a User or Account does not have an email address, when a Service is created, the Service d01 field is combined with defdomain to create an email address for the User and/or Account. The Customer Service Representative is prompted whether to use the value to populate the Account and/or User data. |
| (4) |
The default used for populating the Invday of a new Account
|
| (5) | Default monthly charge for sending an Account fax statements. |
| (6) |
The default state of a new Service.
The state of a service will be changed from WAIT_FOR_PAYMENT to OPEN if either a payment is received or 30 days elapse. |
| (7) | Default postal cost for Accounts that receive postal statements. |
| (8) | 24 hour clock time specifying the end of Prime Time used in Metered Billing. |
| (9) | 24 hour clock time specifying the start of Prime Time used in Metered Billing. |
| (10) | Number of days that a service must be open before referral Store Credit will be issued to the referring Account. |
| (1) |
|
| (2) | Default payment terms for Accounts paying via the check or cash Payment Method. |
| (3) | Default payment terms for Accounts paying via the credit card Payment Method. |
| (4) | Default payment terms for Accounts paying via the ecash Payment Method. |
| (5) | Default payment terms for Accounts paying via the EFT Payment Method. |
| (6) |
When a Service State is changed from Wait_For_Payment State to Open State, should BillMax automatically issue Store Credit for the time the Service State was Wait_For_Payment State?
|
| (1) | Defines how long in days before an Account's credit card expiration date an email may be sent to the Account notifying the Account holder of the impending credit card expiration. See Email Template Files. |
| (2) | Defines the amount to bill an Account when the Account credit card is declined. |
| (3) | The number of days to wait between re-trying a declined credit card. |
| (4) | The maximum number of consecutive unsuccessful attempts to charge a credit card. |
| (5) | The Permissions needed to view the full credit card number. |
| (6) | The default maximum Account balance that will be charged to a credit card through nightly processing. If the Account balance is greater than this amount and this amount is non-zero, credit card processing will not occur for the Account. |
| (7) | The default minimum Account balance that will be charged to a credit card through nightly processing. If the Account balance is less than this amount and this amount is non-zero, credit card processing will not occur for the Account. |
| (8) | The default minimum Account balance (specified as a small negative value) that will be refunded to a credit card through nightly processing. Ignoring the negative sign, if the Account balance is refundable and the amount is less than this amount and this amount is non-zero, credit card processing will not occur for the Account |
| (9) | The default maximum Account balance (specified as a large negative value) that will be refunded to a credit card through nightly processing. Ignoring the negative sign, if the Account balance is refundable and the amount is greater than this amount and this amount is non-zero, credit card processing will not occur for the Account |
| (1) | Defines the number of days a Account, User or Service remains in a Suspended State before being changed to a Closed State. |
| (2) | Specifies how many days before the expiration of a Grace Date an email is sent. Once emails are started, an email is sent daily until Grace Date is reached. See Email Template Files. |
| (3) | A surcharge billed to an Account when the Account becomes overdue. If latepct is specified, the larger of the two is billed. These surcharges are billed monthly every invday without regards to p-rebilldays. |
| (4) |
Determines whether or not Accounts in the Closed State are billed late fees.
|
| (5) | A percentage used to calculate the surcharge billed to an Account when the Account becomes overdue. The surcharge is the amount overdue multiplied by the percentage. If lateamt is specified, the larger of the two is billed. These surcharges are billed monthly every invday without regards to prebilldays. |
| (6) |
Defines whether or not late fees are taxable charges.
|
| (7) |
How often overdue notices are sent. Number of days between overdue notices is odinterval - 1. Examples
|
| (8) |
Maximum number of overdue notices sent to an overdue Account.
|
| (9) | Minimum amount owed by a Account that will trigger Overdue Processing. |
| (10) | Number of days an amount is overdue before overdue notices are sent to an Account. If 0, no notices are sent. |
| (11) | Number of days an amount is overdue before an Account gets suspended. If 0, Accounts are not suspended. |
| (1) |
When the Service end date is specified using the Staff Interface, either by setting the end date or changing the Service State to Closed State, this option defines what to do for Sales that have Payhist Enddates in the future relative to the Service end date. The value supplied may be overridden on a Service by Service basis.
|
| (2) | Default epaydays for an Account. When an invoice is created through automated processing, this value is added to the invoice date to set the invoice's epaydate. Epaydate is the first date an attempt will be made to collect payment for an unpaid invoice through automated payment processing. |
| (3) | A renewable service will be pre-billed this many days before it expires. Statements will be sent to customers this many days before their Invday also. |
| (4) |
Specified whether to-date usage will be billed this config.prebilldays days before the next usage billing period as specified by usage billing options of a Service Definition.
|
| (5) |
Choose whether or not timing for collecting funds for usage data should take into account epaydays.
|
There are two aspects to usage data billing that are controlled by Virtual Company options. These are config.usageepaydays and config.usageprebilldays. The interaction with account.epaydays and config.prebilldays is best described with an example.
Example 3.1. Usage Billing Interaction with Epaydays and Prebilldays
Assume the following:
account.epaydays is 10. "account" as each Account has its own epaydays. config.epaydays is just the default for new Accounts.
config.prebilldays is 10.
service.invdate is 2003-02-01.
The Service Definition specifies that usage billing is to occur monthly on the day the Service is billed.
The billing for the subscription part of the Service occurs on 2003-01-22 and collection for the amount of the subscription part is scheduled for 2003-02-01.
How usage billing and collecting is determined in the following manner:
The usage is billed on 2003-02-01 and collection for the usage amount is scheduled for 2003-02-01. This results in collecting for subscription and usage billings on the same day, but usage billing being done 10 days after subscription billing.
The usage is billed on 2003-02-01 and collection for the usage amount is scheduled for 2003-02-11. The day funds for the subscription part are collected is the day that usage is billed. There is a 20 day gap between the day the subscription is billed and the funds for usage are collected.
The usage is billed on 2003-01-22 and collection for the usage amount is scheduled for 2003-01-22. Funds for the subscription part are collected 10 days later. Although this combination is possible, it makes the least sense.
The usage is billed on 2003-01-22 and collection for the usage amount is scheduled for 2003-02-01. The subscription billing and usage billing are done on the same day. The collections for the subscription and usage billings are done on the same day.