Billing system for a telephone company
The problem
The client ran a telephone callback company based in Sydney, Australia. It had several thousand clients in Australia who could dial a number in America and be connected to a cheaper international "callback" line.
Each month, the client received a text file from the US-based callback company summarising the month's transactions in US dollars. This file had to be converted into a set of invoices for the Australian customers in Australian dollars. The customers' subsequent payments had to be processed, banked, and forwarded on to the US in US dollars. At the time, this function was outsourced to a third party.
To complicate matters more, the client had an arrangement with the US company where monies recovered from some delinquent accounts that were more than a certain period overdue did not need to be forwarded to the US.
Thus, money received in Australian dollars from a customer had to be reconciled with earlier invoices, converted into US dollars at the exchange rate relevant at the time, and then allocated into amounts that were either "sent" to the US company or were "kept" in Australia.
The solution
DI Management carried out a thorough review of the client's existing systems and made a series of recommendations for improvement. One outcome was the commissioning of DI Management to create an improved billing system to enable the client to carry out its billing and account processing functions in-house.
- Receipts: Accepts cash receipts and posts data at end of day.
- Invoices: Everything to do with the creation and production of invoices.
- Customers: Customer queries, maintenance of details, and updating of Master Customer List.
- Traffic call data: Everything to do with the production of call detail traffic reports.
- Accounting: Close customer account; adjust balances.
- Set Up: Sets parameters for system (password protected).
If you are looking for an outsourced call center like this client, there are many options to choose from.
Contact us
Please send us a message.
This page last updated 12 May 2011
