| Course | ACC 491 Auditing |
|---|---|
| Topic | Topic 4 |
| Paper type | Control reliance decision memo |
| Length | About 770 words, 1 pages |
| Format | Memo with APA 7 references |
| School | Grand Canyon University (GCU) |
| Program | BS in Accounting |
| Updated | September 2026 |
Free sample paper for ACC 491 Topic 4
Memorandum
To: Engagement partner, Pioneer Medical Supply audit
From: [Author Name], audit senior
Date: [Date]
Re: Whether to rely on three revenue cycle controls
The Decision
Relying on a control means testing that it worked throughout the year and then doing less substantive testing of the balances it protects. Each choice has a cost: testing a control takes hours, and not relying on it means more hours of detail testing. This memo evaluates three revenue cycle controls at Pioneer Medical Supply, a composite client, and recommends relying on two of them. Hours are estimates.
The Controls and the Walkthrough
The three controls address different assertions. An automated block in the billing system prevents an invoice from being issued unless it matches a shipping record, which addresses the occurrence of sales. A shipping supervisor reviews a monthly report of gaps in the sequence of shipping documents and investigates each, which addresses completeness. And the credit manager approves credit for new customers and increases to existing limits, which addresses the valuation of receivables.
A walkthrough traced one sale, an order for 12 hospital beds, from the customer's purchase order through credit check, shipping, invoicing and collection. It confirmed that each control exists and operates as described, and it showed how the credit control can be bypassed.
Design Evaluation
A control is effectively designed if, operating as intended, it would prevent or detect a material misstatement in the assertion it addresses (American Institute of Certified Public Accountants, 2021). The billing block is well designed: an invoice without a shipment cannot be issued at all. The gap review is well designed: every missing shipping document number is listed and explained, so an unbilled shipment would surface within a month.
The credit control is not effectively designed. During the walkthrough, a regional sales manager showed that the system allows sales managers to raise a customer's credit limit directly, and the credit manager does not receive a report of changes made that way. Sales managers are paid on revenue, so they have an incentive to raise limits for customers who may not pay. The control can be bypassed by the people it is meant to constrain. Under the control framework, control activities should keep approval of a transaction separate from the people who carry it out (Committee of Sponsoring Organizations of the Treadway Commission, 2013).
The Decision for Each Control
Table 1 sets out each decision with its estimated cost.
Table 1
Reliance Decisions and Their Cost
| Control | Assertion | Design | Reliance decision | Hours to test controls | Substantive hours saved or added |
|---|---|---|---|---|---|
| Billing system blocks an invoice without a matched shipping record | Occurrence of sales | Effective | Rely; test once with general IT controls | 6 | Saves about 24 |
| Monthly supervisor review of gaps in shipping document numbers | Completeness of sales | Effective | Rely; test 3 of 12 monthly reviews | 8 | Saves about 16 |
| Credit approval for new customers and limit increases | Valuation of receivables | Not effective: sales managers can raise limits without the credit manager | Do not rely; do not test | 0 | Adds about 20 of allowance testing |
Reasoning
For the billing block, testing is efficient. An automated control that works once works every time, provided the general controls over the system, access and program changes, were effective all year. Six hours of testing, including those general controls, supports a reduction of about 24 hours in detail testing of sales occurrence.
For the gap review, a manual monthly control, the auditor tests a sample of months, here three of twelve, examining the report, the supervisor's notes and the follow-up on each gap. Eight hours supports a reduction of about 16 hours of completeness testing.
For the credit control, testing operating effectiveness would be pointless: a control that is not designed effectively cannot be relied on however consistently it is performed. Instead, the audit will expand substantive work on the allowance for doubtful accounts, including a detailed review of the aging, collections after year end for large past-due balances and a review of credit limit changes made by sales managers, about 20 additional hours (Arens et al., 2020).
Net Effect and Communication
Relying on the first two controls costs 14 hours and saves about 40; not relying on the third adds about 20. The net plan is roughly 6 hours lighter than a fully substantive approach and directs effort to the assertion where controls are weak. The credit control weakness will be communicated in writing to management and to those charged with governance, since sales managers' ability to raise limits unreviewed could allow material bad debts to accumulate. If the reliance tests of the first two controls find deviations, the decision will be revisited and substantive testing restored.
References
American Institute of Certified Public Accountants. (2021). Understanding the entity and its environment and assessing the risks of material misstatement (Statement on Auditing Standards No. 145). AICPA.
Arens, A. A., Elder, R. J., Beasley, M. S., & Hogan, C. E. (2020). Auditing and assurance services (17th ed.). Pearson.
Committee of Sponsoring Organizations of the Treadway Commission. (2013). Internal control: Integrated framework. COSO.
Reading the GCU ACC 491 Topic 4 instructions
The Topic 4 instructions in ACC-491 ask students to decide whether to rely on internal controls. Weak submissions decide without evaluating design. The assignment rewards memos that describe each control and the assertion it addresses, confirm operation with a walkthrough, evaluate design before considering operating tests, and weigh the hours to test controls against the substantive testing they would save. Students should explain how automated and manual controls are tested differently, why a poorly designed control is not tested for operation, how substantive work changes and how deficiencies are communicated.
How the ACC-491 Topic 4 example is put together
The memo treats reliance as a decision with a cost on each side. It first describes each control and the assertion it addresses: an automated block that stops the billing system from invoicing without a matched shipping record, for occurrence; a monthly supervisor review of gaps in shipping document numbers, for completeness; and credit approval for new customers and higher limits, for receivables valuation. A walkthrough of one sale confirms how each operates. The design evaluation finds the first two sound and the third flawed, since regional sales managers can raise limits in the system without the credit manager seeing it. The first two are then tested: the automated control through the general controls over program changes and one instance, the monthly review across a selection of months spread through the year. Both hold, and planned sales testing shrinks accordingly.
ACC 491 Topic 4 rubric: what Excellent looks like
Faculty grading the reliance memo reward design evaluated before testing. Excellent memos find a design flaw in a control that the constrained people can bypass and decline to test it. Credit goes to testing automated controls once with general IT controls and sampling a monthly manual control. The rubric values estimating hours saved and added, so reliance is shown as a cost decision. The highest level expands substantive work where controls fail and communicates the weakness to governance. Memos that rely on every control without design evaluation usually land in a middle band.
Common ACC 491 Topic 4 mistakes, and how to avoid them
Control papers are marked hardest where reliance is claimed and not earned. Relying on a control because the client described it in an interview, with no walkthrough or test of operation, treats inquiry as evidence it can never be on its own. Memos that test a control for operation after finding its design deficient spend effort proving that a flawed control runs as designed. Testing a monthly control only in December supports a conclusion about December, not the year. Papers that decide to rely and then leave the substantive plan unchanged show no grasp of why reliance matters at all. The error that costs most in many sections is a control matched to the wrong assertion, such as credit approval offered as evidence that sales occurred, since that pairing leaves every later conclusion about the account unsupported.
Get an ACC-491 Topic 4 example written to your instructions
Send the ACC-491 Topic 4 instructions, the rubric and the control descriptions or case your section provided. We write a custom example to them, with each control tied to an assertion, design evaluated before operation, tests spread across the period and the substantive plan revised to match the reliance decision, back in 24 to 48 hours. The first one is free.
More ACC 491 papers and BS in Accounting samples
- ACC 491 Topic 1: Audit Opinion Scope Memo
- ACC 491 Topic 2: Covered Member Interest Analysis
- ACC 491 Topic 3: Assertion Level Risk Matrix
- ACC 491 Topic 5: Evidence Sufficiency Discussion Post
- ACC 491 Topic 6: Attribute Sampling Evaluation
- ACC 491 Topic 7: Receivables Confirmation Working Paper
- ACC 491 Topic 8: Opinion Selection Memo
- ACC 240 Topic 4: Closing Entry Sequence
- ACC 486 Topic 4: Common Size Trend Analysis
- ACC 250 Topic 4: Allowance Estimate Review
- ACC 465 Topic 4: Related Party Transaction Review
ACC 491 Topic 4 questions, answered
Is it ever sensible not to rely on controls that work?
Yes. Testing controls costs time, and for some accounts it is cheaper to gather substantive evidence directly, especially for small populations or balances that can be confirmed or recalculated completely. The reliance decision compares the cost of testing with the substantive work it would save. Where the saving is small, an auditor may choose a fully substantive approach even for a well-designed control.
Why test an automated control only once?
Because a program applies the same logic every time it runs, so one instance working correctly shows how it treats every transaction, provided the program has not changed. That proviso is why general controls over program changes and access are tested first. If those are weak, the single instance says little about the rest of the year, and the approach no longer holds.
What happens to the credit control weakness?
The weakness is a deficiency in internal control, and the memo reports it to management, and to those charged with governance if it is significant. For the audit itself, the weakness raises control risk for receivables valuation to maximum, so the evidence has to come from substantive procedures. Whether it rises to a significant deficiency or material weakness is a separate judgment the memo notes and leaves to the engagement team.
Where can I find a free ACC 491 Topic 4 sample paper?
This page carries the complete memo: the decision, the controls and walkthrough, design evaluation, decisions and costs, reasoning and the net effect with communication. Share your controls for a free worked memo.
Why not test the credit control in ACC 491 Topic 4?
It is not effectively designed, since sales managers can raise limits without the credit manager seeing it, so testing its operation could not support reliance.