Accounting Information Systems 12th

Accounting Information Systems 12th,
Marshall B. Romney, Paul J. Steinbart -
solutions manual
SAMPLE
THIS IS NOT THE ACTUAL BOOK.
Receive Solutions to Academic Problems within 24 hours!
We have ALL the solutions for every end-of-chapter exercise in the book.
The payment instruction is going to be sent to you by email and the solutions are going to be delivered
24 hours upon payment.
Prepare to receive your Test Bank and Solutions Manual in the next moment. Contact us at:
examstud12@hotmail.com
or visit
http://accountingsolutionsmanual.com/accounting-information-systems-12th-solutions-manual/
Send us a list of books you need.
Note:
Only Test Banks and Solutions Manuals are available (as an eletronic file). No text books.
Table of Contents
Part I: Conceptual Foundations of Accounting Information Systems
Chapter 1. Accounting Information Systems: An Overview
Chapter 2. Overview of Transaction Processing and Enterprise Resource Planning Systems
Chapter 3. Systems Documentation Techniques
Chapter 4. Relational Databases
Part II: Control and Audit of Accounting Information Systems
Chapter 5. Computer Fraud
Chapter 6. Computer Fraud and Abuse Techniques
Chapter 7. Control and Accounting Information Systems
Chapter 8. Information Systems Controls for System Reliability-Part 1: Information Security
Chapter 9. Information Systems Controls for System Reliability-Part 2: Confidentiality and Privacy

---

Chapter 10. Information Systems Controls for System Reliability-Part 3: Processing Integrity and
Availability
Chapter 11. Auditing Computer-Based Information Systems
Part III: Accounting Information Systems Applications
Chapter 12. The Revenue Cycle: Sales to Cash Collections
Chapter 13. The Expenditure Cycle: Purchasing to Cash Disbursements
Chapter 14. The Production Cycle
Chapter 15. The Human Resources Management and Payroll Cycle
Chapter 16. General Ledger and Reporting System
Part IV: The REA Data Model
Chapter 17. Database Design Using the REA Data Model
Chapter 18. Implementing an REA Data Model in a Relational Database
Chapter 19. Special Topics in REA Modeling
Part V: The Systems Development Process
Chapter 20. Introduction to Systems Development; Systems Analysis
Chapter 21. AIS Development Strategies
Chapter 22. Systems Design, Implementation, and Operation

SAMPLE START
Part of Chaper 2:
2.1 Table 2-1 lists some of the documents used in the revenue, expenditure, and human
resources cycle. What kinds of input or output documents or forms would you find in
the production (or conversion) cycle?

Students will not know the names of the documents but they should be able to identify
the tasks about which information needs to be gathered. Here are some of those tasks:

Requests for items to be produced
Documents to plan production
Schedule of items to be produced
List of items produced, including quantity and quality
Form to allocate costs to products

---

Form to collect time spent on production jobs
Form requesting raw materials for production process
Documents showing how much raw materials are on hand
Documents showing how much raw materials went into production
List of production processes
List of items needed to produce each product
Documents to control movement of goods from one location to another

2.2 With respect to the data processing cycle, explain the phrase "garbage in, garbage
out." How can you prevent this from happening?

When garbage, defined as errors, is allowed into a system that error is processed and the
resultant erroneous (garbage) data stored. The stored data at some point will become
output. Thus, the phrase garbage in, garbage out. Data errors are even more problematic
in ERP systems because the error can affect many more applications than an error in a
non-integrated database.

Companies go to great lengths to make sure that errors are not entered into a system. To
prevent data input errors:

Data captured on source documents and keyed into the system are edited by the
computer to detect and correct errors and critical data is sometimes double keyed.
Companies use turnaround documents to avoid the keying process.
Companies use source data automation devices to capture data electronically to avoid
manual data entry with its attendant errors.
Well-designed documents and screens improve accuracy and completeness by
providing instructions or prompts about what data to collect, grouping logically
related pieces of information close together, using check off boxes or pull-down
menus to present the available options, and using appropriate shading and borders to
clearly separate data items.
Data input screens are preformatted to list all the data the user needs to enter.
Prenumbered source documents are used or the system automatically assigns a
sequential number to each new transaction. This simplifies verifying that all
transactions have been recorded and that none of the documents has been misplaced.
The system is programmed to make sure company policies are followed, such as
approving or verifying a transaction. For example, the system can be programmed to

---

check a customer's credit limit and payment history, as well as inventory status,
before confirming a sale to a customer.

************************************************************************
And so on . . . +12 pages of chapter 2 are available; and similar for all other chapters.
Request all questions/answers for all chapters at:
examstud12@hotmail.com
or visit
http://accountingsolutionsmanual.com/accounting-information-systems-12th-solutions-manual/
Send us a list of all books you need.
Note:
Only Test Banks and Solutions Manuals are available (as an eletronic file). No text books.

---