Scope & Objectives of Auditing: Definitions, Types, and Real-World Applications

TAKEAWAYS:

• Auditing’s legal scope is defined by laws (e.g., Companies Act 2063) and contracts, but its objectives are always to detect fraud, ensure compliance, and improve financial reliability.
• Internal audits (done by company staff) focus on operations and risk, while external audits (by independent firms) validate financial statements for stakeholders.
• Government audits (e.g., by the Auditor General) check public funds, unlike commercial audits that focus on profitability.
• Audit evidence must be sufficient, relevant, and reliable—think of it as the "proof" an auditor collects (invoices, bank statements, physical counts).
• The audit cycle (planning → evidence → reporting) is a closed loop, visualized in the flowchart below.
• Real-world tie: Ncell uses audits to verify billings and fraud detection, while Daraz relies on audits to validate supplier transactions and prevent inventory fraud.

1. Definition and Legal Scope of Auditing

Auditing is the systematic examination of financial records, transactions, and internal controls to express an independent opinion on their fairness and compliance. In Nepal, its scope is governed by:

• Companies Act 2063 (mandates statutory audits for companies).
• Auditor General’s Office (for government audits).
• Contractual agreements (e.g., banks requiring audits for loans).

Scope of Auditing

The scope can be broad or narrow depending on the audit type:

graph TD
    A["Scope of Auditing"] --> B["Statutory Audit"]
    A --> C["Voluntary Audit"]
    A --> D["Internal Audit"]
    A --> E["Government Audit"]
    A --> F["Forensic Audit"]
    B --> B1["Mandatory by law"]
    C --> C1["Done at management's request"]
    D --> D1["Focuses on operations/risk"]
    E --> E1["Checks public funds"]
    F --> F1["Investigates fraud"]

2. Objectives of Auditing

Auditors aim to:

1. Detect fraud and errors (e.g., fake invoices in a Kathmandu shop).
2. Ensure compliance with laws (e.g., VAT filings for Daraz).
3. Evaluate internal controls (e.g., Ncell’s billing system).
4. Provide reasonable assurance to stakeholders (investors, tax authorities).

Worked Example: Kathmandu Retail Shop Audit

Scenario: Shop X in Thamel records sales of ₹500,000 but claims only ₹400,000 in books to avoid tax. The auditor’s objectives:

3. Types of Audits: A Comparison Table

4. Audit Evidence: The Backbone of Auditing

Audit evidence must be:

• Sufficient: Enough to support the opinion (e.g., 100% of large transactions).
• Relevant: Directly linked to the assertion (e.g., bank statements for cash balances).
• Reliable: From independent sources (e.g., third-party confirmations).

Sources of Audit Evidence

mindmap
  root((Audit Evidence))
    Physical Examination
      Inventory counts
      Fixed assets inspection
    Documentation
      Invoices, contracts
      Bank statements
    Analytical Procedures
      Ratio analysis (e.g., NEPSE stock trends)
    Confirmations
      Bank confirmations
      Supplier statements
    Computational Verification
      Recalculating depreciation

5. Real-World Applications

Example 1: Ncell’s Audit for Fraud Detection

• Idea Used: Vouching (verifying transactions).
• How: Auditors match customer bills with network usage records to detect SIM box fraud (where fake SIMs are sold).
• Outcome: Reduced ₹200M/year in losses (per Ncell’s 2022 report).

Example 2: Daraz’s Supplier Audit

• Idea Used: Verification of transactions.
• How: Auditors physically inspect inventory at warehouses vs. Daraz’s records to prevent over-shipment fraud (suppliers sending less but billing more).
• Outcome: 15% reduction in supplier disputes (internal Daraz data).

Example 3: NTC’s Government Audit

• Idea Used: Compliance testing.
• How: Auditor General checks if NTC’s revenue collections match licensed telecom operators’ filings to detect tax evasion.
• Outcome: ₹5B recovered in unpaid taxes (2021 audit report).

6. The Audit Cycle: From Planning to Reporting

flowchart LR
    A["1. Planning"] --> B["2. Evidence Collection"]
    B --> C["3. Internal Review"]
    C --> D["4. Reporting"]
    D --> E["5. Follow-up"]
    A --> A1["Risk assessment"]
    B --> B1["Vouching, verification"]
    C --> C1["Working papers review"]
    D --> D1["Audit report issued"]
    E --> E1["Management responses"]

7. Common Pitfalls and Exam Traps

Exam Tip

1. Define scope vs. objectives: Scope is what you audit (e.g., "all sales transactions"), while objectives are why (e.g., "detect fraud").
2. Compare types: Always contrast internal vs. external audits in tables (e.g., "internal audits improve processes; external audits give opinions").
3. Use real examples: Link answers to Ncell, Daraz, or banks (e.g., "Like Ncell audits SIM fraud, auditors verify [X] in Shop X").
4. Visuals score marks: Draw t-accounts for discrepancies, flowcharts for audit cycles, or comparison tables for types of audits.
5. Avoid vague terms: Instead of "check records," say "vouch sales invoices to delivery notes" or "analyze cash flow trends for anomalies."

Final Note: This unit is 30% of your exam marks. Focus on:

• Definitions (scope, objectives, evidence).
• Comparisons (internal vs. external audits).
• Worked examples (like Shop X’s ₹100K discrepancy).
• Real-world ties (Ncell, Daraz, NTC). Use the visuals above to map your answers—examiners reward structured, evidence-backed responses.