Thursday, August 20, 2015

Important Requirements For Utility Bill Software

By Nancy Gardner


Residents of towns and cities almost always have to pay municipal rates. There are very few property owners who are not subject to these charges. Monthly billing occupies a large amount of the municipality's productive time, and yet at the same time the local authority also has to keep tabs on whether or not residents are paying their bills. The utility bill software that the municipality uses to perform these functions therefore needs to be able to support the latter.

In order to be successful, the software needs to satisfy some basic requirements. The issuing of the bills alone should satisfy several criteria. One of the most important of these is accuracy. There is a standing urban joke about how some people receive inaccurate municipal accounts. These typically refer to the astronomical figures that the bill displays, such as a power bill for millions of dollars. This is not, however, as much of a joke as it may seem.

Another factor is the sheer population of the residential area. A city can have literally millions of residents. Any database with that many files is going to need the magnitude of its population to be taken into account. The municipal software should be able to handle an enormous amount of entries, entries which are constantly updated.

Second, the issue of non-payment arises in some cases. This is a common problem in municipal accounting and as such the software should be able to handle it too. Some residents cannot pay, due to indigence, while others simply refuse to, for whatever reason they may have. If the software cannot reliably detect non-payment, it is obviously not suitable.

The issue of the physical statements that are sent to the residents also arises. These should be acceptable to the residents. To start with, the bills need to reflect the linguistic make-up of the town or city. In some towns and cities, there is more than one language in use. The software should therefore be able to handle bilingualism, or even multilingualism, because the bills might be printed in more than one language, or they might be issued in different languages, depending on who they are being sent to.

Staying with language, some residents are either not literate or have only a very low level of literacy. This does not imply that they are low-income earners, either, so it is not a reliable indication of what area or suburb they reside in. They may be professionals or trained workmen, so there is no automatic indication that they stay in the poor suburbs or that they are themselves poor. The bill therefore needs to be very basic in its language, and simple to understand. Where the entire population receives a document, this is always an issue and it should be reflected in the software.

Turning to the account statement itself, its layout should be transparent and simple, showing the payable amount and associated dates. The bill should be intelligible even if the recipient is entirely illiterate or has little experience in reading such documents.

Municipalities need a reliable and accurate software system for their billing administration. Non-payment is a thorny issue that causes severe emotional responses, at times, and the issuing of inaccurate bills is another. The software that the municipality uses to issue the bills should be easy to use for a system that has as many as millions of entries and thousands of users.




About the Author:



No comments:

Post a Comment