| Course | ACC 335 Accounting Information Systems |
|---|---|
| Topic | Topic 7 |
| Paper type | Control weakness finding |
| Length | About 960 words, 2 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | BS in Accounting |
| Updated | September 2026 |
Free sample paper for ACC 335 Topic 7
One Email Could Redirect $18,400: A Control Weakness Finding on Vendor Bank Changes at Northgate Cold Storage
[Author Name]
Colangelo College of Business, Grand Canyon University
ACC-335: Accounting Information Systems
Topic 7 Assignment
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
One Email Could Redirect $18,400: A Control Weakness Finding on Vendor Bank Changes at Northgate Cold Storage
Summary of the Finding
Northgate Cold Storage, a composite refrigerated warehouse operator, allows its payables clerk to change a supplier's bank account details alone, on the strength of an email, with no call-back to the supplier and no second approval. The next payment run would send the $18,400 due to its refrigerant supplier to whatever account the email named. This finding is written in the condition, criteria, cause and effect format used in control documentation, and every part refers to the same transaction. All figures are illustrative.
Condition: What Exists
On October 14, the payables clerk received an email appearing to come from Polar Gas Supply, Northgate's refrigerant supplier, stating that Polar had changed banks and giving new account and routing numbers. The clerk updated Polar's record in the vendor master file the same afternoon. The system accepted the change without any other approval. No one telephoned Polar to confirm. The clerk then prepared the October 20 payment run, which included Polar's invoice for $18,400 for ammonia refrigerant delivered in September. The controller approved the payment run by reviewing its total and the list of vendors, a list on which Polar appeared as usual. Nothing on the approval screen showed that Polar's bank details had changed six days earlier.
The review team found this during a walkthrough on October 18, before the payment run was released. When the team telephoned Polar using the number on file from a past invoice, Polar confirmed that it had not changed banks.
Criteria: What Should Exist
Any change to a vendor's bank details should be independently verified before the next payment to that vendor. Verification means a call to the vendor at a phone number already on file, not one supplied in the request, by someone other than the person who entered the change, with the call documented. A second person should approve the change in the system before it takes effect. This reflects the control framework's expectation that control activities include authorization and verification appropriate to the risk (Committee of Sponsoring Organizations of the Treadway Commission, 2013), and the separation of the person who maintains master data from the person who prepares payments (Romney et al., 2021).
Cause: Why the Weakness Exists
The payables clerk's system role combines two functions that should be separate: editing vendor master records and preparing payment runs. With both, one person can change where money goes and then send it there. The role was configured this way when Northgate had a single bookkeeper, and it was never split when the controller position was added. There is also no written procedure for bank detail changes, so the clerk followed what seemed reasonable: the email looked genuine, carried Polar's logo and came from an address that differed from Polar's by one letter.
Effect: What Could Result
Had the October 20 run been released, $18,400 would have gone to an account controlled by whoever sent the email. Polar would still be owed the $18,400, so Northgate's loss would equal the full payment, and recovery from a fraudster's account once funds have moved is rare. Beyond this payment, the weakness exposes every vendor: Northgate pays about 90 vendors, and the same email technique would work on any of them.
The scheme is common. Business email compromise, in which criminals impersonate a vendor or executive to redirect payments, generated 21,489 complaints to the FBI's Internet Crime Complaint Center in 2023, with reported adjusted losses of more than $2.9 billion (Federal Bureau of Investigation, 2024).
Severity and Who Should Be Told
Severity depends on how likely the weakness is to be exploited and how large the loss could be. Both point high here. The attempt has already happened once, which shows that Northgate is known to criminals who target vendor payments, and the loss from a single successful attempt would be a full invoice, typically $5,000 to $40,000 for Northgate's larger suppliers. The weakness also sits in a process that runs every two weeks, so exposure recurs with each payment run.
The finding should go to the controller and the owner in writing, with this October attempt as the illustration, rather than being handled informally with the payables clerk. The clerk did what the system and the absence of a procedure allowed, and treating the matter as a personal error would leave the cause in place for the next person in the role. The owner should also ask the company's insurer whether its crime policy covers social engineering losses, since many policies exclude them unless a specific endorsement was purchased.
Recommendation
The recommendation follows from the cause. First, split the role: remove vendor master editing from the payables clerk and assign it to the office manager, who does not prepare payments. Second, write a procedure for bank detail changes requiring a call-back to a number already on file, documented in the vendor record, and a second approval in the system before the change takes effect. Third, add a report of vendor master changes since the last run to the controller's payment approval package, so that a changed bank account is visible at the moment money is released. Fourth, for any vendor whose bank details changed, hold the first payment until the vendor confirms receipt of a small test deposit or the call-back is on file.
Management's immediate response was to reverse the change to Polar's record, report the email to the bank and to the FBI's complaint center, and warn staff, with a copy of the email circulated so that everyone who handles vendor mail can recognize the next attempt. The structural changes above address the cause and should be in place before the November payment run.
References
Committee of Sponsoring Organizations of the Treadway Commission. (2013). Internal control: Integrated framework. COSO.
Federal Bureau of Investigation. (2024). Internet crime report 2023. Internet Crime Complaint Center.
Romney, M. B., Steinbart, P. J., Summers, S. L., & Wood, D. A. (2021). Accounting information systems (15th ed.). Pearson.
The ACC-335 Topic 7 assignment instructions
ACC-335 Topic 7 asks students to document a control weakness and recommend a remedy. Many submissions describe a weakness in general terms. The assignment rewards findings written in condition, criteria, cause and effect format, with every part referring to the same transaction. Students should describe exactly what happened, state the control that should exist, identify the underlying cause, such as a system role that combines incompatible functions, and trace the effect to a specific amount. The recommendation should follow from the cause, and the finding should assess severity and say who should be told.
How this ACC 335 Topic 7 example is built
The finished finding follows the condition, criteria, cause and effect format that control documentation commonly uses, and every part refers to the same transaction. The condition is that supplier bank details can be changed by the payables clerk alone, on the strength of an email, with no call-back to the supplier and no second approval. The criterion is the control that should exist: an independent verification of any change to the vendor master file before the next payment. The cause is a system role that combines editing vendor records with preparing payment runs. The effect is traced to a single illustrative payment of $18,400 due to the company's refrigerant supplier, which the next run would send to the new account without anyone else seeing the change. The recommendation follows from the cause.
Reading the ACC 335 Topic 7 rubric
Faculty grading the weakness finding reward four parts tied to one transaction. Excellent findings show the email, the unverified change and the payment run it would have redirected. Credit goes to criteria that specify a call-back to a number already on file and a second approval. The rubric values a cause located in a system role and an effect quantified in dollars, with evidence on how common the scheme is. The highest level assesses severity and aims recommendations at the cause rather than the clerk. Findings whose recommendation does not match the cause usually land in a middle band.
ACC 335 Topic 7 help: mistakes that cost marks
A weakness written as a general concern, such as vendor management needing improvement, identifies nothing a manager could act on and loses the most marks. Without a transaction attached, the reader cannot see how much is exposed or through which path it would leave. Findings that confuse the condition with the cause recommend fixing the symptom, adding a review of payments when the problem is who can edit the vendor file. Missing criteria leave the finding as the author's preference, since a weakness is a gap measured against a control that ought to exist. Effects stated as possible fraud, without walking the payment through, understate a risk that is concrete. Recommendations that require a new hire, in a payables team of two, will not be implemented, and the finding should propose something the team can actually run.
Get an ACC-335 Topic 7 example written to your instructions
Send the ACC-335 Topic 7 instructions, the classroom rubric and the case or walkthrough notes the assignment provides. We draft a custom example to those criteria, with condition, criteria, cause and effect kept distinct, one transaction traced through the weakness and a fix sized to the team, delivered in 24 to 48 hours. The first request is free.
More ACC 335 papers and BS in Accounting samples
- ACC 335 Topic 1: Cycle Responsibility Map
- ACC 335 Topic 2: Expenditure Cycle Flowchart
- ACC 335 Topic 3: Design Versus Operation Memo
- ACC 335 Topic 4: Incompatible Duties Matrix
- ACC 335 Topic 5: Control Cost Discussion Post
- ACC 335 Topic 6: User Access Rights Review
- ACC 335 Topic 8: Compensating Control Plan
- ACC 260 Topic 7: Make-or-buy Decision Analysis
- ACC 250 Topic 7: Creditor Ratio Briefing
- ACC 240 Topic 7: Statement Assembly Problem
ACC 335 Topic 7 questions, answered
How do condition and cause differ?
The condition is what was found: the clerk can change bank details alone. The cause is why that is possible: the system role combines two permissions and the procedure omits verification. Keeping them apart matters because recommendations should address causes, and a finding that treats the condition as its own cause tends to recommend a patch rather than a repair.
Do I need a dollar figure for the effect?
A figure makes the exposure concrete, and an illustrative one is fine if it is labeled and plausible for the scenario. The more important thing is the path, showing step by step how the transaction would pass through the weakness. A large number attached to a vague path is less persuasive than a modest number attached to a path the reader can follow.
How do I rank one weakness against others?
By the size of the loss it would allow and how easily it could be exploited without detection. A weakness that permits one person to divert an entire payment run, silently, outranks one that permits a small error somebody would notice at month end. State the ranking and the reasoning in a sentence or two, so the reader can disagree with a specific judgment.
Where can I find a free ACC 335 Topic 7 sample paper?
This page holds the complete finding: the summary, condition, criteria, cause, effect, severity and who should be told, and the recommendation. Tell us your weakness for a free worked finding.
What caused the weakness in ACC 335 Topic 7?
The payables clerk's role combined editing vendor records with preparing payment runs, so one person could change where money goes and then send it there.