ACC 337 Topic 2 data preparation log example

Introduction to Accounting Analytics Grand Canyon University Free custom sample in 24 to 48h

This ACC 337 Topic 2 sample paper is a data preparation log for a trucking company's merged invoice extract, opening with 48,000 raw lines worth $12,480,000. It belongs to GCU ACC 337, Introduction to Accounting Analytics, the course listed as ACC-337 in the Grand Canyon University BS in Accounting. Each numbered step states its rows and dollar effect: 312 overlapping lines removed for $96,000, 1,140 credit memos re-signed for $420,000, 86 ambiguous dates flagged rather than dropped and 214 vendor spellings mapped to 61 IDs. The final $11,964,000 agrees to the general ledger, monthly checks guard against offsetting errors and the steps are saved to rerun next quarter.

CourseACC 337 Introduction to Accounting Analytics
TopicTopic 2
Paper typeData preparation log
LengthAbout 960 words, 2 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramBS in Accounting
UpdatedSeptember 2026

Free sample paper for ACC 337 Topic 2

1

Five Numbered Steps From $12,480,000 to $11,964,000: A Data Preparation Log for Mesa Freight's Merged Invoice Extract

[Author Name]

Colangelo College of Business, Grand Canyon University

ACC-337: Introduction to Accounting Analytics

Topic 2 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 gives the starting and ending totals, because a preparation log is judged on whether every dollar between them is explained. Mesa Freight and all figures are illustrative composites.
2

Five Numbered Steps From $12,480,000 to $11,964,000: A Data Preparation Log for Mesa Freight's Merged Invoice Extract

The Extract and Why It Needed Preparing

Mesa Freight, a composite regional trucking company, moved its accounts payable from an older system to a new one in March. The controller wants to analyze vendor invoices for the first half of the year, looking for duplicate payments and unusual price changes. The data comes from two extracts, one from each system, combined into a single file of invoice lines. Before any analysis, the file has to be made consistent: each row one invoice line, each field one kind of value, with signs, dates and names meaning the same thing in every row. Data arranged this way, one observation per row and one variable per column, is far easier to analyze correctly (Wickham, 2014).

The log below records every change, in order, with the number of rows it affected and its dollar effect. The first line records the raw extract before anything is touched, so every later figure can be traced back to it. All figures are illustrative.

The Log

Table 1 is the preparation log.

Table 1

Data Preparation Log, Invoice Lines, January to June

StepChangeRows affectedDollar effectRunning rowsRunning total
0Raw extract as received, both systems combined48,000$12,480,000
1Remove lines duplicated where the two systems' extracts overlapped during the migration fortnight312(96,000)47,68812,384,000
2Re-sign credit memos the older system stored as positive amounts with a type flag1,140(420,000)47,68811,964,000
3Convert text dates from the older system to dates; flag rows whose day and month could be read either way86 flagged, none removed047,68811,964,000
4Standardize vendor names: trim spaces, fix case, map 214 spellings to 61 vendor IDs6,410047,68811,964,000
5Agree the total to the general ledger: invoices posted, January to June47,688$11,964,000 agrees

Step 1: Overlapping Extracts

For two weeks in March, invoices were entered in both systems while staff tested the new one. Both extracts include those lines. Matching on vendor, invoice number, date and amount found 312 lines present in both, totaling $96,000, and the older system's copies were removed. The match was exact on all four fields; lines that matched on three fields but not the fourth were examined individually and kept, because a true duplicate would agree on all four.

Step 2: Credit Memos Stored as Positive Amounts

The older system stored credit memos, amounts vendors owed back to Mesa Freight, as positive numbers with a type code of CM. The new system stores them as negative numbers. Left as they were, the 1,140 older credit memos, with a face value of $210,000, would have been added to the total instead of subtracted. Re-signing them lowers the total by $420,000, twice their face value, because each moves from adding $210,000 in total to subtracting it. This is the step most likely to be missed, and it is the one that would most distort a duplicate payment test, since a credit memo and the invoice it reverses would look like two payments.

Step 3: Ambiguous Dates

The older system exported dates as text in day, month, year order; the new system uses month, day, year. Converting the older dates was straightforward except for 86 rows where both the day and the month were 12 or below, such as 04/05, which could be April 5 or May 4. For 71 of them the invoice number sequence settled the date. The other 15 were flagged and kept rather than dropped, since dropping them would remove $38,000 of real invoices from the analysis; they will be excluded only from tests that depend on the exact date.

Step 4: Vendor Names

The same vendor often appeared under several spellings, such as "Pioneer Tire," "PIONEER TIRE INC" and "Pioneer Tire Inc." with a trailing space. Mapping 214 spellings to 61 vendor IDs affected 6,410 lines and changed no amounts, but it matters for the analysis: without it, a duplicate payment to the same vendor under two spellings would not be caught.

Checks Beyond the Grand Total

A single grand total can agree while errors offset inside it, so three further checks were run. First, the prepared total was agreed month by month to the ledger, not just for the half year; all six months agreed, which rules out a March error hidden by an opposite error in June. Second, the count of negative lines was compared with the count of credit memos in the older system's credit memo report, 1,140 in both. Third, the number of distinct vendors after step 4, 61, was compared with the active vendor list in the new system, which has 63; the two vendors with no invoices in the period were confirmed as inactive.

