PROBLEM ANALYSIS FINAL PROJECT: IMPLEMENTATION
             The following paper discusses a problem with paying duplicate invoices within Shell and an evaluation of three possible alternative solutions. Also included is a plan for implementation of the best of the three alternative solutions. An evaluation of the effectiveness of the chosen solution, once it has been implemented, is also included.
             Problem Analysis: Implementation and Evaluation Plan
             Most companies today are in a cost cutting mode, so the last thing they want to see is duplicate payment of invoices. Even if the number of duplicate payments is not very high, a few that have a high dollar amount can be a real problem. Adequate controls, preventative measures, training, and critical thinking by the people working with the payments are needed to absolutely minimize the risk.
             Shell Exploration and Production Company converted to their SAP R/3 system back in 1998. As a result, the accounting processes and procedures changed significantly from their previous legacy system. The accounts Payable Departments in Houston, New Orleans and a few other locations are responsible for the payment of all Shell Exploration and Production invoices.
             SAP has a built in mechanism that produces a warning message if a duplicate payment for the same invoice is mad. This means that when you attempt to pay an invoice and you keypunch the vendor number, invoice number, invoice date and invoice amount, SAP looks at that data and compares it to data from previously paid invoices. If the system finds a match on all four of the items: the vendor number, invoice number, invoice date and invoice amount, it will give you a warning message. The invoice processor can override the warning message by pressing the enter key. The invoice processor is responsible for making a judgment of what action to take when that message comes up during his or her attempt to pay an invoice. Some...