Launch offer — 25% off with code LAUNCH-25 See plans →
Microlesson · 5-min read

Audit of Purchases – Occurrence Assertion and Control Testing

## Audit of Purchases: Occurrence & Control Testing

### The Purchase Cycle — Know the Flow First

```

Purchase Requisition

Purchase Order (to supplier)

Invoice Received from Supplier

Goods Received at Factory Gate → Gate Entry Register

Goods Receipt Note (GRN) Prepared

Invoice Payment Approval

Payment

```

Understanding this flow is the foundation of purchase audit.

---

### Step 1 – Identify Control Points (General)

  • Is there segregation of duties between ordering, receiving, and payment?
  • Are competitive quotes obtained before large orders?
  • Is there an authorised vendor list?

### Step 2 – Test of Controls

  • Test whether identified controls operate effectively.
  • E.g. verify purchase orders are always approved before goods are ordered.

### Step 3 – Select Random Sample & Examine Documents

  • Select a random sample of transactions.
  • Examine: Purchase Order, GRN, Purchase Invoice, Gate Entry Register.

### Step 4 – Substantive Procedures (Always Mandatory)

Substantive procedures are compulsory regardless of control testing results.

---

### Occurrence Assertion: No Fake Purchases

Risk: The entity records purchases that never happened (to inflate expenses or siphon funds).

CheckWhy It Matters
Examine vendor selection processEnsures purchases are from genuine, approved vendors
Verify quality inspection was doneConfirms goods were actually inspected on receipt
Verify goods received at factory gate / gate registerPhysical evidence of receipt
GRN prepared and signed by authorised personAuthorization control
Purchase invoice approved by authorised personPayment authorization control
Stock records updated after receiptConfirms goods entered inventory

---

### Special Considerations in Purchase Audit

1. Original Invoice Only — Insist on original invoices; photocopies risk duplicate claims.

2. Risk & Reward Transfer — Book the purchase only when ownership risks and rewards have passed to the entity.

3. Related Party Purchases — Verify the transaction is at arm's length and approved by the Board of Directors.

4. Input Tax Credit (ITC) — Reconcile ITC as per books with the GST portal.

Worked example

### Example 1

Fictitious purchase test: The auditor selects a purchase transaction of ₹8 lakhs. The Purchase Order exists and is signed, but there is no GRN and no gate entry record. This is a high-risk transaction — possibly fictitious. The auditor expands the sample and reports the exception.

### Example 2

Related party purchase: A purchase from a director's firm is identified. The auditor checks: (a) Was the price at market rate? (b) Were the board minutes produced approving the transaction? Both conditions are met — the auditor is satisfied, but notes the transaction in the key matters section.

### Example 3

ITC reconciliation: ITC claimed in books for the year = ₹12 lakhs. ITC reflected on the GST portal (GSTR-2A/2B) = ₹10 lakhs. The ₹2 lakh difference means the entity claimed credit for invoices not uploaded by vendors — a compliance risk and potential liability.

⚠️ Common exam mistakes

  • Relying solely on purchase invoices without checking GRNs and gate entry records — invoices alone do not prove goods were received.
  • Not checking related party transactions for arm's length pricing — a frequently tested exam point.
  • Omitting ITC reconciliation with the GST portal as a special consideration.
  • Treating control testing as a substitute for substantive procedures — both are required.
Reference:
Now that you've read this — what's next?
Move from understanding → mastery in 3 clicks. Each option below picks up from this lesson's topic.
Start 15-min diagnostic