A finished ACC-491 Topic 4 control reliance decision memo example, evaluating three revenue controls for design, testing the two worth relying on and redirecting substantive work around the third. Searches like "acc 491 topic 4 assignment example", "acc491 topic 4 sample" and "acc-491 topic 4 example" land here.
What a finished ACC-491 Topic 4 control reliance decision memo looks like
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.
How an ACC-491 Topic 4 example is structured
The memo is arranged control by control, each carried through the same sequence before the next begins. It opens with the reliance question put plainly: whether testing these controls will cost less than the substantive work it saves. For each control, the memo states the risk and assertion addressed, the walkthrough evidence of how it operates, the design evaluation and the decision to test or not. The testing section follows for the two controls kept, describing the procedures, the period covered and the results, with the monthly review sampled across the whole year rather than at year end. A fourth section sets out the consequence for control risk, assessed below maximum for occurrence and completeness and at maximum for valuation. The fifth revises the substantive plan, reducing sales vouching and expanding the aging review and subsequent receipts testing. A final paragraph reports the credit override to management as a deficiency.
Each control tied to one assertion
The invoicing block addresses occurrence, the sequence review completeness and credit approval valuation, so each test result has a specific place to land.
Design evaluated before any testing
A walkthrough shows the credit control can be bypassed by sales managers, and a control that fails on design is not worth testing for operation.
Operation tested across the whole year
The monthly review is examined in months drawn from every quarter, since reliance for the full period needs evidence that the control ran throughout it.
Automated control tested through general controls
Effective controls over program changes let a single instance of the invoicing block stand for the year, a step the memo explains rather than assumes.
Substantive work moved to where reliance failed
Without a working credit control, the memo expands the aging review and subsequent receipts testing on receivables valuation to carry the weight the control could not.
Where marks go in ACC-491 Topic 4
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.
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.