Accounting Information Systems

Accounting Information Systems 3-1. The text provides seven reasons why documenting AISs is important: (1) depicting how the system works, (2) training users, (3) designing new systems, (4) controlling systems development costs, (5) standardizing communication with others, (6) auditing, and (7) controlling end-user support costs. Additional reasons include: (1) to help evaluate the performance of system personnel, (2) to help evaluate the adequacy or efficiency of an existing system, and (3) to provide design specifications to outside vendors who might be proposing new systems. Accountants are interested in system documentation for all these reasons. For example, inadequate documentation makes it difficult to use an integrated accounting package effectively, design one for others to use, or audit a system intelligently. Flowcharts and similar systems documentation are also important to auditors. These charts can help auditors spot internal control weaknesses that are not apparent from prototypes or not obvious wh en observing a system in use. 3-2. Document flowcharts are a type of system flowchart. Whereas system flowcharts are process-oriented, document flowcharts focus on the flow of physical documents through the processing system. Document and system flowcharts are similar in that they use similar symbols in their construction. A few additional symbols, such as envelopes and hand trucks to depict movement of goods, are more likely to appear in document flowcharts than system flowcharts. But system flowcharts contain more detail about processing logic. Accountants can use data flow diagrams (DFDs) to depict the physical flows of data through an AIS (like document flowcharts), or the logical flow of data through an AIS (like system flowcharts). Like document or system flowcharts, their main objective is to document data flows in an orderly, graphic, and easily-understood format. But DFDs use fewer symbols than either document or system flowcharts, and do not require columns (like document flowcharts). Program flowcharts are really the lowest level of system flowcharts because they outline the logic sequence for a particular application program. Thus, they are more used by programmers and system analysts than by accountants and auditors. Still, auditors will need to understand these program flowcharts when looking at program logic and program controls. Program flowcharts use many of the same symbols found in system flowcharts, but also use some special ones such as the decision symbol. 3-3. A document flowchart is a pictorial representation of the physical data flow through the various departments of a business. A document flowchart is used in designing or evaluating an accounting information system. 1. A systems analyst uses it when evaluating a system to see if each department is receiving the necessary data and that unnecessary data are not transferred. 2. A system designer uses it when there is interest in improving or replacing an existing system. 3. A computer p rogrammer can use a document flowchart when preparing system flowcharts. 4. An auditor uses it to help define, follow, and evaluate an audit trail. 5. An internal data security expert uses it to indicate weaknesses in internal control and data control. 3-4. Guidelines for creating document flowcharts, system flowcharts, and data flow diagrams are listed in the text. See relevant chapter sections for document flowcharts, system flowcharts, and data flow diagrams.