ACC 335 Topic 2 expenditure cycle flowchart example

Accounting Information Systems Grand Canyon University Free custom sample in 24 to 48h

This ACC 335 Topic 2 sample paper is an expenditure cycle flowchart for a restaurant group's commissary, drawn from a walkthrough of one tomato and chicken purchase. It belongs to GCU ACC 335, Accounting Information Systems, the course listed as ACC-335 in the Grand Canyon University BS in Accounting. Lanes run from the kitchen manager through purchasing, the supplier, the receiving dock, payables and the controller, and each document shows where its copies go. Four control markers are keyed to the errors they catch: approval, a blind count at the dock, the three-way match and the paid stamp. The walkthrough records Friday produce orders phoned in before purchasing approves, and proposes a standing approval with Monday review.

CourseACC 335 Accounting Information Systems
TopicTopic 2
Paper typeExpenditure cycle flowchart
LengthAbout 970 words, 2 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramBS in Accounting
UpdatedSeptember 2026

Free sample paper for ACC 335 Topic 2

1

From Kitchen Request to Supplier Payment: An Expenditure Cycle Flowchart for Harvest Table's Commissary, With Four Controls Keyed to Their Errors

[Author Name]

Colangelo College of Business, Grand Canyon University

ACC-335: Accounting Information Systems

Topic 2 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.

What this page is doingThe title traces the cycle end to end and promises that every control marker names the error it stops. Harvest Table Restaurant Group and the walkthrough are composites; the controls are standard.
2

From Kitchen Request to Supplier Payment: An Expenditure Cycle Flowchart for Harvest Table's Commissary, With Four Controls Keyed to Their Errors

Scope and Method

Harvest Table Restaurant Group, a composite operator of four restaurants, buys produce, meat, dry goods and supplies through a central commissary kitchen. This flowchart documents how a purchase moves from the kitchen's request to payment of the supplier. It was drawn from a walkthrough: one purchase of 40 cases of tomatoes and 60 pounds of chicken thighs was followed from requisition to payment, with each person interviewed at their own step. The flowchart uses lanes, one for each party, and standard symbols in the original; here each symbol is rendered as a row. Documents show where every copy goes, and control points carry a marker, C1 to C4, keyed to the error each would catch (Romney et al., 2021).

The Flowchart

Table 1 lists the steps in order, by lane.

Table 1

Expenditure Cycle Flowchart, Harvest Table Commissary

StepLaneActionDocument and where copies goControl
1Kitchen managerCounts stock against par levels and requests what is shortPurchase requisition; copy 1 to purchasing, copy 2 kept in the kitchen file
2PurchasingChecks the request against the approved supplier list and budget, then approvesApproved requisition filed by dateC1
3PurchasingPlaces the order at the contract pricePurchase order; copy to supplier, copy to receiving without quantities, copy to payables, copy filed by PO number
4SupplierShips goods with a packing slip; later sends an invoicePacking slip travels with goods; invoice mailed to payables
5Receiving dockCounts and weighs what arrived without seeing the ordered quantities; notes damageReceiving report; copy to payables, copy to kitchen, copy filedC2
6Accounts payableMatches purchase order, receiving report and invoice on item, quantity and priceMatched voucher package filed by due dateC3
7ControllerReviews the voucher package and approves paymentApproved voucher; payment file sent to bank
8Accounts payableMarks every document in the package paid, with date and check or transfer numberPaid voucher package filed by supplierC4

Control Points and What Each Catches

Table 2 keys each control marker to the error or fraud it is designed to catch.

Table 2

Control Points Keyed to Errors

ControlWhereError or fraud it would catch
C1Approval of the requisitionA purchase no one authorized, or from a supplier not on the approved list
C2Blind count at the dockA short or substituted shipment billed as complete
C3Three-way matchA price above the contract, or a quantity billed but never received
C4Paid stamp on every documentA second payment of the same invoice, from a copy or a resent invoice

Why the Receiving Report Records the Count

Step 5 is designed so that the receiving clerk records what arrived, not what was ordered. The receiving copy of the purchase order lists items but not quantities, so the clerk must count and weigh. If the clerk could see the ordered quantity, the easiest way to finish a delivery during a busy morning would be to copy it onto the receiving report. The report would then agree with the purchase order whether or not the shipment was complete, and the three-way match at step 6 would pass an invoice for goods never received. The blind count is what gives the match its meaning.

Why the Match and the Paid Stamp Matter

The three-way match compares three documents created by three different parties: purchasing, which agreed the price; receiving, which counted the goods; and the supplier, which billed. An invoice is paid only when all three agree within a tolerance, $25 or 2% at Harvest Table. The paid stamp at step 8 closes the loop. Once every document in the package is marked paid, a duplicate invoice, a photocopy of the original or an invoice the supplier resent because payment was slow cannot be matched to an open package. Billing schemes, in which an organization is caused to pay false, inflated or duplicate invoices, are among the most common forms of occupational fraud (Association of Certified Fraud Examiners, 2024), and steps 6 and 8 are the controls aimed at them.

Where Practice Departed From the Procedure

The walkthrough found one departure. The written procedure requires every order to pass through purchasing. In practice, the kitchen manager phones produce orders directly to the produce supplier on Friday afternoons, when weekend demand becomes clear, and purchasing enters a purchase order on Monday after the goods have arrived. On those orders, control C1 happens after the purchase rather than before it, and the price on the purchase order is copied from the supplier's invoice rather than from the contract, which weakens C3.

