It is very rare for erven in an urbanized area not to be charged municipal rates and taxes. This constitutes one of the main activities of the municipal authority, and bills are sent to residents on a monthly basis. They also need to be able to monitor the payment of these bills. The utility bill software that is used by the municipality can play a part in the success or failure of this process.
There are some indispensable characteristics that the software should have in order to be effective in the municipality's administration. Even the first stage of the billing process, which is the issuing of the actual paper bills, presents some simple requirements to the administration and, in turn, to the software that they use. One of these is accuracy. The standard off-hand wise-crack about the municipal account that shows a million-dollar water bill is not as humorous as it may sound.
Then again, significant urban settlements may house populations of up to several millions. The municipal database thus has the accompanying number of records or entries, and so its software needs to have the capacity to accommodate this volume of records. These are municipal accounts, so they are updated at least once a month, or on an ongoing basis.
Another criterion is that the software should be able to detect and alert its users to non-payment. Non-payment is a perennial issue for municipalities. Indigent residents sometimes do not pay their accounts on time, or at all, and this is typically observed in the impoverished areas of the town or city. Then there are those residents who simply won't pay, for various reasons. Software that cannot pick up non-payment is useless.
Concerning the actual physical paperwork, i. E. The bills that are sent to the residents, this should be acceptable to them. Where a town or city has a linguistically diverse population, the paperwork needs to be sensitive to that. Sometimes, a bill in more than one language is sufficient, but in other towns or cities it is necessary to issue the bills in more than one language, depending on the recipient. The software should be designed to include more than one language where this is an issue.
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.
Inaccuracies in statements are embarrassing to the municipality, and non-payment is a serious threat to the budget. Municipal software needs to address both of these issues. At the same time, the municipal administration presents it with thousands of users and millions of entries, so it should be as easy to use as possible.
There are some indispensable characteristics that the software should have in order to be effective in the municipality's administration. Even the first stage of the billing process, which is the issuing of the actual paper bills, presents some simple requirements to the administration and, in turn, to the software that they use. One of these is accuracy. The standard off-hand wise-crack about the municipal account that shows a million-dollar water bill is not as humorous as it may sound.
Then again, significant urban settlements may house populations of up to several millions. The municipal database thus has the accompanying number of records or entries, and so its software needs to have the capacity to accommodate this volume of records. These are municipal accounts, so they are updated at least once a month, or on an ongoing basis.
Another criterion is that the software should be able to detect and alert its users to non-payment. Non-payment is a perennial issue for municipalities. Indigent residents sometimes do not pay their accounts on time, or at all, and this is typically observed in the impoverished areas of the town or city. Then there are those residents who simply won't pay, for various reasons. Software that cannot pick up non-payment is useless.
Concerning the actual physical paperwork, i. E. The bills that are sent to the residents, this should be acceptable to them. Where a town or city has a linguistically diverse population, the paperwork needs to be sensitive to that. Sometimes, a bill in more than one language is sufficient, but in other towns or cities it is necessary to issue the bills in more than one language, depending on the recipient. The software should be designed to include more than one language where this is an issue.
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.
Inaccuracies in statements are embarrassing to the municipality, and non-payment is a serious threat to the budget. Municipal software needs to address both of these issues. At the same time, the municipal administration presents it with thousands of users and millions of entries, so it should be as easy to use as possible.
Aucun commentaire:
Enregistrer un commentaire