Best practices involved in changing the Accounting Information System AIS

This particular report is an evaluation on AIS through case analysis and presentation involving AIS failure, possible alternatives the firm may have had and just how the management should have strategized to avert the failure. In the end, the paper reveals best practices for migration from another system to AIS.

Accounting info systems (AIS) has transformed business processes on a worldwide scale. When financial data is entered into the AIS, financial statements and reports are created at several business levels to make profitability certain. Steinbart and romney (2012) revealed that the accounting systems process information to offer data to users so that they can not only plan, but also manage and operate respective businesses. Given this situation, accounting info system are viewed as a method which helps management in their planning and balance processes by offering data that is both reliable and relevant for decision making. The essential objective of accounting systems is providing accounting data to outside parties, operational personnel and the management.

An American automotive manufacturer, American LaFrance (ALF), manufactured fire aerials, fire engines as well as emergency apparatus like ambulance and rescue cars. Established in 1873, ALF had probably been the pioneer in fire apparatus production in the United States and by the mid-2000s was recognized as the top brand of custom made fire-fighting, rescue cars as well as ambulances (Huber and Daft, 1986; Bhagwani, 2009). In 2008, ALF underwent a fiscal problem and then recognized that this failure was caused by IBM's unsuccessful Enterprise Resource Planning (ERP) execution. Precisely, the information filed in the bankruptcy court of law, recognized that the issues took place when ALF had stemmed out as an independent firm from its parent company Freightliner, its prior owner. Of the transition, ALF outsourced manufacturing, payroll, inventory, and accounting process services to its prior owner. As component of the transition, ALF created a separate ERP system to give support to the company subsequent to the separation from Freightliner (Bhagwani, 2009). Regardless of the excessive complications experienced by ALF, they made an effort to figure out the IBM’s ERP software. Nevertheless, American LaFrance was not able to solve these major conflicts and underwent loss consequently. The consequences included, incapacity to manage inventory, distribute finished products as well as produce cash flow. This particular liquidity crisis is exactly what inevitably bankrupted this multinational enterprise.

The procedure for applying a financial management info product is a rigorous process which must be perfectly planned prior to initiation of project. The project unit that's tasked with the integration of the AIS must be properly trained in addition to knowledgeable in order to confirm positive system results. When applying an accounting info system, it's imperative that the company is actually prepared and ready; in order to devote the attention that's essential to make the AIS work properly for their specific needs (Bhagwani, 2009). Because no company is actually the same, one will find divergent factors which figure out the failure or success of applying an AIS in a company.

The evaluation of the costs wasn't huge in this case simply because they chose to file for bankruptcy. Additionally, when ALF got independence from Freightliner, they didn't understand just how to keep an eye on the brand-new systems since they were not aware of it (Bhagwani, 2009).

Employees weren't adequately trained. Businesses will occasionally take short cuts due to cost and time related with training employee might be pricey. This however can lead to the business not being in a position to reach its anticipated bottom-line (Iskandar, 2015). Lack of workforce training may also lead to staff members having to question other personnel that are experts in utilizing the systems for assistance thereby decreasing efficiency of coworkers as well as enhancing costs for the company.
Bad system planning is yet another contributory element. Management at times could have impractical expectations and goals from the AIS or maybe the product might be way too complicated to understand which could lead to the system failure. Therefore, the management must set practical and achievable expectations and goals. Management must make a feasibility evaluation and deal with 5 key aspects (legal, technical, scheduling, economic, as well as operational feasibility) (Iskandar, 2015).

Lack of enough comprehensive system testing is actually the other key component that contributed to the AIS failure in this case. Inadequate system testing can be quite expensive for an enterprise. Testing ought to be done to learn and do away with issues in the development phase, as prematurely as possible (Iskandar, 2015). To decrease this threat firms must use debugging methods to be capable of learning and eliminating problems. Businesses must also test the system by using testing techniques like; processing test information, walk through along with acceptance tests.

