ACC 680 Topic 1 analytic assertion coverage map example

Auditing and Data Analytics Core Grand Canyon University Free custom sample in 24 to 48h

This ACC 680 Topic 1 sample paper maps five planned audit data analytics to the assertions each can support for a distributor. It was written for GCU ACC 680, Auditing and Data Analytics Core, catalog code ACC-680, in the Grand Canyon University MS in Accounting. A three-way match of all 61,000 purchase invoices supports occurrence and accuracy, a shipping number gap test addresses revenue completeness, an aging rebuild supports the aging's accuracy, and a search of 4,300 later disbursements tests payables completeness. A revenue dashboard tests nothing and moves to risk assessment, and inventory existence, uncovered by any analytic, goes to the count.

CourseACC 680 Auditing and Data Analytics Core
TopicTopic 1
Paper typeAnalytic assertion coverage map
LengthAbout 990 words, 2 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramMS in Accounting
UpdatedSeptember 2026

Free sample paper for ACC 680 Topic 1

1

Which Assertion Does Each Analytic Test? A Coverage Map for Five Planned Procedures, One Reclassified and One Gap Left for the Count

[Author Name]

Colangelo College of Business, Grand Canyon University

ACC-680: Auditing and Data Analytics Core

Topic 1 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.

What this page is doingThe title states the map's organizing question and its two findings: an analytic that tests nothing and an assertion no analytic reaches. The company and figures are illustrative composites; the standards and sources are real.
2

Which Assertion Does Each Analytic Test? A Coverage Map for Five Planned Procedures, One Reclassified and One Gap Left for the Count

What Counts as Evidence

An audit data analytic counts as substantive evidence only if its result would support or contradict a named assertion for a named account. Running a procedure on all the data does not by itself make the result evidence of anything; what matters is whether a misstatement in a particular assertion would change the result (American Institute of Certified Public Accountants, 2020). This map applies that test to the five analytics planned for the audit of Halsey Industrial Supply, a composite distributor, and lists what remains untested.

The Coverage Grid

Account and assertion pairs run down the side and the five analytics across the top. A filled cell states why the analytic's result bears on that pair.

Table 1

Assertion Coverage by Analytic

Account and assertionThree-way matchShipping number gap testAging rebuildSubsequent disbursement searchRevenue dashboard
Purchases and payables, occurrenceSupports: each invoice traced to an order and a receipt
Purchases and payables, accuracySupports: price and quantity agreed to order and receipt
Payables, completenessSupports: payments after year end traced back to receipts before it
Revenue, completenessSupports: gaps in shipping numbers would reveal unbilled shipments
Receivables, valuationSupports accuracy of the aging the estimate relies on, not collectibility
Inventory, existenceNot covered; routed to the count

The Five Analytics

The three-way match compares all 61,000 purchase invoices for the year with purchase orders and receiving records, matching vendor, item, quantity and price within set tolerances. An invoice with no order or no receipt could be a fictitious purchase, and a price or quantity that differs could be an overbilling, so the match supports occurrence and accuracy of purchases and the payables they create.

The gap test lists shipping document numbers for the year and identifies any missing from the sequence. A shipment made but never billed would leave a shipping document with no matching invoice, so the test addresses completeness of revenue, provided the shipping numbers are system-assigned and cannot be skipped without a record.

The aging rebuild recomputes the receivables aging from invoice-level data, invoice by invoice, and compares it with the client's aging report. It supports the accuracy of the aging, which management uses to estimate the allowance. It does not test collectibility itself, which depends on customers' ability to pay and requires other evidence such as subsequent receipts.

The subsequent disbursement search examines all 4,300 payments made in the 45 days after year end and matches each to its receiving date. A payment for goods received before year end that was not recorded as a payable at year end is an unrecorded liability.

Direction

Three of the analytics, the three-way match, the aging rebuild and the dashboard, start from recorded transactions. They can find recorded items that should not be there or are wrong, but they cannot find items that were never recorded, so they bear on occurrence, accuracy and existence, not completeness. The subsequent disbursement search starts outside the payables ledger, from cash that actually left the bank, and traces back to the ledger. That direction is what lets it test completeness of payables. The shipping gap test also addresses completeness, because its population, shipping documents, is independent of the invoices it tests (Arens et al., 2020).

The Data Behind Each Analytic

Coverage on the map assumes the data are complete and accurate, and each analytic carries its own condition. The purchase invoice file must reconcile in count and total to purchases in the general ledger before the three-way match is run; otherwise invoices missing from the file would escape the test. The shipping document sequence must come from the warehouse system's own log, not from a list prepared by the sales team, or the gap test would inherit any omission in that list. The invoice-level receivables file must total to the receivables control account at year end. The disbursement file for the search must be the bank's own record of payments, downloaded by the audit team, since a client-prepared listing could omit the very payments the search is looking for.

Each condition is tested and documented before the analytic is run. A cell on the map is marked as covered only after its data condition is met.

The Dashboard Reclassified

The fifth planned analytic is a dashboard of revenue by customer and month. It is useful: it shows a spike in December sales to three distributors and a new customer that became the fifth largest in its first year. But it has no expectation, no threshold and no follow-up rule, so no result it produces would support or contradict any assertion. The map reclassifies it as a risk assessment procedure. Its findings, the December spike and the new customer, are carried to the risk assessment as indicators that revenue occurrence and cutoff deserve focused testing (American Institute of Certified Public Accountants, 2021).

