|
MegaBillback provides a method of billing telephone and other miscellaneous charges back to specific organizational
departments or areas and to the appropriate general ledger accounts. It can be used in conjunction with MegaRates
phone charges or with call charges already rated from other sources, such as calling cards.
Billing Cycles
MegaBillback's billing cycles are flexible. All billing periods and cutoff dates are user-defined.
Managing Charges
In conjunction with MegaRates, MegaBillback lets the user set up multiple markup strategies. Each strategy contains
one or more of the following elements:
- A default pricing method
- Pricing methods that differ from the default for each type of call (fax call, long distance call, etc.) and
for dialed digits with specific destinations.
- Call charges can be assigned to organizational units based on a call's station or its authorization or account
code, and the user can define which method is used (as covered by MegaCall).
- Pricing methods that differ from the default for each transaction type to which they apply.
Transactions (charges)
Each transaction has an effective date (the current date, past, or future date), a serial number, a transaction
type, a description and a user reference field. A transaction will have both cost and charge fields, which MegaBillback
will attempt to fill with the appropriate price method.
MegaBillback maintains a record of the user ID associated with a transaction's origin, whether entered manually,
through an automated external system or set up as a recurring transaction and generated by MegaBillback as part
of the billing procedure.
MegaBillback also indicates where an automatically-entered transaction was manually overridden.
The user may define an unlimited number of transaction types and assign each to one of the following classes:
- repairs
- add/move/delete
- monthly charges
- miscellaneous charges
- finance charges
- call charges.
Transaction data can be optionally imported from other software packages into MegaBillback.
For speed of data entry while entering transactions, once the transaction type has been entered, additional
information, if any, is automatically copied from a memorized transaction list. Recurring transactions can be memorized
for speed of data entry or for automatic entry by the system.
|
