Designing an application like accounting

From Windows to Web based, computerised accounting application has come a long way.

In Allstaff we have taken the long and winding road in the use and application of accounting system. Back many years we embarked on the development of a simple accounting system for our internal use. Using Visual Basic 6 we created a simple easy to use, "data-entry" centered application that we used for quite a number of years. We called it posit.

Faced with the non ending problems of dll (dynamic linked libraries) compatibilities, version upgrades issues and Window's constant upgrade of SP, we were forced to switch to a simpler-to-deploy and high-productivity platform; we found Linux and php.

Since then we never looked back.

When we first started with php, there was the constant nagging doubt of the capability of the Web technology handling "data-entry" based application. Security and speed was always our concerns. We were aware of Web technology weakness in handling state, and therefore we put great effort in carefully crafting the entry modules, such journal and budget entry.

In short, the simple rule in designing an accounting application is to create a robust, easy-to-use and responsive system. The system should work like a black box where entries are form validated and also checked for "debit=credit" balance. Once you have such a system developed, the next requirement is to have a good and strict manual procedure in place, this is to ensure that data from input documents are entered accurately, and strictly following the accounting rules.

Our php based accounting system called ipost has been running for over 4 years now and is still running superbly well. A Chinese version is ready for deployment and more enhancements are in the pipe line.