ACCT90004 Chap.11 Accounting Processes, Risks and Controls
Accounting Processes, Risks and Controls
Accounting information depends on the process that creates it. This chapter maps purchasing, sales, inventory and cash activities from initiation to recording, identifies what can go wrong and matches controls to specific risks. It distinguishes preventive and detective responses and evaluates segregation, authorisation, matching, reconciliations and retained evidence.
The goal is not to list controls, but to explain how a named control interrupts a named error or fraud path while recognising practical limitations.
What this chapter covers
- 01
Process mapping
- 02
Error and fraud risks
- 03
Authorisation controls
- 04
Segregation of duties
- 05
Document matching
- 06
Reconciliations, evidence and control limits
Worked example · free
Design a purchasing control
- 1The combined access allows a fictitious supplier or unsupported invoice to be created and paid.
- 2Separate supplier-master maintenance from invoice approval and payment release.
- 2Require an independent match of purchase order, receipt evidence and supplier invoice before payment.
Key terms
- Segregation of duties
- Allocation of incompatible tasks to different people or controlled roles.
- Three-way match
- Comparison of order, receipt and supplier invoice before payment approval.
- Preventive control
- A control designed to stop an error or unauthorised action before it occurs.
- Detective control
- A control designed to identify an error or exception after it occurs.
Accounting Processes, Risks and Controls FAQ
What makes a control recommendation specific?
It names the risk, responsible role, action, timing and evidence retained. Saying only that management should improve controls does not explain which failure is prevented or detected, who performs the control or how completion can be verified.
Why is segregation important?
Separating initiation, custody, recording and approval reduces the opportunity for one person to create and conceal an unauthorised transaction. Smaller organisations may need compensating review controls when full separation is impractical.
Does a reconciliation prevent every error?
No. A reconciliation is usually detective and depends on independent, reliable records and timely review. It may reveal a difference without identifying its cause, so exceptions still need investigation, correction and documented follow-up.
How should I evaluate whether a control actually operated?
Look for evidence of performance by the assigned independent role at the required time, plus documented handling of exceptions. A policy statement alone does not prove operation. Shared access, late review, ignored differences or missing sign-off can make a sound control design ineffective in practice.
Exam move
Draw each process as a sequence of events, records, systems and roles. At every handoff, ask what could be omitted, duplicated, misstated or performed without authority. State the risk as a cause and consequence, not as a vague lack of control. Then select a control whose operation interrupts that precise path.
Build a matrix covering authorisation, access, segregation, sequence checks, three-way matching, reconciliations and supervisory review, but avoid treating any control as universally effective. For each recommendation, name who performs it, when, using which evidence and what happens to exceptions. Practise evaluating limitations such as collusion, override, poor source data and delayed review.
Link process weaknesses back to account balances and decisions so the answer remains accounting focused. Use the course scenarios to learn process types, then create fresh businesses and facts for drills. In final revision, alternate design questions with critique questions: identify why a proposed control would fail, then repair its ownership, independence, timing or evidence.
Finish every response with a closing move that connects the control to a more reliable ledger or decision. Take one transaction cycle and produce a swim-lane map showing requester, custodian, recorder, approver and reviewer. Mark system boundaries and every point where information is re-entered, because interfaces create risks beyond deliberate fraud.
For each risk, write the possible misstatement and affected account before selecting a response. Compare preventive and detective options and state why both may be needed. For three-way matching, test exceptions such as partial delivery, price disagreement and missing receipt evidence; define who can approve an override and what record remains.
For reconciliations, specify the independent source, frequency, reviewer and escalation of old differences. Add access-control cases involving new users, departed staff, privileged roles and temporary delegation. Do not conclude that a named control eliminates risk: assess collusion, override, configuration and evidence limitations.
When a weakness has already caused an error, separate the journal correction and recovery action from the redesigned control. Close every practice response with the expected improvement in ledger reliability or decision usefulness. In a final comparison grid, rank recommendations by the specific risk addressed, practicality and strength of retained evidence rather than by how technical the control sounds.
Test each proposed control with a plausible override or exception; then add the monitoring evidence needed to reveal that residual failure.
Working through Accounting Processes, Risks and Controls in ACCT90004? Sia is AskSia’s AI Accounting tutor — ask any ACCT90004 Accounting Processes, Risks and Controls question and get a clear, step-by-step explanation grounded in how ACCT90004 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