The departure has a sound business reason, since weekend demand cannot be predicted on Thursday. The remedy is not to forbid Friday orders but to give the kitchen manager a standing approval for produce up to a set dollar limit at contract prices, with purchasing reviewing Friday orders against the contract price list on Monday before the invoice is matched. The control framework recognizes that control activities must be deployed through policies that people can actually follow (Committee of Sponsoring Organizations of the Treadway Commission, 2013).

What the Walkthrough Purchase Showed

The tomatoes and chicken followed the flowchart without exception, apart from one detail at the dock. The delivery arrived with 38 cases of tomatoes, not 40, and the receiving clerk recorded 38. The supplier's invoice billed 40. At step 6 the match failed on quantity, payables held the invoice, and the supplier issued a credit for two cases within a week. That single transaction shows three controls working together: the blind count captured the short shipment, the match stopped the overpayment and the hold created a record that purchasing can use when it next reviews this supplier's delivery accuracy.

References

Association of Certified Fraud Examiners. (2024). Occupational fraud 2024: A report to the nations. https://legacy.acfe.com/report-to-the-nations/2024/

Committee of Sponsoring Organizations of the Treadway Commission. (2013). Internal control: Integrated framework. COSO.

Romney, M. B., Steinbart, P. J., Summers, S. L., & Wood, D. A. (2021). Accounting information systems (15th ed.). Pearson.

Reading the GCU ACC 335 Topic 2 instructions

The Topic 2 instructions in ACC-335 ask students to document a business process with a flowchart and identify its controls. Weak submissions draw the written procedure without checking it. The assignment rewards flowcharts built from a walkthrough, with a lane for each party, every document and the destination of its copies, and control points marked distinctly. Students should key each control to the specific error or fraud it would catch, explain why design details such as a blind count matter, record any step where practice departs from procedure and propose a remedy that fits the business reason for the departure.

Inside the ACC 335 Topic 2 example

The finished flowchart uses standard symbols and a lane for each party: the kitchen manager, purchasing, the receiving dock, accounts payable, the controller and the supplier. A requisition becomes a purchase order, goods arrive against a receiving report that records what was counted rather than what was ordered, and the supplier's invoice waits in payables until all three documents agree. Each document shows where its copies are filed. Control points are drawn as a distinct marker, and each marker is keyed to a note naming the error it would catch: an unauthorized purchase at approval, a short shipment at the dock, a price change at the match, a second payment of one invoice at the paid stamp. The chart was drawn from a walkthrough, and a note records one step where practice departed from the written procedure.

ACC 335 Topic 2 rubric: what Excellent looks like

Faculty grading the flowchart reward controls keyed to errors. Excellent flowcharts show a receiving report that records what was counted and explain why that gives the three-way match its meaning. Credit goes to document copies traced to their files and to a paid stamp that blocks duplicate payment. The rubric values evidence from an actual walkthrough, including a departure from the written procedure. The highest level proposes a practical fix for the departure rather than simply forbidding it. Flowcharts that mark controls without naming what they catch usually lose marks.

ACC 335 Topic 2 help: mistakes that cost marks

Flowcharts that trace every document and mark no control are the commonest shortfall on this assignment. They show a purchase moving through the organization without showing where anything could stop it, so nobody reading the chart can judge whether the process is sound. Charts drawn from the procedures manual look tidy and describe a process nobody may follow, and markers who ask how the information was gathered notice the difference. Symbols used inconsistently, a document shape here and a process shape there for the same thing, make the chart unreadable to anybody trained in the conventions. Controls marked without the error each one addresses are decorations. Leaving the supplier or the bank off the chart hides the two points where money and goods actually cross the organization's boundary, and those are where the most expensive errors happen.

Get an ACC-335 Topic 2 example written to your instructions

Send the ACC-335 Topic 2 instructions, your classroom rubric and the process narrative or case the assignment supplies. We build a custom example to those criteria, with lanes for each party, standard symbols keyed, every control tied to the error it catches and the practice gap recorded, in 24 to 48 hours. Your first one costs nothing.

More ACC 335 papers and BS in Accounting samples

ACC 335 Topic 2 questions, answered

Should I use a document flowchart or a systems flowchart?

Whichever the instructions name, and if they name neither, the purpose decides. A document flowchart follows paper and electronic records between people and is the better tool for showing segregation and handoffs. A systems flowchart follows data through programs and files and is better for showing automated checks. Many examples combine them, provided the key explains every symbol used.

What is a blind receiving count?

A receiving report prepared without the ordered quantity visible, so the dock staff must count what actually arrived rather than confirm a number already printed. It exists to catch short shipments, which a copy of the purchase order would invite people to sign off without counting. Marking it on the flowchart, with the error it addresses, is a typical example of a control shown doing its job.

How do I show a control the system performs?

Place it inside the lane of the system or program, using the process symbol, and key it to the error it catches just as you would a manual control. An automated three-way match that blocks payment when quantities differ is a control whether or not a person touches it. Note any override that lets somebody release a blocked invoice, because an override is where automated controls usually fail.

Where can I find a free ACC 335 Topic 2 sample paper?

The complete flowchart sits above, with the scope and method, the step table, control points keyed to errors, the blind count, the match and paid stamp, where practice departed and the walkthrough purchase. Share your process for a free worked flowchart.

Why is the receiving count blind in ACC 335 Topic 2?

If the clerk could see ordered quantities, a short shipment could be recorded as complete, and the three-way match would then approve payment for goods never received.