Vouching & Verification: Techniques, Evidence & Audit Trail

TAKEAWAYS:

• Vouching is the audit procedure that checks if recorded transactions exist and are correctly classified, using source documents as proof.
• Verification extends vouching to confirm balances (e.g., bank statements for cash, invoices for creditors) and detect fraud or errors.
• Liabilities verification (trade creditors, loans, contingent liabilities) requires third-party confirmation or analytical procedures.
• Rectifying entries are prepared when discrepancies are found (e.g., overcast purchase book → adjust purchases and profit).
• Audit trail ensures every transaction can be traced from source documents to final accounts via journal → ledger → trial balance.
• Real-world tie-ins: Khalti’s transaction logs (vouching for digital payments), Ncell’s loan agreements (verifying borrower liabilities), and Daraz’s order invoices (tracing sales returns).

1. Concept of Vouching: The Audit Backbone

Vouching is the examination of source documents to ensure:

• Transactions recorded in the books actually occurred.
• Amounts are correctly posted to the right accounts.
• No fraud or errors exist (e.g., fictitious suppliers, duplicate payments).

Why is vouching called the "backbone" of auditing?

graph LR
    A["Vouching"] --> B["Source Documents"]
    A --> C["Journal Entries"]
    A --> D["Ledger Postings"]
    A --> E["Financial Statements"]
    B -->|"Evidence"| C
    C -->|"Accuracy"| D
    D -->|"Reliability"| E
    E -->|"Trust"| F["Investor/Regulator Confidence"]

Key Idea: Without vouching, auditors cannot prove the truthfulness of financial statements.

2. Importance and Objectives of Vouching

Why Vouch?

3. Vouching Procedures: Step-by-Step

Auditors follow these 6 steps to vouche a transaction:

1. Select a sample of transactions (e.g., 20% of purchase invoices).
2. Obtain source documents (invoice, receipt, contract, email approval).
3. Trace to journal entry:
   • Check if the document number matches the journal.
   • Verify dates, amounts, and accounts.
4. Trace to ledger:
   • Confirm the amount is correctly posted (debit/credit).
5. Reconcile differences:
   • If a discrepancy exists (e.g., invoice Rs. 10,000 but journal shows Rs. 8,000), investigate.
6. Prepare rectifying entry (if needed):
   • Example: Overcast purchase book by Rs. 20,000 → Adjust purchases and profit.

WORKED EXAMPLE: Overcast Purchase Book Scenario: A Kathmandu retail shop’s purchase book shows total purchases of Rs. 5,00,000, but the actual total of invoices is Rs. 4,80,000. The auditor finds the error.

Step 1: Identify the Error

• Overcasting means the total in the purchase book is higher than the actual invoices.
• This overstates purchases and understates profit (since purchases reduce profit).

Step 2: Prepare the Rectifying Entry

| Date       | Particulars                     | L.F. | Dr (Rs.) | Cr (Rs.) |
|------------|---------------------------------|------|----------|----------|
| 2023-12-31 | To Purchases A/c                |      | 20,000   |          |
|            | By Suspense A/c                 |      |          | 20,000   |
|            | (Being the overcasting of purchase book rectified) |      |          |          |
| 2023-12-31 | To Profit & Loss A/c            |      |          | 20,000   |
|            | By Suspense A/c                 |      | 20,000   |          |
|            | (Being the effect of overcasting on profit) |      |          |          |

Explanation:

1. First entry: Reduces purchases by Rs. 20,000 (corrects the overstatement).
2. Second entry: Increases profit by Rs. 20,000 (since purchases were overstated, profit was understated).

4. Verification of Liabilities: How to Confirm "What You Owe"

Liabilities are high-risk audit areas—understating them inflates profit. Auditors verify them using:

• Third-party confirmation (e.g., bank statements for loans).
• Analytical procedures (e.g., comparing creditor balances to past years).
• Physical inspection (e.g., checking outstanding cheques).
• Review of agreements (e.g., loan terms, lease contracts).

Verification Methods for Key Liabilities

(Shows a ledger with Dr/Cr entries and confirmation replies from suppliers like "Daraz Suppliers Ltd.")

5. Vouching vs. Verification: Key Differences

6. Special Cases: Contingent Liabilities and Unrecorded Liabilities

Contingent Liabilities

• Definition: Potential obligations arising from past events (e.g., pending lawsuits, guarantees).
• Audit Approach:
  1. Review management letters for disclosed contingencies.
  2. Check legal documents (e.g., court cases, warranty claims).
  3. Confirm with legal advisors if needed.
• Example: A Kathmandu restaurant has a Rs. 50,000 claim for food poisoning. The auditor must:
  • Verify if it’s recorded in the books.
  • If not, ensure it’s disclosed in the notes to financial statements.

Unrecorded Liabilities

• Risk: Companies may omit liabilities to boost profit.
• Detection Methods:
  • Analytical review: Compare creditor balances to past years.
  • Cut-off testing: Check transactions near year-end.
  • Physical inspection: Review unpaid invoices in the supplier’s files.
