









Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
The core of the ACCT 331 Audit & Assurance course is the systematic process an independent auditor follows to determine if a company's financial statements are presented fairly. It begins with Foundation (ethics and legal responsibility), moves to Planning (understanding the client and assessing high-risk areas using the RMM model), continues with evaluating and **Testing Controls** for efficiency, and culminates in Substantive Procedures where direct evidence (like confirmations and recalculations) is gathered for account balances; the entire process concludes with a final review of Subsequent Events and the issuance of the Audit Opinion (Unmodified, Qualified, or Adverse) which communicates the auditor's final verdict to users.
Typology: Study notes
1 / 17
This page cannot be seen from the preview
Don't miss anything!










Total Risk (RMM) = Natural Danger (IR) × Weak Security (CR)Of course! Here is a rewritten version of your notes with a fresh, unique structure and engaging new analogies while maintaining 100% accuracy.
Forget just checking numbers. The smart auditor's first move is to crack the client's security system. Internal Controls are the company's own antivirus software—the rules and tools management installs to stop errors and hackers (including fraudulent employees) before they cause a disaster. Our mission: See if this "software" is actually running, or if it's just unused bloatware.
Before we test anything, we need the system architecture. We use the industry- standard COSO Framework, which is like the five core components of any security suite.
Our Finding: Control Risk (CR) is Low. The client's security is strong. Our Move: We can accept a Higher Detection Risk (DR). Translation: We can be more efficient. We do LESS of our own tedious number- checking later because we trust their system. This is the efficiency win we were hoping for. SYSTEM COMPROMISED (Controls Are Weak):
Procedure What It Means Why We Use It Inspection of Records/Docume nts Examining client documents (internal or external). To check Existence (Did this sale really happen?) or Completeness (Did they record all liabilities?). Inspection of Tangible Assets Physically counting inventory, cash, or fixed assets. The best way to test the Existence and Valuation of physical assets. Observation Watching client personnel performing their duties. Helps with understanding controls, but weak for substantive testing.
Financial Statement Assertion What We are Testing Example Substantive Procedure Existence (Overstatement Risk) Did the sale/A/R actually occur? Confirmation: Send requests to a sample of customers asking them to confirm the outstanding balance. Completeness (Understateme nt Risk) Were all sales that occurred actually recorded? Tracing: Trace a sample of shipping documents (evidence of
journal and accounts receivable ledger. Cutoff (Timing Risk) Were sales recorded in the correct period? Review sales recorded near year-end (a few days before and after) to ensure the shipment date matches the recognition date. Valuation Is Accounts Receivable stated at the net realizable value (A/R less the allowance for doubtful accounts)? Testing Estimates: Scrutinize the client's allowance for doubtful accounts calculation, focusing on old, past-due balances and general economic conditions.
Financial Statement Assertion What We are Testing Example Substantive Procedure Completeness (Understateme nt Risk) Were all purchases and resulting liabilities recorded? Search for Unrecorded Liabilities: Examine cash disbursements made
the new year) and trace them
at year-end but was omitted. Existence Do these recorded liabilities actually exist? Confirmation: Confirm balances with major vendors (especially vendors with zero or unusually small balances— testing for omissions). Accuracy Were purchases and accounts payable correctly calculated? Recalculation: Check the mathematical accuracy of a sample of vendor invoices and compare them to the general ledger recording. Cutoff Were purchases recorded in the correct period? Review receiving reports for inventory received near year-end and match the receipt date to the liability recording date.
Module 5 focuses on stepping back from individual transactions to view the entire picture, which includes the financial statements as a whole. We finish the fieldwork and deliver the most anticipated document in business: the Audit Opinion.
asserts they have met their responsibilities, such as preparing the statements, and have provided all relevant information, including disclosure of all known frauds, unrecorded liabilities, and subsequent events. * Crucial Note: It serves as evidence but does not replace other evidence. We can’t use it to excuse ourselves from testing cash, but it does provide legal backing and requires management to formally take responsibility.