ACCT20007 Chap.2 Business Processes and Flowcharts
Business Processes and Flowcharts
A process view follows how work crosses functions from a defined trigger to a defined output. This chapter uses swimlanes, activity and decision symbols, documents, data stores and sequence arrows to reveal control ownership and hand-off risk.
The worked method converts a purchasing narrative into actors, evidence, a receipt weakness and measurable redesign.
A business function describes behaviour associated with an organisational unit, while a process explains how linked activities achieve a goal. The distinction matters because risk often sits between functions.
A request may be valid when it leaves one team yet lose its identifier, approval or supporting document before the next actor uses it. A cross-functional map makes those transfers visible.
Start every diagram by naming the trigger and completed output. Boundaries prevent a case analysis from drifting into unrelated activities and clarify which inputs arrive from other processes.
Within the boundary, an activity shows work, a decision shows branching logic, a document records evidence and a data store holds persistent information. Sequence arrows should explain how one step authorises or informs the next.
Swimlanes make segregation and self-review observable. When the same lane creates a supplier, approves an order and verifies delivery, the drawing exposes concentrated authority.
A decision diamond with no data input reveals unsupported judgement. A process that pays from an order but never receives independent fulfilment evidence reveals the exact location where a transaction can become invalid.
Read narratives and diagrams against each other. A step described in prose but absent from the map may be the missing control; a store shown without an update path may explain stale data.
After redesign, verify that every new record has an owner, every exception returns to a decision point and the final output still reaches the next process. A control that creates a dead end is not an effective improvement.
A well-designed exception route shows who investigates, what evidence is allowed, who approves the override and where the result is recorded.
Without that path, staff often create informal workarounds outside the diagram.
Timing must also be visible. A review after payment is detective even when it is called approval, while a verified decision before release may prevent the event. Classify from position and effect, not the label inside a box.
Use the map to design KPIs.
Hand-off delay comes from timestamps, missing evidence from unmatched document IDs and rework from repeated status changes. Each measure should point back to the process objective and weakness.
After redesign, walk one normal case and one exception case through every lane.
Confirm that evidence reaches the next actor, no role reviews its own work and the final output remains complete.
Document stores deserve ownership and change rules. A flowchart that shows data entering a store but not who may update, approve or reconcile it leaves the most important integrity question unanswered.
Use concise labels that describe actions and evidence rather than departments alone.
Clear verbs make sequence testable and help a reviewer distinguish a business decision from data entry or transmission.
For revision, redraw one narrative without looking at the supplied map. Mark the trigger, output, actors, decisions, documents and stores first; add arrows only after the nodes are complete. Then walk a normal case and an exception case through the result.
Any unsupported decision, self-review, dead end or missing evidence transfer becomes a specific improvement to explain.
What this chapter covers
- 01
Function and process views
- 02
Process boundaries
- 03
Swimlane responsibility
- 04
Flowchart symbols
- 05
Hand-off evidence
- 06
Narrative and diagram comparison
Worked example · free
Add the missing receipt lane
- 1Define the process from approved need to received goods and recorded obligation.
- 1Add requester, buyer, receiver and accounts payable as separate lanes.
- 2Require independent receipt evidence and match it to order and invoice before payment.
- 1Monitor missing receipts and entry delay using timestamps.
Key terms
- Business Process
- A business process is a linked set of activities with a defined start, end and goal.
- Swimlane
- A swimlane assigns process activities to the responsible actor or function.
- Process Boundary
- A process boundary states the trigger and completed output included in the analysis.
Business Processes and Flowcharts FAQ
Why draw swimlanes instead of one simple sequence?
Swimlanes reveal which actor performs each step and where evidence crosses responsibility boundaries. That makes segregation of duties, missing acknowledgements and self-review visible. A plain sequence can show timing while hiding the ownership problem that creates the control risk.
What should be checked at every decision symbol?
Identify the criterion, source data, decision owner and exception route. A diamond labelled only approve or reject is incomplete when the diagram does not show what evidence supports the judgement or who may override the result.
How do narratives and diagrams work together in a case?
Compare them rather than assuming they agree. A control described in prose but absent from the diagram, or a data store shown without an update path, may expose the weakness. Explain the discrepancy and its consequence before recommending a change.
Exam move
Redraw short narratives in four lanes and label every document or data store. For each arrow, ask what authorises the next step. For each decision, write the rule and evidence. Then practise finding one missing input, one unsupported decision and one hand-off that loses transaction identity.
Working through Business Processes and Flowcharts in ACCT20007? Sia is AskSia’s AI Accounting tutor — ask any ACCT20007 Business Processes and Flowcharts question and get a clear, step-by-step explanation grounded in how ACCT20007 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
