One of the primary activities that municipalities are involved in is the charging and receiving of municipal rates and tariffs. It is unusual for a property in a town or city to be free of such charges. The local authority then needs to send bills to residents every month and also take the monies paid to them. Their utility bill software therefore needs to be able to handle these tasks.
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.
Also, towns and cities are home to large populations, sometimes numbering several millions of people. This makes the municipal database of residents extremely large, so the software that is used should be able to accommodate a database of this size. These records are also being updated on a monthly basis, or at least continuously.
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.
Third, the software needs to allow its users to produce paperwork that is appropriate to the local residents. Some urban settlements are home to more than one language. This should be accommodated through the use of bilingual bills, or bills issued in the language of a specific resident's area. The software should be able to handle more than one language where this is required.
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.
The bill itself should be easy to analyze. It should have an open, simple layout that shows the important amounts and dates, even to a person who is not used to assessing such documents or who has a low level of literacy.
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.
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.
Also, towns and cities are home to large populations, sometimes numbering several millions of people. This makes the municipal database of residents extremely large, so the software that is used should be able to accommodate a database of this size. These records are also being updated on a monthly basis, or at least continuously.
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.
Third, the software needs to allow its users to produce paperwork that is appropriate to the local residents. Some urban settlements are home to more than one language. This should be accommodated through the use of bilingual bills, or bills issued in the language of a specific resident's area. The software should be able to handle more than one language where this is required.
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.
The bill itself should be easy to analyze. It should have an open, simple layout that shows the important amounts and dates, even to a person who is not used to assessing such documents or who has a low level of literacy.
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.
0 commentaires:
Enregistrer un commentaire