Case Study Plaskor Inc.Accounting Information Systems Internal

Plaskor Inc.Accounting Information Systems Internal Controls and Risks in IT Systems - Case Study Example Thus, Plaskor Inc. has underscored implementation of this strategy in carrying out manufacturing of automotive parts since it needs to trade with other partners. a) This section of the paper seeks to describe the extra IT system risks that Plaskor should consider as it evaluates whether to buy or develop an Internet EDI system. According to Segev, Porrar, and Roldan (n.d.), the main risk that can be faced by Plaskor is related to the aspect of security. Whether to buy or develop the system, there are certain risks that are likely to be faced. For instance, the system can be intruded by hackers who are bent on stealing business information belonging to other organizations. The security risk is more threatening to the viability of business since this can impact its operations. The system is also likely to be infiltrated by spyware which can affect the operations of the company. The company can lose vital information as a result of spyware that can be picked from the Internet. Therefore, there is a need to build strong firewalls in order to protect data from being stolen by other unscrupulous people. Plaskor can choose to develop the EDI system, which implies that it should also develop translators which can code the data so that it can be exchanged smoothly between two different companies. However, the risk likely to be encountered is that the translators may not be compatible with transmission and security systems and back end systems that ultimately process EDI instructions (Segev, Porrar, & Roldan, n.d.). This may affect the seamless flow of information, hence the need to put concerted efforts in order to ensure that the translators are compatible with the internal systems of the company. Failure to do so may impact the smooth flow of information between linked computers. b) This section of the paper seeks to describe IT internal controls that should be incorporated into an Internet EDI system. Systematic scheduling has to be put in