| Course | ACC 315 Accounting Information Systems |
|---|---|
| Module | Module 2 |
| Paper type | undergraduate business process documentation with narrative, flowchart description and data flows |
| Length | About 1,000 words, 6 pages |
| Format | APA 7 student paper |
| School | Southern New Hampshire University |
| Program | BS Accounting |
| Updated | October 2026 |
Free sample paper for ACC 315 Module 2
Documenting the Revenue Cycle at a Composite Propane Distributor: Narrative, Flowchart and Data Flows
[Student Name]
Southern New Hampshire University
ACC 315: Accounting Information Systems
Module Two Assignment
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Documenting the Revenue Cycle at a Composite Propane Distributor: Narrative, Flowchart and Data Flows
Introduction
Documentation is how accountants and auditors see a process they did not design. Romney et al. (2021) describe three complementary tools: narratives, which explain a process in words; document flowcharts, which show who handles which documents; and data flow diagrams, which show how data moves among processes and stores regardless of who does the work. This assignment uses all three to document the revenue cycle at a composite propane and heating oil distributor in central Vermont with about 5,400 accounts, nine delivery trucks and a five-person office. The company uses a route software package on drivers' tablets and a separate accounting package in the office.
Process Narrative
The revenue cycle runs as follows.
1. Each morning the route software produces a delivery list of automatic-delivery customers whose tanks are estimated to be at or below 30 percent, based on degree days and each customer's usage factor. Will-call orders taken by phone are added by the dispatcher.
2. The dispatcher prints a route sheet for each driver and assigns trucks.
3. At each stop the driver fills the tank, reads the truck meter and writes the gallons, price code, tank percentage and any service notes on a three-part paper delivery ticket.
4. The driver leaves the white copy at the customer's door, keeps the yellow and pink copies and marks the stop complete on the tablet.
5. At day's end the driver drops yellow copies in the billing tray and keeps pink copies in the truck book.
6. The next morning, a billing clerk sorts the yellow copies by route and keys each ticket into the accounting package, selecting the customer and typing the gallons and price code.
7. The accounting package prices the delivery, creates an invoice and posts it to the customer's account, debiting accounts receivable and crediting propane revenue.
8. The clerk files the yellow copies by date.
9. Invoices for customers not on a budget plan are printed and mailed weekly; budget plan customers receive a monthly statement showing their fixed payment and balance.
10. Payments arrive by mail, by phone card payment and through the bank's online bill pay.
11. The second billing clerk opens the mail, lists checks on a remittance log and posts payments to customer accounts.
12. The same clerk prepares the deposit slip and takes checks to the bank.
13. Card payments taken by phone are entered in the card terminal and posted by the same clerk.
14. At month end the controller reviews the aged receivables report and a revenue report by product, and compares gallons sold with gallons purchased.
Document Flowchart
The document flowchart uses four columns, one for each area of responsibility. Table 1 describes its elements in order so that a reader can follow it without the drawing.
Table 1. Document Flowchart Elements by Column
| Column | Symbol | Element | Flow |
|---|---|---|---|
| Dispatch | Computer process | Route software generates delivery list | To route sheet |
| Dispatch | Document | Route sheet, printed | To driver |
| Driver | Manual operation | Fill tank, read meter, write ticket | Creates three-part ticket |
| Driver | Document, three parts | Delivery ticket | White to customer; yellow to billing; pink to truck file |
| Driver | Offline file | Truck book of pink copies, by date | Kept in truck |
| Billing | Manual input | Clerk keys ticket | To accounting package |
| Billing | Computer process | Price, create invoice, post receivable | To customer master and sales files |
| Billing | Offline file | Yellow copies, filed by date | Kept in office |
| Billing | Document | Invoice or monthly statement | To customer |
| Cash receipts | Manual operation | Open mail, list checks | Creates remittance log |
| Cash receipts | Computer process | Post payments | To customer master file |
| Cash receipts | Document | Deposit slip with checks | To bank |
| Controller | Document | Aged receivables and revenue reports | Reviewed monthly |
Data Flow Diagram
The level-zero data flow diagram ignores who performs each step and shows only how data moves. Hall (2019) stresses that a data flow diagram shows logical processes, so a clerk and a computer program performing the same function appear as one process.
Table 2. Level-Zero Data Flow Diagram Elements
| Element type | Name | Data in | Data out |
|---|---|---|---|
| External entity | Customer | Invoice, statement | Order, payment |
| External entity | Bank | Deposit | Bank statement |
| Process 1.0 | Schedule deliveries | Customer usage data, orders | Delivery list |
| Process 2.0 | Record deliveries | Delivery list, meter readings | Delivery data |
| Process 3.0 | Bill customers | Delivery data, prices | Invoices, receivable entries |
| Process 4.0 | Collect cash | Payments | Payment records, deposit |
| Data store D1 | Customer and tank file | Usage factors, addresses | To processes 1.0 and 3.0 |
| Data store D2 | Sales and receivables file | Invoices, payments | To reports |
| Data store D3 | Price file | Price codes | To process 3.0 |
Weaknesses Found While Documenting
Documenting the process revealed four weaknesses that the control analysis in the next module will address. First, at steps 3 and 6, gallons are written by hand and retyped, so a misread digit becomes a billing error with no check. Second, nothing compares the meter totals in the pink copies with gallons billed from the yellow copies, so a ticket that never reaches billing, whether lost or diverted, would go unnoticed. Third, at steps 11 through 13, one clerk opens the mail, posts payments and makes the deposit, and the same clerk can issue account credits, a combination that would allow cash to be taken and hidden with a credit. Fourth, at step 6, price codes are typed rather than pulled from the customer file, so a customer could be billed at a lower commercial price. Doyle et al. (2007) found that material weaknesses in internal control are more common in smaller and more complex firms with fewer resources for control, which describes a five-person office well.
Conclusion
The revenue cycle at this distributor works, but it depends on paper and memory at the two points where value changes hands: the meter and the mail. Documenting it in three forms made those points visible. The flowchart shows where documents go; the data flow diagram shows that delivery data is stored in two places that never meet. The next module will design controls for the four weaknesses identified here.
References
Doyle, J., Ge, W., & McVay, S. (2007). Determinants of weaknesses in internal control over financial reporting. Journal of Accounting and Economics, 44(1-2), 193-223. https://doi.org/10.1016/j.jacceco.2006.10.003
Hall, J. A. (2019). Accounting information systems (10th ed.). Cengage Learning.
Romney, M. B., Steinbart, P. J., Summers, S. L., & Wood, D. A. (2021). Accounting information systems (15th ed.). Pearson.
What the ACC 315 Module 2 instructions ask for
The Module Two assignment in ACC 315 usually asks you to document a business process, most often the revenue or expenditure cycle, for a company described in a case or one you know. Expect to prepare a narrative that describes each step, who performs it and which documents and files are used, then a flowchart and, in many versions, a data flow diagram. Follow standard symbols and conventions and keep physical flows, such as documents moving between people, separate from logical flows of data. Many prompts also ask you to identify weaknesses you notice while documenting. Submit the diagrams in the required format and include a short written explanation that a reader could follow without the diagram.
How this ACC 315 Module 2 business process documentation assignment example is built
This sample documents the revenue cycle of a propane distributor serving about 5,400 accounts. A fourteen-step narrative runs from the route software's automatic delivery list through the driver's paper ticket, billing, invoice mailing, budget plan payments and the deposit. A document flowchart is described in a table with four columns, dispatch, driver, billing and cash receipts, naming each symbol and flow. A data flow table identifies the external entities, processes and data stores at level zero. A final section flags four weaknesses found while documenting: illegible tickets, no reconciliation of gallons pumped to gallons billed, one clerk handling both checks and customer credits, and price codes typed by hand.
Where the ACC 315 Module 2 rubric puts the points
Rubrics for the ACC 315 documentation assignment typically award points for a complete and accurate narrative, correct use of flowchart conventions, a correct data flow diagram where required and identification of weaknesses, with a row for writing and format. Top papers make every step traceable from the narrative to the diagram, use standard symbols consistently and keep the flowchart's physical view and the data flow diagram's logical view distinct. Graders look for every document's origin and destination, including where copies are filed. Missing steps, unlabeled flows and mixing processes with data stores are the most common deductions. Weaknesses that are specific, tied to a step, earn more than general ones.
ACC 315 Module 2 help: the mistakes that cost points
Students lose points in this assignment by skipping steps that seem obvious, such as who opens the mail or where a copy of the invoice goes, by drawing a data flow diagram that shows people and documents instead of processes and data, and by leaving the flowchart unexplained. Another common problem is mixing levels, showing detail in a context diagram. If your case is the expenditure or payroll cycle, or a service business, send it and the documentation will follow that process. Write the narrative first and number the steps; then make sure every numbered step appears on the flowchart. That single cross-check catches most of the errors graders find.
Get ACC 315 Module 2 written to your instructions
Send the ACC 315 Module 2 instructions and your case. The paper will document the process as a numbered narrative, describe the flowchart and data flow diagram element by element and flag the points where errors could enter. A first sample is free, usually back in two days. The paper above is an original model document written by our desk, not a submitted student paper and not an official Southern New Hampshire University document.
More ACC 315 papers and related BS Accounting samples
- ACC 315 Module 1 Discussion: How One Delivery Ticket Becomes Revenue
- ACC 315 Module 3 Internal Control Assignment: COSO Controls Over Wholesale Propane
- ACC 315 Module 4 Project One: Evaluating the Current System
- ACC 311 Module 1 Discussion: Why a City Bid Needs a Real Cost Number
- QSO 340 Module 5: sample paper, in real form
- PSY 365 Module 2 Trait and Behavioral Leadership Analysis
- ACC 202 Module 1 Cost Behavior Discussion
ACC 315 Module 2 questions, answered
Where can I find a free ACC 315 Module 2 process documentation sample?
This page includes a full ACC 315 Module 2 assignment documenting a propane distributor's revenue cycle with a narrative, a flowchart description and a data flow diagram.
What is the difference between a flowchart and a data flow diagram?
A document flowchart shows the physical flow of documents and who handles them. A data flow diagram shows the logical flow of data among processes, data stores and external entities.
What is included in the revenue cycle?
Sales order entry, shipping or delivery, billing, and cash collections, along with the related records for customers, inventory and receivables.
How detailed should a process narrative be?
Detailed enough that a reader could perform the process: who does each step, what document or system is used and where the output goes.
Do I need to list weaknesses in a documentation assignment?
Many prompts ask for it, and even when they do not, noting weaknesses shows that you understand why the process is documented.