| Course | AC550 Accounting Information Systems |
|---|---|
| Unit | Unit 9 |
| Paper type | Control gap assessment |
| Length | About 790 words, 5 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | MS in Accounting |
| Updated | October 2026 |
Free sample paper for AC550 Unit 9
Two Breaks Between the Handheld and the Bill: A Unit 9 Control Gap Assessment of a Cylinder Rent Cycle
[Student Name]
Purdue University Global
AC550: Accounting Information Systems
Unit 9 Control Gap Assessment
[Instructor Name]
[Date]
Halvorsen Welding Supply and every figure are composite; the framework, standard and textbooks cited are real.
Summary
Two points in the cylinder rent cycle allow the record that drives billing to change without evidence. First, a driver can void a stop's scans and rescan before the handheld syncs, leaving no record of the first count. Second, the nightly transfer overwrites each account's holdings count, replacing manual corrections and late-keyed counter swaps without logging the prior value. Accounts where the billing count disagrees with the last physical scan of each cylinder number 468, and the rent attached to the disputed cylinders is about $18,000 a month.
Step Table
The cycle was followed through nine steps. For each, the assessment asked what evidence the step leaves, whether that evidence survives to the bill, and what application or general control is expected.
Steps one to three, order entry, dispatch and loading, leave a sales order and route sheet; both survive. Step four, the driver's scan, leaves a serial-level record, but the void-and-rescan feature means the evidence may not reflect the first count. Step five, the sync, transfers scans intact. Step six, the nightly transfer, replaces holdings with a total and leaves no prior value; evidence does not survive. Steps seven to nine, counter swaps, rent billing and ledger posting, depend on step six and inherit its weakness.
Gap 1: Handheld Void and Rescan
An application control should prevent a recorded transaction from being deleted without trace. The handheld allows voids without a reason code and does not keep voided scans. The risk is that a driver who disputes a count with a customer, or who misplaced a cylinder, can make the record agree with whatever he chooses. Exposure is hard to size directly because voids leave nothing, but drivers interviewed estimate several voids a week across all routes.
Fix: configure the handheld to require a reason code for every void and to retain voided scans in the synced data, visible to the branch operations manager. Owner: IT administrator. Date: within thirty days, before the new package's cutover.
Gap 2: Nightly Overwrite
A general control over data processing should ensure automated jobs change records only through authorized, logged transactions. The nightly job writes totals directly, so a correction made at 9 a.m. can be undone at 2 a.m. with no record. This gap explains most of the 468 disagreeing accounts.
Fix: retire the job with the old system; until then, run a daily report comparing each account's billing count with the scan database and hold rent bills for accounts that differ by more than two cylinders. Owner: controller. Date: report within two weeks; retirement at cutover.
Both gaps sit at the point where serial-level evidence becomes a summary number, which is why monthly reviews of the ledger never found them: the ledger was right about the numbers it received, and the numbers were wrong before they arrived.
Other Steps Reviewed
The other seven steps were reviewed and found adequate for now. Sales orders require a customer number and are approved by customer service. Route sheets are printed from the system and signed by drivers. The sync from handheld to scan database is complete and logged. Ledger posting reconciles daily. The weaknesses are concentrated at the two points where serial data becomes totals, which is also where the new package will make its biggest change.
Why These Gaps Persisted
Both gaps have existed for years. Nobody designed them; they grew from reasonable choices, a void button added to help drivers fix mis-scans and a nightly job written when the scan database was added. Neither choice was reviewed as a control decision, because no one owned the holdings field until the governance brief assigned it.
Severity
For Halvorsen's financial statements, $18,000 a month of disputed rent is about $216,000 a year against $4.9 million of rent revenue. Individually and together, the gaps create a reasonable possibility that rent revenue and receivables are misstated by more than a trivial amount, and the auditors should be told in writing. Whether the combined deficiency is a material weakness depends on materiality for the year, which the auditors will set (American Institute of Certified Public Accountants, 2012).
Monitoring After the Fix
The branch operations manager will review void reason codes weekly, and the controller will review the daily comparison report until cutover. After cutover, the change log in the new package replaces both (Committee of Sponsoring Organizations of the Treadway Commission, 2013; Romney et al., 2021).
References
American Institute of Certified Public Accountants. (2012). Communicating internal control related matters identified in an audit (AU-C Section 265). AICPA.
Committee of Sponsoring Organizations of the Treadway Commission. (2013). Internal control: Integrated framework. COSO.
Romney, M. B., Steinbart, P. J., Summers, S. L., & Wood, D. A. (2021). Accounting information systems (15th ed.). Pearson.
What the AC550 Unit 9 assignment asks for
Unit 9 of AC550 asks you to assess the controls in a process and identify gaps. Summarize the gaps and their exposure first. Follow the process step by step in a table, stating for each step the evidence it leaves, whether that evidence survives to the financial record, and the application or general control expected there. Describe each gap: the missing control, the risk it creates and how large the exposure is, estimating where direct measurement is impossible. Propose a fix for each with an owner and a date, separating low-cost interim controls from permanent fixes. Explain why the gaps persisted. Assess severity in terms of possible misstatement and whom it must be reported to. Describe monitoring after the fix. Support the assessment with the control framework, the internal control communication standard and an accounting information systems text in APA 7.
How the AC 550 Unit 9 example is put together
The sample's summary names both gaps and the $18,000 monthly exposure on 468 accounts. A nine-step table follows the cycle, showing evidence surviving at order entry, dispatch and sync, compromised at the handheld and lost at the nightly transfer, with later steps inheriting the loss. The first gap section requires void reason codes and retention of voided scans. The second requires a daily comparison report with rent held where counts differ, until the job is retired. The highlighted sentence explains why ledger reviews never found the gaps. Sections cover the seven adequate steps, why the gaps persisted, severity at about $216,000 a year against $4.9 million of rent, and monitoring.
AC550 Unit 9 rubric: what earns full points
Control gap assessments in AC550 earn points for precise location of gaps and realistic remedies. Graders check the step table, the classification of expected controls as application or general, and the sizing of exposure. The rubric rewards separating interim controls from permanent fixes, assigning owners and dates, and explaining why gaps escaped existing reviews. Severity should be framed in terms of reasonable possibility of misstatement, with the duty to report to auditors noted. Monitoring after remediation shows completeness. Assessments that list generic control weaknesses, propose fixes without owners, or claim severity without reference to materiality lose credit. Reference COSO, the communication standard and the systems text in APA 7.
Common AC550 Unit 9 mistakes, and how to avoid them
Weak Unit 9 assessments list every possible control weakness without identifying where the actual evidence breaks. Exposure is described as significant with no estimate. Fixes are proposed without owners or dates, or only as a new system that is months away. Application and general controls are confused. Students declare a material weakness without considering materiality. Monitoring after the fix is forgotten, so there is no way to know the fix works. If your section's process differs, such as purchasing or payroll, a writer can build the step table and gap analysis for that cycle.
Get an AC550 Unit 9 example written to your instructions
Aim the custom assessment at whichever cycle the Unit 9 case covers: send the case along with any earlier narrative or flowchart, and the rubric. Every step is followed for the record it leaves, and each break is sized and assigned an owner. It returns within 24-48h, and your first custom sample is free. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More AC550 papers and MS in Accounting samples
- AC550 Unit 1: Data Capture Discussion
- AC550 Unit 2: Business Process Narrative
- AC550 Unit 3: Accounting System Flowchart
- AC550 Unit 4: System Requirements Analysis
- AC550 Unit 5: Software Selection Matrix
- AC550 Unit 6: Data Governance Brief
- AC550 Unit 7: System Implementation Plan
- AC550 Unit 8: Audit Trail Seminar Reflection
- AC550 Unit 10: Systems Evaluation Report
- AC507 Unit 9: Tax-Free Reorganization Case Study
- AC505 Unit 9: Capital Investment Analysis
- AC504 Unit 9: Board Governance Critique
- AC503 Unit 9: Auditor Going Concern Evaluation
AC550 Unit 9 questions, answered
What is the difference between application and general controls?
Application controls operate within a specific process: input edits, batch record counts, matching, output reconciliations. General controls operate across systems: access, change management and computer operations. A shared login is a general control failure affecting every application it reaches, and the assessment keeps the two families apart because different people own them.
What does a record count or hash total do in a batch transfer?
A record count confirms that the number of records received equals the number sent. A hash total sums a field with no business meaning, such as serial numbers, to show that the same records arrived unaltered. Either would reveal a partial or altered transfer the next morning, and the assessment proposes both, reconciled daily by billing.
Should the assessment propose a whole new system?
Only where the case asks. At Halvorsen the package selection is already underway, so the assessment separates interim controls, which cost little and start now, from permanent ones that depend on the new system. Graders tend to reward that distinction, since exposure continues every month until the replacement actually runs.
Where can I find a free AC550 Unit 9 sample paper?
This page holds a full AC550 Unit 9 control gap assessment of the cylinder rent cycle at Halvorsen Welding Supply with a nine-step evidence table, two gaps, sized exposure, fixes and APA 7 references.
Why use a daily comparison report before the new system arrives?
It is a low-cost interim control. Comparing each account's billing count with the scan database and holding rent where they differ stops most wrong bills now, while the permanent fix waits for cutover.