This paper concentrates on the primary theme of Accounting Flow Work : Supplemental Guidelines for Preparing System Flowcharts in which you have to explain and evaluate its intricate aspects in detail. In addition to this, this paper has been reviewed and purchased by most of the students hence; it has been rated 4.8 points on the scale of 5 points. Besides, the price of this paper starts from £ 40. For more details and full access to the paper, please refer to the site.
Accounting Flow Work
Supplemental Guidelines for Preparing System Flowcharts
- Frequently the same person or the same machine performs a sequence of elementary operations. If these operations are performed with the same set of inputs and outputs, they can be consolidated into one operation and represented by a single symbol (i.e., Match and post; match and approve.)
- Flow lines should not cross each other.
- The decision symbol (diamond) is a program flowcharting symbol and should NOT be used in a system flowchart.
- Use an arrow head to positively identify the direction of an information flow. When an off-line or on-line file is used in an operation:
- An arrow head directed to the operation means RETRIEVAL or query of information.
- An arrow head directed to the file means ADDING information to the file.
- UPDATING a file requires an arrow head in each direction.
- When an operation involves retrieving information from or updating the record of an off-line file, a document symbol between the off-line file and the operation should NOT be shown.
- When a document is taken out of an off-line file and used in succeeding operations, it should be shown between the off-line file and the operation where the document is taken out.
- When a new document is filed in an off-line file, it should be indicated between the off-line file and the operation.
- All input documents used in any operation must be traced to the locations where they are finally disposed. There are three main ways to dispose documents:
- To send them to other systems or subsystems.
- To send them to other parts of the flowchart.
- To file them in off-line files. In the last case, show how long the files are kept unless they are master files kept semi-permanently.
- Avoid the occurrence of loops whenever possible. A loop violates the sequential nature of a system flowchart. If it cannot be avoided then use a broken line.
- Depicting sorting operations. When a sorting operation separates documents into groups according to a certain rule, all groups created should be clearly identified and shown on separate flow lines.
EXAMPLE PROVIDED IN CLASS: