ACCT20007 Chap.5 Control Levels and Processing Modes
Control Levels and Processing Modes
Controls operate at entity, process and application levels, and each layer depends on the others. Governance can fail to enforce a strong field check, while a sound policy can be defeated by weak access configuration.
Batch and real-time processing also expose errors differently, changing which totals, locks, validations and exception routes are appropriate.
Entity-level controls shape governance, ethics, oversight, delegation, training and the response to known weaknesses. They apply broadly and determine whether exceptions are escalated or tolerated.
A quarterly access report has little value when management accepts shared administrator credentials and takes no action.
Process-level controls coordinate people, documents and hand-offs. They include segregation, approval, reconciliation and supervisory review. Application controls operate through configured access, required fields, range checks, matching and transaction rules.
The layers interact: a programmed tolerance depends on authorised configuration and change control, while process review depends on complete system evidence.
Batch processing groups transactions and supports record counts, monetary totals, hash totals, sequence checks and unique batch identifiers. Real-time processing updates immediately and needs validation, atomicity, isolation and timely exception handling.
The same control cannot be assumed suitable for both modes. A nightly population comparison detects transfer loss, while a stock reservation needs concurrency protection before confirmation.
Diagnose the layer and timing before proposing the fix. Then state residual risk.
Control totals may expose missing records without proving field accuracy; record locking may prevent double reservation without proving starting inventory was valid. A complete recommendation joins the technical mechanism to process ownership, follow-up evidence and governance escalation.
General technology controls support applications through access administration, controlled change, operations and recovery.
Weak foundations can undermine programmed matching across many processes at once.
Emergency access needs a designed route. Named temporary rights, short expiry, reason, approval, complete logging and post-use review allow urgent work while preserving attribution.
For interfaces, test completeness and duplication. A destination may receive fewer records, load the same batch twice or transform values incorrectly.
Combine identity, count and amount evidence.
Every technical exception needs process ownership and governance escalation. A precisely detected failure still reaches reports when nobody is responsible for clearing it before downstream processing.
Configuration data sits between policy and transaction processing.
Thresholds, tolerances and role mappings need ownership, approval, version history and testing because one change can alter thousands of decisions.
Review metrics at the same level as the control.
Application failures need transaction or exception data, process failures need hand-off and resolution evidence, and entity issues need patterns of overdue findings and tolerated breaches.
For revision, classify each weakness twice: first by entity, process or application level, then by batch or real-time behaviour. Choose evidence that matches both classifications and state what the control still cannot prove.
Revisit the answer from the next level up to confirm that exception ownership, configuration change and escalation support the technical rule instead of leaving it isolated.
What this chapter covers
- 01
Entity-level controls
- 02
Process controls
- 03
Application controls
- 04
Batch processing
- 05
Real-time processing
- 06
Access governance
- 07
Interface evidence
Worked example · free
Fix shared administrator access
- 1The validation is an application control but does not establish user identity.
- 1Shared credentials create a process-level accountability failure.
- 1Management tolerance reveals an entity-level enforcement weakness.
- 2Use named accounts, independent approval, technical prohibition and escalation.
Key terms
- Entity-level Control
- An entity-level control shapes governance, culture, risk oversight and accountability across processes.
- Application Control
- An application control acts through programmed validation, access, matching or processing rules.
- Batch Control
- A batch control compares population identity, count or value across grouped processing stages.
Control Levels and Processing Modes FAQ
How do process and application controls differ?
Process controls coordinate actors, evidence, approvals and reconciliations across a workflow. Application controls operate through configured access, validation, matching and transaction rules. A control may combine both, but the answer should state which layer owns the weakness.
What makes a batch transfer reliable?
Use a unique batch identifier, source and destination record counts, monetary or hash totals, duplicate prevention and an exception queue. An accountable reviewer must resolve differences before posting, because a transmitted file alone does not prove complete and accurate loading.
Why does real-time processing need concurrency control?
Two sessions can read the same available state and then both commit incompatible updates. Atomic transactions, locking or version checks ensure the second action sees the first result. Residual failures still need a process for customer communication and correction.
Exam move
Make a three-row control-level grid and place every case fact in the most direct row. Then ask whether transactions are processed in batches or immediately. Choose evidence that fits the timing: totals and sequence for batches, validation and concurrency protection for real-time work.
Working through Control Levels and Processing Modes in ACCT20007? Sia is AskSia’s AI Accounting tutor — ask any ACCT20007 Control Levels and Processing Modes 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.
