Do My Liberty ACCT 432 Course for Me

Week one covers auditing, internal control and IT governance. Project 1 is worth 50 points, and Forum 1 often asks about segregation of duties within the IT function: which duties must be kept apart and why.

Week two is about security: operating systems, networks and databases. Project 2 is worth 75, and Forum 2 asks for a security problem, such as weak password controls or an unreviewed firewall rule, and the control an auditor would test.

Week three covers systems development and program changes. Project 3, worth 75, usually turns on whether a change can reach production without independent approval and testing.

Week four studies how transactions are processed and reported. Project 4, the largest at 100 points, sits beside Forum 3 on the audit trail in a computerized system.

Week five covers computer-assisted audit tools and techniques. Project 5 is worth 60, and the group faith essay is due the same week.

Week six covers data extraction and analysis, with Project 6 worth 80; week seven covers the revenue and expenditure cycles, with Project 7 worth 75 and ACL Assignment 1 worth 80.

Week eight covers ERP systems and fraud, with Project 8 worth 90 and ACL Assignment 2 worth 125, in a week that ends on Friday.

Across the eight weeks the course moves from general controls, which protect the whole system, to application controls inside particular programs, and then to tools that let the auditor test the data directly.

Every project follows the same pattern, because it fits nearly every IT audit mini-case: the weakness in the case, the risk it creates, the control that would address it and the procedure an auditor would use to test it.

A program change case, for example, traces the path a change takes from request to production and finds the step where it can skip approval or testing, then recommends a control and the test that would detect a skipped step.

For the CAATT project, each tool is matched to its purpose: test data to check how a program handles chosen inputs, parallel simulation to reprocess real data with the auditor's own program, and embedded modules to monitor live transactions.

For the data extraction project and the ACL work, the tests are specific: duplicate payments to the same vendor for the same amount on the same date, gaps in check numbers, and payments to vendors added only days earlier.

Forum threads answer a problem from the approved list in a focused post with three scholarly citations, and replies to two classmates each carry a citation.

Every piece arrives before its deadline, ready for you to upload or post.

The CAATT answers also say when each tool is the better choice, since that is what Project 5 usually asks.

ACCT 432 coursework is done by an IT auditor, usually someone who has tested general and application controls at a public accounting firm or inside a company, often holding the CISA.

They write control findings for audit reports, which keeps the project answers short and precise, and they use data analysis tools on real engagements, which is what the ACL assignments call for.

A second reviewer checks each project and post before delivery, and one writer handles the whole term so the answers and terminology stay consistent from week one to week eight.

Your details stay with the coordinator. If a chapter is unclear before you read a project's answer, a short explanation can be sent, such as what an embedded audit module actually does.

Several have run SOX IT general control testing, which covers the same access, change and operations controls as the early chapters.

Project answers lose points when they describe the problem but stop before the control and the auditor's response, which is where most of each project's points sit.

Security answers lose points when they offer only a preventive control, since auditors expect a detective control as a second layer.

The week-four project loses points when its controls are not organized by input, processing and output, the way the chapter classifies them.

ERP cases in week eight lose points when they miss the real risk, which is usually role design: one user holding conflicting permissions inside a single integrated system.

Forum threads lose points without three scholarly citations, even though they are only 300 words long.

ACL assignments lose points when a test is run without a sentence explaining what its results mean for the audit.

Revenue and expenditure cycle cases in week seven lose points when the assertion being tested is not named.

Fraud questions lose points when the answer names the fraud but not the control that would have prevented or caught it.

Projects arrive a few days before each week closes, every week of the term.

In the forum weeks you have the thread within the first days and the two responses later in the week.

Your essay section is timed to the group's week-five cutoff; ACL work comes a few days ahead of weeks seven and eight closing.

Projects are priced by their points, the ACL assignments by their tests, and the forums and essay share are smaller lines. Booking the whole term in week one is the simplest and least expensive plan, and a late start covers only the weeks still ahead.

A late start is common in this course, since the first two projects are short; the plan then begins with Project 3.

If you have already submitted some projects, send the grades and comments so the later ones build on them.