None of these checks changed the data. They are recorded in the log because a later reader, perhaps an auditor reviewing the duplicate payment results, will want to know not only that the total agreed but that it agreed for the right reasons.

Agreeing to the Ledger

The prepared total of $11,964,000 agrees with the general ledger's total of invoices posted from January through June. That agreement is the evidence that preparation neither lost nor invented anything. Had the totals differed, the log would show at which step the difference arose, since each step restates the running total. Audit data analytics guidance stresses establishing that the data used is complete and accurate before relying on the results (American Institute of Certified Public Accountants, 2017), and this reconciliation is how that is shown.

The log, the matching rules and the script that performs each step are saved together, so the preparation can be rerun on the next quarter's extract and produce the same results (Sandve et al., 2013).

References

American Institute of Certified Public Accountants. (2017). Guide to audit data analytics. AICPA.

Sandve, G. K., Nekrutenko, A., Taylor, J., & Hovig, E. (2013). Ten simple rules for reproducible computational research. PLoS Computational Biology, 9(10), Article e1003285. https://doi.org/10.1371/journal.pcbi.1003285

Wickham, H. (2014). Tidy data. Journal of Statistical Software, 59(10). https://doi.org/10.18637/jss.v059.i10

What the ACC 337 Topic 2 instructions ask for

The Topic 2 instructions in ACC-337 ask students to document how a dataset was prepared for analysis. Weak submissions describe cleaning in general terms. The assignment rewards logs that record the raw extract's row count and total before any change, then list each change as a numbered step with the rows affected, the dollar effect and the running total. Students should explain the reasoning behind each step, keep uncertain records flagged rather than silently dropped, agree the prepared total to the general ledger and describe further checks that would catch offsetting errors.

How this ACC 337 Topic 2 example is built

The finished log is a numbered table, one row per change, and it opens with the raw extract's row count and dollar total before anything is touched: 48,000 lines and $12,480,000. Step one removes 312 lines duplicated where the two systems' extracts overlapped during the migration, taking out $96,000. Step two re-signs 1,140 credit memos the older system stored as positive amounts with a type flag, which lowers the total by $420,000, twice their $210,000 face value. Step three converts dates stored as text in the old system and flags 86 rows whose day and month could be read either way, keeping them rather than dropping them. After each step the log restates the running total, and the final $11,964,000 is agreed to the general ledger's figure for invoices posted in the same period.

Where the marks sit in the ACC 337 Topic 2 rubric

Faculty grading the preparation log reward a total that can be traced. Excellent logs start from the raw count and restate the running total after every step. Credit goes to handling system differences such as credit memos stored as positive amounts, and to explaining why re-signing changes the total by twice their face value. The rubric values flagging ambiguous records instead of deleting them. The highest level agrees the result to the ledger month by month and saves the steps to rerun. Logs that report only a final clean total usually lose marks.

ACC 337 Topic 2 help: mistakes that cost marks

Cleaning performed without a record is the loss markers find first on this assignment, since a total that changed with no explanation cannot be trusted by anyone downstream. Logs listing the steps but not their effect on rows and dollars describe the work without letting a reader judge it. Dropping every problem row is a frequent shortcut, and here it would have discarded 86 real invoices along with their amounts. Treating credit memos as ordinary invoices overstates purchases, and the error stays invisible until the total is compared with the ledger. A preparation log that ends without that comparison has no evidence the cleaned file is right. Papers that hurry through preparation to reach the charts usually omit the reasoning behind each fix, which is the part a later reader relies on most.

Get an ACC-337 Topic 2 example written to your instructions

Send the ACC-337 Topic 2 instructions, the rubric in your classroom and a description of the dataset your section provided. The custom example comes written to those criteria, with raw totals captured, each change logged with its rows and dollars, doubtful records flagged rather than dropped and the cleaned file tied to a control figure, in 24 to 48 hours. The first is free.

More ACC 337 papers and BS in Accounting samples

ACC 337 Topic 2 questions, answered

Why not simply delete rows that look wrong?

Because a row that looks wrong is often a real transaction recorded under a different convention. Deleting it removes the amount from every total that follows, and nobody downstream can tell it happened. Flagging it keeps the money in the data while letting a particular question exclude it on purpose. Deletion is right for true duplicates and test records, and even then the log should say how many and how much.

What is a control total for?

Proving that cleaning changed only what it was meant to change. Record the row count and dollar total of the raw extract, restate them after every step, and compare the final figure with an independent source such as the general ledger. When the two agree, the preparation is supported by evidence; when they differ, the log shows at which step the gap appeared, which is usually where the mistake is.

How much detail belongs in the log?

Enough for a colleague to repeat each step on the raw file and reach the same result. That means the rule applied, stated precisely, the rows it affected and the effect on the total. Keystrokes and screenshots are unnecessary. Where a step needed judgment, such as deciding which date format a row used, a sentence on how the judgment was made is worth more than any amount of mechanical detail.

Where can I find a free ACC 337 Topic 2 sample paper?

The complete log sits above, with the extract, the numbered steps, overlapping extracts, credit memos, ambiguous dates, vendor names, checks beyond the total and agreement to the ledger. Share your extract for a free worked log.

Why does re-signing lower the total by $420,000 in ACC 337 Topic 2?

The $210,000 of credit memos were being added instead of subtracted, so correcting them removes the $210,000 wrongly added and subtracts $210,000 more.