The primary risk was the point that the AIS wasn't prepared properly. All through the contract period, Freightliner didn't effectively record inventory and info was lost during this time. After the separation took place, the change from one accounting system to ALF's novel ERP system led to system collapse by losing data which cost the firm nearly one hundred million dollars (Bhagwani, 2009).

Since ALF's inventory wasn't being tracked properly and there were several instances where accounts didn't balance, there was no "red flag" to suggest that errors have occurred in the AIS. ALF's system was created to let them both input and output data related to inventory. Nevertheless, after the change in systems took place from Freightliner to ALF, inventory along with other significant data pertaining to the business had been lost and became unrecoverable (Bhagwani, 2009). Because this data had been unrecoverable, a number of orders as well as details had been lost and the firm was unable to deliver and satisfy the customer needs, which is the real reason why they faced bankruptcy.

Responsibility
The ALF management team had the duty of making sure that the AIS that's implemented worked properly and was capable to meet its goals together with the organizational objectives and goals. The profitable execution of an accounting info system is thought to be led by a task manager in order to dedicate time, budget, along with strategizing for the workflow and process. The staff members must additionally be properly trained before the transformation is actually made to the new AIS. The project staff must take sufficient time to ensure that they pick an alternative AIS after going through extensive training and technical support.

Managers may have helped reduce the danger of behavioral issues by electing a task manager who could help rally, boost employee 's moral and encourage the entire workforce to support as well as cooperate with the systems deployment. The manager must involve anyone that's influenced by the transformation to the brand-new system. Management must let staff members offer suggestions and assistance in the decision-making process. Management requires to make employees aware which feedbacks will be utilized and which won't be used and reasons for the same. When they do this, employees start to be more skillful, better trained, as well as, a lot more dedicated to making use of the novel system. Thirdly management must properly communicate with everyone who's going to be impacted by the system change. The worker must be advised of the changes which are likely to be made as well as the advantages the changes can provide to them. Top Management must help ease employee concerns and stress by dealing with the fears and also give confidence that job losses as well as responsibility-transfer won't take place. Management must also reassure workers that they are going to be correctly trained on how they can make use of the AIS.

The sizable failure to the AIS system took place in design stage. This is really because the business requirements might have been taken into consideration when developing the accounting system. The business might have averted the failed system results in the design phase by sticking with the subsequent business needs that should have been resolved by the AIS. The business requirements comprise of the following:
• Offer an accounting system which might satisfy the rising business demands
• A method which might effectively monitor and stand for the financial operations
• Transform the current semi manual system into computerized and automatic system
• Carryout double-checks over the transactions

The AIS development ought to have been recommended by top management as they're in the best position to create the AIS where initial assessments, system analyses, feasibility reviews, data needs as well as system-requirements assessments are carried out. This will make it possible to better recognize user requirements and be utilized to product a system analysis survey to offer to the AIS design-team for both review and development (Steinbart and Romney, 2012).

Subsequently, it would have gone through a conceptual design procedure to be able to determine and evaluate alternatives. Here, design specifications would have been created, and conceptual design needs provided for. When all this data would have been collected, it would have been given it to the systems design and development team.

The succeeding phase would be the actual physical output where all of the framed outputs, including database are actually produced. Immediately after this particular procedure, the outcome of the actual physical system design would have been handed to the data system committee for execution and transfer phase; and in this phase, all the software and hardware would have been installed; and all the workers affected by the brand-new system trained; and the novel AIS adequately tested and documented (Steinbart and Romney, 2012). Immediately after this particular phase, an ultimate report would have been provided to the info steering committee.

Lastly, the AIS would have been altered to make it totally free of virtually any bugs; and regularly reviewed to ensure that the product is fulfilling all the demands of the organization. The AIS would additionally be modified as structural and organizational designs change (Steinbart and Romney, 2012).

