MP121 Accounting Information Systems - Free Samples to Students

s an organization which has had an accounting information system before, but because of the expansion of the firm, the system has proved inadequate to meet the developing needs of the firm as Mr. Alex, the firm CEO explains (Bolden, 2016). For that matter, Mr. Alex who represents the firm management team will have several roles in the development and design of a new accounting system.

Among the roles which Mr. Alex will play is the identification of the faults in the current system which must be avoided in the new accounting system under development. As the CEO of the firm Alex must be in deep understanding of the faults or rather the parts of the current accounting system which are making it inadequate to meet the needs of the business (Kerzner & Kerzner, 2017). Explaining and advising the new system development team will help it avoid repeating the same faults in the new system. Also, considering the fact that the management team is among the few departments within any firm which is greatly exposed to the organization systems after the IT department team, it is expected that the CEO has a proper understanding of the current accounting system and can easily advise the development team on the areas which have had issues in the system so that they can be given more attention.

The CEO and the management team are also the strategic planners of the organization and can easily perceive where the organization accounting system should be developed with flexibility to curb the problem of inadequacy in meeting the developing needs of the firm as being faced by the current system. Advising the development team in that direction will enable it to strategize on how to take care of that and come up with a flexible accounting system which will be able to stand the test of time even when the business expands further in future (Oinas-Kukkonen & Harjumaa, 2018).

Question 2: Would you expect that the people who will use the new system should have a role in any analysis leading up to, in the selection of an implementation of the new accounting information system should one be selected?

In regard to the users of the new system, I expect them to play a major role in the design and the analysis of the new system before implementation. This is because their involvement in the development will be a vital mechanism in enhancing the system quality and ensuring its successful implementation. In the current competed and fluctuating market situations, innovations from user needs have proved to be an effective way of supporting market success. So, involving the users in the system development cycle will allow the gathering of more information details which could be helpful to the developers (Bano & Zowghi, 2015).).

In the initial stages of system development, system developers have to observe the prevailing problems in the system and identify all the requirements which will make the new system overwhelming. With that in mind, it is also common knowledge that except for the developers who might have an experience with the organization system currently in place, other developers may not be familiar with the system; they, therefore, lack a thorough understanding of the system environment, and for them to understand the system, the best way will be communication with end-users of the system (Brhel, Meth, Maedche & Werder, 2015). Research has indicated that system users are the top experts of the system and so for a thorough understanding of the system requirements, effective communication with them should be given the first priority during the definition process. It is therefore incredible to involve them during the process. System developers must select them carefully in order to obtain the most valuable information.

User involvement will also offer more reliable approaches to organizing features like dialog boxes and menus based on user data. Comparing the system development methodology which seldom considers user working habits with the current systems which are developed in a user-oriented approach, the developer-oriented ones always pose challenges to the end-users trying to manipulate them. Their involvement further eliminates the clash between them and the developers which makes the development phase easy and fast (Salah, Paige & Cairns, 2014).

Question 3: Write a clear and comprehensive report on what would be involved in the adoption of a life-cycle approach to adopting a new accounting information system. Specifically, identify the stages that would need to be engaged in, and staff likely to be involved.

In the adoption of a new system in an organization, a systematic procedure is necessary considering the fact that the employees may not be conversant with the functionality of the new system. Mainly, the adoption of new systems into an organization setting follow five stages, which are creating system awareness, system interest, carrying system evaluation, system testing and then system adoption. Although many organizations tend to relax after the development phase of a system, it is equally important to create a procedure that walks the users of the system through the adoption process (Lin, 2014).

Creating System Awareness

This is the first stage in the adoption process and which entails creating awareness to the organization staff about the new system.  It is very important that the company comes up with a favorable avenue to gather all the staff members together to brief them of the system (Rajan & Baral, 2015). This can be achieved through an audio-visual presentation by one of the development team members with a deep understanding of the system and also excellent presentation skills. The presenter is supposed to utilize creativity and wit in a greater way in order to engage the users fully in this stage.

Creating System Interest

In this stage, the system developers will guide the users through the interest stage which will entail providing them with easily accessible usage information about the system. Among the main methods utilized in the current business environment involves demonstrating to the users the advantages which will be realized through the adoption of the system so that the users can have a positive attitude towards it.

Carrying Out System Evaluation

After the guidance by the system developers, the staff members are allowed to interact with the system and examine it. At this stage, each staff member is first allowed to navigate through the system in order to identify any challenges while performing his or her duties (Rosenkilde et al., 2015). This process makes the users clarify all their doubts with the system developers hence intensifying the need to having the system within the organization. It is also in this platform that the users get a chance to be explained some of the new features which may be available in the new system but lacking in the former.

Carrying Out System Testing

This is the stage the staff members will be allowed to interact with the new accounting information system on their own while performing their distinct duties although being monitored centrally by the IT team. Apart from being gauged on whether they are able to use the system effectively, it is also the stage where the system is monitored as to whether it outputs the right results or whether it is operating as expected.

