Take My Liberty ACCT 660 Class

ACCT 660 reads Nigrini's Forensic Analytics from cover to cover, two to four chapters a week. The book is a practitioner's manual for finding fraud in data, and the course treats it that way.

The first chapters introduce forensic analytics and the work of preparing data, where the first question is always whether the data are complete and accurate.

The middle chapters cover the digit-based tests for which Nigrini is known, including Benford's law, the second-order test and the last-two-digits test, each of which can expose invented numbers in a different way.

Later chapters turn to tests of relative size and correlation, number duplication, and the matching of records such as vendor addresses against employee files.

Closing chapters ask whether forensic tests should run all the time rather than only after a red flag.

Running beside the reading is a term project on one recent case where computers and systems were the fraudster's tools. Payroll manipulation, altered ERP entries, insider data theft and vendor schemes run through payables systems all qualify.

A Monday start opens the term; from then on Liberty's Saturday-to-Friday week sets every deadline.

Data preparation gets more attention than students expect, since a test run on incomplete data proves nothing. The early chapters spend real time on it.

Several chapters show how to run the tests in common software, which the forums often ask about.

ACCT 660 runs on three tracks: forums in alternate weeks, outlines kept as the reading goes, and the project from topic to detection plan.

Each forum thread is long, at least 750 words with three scholarly references, and it answers its prompt from the chapters just read. Two replies follow in the next week.

The reading outlines are built as a field manual. Every test in the book gets its own entry, written so you could pick it up later and run it.

The project company is chosen by week two from cases with enough public reporting, news coverage, SEC filings or Justice Department releases, to support a full background.

Part 1 tells the case's story with the systems in the foreground, so the weak point is plain.

Part 2 then matches Nigrini's tests to those facts and shows how each would have flagged the scheme. It also considers how a biblical worldview shapes the approach to the case.

Every item is delivered as a file you can read and adjust before submitting.

Replies take up a classmate's point and add references of their own. They engage the argument rather than agreeing with it.

The topic submission in week two is handled as part of the project, so the company is settled before the research begins.

Outlines are written as a reference you can keep.

ACCT 660 goes to a forensic data analyst, usually a CPA or CFE who runs analytic tests on investigations or internal audits.

They have applied Benford's law, duplicate tests and relative size factors to real ledgers. That makes the forums and outlines practical rather than theoretical.

Their familiarity with reported technology frauds makes it easy to find a case with a deep public record.

Many have built continuous monitoring routines for clients, which is the subject of the final forum.

Each forum, outline and project part is reviewed by a second analyst before release. A single analyst sees your course through.

Only the coordinator knows your name. If a test in the reading is unclear, a short worked example can be sent.

They write in plain terms for readers who are not data specialists.

Their examples come from real ledgers rather than textbook exercises.

The reading pace is the first difficulty. Four chapters in week one and two a week after that, all technical, add up quickly.

The outlines are the second. Each chapter needs at least a double-spaced page of substantive notes, and outlines that copy headings without content lose points.

The forums are the third, since a 750-word thread with three scholarly references is closer to a short paper than a discussion post.

Choosing the project company is the fourth. A fraud with little public reporting cannot support 2,000 words of background, and one where technology played no real part does not fit the brief.

Part 2 is the fifth, since a plan for catching the fraud can only be as specific as the story behind it. Students who wrote a general background find little to build on.

The digit tests themselves trip students who can describe Benford's law but cannot say what a failed second-order test means.

Long replies add to the load, since each must reach 250 words with its own references.

Matching tests, such as vendor addresses against employee records, are easy to describe and hard to explain well, since false matches have to be ruled out.

Booking before the term starts leaves the opening week for a long first thread and four chapters of reading.

Threads land at the start of their weeks; replies follow your classmates. The topic choice is settled before week two closes.

The first outline comes in week three and the second in the final week, each ahead of its Friday.

Project Part 1 is delivered in week four and Part 2 in week seven, in each case before the deadline.

The two project parts are the largest lines, then the forums and the outlines. A start after week two is quoted from the next item due.

Each forum is one line covering its thread and replies, and booking the full term lowers every line.

Every delivery arrives as a file you can edit before submitting.