Configuring Company Details in CentreBillA logical procedure is followed in adding
new companies and getting them set up. The screen below is for an existing company set up and fully operational in CentreBill. At the highest level of the tree structure it also shows that there are three
other companies configured in the system. The default screen above shows the minimum information that needs to be supplied in order to effectively run CentreBill. The fields include:
|
|
|
as it is to appear on all customer based correspondence |
|
|
|
a company registration number if this is required to appear on tax invoices |
|
|
|
a short name for the company to be used by the system |
|
Address and Contact Details: |
|
all information associated with the company |
|
|
|
internally assigned number for use by the application |
|
|
|
the companies' primary bank which receives the customer's payments |
|
|
|
|
|
|
to be presented on the remittance slip |
|
Email and Domain information: |
|
presented on emails, correspondence and used internally |
|
|
|
how many days after invoice is raised (as opposed to charge being raised, if different) is payment due |
|
|
|
government taxes on each charge raised |
|
|
|
this is used to determine how many days are to lapse after the payment due date prior to sending out automatic overdue account notices |
|
|
|
this is used to generate the report for exception management is chasing up poor payers. It may also be used to automatically suspend these customers (currently
disabled) |
|
|
|
the number of elapsed days after raising the invoice and before automatically charging the customer's credit card are entered here |
|
|
|
this is used in financial reporting and for purging old data |
|
|
|
this is the amount the Company wishes to retain for itself and not make available for distribution to staff as part of the Contribution Margin
determination calculations |
|
|
|
how many licenses have been allocated out of the total pool of licenses to that particular company |
|
|
|
the timeout period for a license after no activity |
|
|
|
whether a user may be logged in more than once with the same username and password |
|
|
|
are also uploaded here and are used for both the online interface in MI3 and on printed reports, such as invoices, receipts and statements |
|