System Adoption

This is the final stage in the adoption process where staff members are now fully equipped and are exposed to use the new accounting system to carry out their distinct duties. There is, however, an open platform where any problem faced in the process can be directed to the organization’s IT department for assistance. It is the stage which takes some time before it can be assumed that all the staff members are fully equipped to carry out their duties with minimal errors.

Part 2:

 Weaknesses in Luxurious Firm Existing Expenditure Cycle Procedures (Elías-Maxil,  van der Hoek, Hofman & Rietveld, 2014)

Weakness/Problem	Applicable Control
Purchasing requests are reviewed and approved after the submissions. The ordering of unnecessary items can easily be carried out.	Purchase requisitions must be reviewed and approved from original department manager before being processed.
Periodic physical counting of inventories has not been mentioned. Therefore, a perpetual record of inventories is likely to be inaccurate over time and will be hard to detect.	Physical counting of inventories should be conducted regularly. Discrepancies having perpetual records of inventories records should be investigated promptly.
Receiving department employees is expected to unload deliveries even before verifying whether all the purchased orders have been approved. This turns into time wastage when unloading and contacting suppliers to return all unordered items.	Creation of policies which demand that receiving department employee to be verifying the validity of purchased orders before accommodating delivery. Publishing and enforcing sanctions for policy violations. Scheduling additional assistance during the busy periods.
Receiving department employees informing about discrepancies purchasing between the quantities received and ordered exceeding 5%. There is a likelihood of failure during the busy periods which also results in the failure of resolving problems in time.	Configuring the systems to compare all the received quantities to the ordered ones. The system is supposed to send all discrepancies above the tolerable deviation to the purchasing manager directly.
All the accounts which are under payable clerks are likely to create one-time records of supplier without reviewing and approving payments to the suppliers. This opens a chance of fraudulent disbursements.	Systems should be set to print the entire list of one-time suppliers.   The management should also review the list regularly. All the payable accounts must not be allowed to create new records of suppliers – that should be done by the purchasing manager only.

Part 3:

Five Examples of Improper Segregation of Duties (Ballesteros,Batten, Pan & Li, 2015)

Employee A ordering the inventory and maintaining supplier master – altering the supplier master in order to order from the unapproved suppliers.

Employee C is maintaining supplier master files and approving invoices- can easily submit and approve the payments to fabricated vendors.

Employee D maintaining supplier master and approving invoices – could easily submit and approve some invoices from fictional suppliers.

Employee D is approving invoices and making EFT payments – can approve the disbursal of money to himself.

Employee G is approving invoices and mail checks – through the custody of the signed checks, he or she can easily alter them (Marshall & Steinbart, 2017). 

References

Ballesteros, S., Batten, L., Pan, L., & Li, G. (2015). Segregation-of-duties conflicts in the insider threat landscape.

Bolden, R. (2016). Leadership, management, and organizational development. In Gower handbook of leadership and management development (pp. 143-158). Routledge.

Bano, M., & Zowghi, D. (2015). A systematic review of the relationship between user involvement and system success. Information and Software Technology, 58, 148-169.

Brhel, M., Meth, H., Maedche, A., & Werder, K. (2015). Exploring principles of user-centered agile software development: A literature review. Information and Software Technology, 61, 163-181.

Elías-Maxil, J. A., van der Hoek, J. P., Hofman, J., & Rietveld, L. (2014). Energy in the urban water cycle: Actions to reduce the total expenditure of fossil fuels with emphasis on heat reclamation from the urban water. Renewable and Sustainable Energy Reviews, 30, 808- 820.

Kerzner, H., & Kerzner, H. R. (2017). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.

Lin, H. F. (2014). Understanding the determinants of electronic supply chain management system adoption: Using the technology–organization–environment framework. Technological Forecasting and Social Change, 86, 80-92.

Marshall, B. R., & Steinbart, P. J. (2017). ACCOUNTING INFORMATION SYSTEMS. PEARSON EDUCATION LIMITED.

Oinas-Kukkonen, H., & Harjumaa, M. (2018). Persuasive systems design: key issues, process model and system features. In Routledge Handbook of Policy Design (pp. 105-123). Routledge.

Rajan, C. A., & Baral, R. (2015). Adoption of ERP system: An empirical study of factors influencing the usage of ERP and its impact on the end user. IIMB Management Review, 27(2), 105-117.

Rosenkilde, M., Morville, T., Andersen, P. R., Kjær, K., Rasmusen, H., Holst, J. J., ... & Helge, J. W. (2015). Inability to match energy intake with energy expenditure at sustained near- maximal rates of energy expenditure in older men during a 14-d cycling expedition. The American journal of clinical nutrition, 102(6), 1398-1405.

Salah, D., Paige, R. F., & Cairns, P. (2014, May). A systematic literature review for agile development processes and user-centered design integration. In Proceedings of the 18th international conference on evaluation and assessment in software engineering (p. 5). ACM.