What Remains Untested

The grid shows pairs that no analytic reaches. The most important is existence of inventory, which at $38 million is the largest asset on the balance sheet. No analytic of recorded data can establish that the goods physically exist, because the data would look the same whether or not they do. Existence is assigned to observation of the year-end physical count, with test counts traced to the final inventory listing.

Other pairs are assigned as follows. Occurrence of revenue is addressed by confirmation of receivables with the three distributors the dashboard highlighted and by cutoff testing of December shipments. Valuation of receivables beyond the aging's accuracy is addressed by testing cash received after year end. Rights to inventory held at third-party warehouses are addressed by confirmation with the warehouse operators.

Analytics can reach far more of the population than traditional selections, and they do change how evidence is gathered (American Institute of Certified Public Accountants, 2017). The map's purpose is to make sure that reach is not mistaken for coverage.

References

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.

American Institute of Certified Public Accountants. (2021). Understanding the entity and its environment and assessing the risks of material misstatement (Statement on Auditing Standards No. 145). 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 1 instructions ask for

ACC-680 opens with Topic 1, where students connect audit data analytics to assertions. Many papers describe analytics without naming what they prove. The assignment rewards maps that state when an analytic counts as evidence, set account and assertion pairs against each analytic with a reason for every filled cell, and address the data each analytic depends on. Students should explain direction of testing for completeness, reclassify analytics that test no assertion, list uncovered pairs and assign a procedure to each.

How this ACC 680 Topic 1 example is built

The finished map is a grid with accounts and assertions down the side and five planned analytics across the top; all figures are illustrative. A three-way match of all 61,000 purchase invoices against orders and receiving records supplies evidence on occurrence and accuracy for purchases and payables. A gap test on shipping document numbers addresses completeness of revenue. A receivables aging rebuilt from invoice-level data tests the accuracy of the aging that the valuation estimate relies on, not collectibility itself. A search of 4,300 disbursements in the 45 days after year end, matched to receiving dates, addresses completeness of payables from outside the ledger. The fifth, a dashboard of revenue by customer and month, tests no assertion, and the map reclassifies it as risk assessment. Existence of inventory is covered by no analytic and is routed to the count observation.

ACC 680 Topic 1 rubric: what Excellent looks like

Faculty grading the coverage map reward a reason in every filled cell. Excellent maps separate the aging's accuracy from collectibility. Credit goes to explaining that tests starting from recorded transactions cannot find unrecorded ones. The rubric values moving a dashboard with no expectation to risk assessment. The highest level lists every uncovered pair, inventory existence first, with the procedure assigned. Maps that equate testing the whole population with covering every assertion, or that leave the data behind each analytic untested, usually lose marks.

ACC 680 Topic 1 help before you submit

Marks drain away first from maps that list analytics by technique, matching, recomputation, visualization, without an assertion attached to any of them. A dashboard counted as evidence is the characteristic error, since a chart of revenue by month can prompt questions and cannot answer one. Papers that credit an analytic over recorded invoices with testing completeness have the direction reversed, and markers look for that reversal specifically. Claiming the rebuilt aging establishes collectibility overstates it; the rebuild shows the aging is arithmetically right, and valuation still needs evidence that the balances will be collected. Maps showing full coverage invite suspicion, because some assertions, inventory existence above all, need procedures no data file can replace. A last deduction goes to papers that never say what an analytic must do to count, leaving every cell in the grid unargued.

Get an ACC-680 Topic 1 example written to your instructions

Send the ACC-680 Topic 1 instructions, the rubric from your classroom and the client case or planned procedures your section was given. We write a custom example to them, with each analytic tied to a named account and assertion, direction checked, non-evidence reclassified and uncovered assertions routed to other procedures, back in 24 to 48 hours. The first one is free.

More ACC 680 papers and MS in Accounting samples

ACC 680 Topic 1 questions, answered

Is a data visualization ever audit evidence?

Rarely on its own. A chart can show where amounts cluster or change, which is valuable for deciding where to test, but it does not compare recorded amounts with anything that would confirm or contradict them. When a visualization is built on an expectation and differences from that expectation are investigated, the investigation produces evidence. The chart by itself belongs to risk assessment.

Why can't a three-way match test completeness?

Because it starts from invoices already recorded and checks that each has a matching order and receiving record. A purchase that was never recorded produces no invoice in the file, so the match cannot find it. Completeness needs a starting population the ledger did not generate, payments after year end or receiving records, traced back to see whether each liability was recorded.

How many analytics should a plan include?

As many as there are assertions they can genuinely address, and no more. A plan with twenty analytics clustered on occurrence has less coverage than one with five aimed at different assertions. The map exists to show that distribution. Where the assignment specifies the analytics, the example maps those, and it notes any assertion the specified set leaves uncovered.

Where can I find a free ACC 680 Topic 1 sample paper?

The whole map is above: what counts as evidence, the coverage grid, the five analytics, the data behind each, direction, the reclassified dashboard and what remains untested. Share your planned analytics and the accounts they cover for a free worked map.

Why is the dashboard reclassified in ACC 680 Topic 1?

It has no expectation, threshold or follow-up rule, so no result could support or contradict an assertion; its findings feed risk assessment instead.