| Course | ACC 335 Accounting Information Systems |
|---|---|
| Topic | Topic 3 |
| Paper type | Design versus operation memo |
| Length | About 760 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 335 Topic 3
Memorandum
To: Controller, Cedar Basin Plumbing Supply
From: [Author Name], staff accountant
Date: [Date]
Re: Evaluation of the automated three-way match: design and operating effectiveness
Two Verdicts
The automated three-way match in our purchasing and payables system is well designed. It is not operating effectively, because supervisors release held invoices without recording a reason, and in a sample of 25 paid invoices, 9 were released that way. The remedy is to control overrides, not to redesign the match. The evidence for each verdict follows, kept separate, because a control can be designed well and still fail in operation, and the fix is different in each case (Public Company Accounting Oversight Board, 2007).
Design: Is the Control Capable of Preventing the Error?
The risk the match addresses is paying for goods never received or at a price nobody agreed. A control is effectively designed if, operated as intended by people with the needed authority and competence, it would prevent or detect that error. Three pieces of evidence support a positive design verdict.
First, the configuration screen shows that the system compares item, quantity and unit price across three records, what was ordered, what the dock counted and what the supplier billed, and holds any invoice where the difference exceeds 2% of the line or $50, whichever is less.
Second, a test transaction confirmed that the configuration works. I entered, in the test environment, an invoice for 100 fittings at $4.20 against a purchase order at $4.00 with 100 received. The system held it with the reason code for price variance. A second test invoice for 110 fittings against 100 received was also held.
Third, the tolerance is reasonable for a distributor whose invoices average about $2,400: small rounding differences pass, and anything material stops.
Operation: Is the Control Working as Designed?
Operating effectiveness asks whether the control actually worked throughout the period. I selected 25 paid invoices at random from the 212 paid in the second quarter and traced each through the system log. Table 1 summarizes the results.
Table 1
Results of the Operating Test
| Sample of 25 paid invoices | Count | Detail |
|---|---|---|
| Matched within tolerance and paid | 16 | |
| Released by supervisor override | 9 | No reason recorded on any |
| Of the overrides, difference explained by freight not on the purchase order | 7 | Freight between $38 and $210 |
| Of the overrides, paid above the contract price | 2 | Overpayment of $1,340 in total |
Reading the Results
Nine of 25 invoices, 36%, were released by a supervisor using the override function, and none of the nine has a reason recorded. The override log for the full quarter shows 41 overrides among 212 invoices, about 19%, so the sample rate is high but the practice is widespread. Of the nine sampled overrides, seven were released because the supplier billed freight that was not on the purchase order; the amounts are small and the payments appear correct. Two were released for price differences, and comparison with the contract price list shows Cedar Basin overpaid by $1,340 on those two invoices.
The overrides defeat the match in operation. A control that stops an invoice is effective only if releasing it requires the same scrutiny the match was meant to supply, and an override without a reason supplies none.
Remedy Matched to the Failure
Because the design is sound, redesigning the match would spend effort where there is no weakness. The failure is in operation, and the remedy should address it directly. I recommend three changes. Restrict the override permission to the controller and the assistant controller, removing it from the two purchasing supervisors. Configure the system to require a reason code and a comment before any override. And review the weekly override report, listing every released invoice with its reason, at the controller's Monday meeting.
The freight overrides point to a fixable cause. Adding an estimated freight line to purchase orders for suppliers who bill freight separately, or setting a separate tolerance for freight, would remove most legitimate overrides and make the remaining ones stand out. The internal control framework expects control deficiencies to be evaluated and communicated to those responsible for corrective action (Committee of Sponsoring Organizations of the Treadway Commission, 2013); I also recommend asking the two suppliers for a credit of the $1,340 overpaid.
Retesting
After the changes are in place for a full month, a new sample of 25 invoices should be tested the same way. The target is no override without a reason and no payment above contract price. Automated controls are reliable only while the settings and permissions around them stay controlled, so the override report should remain part of the monthly close (Romney et al., 2021).
References
Committee of Sponsoring Organizations of the Treadway Commission. (2013). Internal control: Integrated framework. COSO.
Public Company Accounting Oversight Board. (2007). An audit of internal control over financial reporting that is integrated with an audit of financial statements (Auditing Standard No. 5, now AS 2201). PCAOB.
Romney, M. B., Steinbart, P. J., Summers, S. L., & Wood, D. A. (2021). Accounting information systems (15th ed.). Pearson.
What the ACC 335 Topic 3 instructions ask for
ACC-335 Topic 3 asks students to evaluate whether a control is designed and operating effectively. Many papers merge the two questions into a single conclusion. The assignment rewards memos that reach separate verdicts on design and operation, state the evidence for each, such as configuration settings and test transactions for design and a sample and system logs for operation, and quantify what the operating failure has cost. Students should match the remedy to whichever element failed, identify the underlying cause of exceptions where possible and propose how the control will be retested.
How this ACC 335 Topic 3 example is built
The finished memo reaches two verdicts about a single control and keeps them apart. On design, it concludes the match is sound: the system compares quantity and price across the purchase order, the receiving report and the invoice, and it holds anything outside a stated tolerance, which addresses paying for goods never received or at a price nobody agreed. On operation, it concludes the control is failing, because in an illustrative sample of 25 paid invoices, 9 were released by a supervisor override with no reason recorded. The evidence for each verdict is stated: the configuration screen and a test transaction for design, the sample and the override log for operation. The memo then matches the remedy to the failure, restricting and reviewing overrides rather than redesigning a match that already works.
Where the marks sit in the ACC 335 Topic 3 rubric
GCU's rubric for the design versus operation memo rewards keeping the verdicts apart. Excellent memos show that the match works as configured and then show, with a sample, that overrides defeat it. Credit goes to quantifying the effect, including any overpayment found. The rubric values a remedy aimed at the actual failure, restricting and reviewing overrides, rather than redesigning a sound control. The highest level finds the cause of routine overrides, such as freight missing from purchase orders, and sets a retest. Memos that recommend redesign when only operation failed usually land in a middle band.
ACC 335 Topic 3 help: mistakes that cost marks
Treating design and operation as one judgment is where this assignment usually costs the most. A memo concluding that the control is effective because it exists in the system has evaluated design and stopped, and the override log would have told a different story. The reverse error, condemning a well-designed control because people bypass it, leads to a redesign that the same people will bypass again. Controls described without the risk they address give a reader no way to decide whether the design is adequate, since adequacy is always measured against something specific. Evidence missing from either verdict turns the memo into opinion. Recommendations that do not follow from the finding, such as more training when the problem is an unrestricted override, suggest the analysis and the remedy were written separately.
Get an ACC-335 Topic 3 example written to your instructions
Send the ACC-335 Topic 3 instructions, the rubric posted in your classroom and the control or case the assignment describes. A custom example is prepared to those criteria, with the risk named as a transaction, design and operation judged separately on stated evidence and a remedy fitted to the gap, within 24 to 48 hours. The first one is on the house.
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 4: Incompatible Duties Matrix
- ACC 335 Topic 5: Control Cost Discussion Post
- ACC 335 Topic 6: User Access Rights Review
- ACC 335 Topic 7: Control Weakness Finding
- ACC 335 Topic 8: Compensating Control Plan
- ACC 260 Topic 3: Contribution Format Restatement
- ACC 250 Topic 3: Revenue Timing Memo
- ACC 240 Topic 3: Accrual Adjustment Schedule
ACC 335 Topic 3 questions, answered
Can a control be designed well and still fail?
Regularly. Design only asks whether the control would work if performed as intended, and operation asks whether it is performed, consistently, by the right person, over the whole period. A well-designed approval is worthless if the approver signs without looking, and a paper that tests only the design will call that control effective when it protects nothing.
What counts as evidence of operation?
Something produced by the control actually being performed across a period: signed approvals on a sample of documents, a system log of holds and releases, a reviewer's notes with dates. A policy document, an interview with the control owner or a demonstration on the day of the review shows design at best, and a strong memo says which kind of evidence supports which verdict.
Is an override always a weakness?
No. Most automated controls need one, since legitimate exceptions occur, such as a price increase agreed by phone. The override becomes a weakness when it is unrestricted, unexplained or unreviewed, because then anybody holding it can bypass the control silently. The usual remedy limits who can override, requires a recorded reason and puts the override report in front of somebody else.
Where can I find a free ACC 335 Topic 3 sample paper?
The whole memo appears here, with two verdicts, the design evidence, the operating test, reading the results, the remedy matched to the failure and retesting. Send your control for a free worked evaluation.
Why not redesign the match in ACC 335 Topic 3?
Its design works: tests show it holds variances as configured. The failure is overrides released without reasons, so the fix is to restrict and review overrides.