ACCT 332 Week 1 Discussion Board Forum 1 Example

Discussion Board Forum 1: Accounting Information Systems, Business Processes and Firm Value

ACCT 332 Accounting and Control, Discussion Board Forum 1

Thread by [Student Name]

The distributor and the three classmates are composites; the textbook, Scripture and the peer-reviewed sources cited are real.

A composite plumbing supply distributor with six branches runs three separate programs: one for customer orders, one for warehouse inventory and one for accounting. A single sale is entered three times, inventory counts disagree with the books every month and the controller spends the first week of each month reconciling the systems. The owners are considering an enterprise resource planning system that would share one database across all three functions.

Richardson et al. (2018) explain that an accounting information system adds value by providing information that improves decisions and by making business processes more efficient, and they connect the AIS to the value chain of primary activities, such as inbound logistics and sales, and support activities. For the distributor, an ERP would let a sale update inventory, receivables and the general ledger at once, cutting duplicate entry and giving branch managers current stock levels.

Research supports the idea that this value is real but not automatic. In Hitt et al. (2002), companies that put money into ERP outperformed nonadopters on productivity and were valued more highly by the market, although performance dipped briefly after implementation. Nicolaou (2004) compared 247 adopting firms with matched nonadopters and found that adopters showed higher differential performance only after two years of continued use, and that implementation choices such as the modules installed helped explain the results. An ERP system does not create value on the day it goes live; the value comes from the processes the company redesigns around it. For the distributor, that means budgeting for a learning period and redesigning order-to-cash procedures rather than copying old habits into new software.

Proverbs pictures a household raised through wisdom and furnished with treasures through knowledge (English Standard Version Bible, 2001/2016, Proverbs 24:3-4). A good AIS is built the same way, with an understanding of the business processes it serves. For the distributor, wisdom means studying how orders, stock and cash actually move through the six branches before buying anything, and knowledge means training the people who will fill the new system with data every day. Software bought in haste, without that groundwork, tends to reproduce the old confusion at greater cost.

Reply to Kendra

Kendra, you suggested that small firms can get most of the benefit of an ERP from cloud accounting software. I agree that cost matters, but Richardson et al. (2018) stress that value comes from integrating business processes, and a cloud ledger alone does not connect inventory and sales. For a distributor, the inventory link may be where most of the value lies. A cloud ERP built for small companies might give your bakery client the same integration without the cost of an on-premise system. The question I would ask the bakery is where its errors happen today. If most of them come from re-keying orders into the ledger, integration is worth paying for; if the ledger is the only pain point, a simple cloud package may be enough for now.

Reply to Marcus

Marcus, you wrote that an ERP system prevents fraud because every transaction is recorded automatically. Automation helps, but evidence suggests it does not remove judgment. Brazel and Dang (2008) found that after ERP implementations, firms showed larger discretionary accruals, a sign of greater earnings management, and more of it when they adopted more modules. Faster, more integrated data may make it easier, not harder, to manage the numbers near a deadline, so controls still need people who review them. I would add that an ERP also makes some fraud easier to detect, since every change leaves a log, but only if someone actually reviews the logs and the access rights behind them. Segregation of duties has to be designed into user roles.

Reply to Hope

Hope, your post on documenting business processes before choosing software is a point the distributor in my thread should take seriously. Nicolaou (2004) found that implementation characteristics, such as which modules a firm installed and why, helped explain whether ERP adopters outperformed. A company that has mapped its order-to-cash and purchasing processes first can choose those modules deliberately. Your flowchart of the purchase process would be a good starting point for deciding which steps to automate first. It would also show where approvals sit today, which matters because an ERP can route approvals electronically, and a map drawn before the change becomes the baseline for measuring whether the new process is actually faster.

References

Brazel, J. F., & Dang, L. (2008). The effect of ERP system implementations on the management of earnings and earnings release dates. Journal of Information Systems, 22(2), 1-21. https://doi.org/10.2308/jis.2008.22.2.1

English Standard Version Bible. (2016). Crossway. (Original work published 2001)

Hitt, L. M., Wu, D. J., & Zhou, X. (2002). Investment in enterprise resource planning: Business impact and productivity measures. Journal of Management Information Systems, 19(1), 71-98. https://doi.org/10.1080/07421222.2002.11045716

Nicolaou, A. I. (2004). Firm performance effects in relation to the implementation and use of enterprise resource planning systems. Journal of Information Systems, 18(2), 79-105. https://doi.org/10.2308/jis.2004.18.2.79

Richardson, V. J., Chang, C. J., & Smith, R. (2018). Accounting information systems (2nd ed.). McGraw-Hill Education.