• Example: NTC finds Rs. 20,000 of unrecorded bills in a shop’s files. The auditor must:
  • Prepare an adjusting entry to record the liability.
  • Adjust profit (since expenses were understated).

7. The Audit Trail: From Source to Financial Statements

Every transaction follows this paper trail:

flowchart TD
    A["Source Document\n(Invoice, Receipt)"]
    --> B["Journal Entry\n(Recorded in Journal Book)"]
    --> C["Ledger Posting\n(Debit/Credit in Ledger)"]
    --> D["Trial Balance\n(Summary of Ledger)"]
    --> E["Financial Statements\n(Balance Sheet, P&L)"]
    A -->|"Vouching"| B
    B -->|"Verification"| C
    C -->|"Reconciliation"| D

Key Checkpoints for Auditors:

1. Source → Journal: Does the invoice match the journal entry?
2. Journal → Ledger: Is the amount correctly posted?
3. Ledger → Trial Balance: Do totals reconcile?
4. Trial Balance → Statements: Are adjustments properly reflected?

8. Common Errors and How to Detect Them

In the Real World

1. Khalti’s Transaction Logs

   • Idea Used: Vouching of digital payments.
   • How: When auditing a merchant’s Khalti transactions, auditors vouche each payment request against the merchant’s records to ensure:
     • No fake transactions (e.g., refunds to non-customers).
     • Amounts match bank reconciliations.
   • Example: A Kathmandu café claims Rs. 50,000 in Khalti sales. The auditor checks Khalti’s transaction logs and the café’s POS system to confirm authenticity.

2. Ncell’s Loan Agreements

   • Idea Used: Verification of loans (liabilities).
   • How: Auditors verify Ncell’s customer loans by:
     • Obtaining signed loan agreements.
     • Confirming interest rates match bank records.
     • Checking repayment schedules for accuracy.
   • Example: If Ncell reports Rs. 10,00,000 in outstanding loans, the auditor sends confirmation letters to borrowers to validate the balance.

3. Daraz’s Supplier Invoices

   • Idea Used: Vouching of purchases and trade creditors.
   • How: Auditors verify Daraz’s purchase transactions by:
     • Matching invoice numbers to journal entries.
     • Sending creditor confirmation letters to suppliers (e.g., "Do you confirm Rs. 2,00,000 owed to Daraz?").
   • Example: If Daraz’s purchase book shows Rs. 8,00,000 but invoices total Rs. 7,50,000, the auditor prepares a rectifying entry to adjust purchases and profit.

4. NEPSE Shareholder Audits

   • Idea Used: Verification of preference share capital and contingent liabilities.
   • How: Auditors verify:
     • Share certificates to confirm issued capital.
     • Dividend records to ensure preference shareholders are paid first.
     • Pending lawsuits (contingent liabilities) disclosed in financial statements.
   • Example: A NEPSE-listed company reports Rs. 50,00,000 in preference shares. The auditor checks share registers and dividend payment records to ensure accuracy.

5. Bank Reconciliation (Nabil Bank)

   • Idea Used: Verification of cash balances.
   • How: Auditors reconcile bank statements with the company’s cash book to detect:
     • Unrecorded deposits (e.g., loan proceeds).
     • Unauthorized withdrawals (fraud risk).
   • Example: If Nabil Bank shows Rs. 5,00,000 in the company’s account but the cash book shows Rs. 4,50,000, the auditor investigates the Rs. 50,000 difference (likely an unrecorded deposit).

Exam Tip

How to Score Full Marks in TU/PU Exams

1. For "Rectifying Entries" Questions (e.g., overcast purchase book):

   • Always show the impact on profit/loss (e.g., "overcasting reduces profit").
   • Use a table for clarity (like the Kathmandu shop example above).
   • Mention the suspense account if adjusting errors.

2. For Verification of Liabilities:

   • List methods (confirmation letters, analytical review, physical inspection).
   • Give a real-world example (e.g., "For trade creditors, send letters to Daraz suppliers").
   • Explain risks (e.g., "Understated liabilities inflate profit").

3. For "Vouching is the Backbone" Essays:

   • Structure: Concept (1 mark) → Importance (3 marks) → Objectives (6 marks).
   • Use bullet points for objectives (easier to read and score).
   • Link to audit trail (e.g., "Without vouching, auditors cannot trust the audit trail").

4. Numerical Problems:

   • Show workings (e.g., "Invoice total = Rs. X, Book total = Rs. Y, Difference = Rs. Z").
   • Label entries clearly (e.g., "Being rectification of overcasting").
   • Assume a business name (e.g., "Kathmandu Retail Shop") to make it relatable.

5. Common Pitfalls to Avoid:

   • ❌ Forgetting to adjust profit in rectifying entries.
   • ❌ Not reconciling totals (e.g., Dr = Cr in ledger postings).
   • ❌ Vague answers for verification methods (e.g., "check books" → specify "send confirmation letters").

Final Checklist Before Submission:

• All Dr/Cr columns balance in tables.
• Real-world examples tied to Nepali businesses (Khalti, Ncell, Daraz, etc.).
• Visuals (t-accounts, flowcharts, tables) included for key concepts.
• Exam tips directly linked to past question patterns.