| Course | ACC 680 Auditing and Data Analytics Core |
|---|---|
| Topic | Topic 6 |
| Paper type | Analytic evidence working paper |
| Length | About 1,010 words, 2 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | MS in Accounting |
| Updated | September 2026 |
Free sample paper for ACC 680 Topic 6
Working Paper R-7: Revenue Occurrence Tested by Matching Every Invoice to Cash, With $5.6 Million of Differences Resolved Line by Line
[Author Name]
Colangelo College of Business, Grand Canyon University
ACC-680: Auditing and Data Analytics Core
Topic 6 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.
Working Paper R-7: Revenue Occurrence Tested by Matching Every Invoice to Cash, With $5.6 Million of Differences Resolved Line by Line
Reference and Assertion
Reference: R-7. Client: Summit Industrial Fasteners, a composite manufacturer. Period: year ended December 31. Assertion: occurrence of revenue. Prepared by: [Preparer], date. Reviewed by: [Reviewer], date. Every block below answers to the assertion: whether revenue recorded in the year represents sales that actually took place.
Data Sources
Source 1, invoice table. Obtained from the billing system by the client's systems analyst on January 18, using a query written by the audit team and run while a team member observed. The table contains 52,400 invoices for the year. Completeness and accuracy: the invoice table was reconciled to revenue in the general ledger, $214.0 million, in total and by month, with no differences; invoice numbers were checked for gaps and duplicates, with none found.
Source 2, bank receipts. Downloaded by the audit team directly from the bank's online portal, using read-only credentials provided by the client's treasurer, for all operating accounts, covering January 1 through February 28 of the following year. The file contains 49,800 receipt lines. Completeness and accuracy: the file's opening and closing balances for each account were agreed to the bank statements confirmed directly with the bank at C-2. Obtaining this file independently matters because a receipts file supplied by the client could be altered, and the analytic's value rests on the cash coming from outside the company (American Institute of Certified Public Accountants, 2020).
Parameters
The parameters were set and recorded on January 20, before the run. An invoice is matched if a receipt exists from the same customer, identified by bank account and remittance reference, for the invoice amount within $1, received on or after the invoice date and no later than February 28. The $1 tolerance allows for bank rounding and small currency differences on the few foreign customers; a wider tolerance would admit partial payments as matches. The two-month cutoff after year end allows year-end invoices a normal collection period while keeping the test within fieldwork.
Execution Record
Script: rev_cash_match, version 1.3, stored in the engagement file with its code. Run date: January 21. Run by: [Preparer]. Rows in: 52,400 invoices and 49,800 receipt lines. Rows out: 50,960 invoices matched and 1,440 unmatched. A second run on January 22 by the reviewer produced identical counts.
Results
Matched invoices total $208.4 million, 97.4 percent of recorded revenue. For these invoices, cash was received from the customer named on the invoice, for the invoiced amount, after the invoice date. That is strong evidence that the sales occurred, because the evidence of payment originates with the customer and the bank rather than with the company.
Differences
The unmatched invoices total $5.6 million. Each part is resolved and cross-referenced.
Table 1
Resolution of Unmatched Invoices
| Difference | Amount | Resolution | Cross-reference |
|---|---|---|---|
| Receivables still open at February 28 | $4.1 million | Carried to receivables confirmation; 88 percent of the balance confirmed without exception | C-4 |
| Credit memos issued after year end against December invoices | $1.2 million | Sent for cutoff testing to determine whether the December sales should have been recorded | R-9 |
| Invoices with no receipt, no open balance and no credit memo | $0.3 million | Written off in January as billing errors; revenue overstated | Summary of misstatements |
| Total | $5.6 million |
Notes on the Differences
The open receivables are not a problem for occurrence in themselves; they have simply not been paid yet, and confirmation replaces the missing cash evidence for them (Arens et al., 2020). The credit memos are more significant. December sales reversed in January can indicate shipments made to meet a target that customers never wanted, so the $1.2 million is tested for cutoff rather than accepted. The $0.3 million had been billed in error and reversed through bad debt expense rather than revenue, so recorded revenue is overstated by that amount; it is below the clearly trivial threshold but is recorded on the summary for completeness.
What the Analytic Does Not Establish
The match supports occurrence. It does not establish that revenue was recorded in the right period: a sale shipped in January but invoiced in December would still be paid and would match. Cutoff is tested separately at R-9 by comparing shipping dates with invoice dates for the last and first ten days of the year. Nor does the match establish that revenue was measured correctly under the contract terms, such as volume rebates owed to customers, which are tested at R-11 against rebate agreements. A matched invoice could also be paid by a related party posing as a customer. The customer master file was therefore compared with vendor and employee records for shared bank accounts and addresses; no matches were found. Finally, the analytic says nothing about revenue that should have been recorded and was not. Completeness of revenue rests on the shipping document gap test at R-5.
Points Raised in Review
The reviewer asked why receipts were matched by bank account and remittance reference rather than by customer name. Names in bank data are often truncated or abbreviated, and matching on them would have produced false exceptions; bank account numbers from the customer master were agreed to remittance advice for a sample of 40 customers before the run. The reviewer also asked whether any single customer paid unusually large amounts shortly after year end. Three customers accounted for 22 percent of February receipts; their December invoices were included in the cutoff selection at R-9.
Conclusion
Subject to the results of cutoff testing at R-9 and confirmation at C-4, revenue of $213.7 million is supported as having occurred, and $0.3 million is recorded as a misstatement. Matching every invoice to independent cash evidence covered the full population in a way a sample could not (American Institute of Certified Public Accountants, 2017).
Reviewer sign-off: [Reviewer], date. The reviewer re-ran the script and agreed the results and cross-references. The analytic was designed as a substantive procedure, not only an analytical review, because it compares each item with external evidence rather than comparing a total with an expectation (American Institute of Certified Public Accountants, 1988).
References
American Institute of Certified Public Accountants. (1988). Analytical procedures (Statement on Auditing Standards No. 56). AICPA.
American Institute of Certified Public Accountants. (2017). Guide to audit data analytics. AICPA.
American Institute of Certified Public Accountants. (2020). Audit evidence (Statement on Auditing Standards No. 142). AICPA.
Arens, A. A., Elder, R. J., Beasley, M. S., & Hogan, C. E. (2020). Auditing and assurance services: An integrated approach (17th ed.). Pearson.
What the ACC 680 Topic 6 instructions ask for
The Topic 6 instructions in ACC-680 ask students to document an audit data analytic as evidence. Weak submissions report results without their inputs. The assignment rewards working papers that state the reference and assertion, document each data source with how it was obtained and tested, fix parameters before the run and record the script, version, date and row counts. Students should present results in dollars and percentage, resolve every difference with cross-references, state what the analytic does not establish and close with a conclusion and sign-off.
How this ACC 680 Topic 6 example is built
At the top of the finished paper sit its reference, R-7, sign-off fields for preparer and reviewer, and the assertion it serves: occurrence of revenue. Figures throughout are illustrative. Two sources feed it: the billing system's invoice table, reconciled before use to recorded revenue of $214 million, and a bank receipts file the audit team downloaded from the bank's portal itself. Parameters were fixed first: a match on customer, amount within $1 and receipt within two months of year end. The script, its version and run date are recorded. Invoices worth $208.4 million, 97.4 percent of revenue, match cash. The unmatched $5.6 million splits three ways: $4.1 million of receivables still open, cross-referenced to the confirmation paper; $1.2 million of credit memos issued after year end, sent for cutoff testing; $0.3 million carried to the summary of misstatements.
Where the marks sit in the ACC 680 Topic 6 rubric
Faculty grading the working paper reward inputs a reviewer can trust. Excellent papers obtain the bank file directly rather than from the client. Credit goes to parameters dated before the run with reasons for each tolerance. The rubric values resolving unmatched amounts line by line with cross-references. The highest level states that matching supports occurrence but not cutoff or completeness. Working papers that report a match rate without the data tests behind it, or leave differences unresolved, usually lose marks.
ACC 680 Topic 6 help before you submit
Working papers for analytics are marked hardest on the data section, since an unmatched percentage computed from untested inputs is not evidence of anything. Describing the invoice extract without reconciling it to recorded revenue leaves open the chance that the analytic ran on part of the population. A bank file obtained from the client rather than directly weakens the external side of the match, and reviewers ask where it came from. Parameters with no date, or dated after the results, suggest tolerances adjusted until the match looked acceptable. Reporting the 97.4 percent and stopping leaves $5.6 million unexplained, which is exactly where occurrence risk would sit. Missing script versions make the result impossible to reproduce, and a paper nobody can reproduce fails the documentation standard, which asks that an experienced auditor new to the engagement could follow the work.
Get an ACC-680 Topic 6 example written to your instructions
Send the ACC-680 Topic 6 instructions, the rubric and the analytic or engagement case your section is documenting. We write a custom example to them, with the assertion named, each data source tested and described, parameters dated before the run, the execution recorded, differences resolved and cross-referenced and a reviewer-ready conclusion, back in 24 to 48 hours. The first one costs nothing.
More ACC 680 papers and MS in Accounting samples
- ACC 680 Topic 1: Analytic Assertion Coverage Map
- ACC 680 Topic 2: Benford Screen Risk Memo
- ACC 680 Topic 3: Journal Entry Testing Workpaper
- ACC 680 Topic 4: Exception Triage Log
- ACC 680 Topic 5: Full Population Testing Dq Post
- ACC 680 Topic 7: Substantive Analytic Simulation
- ACC 680 Topic 8: Review Note Response Memo
- ACC 670 Topic 6: Distress Model Miss Analysis
- ACC 669 Topic 6: Redemption Attribution Memo
- ACC 663 Topic 6: Coverage Needs Calculation
- ACC 653 Topic 6: Value Chain Linkage Analysis
ACC 680 Topic 6 questions, answered
Why test data the client produced?
Because the analytic's result depends entirely on it. Information produced by the entity may be incomplete, filtered or altered, deliberately or by a faulty report, and an analytic run on a partial extract can show a clean match over the wrong population. Reconciling the extract to the general ledger and understanding how it was produced gives the auditor grounds to treat the output as covering what it claims to cover.
What makes an analytic reperformable?
A second auditor holding the working paper should be able to obtain the same data, apply the same parameters with the same script and reach the same figures. That requires the sources and extraction details, the dated parameters, the script name and version, and the row counts in and out. Where any of these is missing, a reviewer has to trust the preparer, which documentation standards are designed to avoid.
Does a high match rate settle occurrence?
It supports occurrence strongly for the matched portion, since cash received from customers is evidence from outside the company. The unmatched remainder is where the assertion's risk concentrates, so the paper resolves it rather than treating 97.4 percent as close enough. A high rate with an unexplained remainder is a partial result, and the conclusion should be limited accordingly.
Where can I find a free ACC 680 Topic 6 sample paper?
The complete working paper appears above: reference and assertion, data sources, parameters, the execution record, results, differences, notes on them, what the analytic does not establish, points raised in review and the conclusion. Send your data sources for a free worked paper.
How is the $5.6 million resolved in ACC 680 Topic 6?
$4.1 million of open receivables goes to confirmation, $1.2 million of later credit memos to cutoff testing and $0.3 million to the summary of misstatements.