1. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 138 DOCUMENT FLOWCHARTS A document flowchart shows the flow of documents and information among areas of responsibility in an organization. These flowcharts trace a document from cradle to grave and show: –Where a document comes from –Where it’s distributed –How it’s used –It’s ultimate disposition –Everything that happens as it flows through the system

2. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart2 of 138 DOCUMENT FLOWCHARTS Internal control flowcharts are document flowcharts used to evaluate the adequacy of internal controls, such as segregation of duties or internal checks. They can reveal weaknesses or inefficiences such as: –Inadequate communication flows –Unnecessarily complex document flows –Procedures that cause wasteful delays Document flowcharts are also prepared in the system design process.

3. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart3 of 138 This is part of the document flowchart from Figure 3-9 in your textbook.

4. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart4 of 138 GUIDELINES FOR PREPARING FLOWCHARTS Let’s step through some guidelines for preparing flowcharts: –As with DFDs, you can’t effectively prepare a flowchart if you don’t understand the system, so: Interview users, developers, auditors, and management. Administer questionnaires. Read through narratives. Walk through systems transactions

5. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart5 of 138 GUIDELINES FOR PREPARING FLOWCHARTS –Identify: Entities to be flowcharted, e.g., departments, functions, external parties (the parties who “do” things in the story) Documents or information flows Processes –As you read through a narrative, you may want to mark the preceding items with different shapes (e.g., drawing a rectangle around entities, circling documents, etc.).

6. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart6 of 138 GUIDELINES FOR PREPARING FLOWCHARTS –Use separate columns for the activity of each entity. Example: If there are three different departments or functions that “do” things in the narrative, there would be three columns on the flowchart.

7. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart7 of 138 What are the entities in this flowchart?

8. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart8 of 138 GUIDELINES FOR PREPARING FLOWCHARTS –Flowchart the normal course of operations, and identify exceptions with annotations. –As much as possible, the flow should go from top to bottom and left to right. –Use standard flowcharting symbols, and draw with a template or computer. –Clearly label all symbols. Use annotations if necessary to provide adequate explanation.

9. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart9 of 138 GUIDELINES FOR PREPARING FLOWCHARTS –Give the flowchart a clear beginning and ending. Show where each document originated and its final disposition. –One approach you can use is to read through the narrative and for each step define: What was (were) the input(s) What process was carried out What was (were) the output(s) –Note on the next slide that the flow sequence is input -- process – output.

10. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart10 of 138 Identifies where input is coming from

11. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart11 of 138 Inputs

12. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart12 of 138 Process

13. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart13 of 138 Output to storage

14. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart14 of 138 Input for next process

15. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart15 of 138 Process

16. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart16 of 138 Output

17. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart17 of 138 GUIDELINES FOR PREPARING FLOWCHARTS –Every manual process should have at least one input and at least one output. –Show all data entered into or retrieved from a computer file as passing through a process first. –Do not show process symbols for: Forwarding a document to another entity Filing a document

18. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart18 of 138 Forwarding a document

19. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart19 of 138 Filing a document

20. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart20 of 138 GUIDELINES FOR PREPARING FLOWCHARTS –Do not connect two documents except when forwarding to another column. When a document is forwarded, show it in both locations.

21. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart21 of 138 Show forwarded document in both locations

22. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart22 of 138 GUIDELINES FOR PREPARING FLOWCHARTS –When using multiple copies of a document, place document numbers in the upper, right-hand corner.

23. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart23 of 138 What happens to the document numbers as the documents move to other locations?

24. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart24 of 138 GUIDELINES FOR PREPARING FLOWCHARTS –Show on-page connectors and label them clearly to avoid excess flow lines.

25. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart25 of 138

26. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart26 of 138 GUIDELINES FOR PREPARING FLOWCHARTS –Use off-page connectors if the flow goes to another page.

27. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart27 of 138 Are there other off- page connectors on this flowchart?

28. © 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart28 of 138 GUIDELINES FOR PREPARING FLOWCHARTS –If a flowchart takes more than one page, label the pages as 1 of 5, 2 of 5, 3 of 5, etc. –Show documents or reports first in the column where they are created. –Start with a rough draft; then redesign to avoid clutter and crossed lines. –Verify the accuracy of your flowchart by reviewing it with users, etc. –Place the flowchart name, the date, and the preparer’s name on each page of the final copy.