AIS happens to include six primary components. When the system is initially executed or even converted from a current system, organizations often make the error of not looking at all of these 6 parts and managing them likewise in the implementation process. Many organizations, even bigger ones, employ outside consultants who are aware of the organization needs and who then work to assist the company select and execute the perfect configuration, keeping all 6 elements in mind (Gelinas, Dull and Wheeler, 2011).

The steps required to successfully apply an AIS are as follows
Comprehensive Requirements Analysis
All of the staff members active in the process are interviewed. By doing this, the present AIS is understood completely, together with problems, and a comprehensive documentation of the product is carried out (reports, transactions, as well as questions that have to be answered are collected). Moreover, what the users need to increase efficiency and is absent in the current AIS is both outlined as well as recorded. Everyone is included in this survey, from top management to data entry operators (Reifer, 2006). The needs analysis not just gives the developer with the particular needs, what's more, it helps users agree to the change. It is noteworthy that users that ask questions as well as offer input are a lot more positive and receptive to this change, than those that take it easy and do not express concerns.
Systems Design (synthesis)
The needs analysis is comprehensively reviewed as well as a brand-new system is produced. The system which surrounds the AIS is usually the most crucial. What data requires to get into the system and how's this likely to be managed? What kind of data has to emerge from the AIS, and how's it going to be formatted? In case, the output is known, then what has to be placed into the system is likewise known, as well as the system selected will have to properly handle the procedures including documentation of all the vendors (Gelinas et al., 2011).
Documentation
When the system is actually being designed, it must be documented. Vendor documentation of the system and procedures, comprehensive instructions which help users manage each business procedure specific to the business are included by the documentation. Procedures and documentations should actually be online and this is beneficial in case organizations are able to enhance the user manuals offered by the program vendor (Peppard and Ward, 2016). Procedures and documentation have a tendency to be an afterthought, although they are a tool that can be used during training and testing, just before launch. The documentation is actually tested throughout the training period to ensure that once the system is actually launched, there's no question that it really works and that the users are comfortable working with it.
Testing
Before launch, all procedures are actually tested from start to finish, making use of the documentation as being a tool to make sure all procedures are documented and workers can very easily follow procedures so they know it really works and that the processes will likely be used uniformly by all workers. The generated reports are subsequently reviewed as well as verified, to make certain it is not really a garbage-in-garbage-out system. This's all completed in a final assessment that is not yet loaded with real live information. The business processes and documentation might be altered all through these final tests (Peppard and Ward, 2016; Gelinas et al., 2011). Most identified transactions have to be tested during this step of the implantation. Online information and all other reports should be confirmed and tracked via "audit test" so management is actually sure that transactions are actually managed consistently and reliably.
Training
Before launch, all users have to be informed about all the necessary procedures. The procedures typically have to be updated all through training as workers illustrate their individual circumstances and needs and the system is subsequently modified with this new data (Gelinas et al., 2011).
Data Conversion
Tools are actually put together to turn the information from the present system (which were recorded in the needs analysis phase) to the brand new AIS. The information is charted from one system to the another and data records are made which can be used with the newly designed tools. The conversion is adequately tested and verified just before final conversion (Peppard and Ward, 2016). Naturally, there is a backup to ensure that it may be restarted, in case needed.
Launch
The product is actually implemented only after each of the above phases are actually finished. Entire workforce is actually conscious of the date of launch. Quite often, the existing system is maintained and sometimes operated in "parallel" until the brand-new system is in total operation and thought to be operating accurately and precisely (Peppard and Ward, 2016). The "parallel" run which is necessary with software tailor-made to a business is usually not carried out by most firms.
Tools
Online resources are actually offered to support the strategic planning process involved with AIS. For instance, financial data forms help in deciding the particular requirements of each business, and also assign responsibility to the principles who are involved.
Support
The end users and top management ought to have support available throughout the execution and testing phase. System upgrades are adequately monitored and recorded in an effective manner along with training of both end users and top management.