ACCT 531 Week 1 Case Study Example

One Database, Fewer Reconciliations, New Risks: A Case Study of a Medical Supply Distributor's Move to an Enterprise System

Case Background

Cascade Medical Supply distributes surgical and patient-care products to 900 clinics in three states. Until this year it ran separate systems for order entry, warehouse management, purchasing and the general ledger, connected by nightly file transfers and a monthly reconciliation that took the accounting team six days. Customer records existed in two versions, one in order entry and one in the ledger, and prices were maintained separately by sales and by purchasing. Managers wanted a single view of inventory and margins, and the auditors had noted recurring differences between the subledgers and the general ledger. It is replacing all four with a single enterprise resource planning system, with 140 users across sales, warehouse, purchasing and accounting.

What Integration Changes

Gelinas et al. (2015) describe enterprise systems as integrated, process-oriented systems built on a shared database, so that a sale entered once updates inventory, receivables and the ledger at the same time. For Cascade, that means the nightly transfers and much of the monthly reconciliation disappear, because the sales and ledger records can no longer disagree. It also means that an error entered once spreads everywhere at once. A wrong price in the item master now flows instantly to invoices, margins and the financial statements, with no nightly batch to pause it. Integration removes the reconciliations that used to catch errors, so prevention has to do the work detection once did.

Risks and Controls

Three risks rise in the move. First, access: 140 users will share one system, and broad roles copied from the old systems could let a buyer both create vendors and approve payments. Cascade should design roles around its processes and review conflicts before go-live. Second, conversion: customer, vendor and price records moved from four systems may be incomplete or duplicated, so the conversion team should reconcile record counts and balances between old and new systems and have the business owners sign off. Third, process redesign: controls that lived in the old workflow, such as a purchasing manager's paper approval of large orders, may not be rebuilt in the new one. In their review of ERP research, Grabski et al. (2011) describe these systems as the largest and most complex that most firms ever implement, with a transforming effect on accounting, which is why the control design deserves as much attention as the technical cutover. Each of the three controls can be tested before go-live, which gives management evidence that the new system starts clean. The payoff is real: Morris (2011) found that firms which had completed ERP implementations disclosed fewer SOX 404 material weaknesses than comparable firms without such systems, a result that depends on the controls being designed in rather than left to chance.

Conclusion

Cascade should address access first, since role conflicts persist long after go-live, then conversion, which must be complete before the old systems are retired, and finally a review of redesigned processes to confirm that each old control has a new one. A short control map, listing each old control and its replacement, would give management and the auditors a single document to work from during the first year on the new system.

References

Gelinas, U. J., Dull, R. B., Wheeler, P. R., & Hill, M. C. (2015). Accounting information systems (10th ed.). Cengage Learning.

Grabski, S. V., Leech, S. A., & Schmidt, P. J. (2011). A review of ERP research: A future agenda for accounting information systems. Journal of Information Systems, 25(1), 37-78. https://doi.org/10.2308/jis.2011.25.1.37

Morris, J. J. (2011). The impact of enterprise resource planning (ERP) systems on the effectiveness of internal controls over financial reporting. Journal of Information Systems, 25(1), 129-157. https://doi.org/10.2308/jis.2011.25.1.129